From: Gregg Malcolm (greggm@xxxxxxxxxxxxx)
Date: Sat Mar 02 2002 - 22:23:22 GMT-3
Yuen,
I'm no expert on this subject, but I'd try removing promiscuous and peer on
demand. Hard code your remote peer statements to make it easier to
troubleshoot. You can put the lsap-output-list on the remote peer
statement. If that prevents circuits from building, you can incrementally
add prom and peer on demand to see if one of these are causing the problem.
Seems to me that your access list is right and should prevent circuits from
activating.
I'm curious about what you'll find out, Gregg
----- Original Message -----
From: "yuen me" <yuen_me@hotmail.com>
To: <ccielab@groupstudy.com>
Sent: Saturday, March 02, 2002 4:31 PM
Subject: lsap-output-list does not function
> I deliberatly put a deny 0x0000 0xffff filter in the dlsw lsap-output-list
> but circuits still build. i have disable dlsw and enable it again, reboot
> the router. All don't help. Appreciate any help.
>
> R1-----------R2----------r7--------------r3
>
> On R2
>
> dlsw local-peer peer-id 200.2.0.2 group 123 promiscuous
> dlsw peer-on-demand-defaults lsap-output-list 200
> dlsw prom-peer-defaults lsap-output-list 200
>
> access-list 200 deny 0x0000 0xFFFF
>
> On R1
>
> dspu pu 3174 rmac 0040.0040.0040 rsap 4 lsap 4
> !
> dspu pu 3174R6 rmac 0068.0068.0068 rsap 8 lsap 4
> interface TokenRing0
> dspu enable-pu lsap 4
> dspu start 3174
>
> Stat on R2
>
> r2#sh dlsw circuits
> Index local addr(lsap) remote addr(dsap) state
uptime
> 4043309057 0000.302c.09ea(04) 0040.0040.0040(04) CONNECTED
> 00:12:17
> 771751938 0000.302c.09ea(04) 0068.0068.0068(08) CONNECTED
> 00:12:04
> Total number of circuits connected: 2
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:51 GMT-3