From: Umair Hoodbhoy (umair@cisco.com)
Date: Sun Oct 13 2002 - 01:27:29 GMT-3
Thanks Nick but I still don't quite follow this. At http://www.cisco.com/warp/public/473/111_12.html, several SNA SAPs are listed. 04 is assigned to IBM SNA Path Control (Individual). But there are other SNA SAPs in that list. And they don't seem to be multiples of 0x04.
-- Umair
-----Original Message-----
From: Nick Shah [mailto:nshah@connect.com.au]
Sent: Saturday, October 12, 2002 20:13
To: Umair Hoodbhoy; ccielab@groupstudy.com
Subject: Re: DLSw SNA filters
Umair
The remote router can also advertise unreachability of SAPS, this way the
local router will not send any explorers for those SAPS.
Like RTA advertises dlsw icannotreach saps f0, to RTB, advertising that it
doesnt want netbios traffic. Similarly for SNA the saps would be 04
rgds
Nick
----- Original Message -----
From: Umair Hoodbhoy <umair@cisco.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, October 13, 2002 12:45 PM
Subject: DLSw SNA filters
> The lab I'm doing says there are 2 ways to filter SNA traffic through
DLSw. One way I know is through lsap-output-list. Like:
>
> !
> dlsw remote-peer 0 tcp <IP> lsap-output-list 200
> !
> access-list 200 permit 0x0000 0x0D0D
> access-list 200 deny 0x0000 0xFFFF
> !
>
> What's another way? As I understand it, SNA SAPs range from 0x00 to 0xFF
in multiples of 0x04. If I'm correct and that's the case, then there would
be too many 'dlsw icanreachsaps' statements. There must be an easier way.
>
> -- Umair
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:45 GMT-3