From: Bernard Dunn (dunn@xxxxxxxxx)
Date: Mon Jan 29 2001 - 16:30:52 GMT-3
Bob,
Agree with your response! My bad again.
On Mon, 29 Jan 2001, Bob Chahal wrote:
> I don't agree with your statement.
>
> SNA staions send out All-routes explorers
>
> Design Guide
> http://www.cisco.com/univercd/cc/td/doc/cisintwk/idg4/nd2004.htm#xtocid26353
> 4
>
> "SNA end stations generally produce an all-routes explorer packet. NetBIOS
> end stations produce a spanning explorer packet."
>
> Source-bridge spanning enables the propagation of single-route explorers.
>
>
> ----- Original Message -----
> From: Bernard Dunn <dunn@cisco.com>
> To: David Ankers <d.ankers@chello.nl>
> Cc: <ccielab@groupstudy.com>
> Sent: Monday, January 29, 2001 1:40 PM
> Subject: more Re: DLSw testing with DSPU
>
>
> > David,
> >
> > The command 'source-bridge spanning' is to enable automatic spanning-tree
> > (AST) on the interface, for the reason that when all-routes explorers are
> > out there, we need to 'optimise' path discovery, and work on stopping the
> > all-routes explorers going everywhere.
> >
> > SNA stations will send single-route explorers, whereas NetBIOS will send
> > all-routes explorers. If you have a network with purely just the former,
> > then the command 'source-bridge spanning' is not needed. Conversely, if
> > you have suspected a broadcast storm/explorer storm, but not sure why, and
> > the customer is just bridging SNA, not NetBIOS, then removing the command
> > off the interface is a good thing to eliminate problems.
> >
> >
> > Regards
> >
> > Bernard.
> >
> >
> > On Mon, 29 Jan 2001, David Ankers wrote:
> >
> > > Bernard,
> > >
> > > Thanks, I'll have a play with that tomorrow, I need to brush up on my
> IBM
> > > skills... One question in your configs below R1 & R2 don't have
> source-bridge
> > > spanning enabled. I was *told* that this command should always be there
> or
> > > else things don't work, is this info incorrect?
> > >
> > > Regards,
> > >
> > > David
> > >
> > >
> > > On Sunday 28 January 2001 11:26, you wrote:
> > > > All,
> > > >
> > > > Here's a simple way to test dlsw functionality. Have just made a
> quick'n
> > > > dirty setup, just on token ring routers. We use this type of thing to
> test
> > > > dlsw in our lab also. All up you'll need 4 routers.
> > > >
> > > > You can play around with defining multiple PUs, different lsap/ssap,
> > > > etcc.. The end result is to be able to bring up multiple circuits,
> check
> > > > reachability cache, test your filtering..
> > > >
> > > > Topology:
> > > >
> > > > dspu host -- ( ) -- r1 ---z___ r2 -- ( ) -- dspu pu
> > > >
> > > >
> > > > Key points
> > > > ==========
> > > >
> > > > dspu host - router pretends to be FEP/host side
> > > > dspu pu - router pretends to be client/end station/PU2.x
> > > > r1 & r2 - routers configured for dlsw
> > > >
> > > > What happens is that dspu host is configured to accept traffic from a
> > > > particular client/PU. The dspu pu downstream router is defined, uses
> > > > and sends out an xid, so will try and start a dlsw circuit.
> > > >
> > > > In real environments, a real SNA host sits behind the dspu host.
> > > >
> > > > Configurations
> > > > ==============
> > > > (dspu host)
> > > > dspu host is defined to recognise the dspu pu:
> > > >
> > > > <snip>
> > > > dspu pu TOK1 rmac 4000.1010.0001 rsap 4 lsap 4
> > > >
> > > > interface TokenRing0
> > > > mac-address 4000.3745.0001
> > > > no ip directed-broadcast
> > > > ring-speed 16
> > > > dspu enable-pu lsap 4
> > > > dspu start TOK1
> > > > </snip>
> > > >
> > > > Verify the results:
> > > >
> > > > ad-c2513-2-2#sh dspu pu TOK1
> > > > dspu pu TOK1 TokenRing0 PU STATUS Active
> > > > RMAC 4000.1010.0001 RSAP 4 LSAP 4
> > > > XID 01010101 RETRIES 4 RETRY_TIMEOUT 30
> > > > WINDOW 7 MAXIFRAME 1472
> > > > ACT BUFFERS 0 SAP ACT BUFFERS 0
> > > > FRAMES RECEIVED 1 FRAMES SENT 1
> > > > LUs USED BY DSPU 0 LUs ACTIVE 0
> > > > LUs USED BY API 0 LUs ACTIVE 0
> > > > LUs ACTIVATED BY HOST BUT NOT USED 0
> > > >
> > > >
> > > > -------------------------------
> > > > (r1)
> > > >
> > > > source-bridge ring-group 505
> > > > dlsw local-peer peer-id 150.100.20.1
> > > > dlsw remote-peer 0 tcp 64.10.1.1
> > > > !
> > > > interface Loopback0
> > > > ip address 150.100.20.1 255.255.255.0
> > > > !
> > > > interface TokenRing0
> > > > ip address 150.100.17.1 255.255.255.0
> > > > ring-speed 16
> > > > source-bridge 301 4 505
> > > >
> > > > Verify the results:
> > > >
> > > > ad-c2504-2-4#sh dlsw peer
> > > > Peers: state pkts_rx pkts_tx type drops ckts
> TCP
> > > > uptime
> > > > TCP 64.10.1.1 CONNECT 105 102 conf 0 1
> 0
> > > > 00:46:43
> > > > Total number of connected peers: 1
> > > > Total number of connections: 1
> > > >
> > > > ad-c2504-2-4#sh dlsw cir detail
> > > > Index local addr(lsap) remote addr(dsap) state
> > > > uptime
> > > > 1040187392 4000.3745.0001(04) 4000.1010.0001(04) CONNECTED
> > > > 00:30:29
> > > > PCEP: 1470A0 UCEP: 5952D0
> > > > Port:To0 peer 64.10.1.1(2065)
> > > > Flow-Control-Tx CW:20, Permitted:39; Rx CW:20,
> > > > Granted:19; Op: Repeat
> > > > Congestion: Low(02), Flow Op: Half: 0/0 Reset 0/0
> > > > RIF = 0630.1F94.12D0
> > > > Bytes: 18/229 Info-frames: 1/1
> > > > XID-frames: 2/4 UInfo-frames: 0/0
> > > > Total number of circuits connected: 1
> > > >
> > > > ad-c2504-2-4#sh dlsw reach
> > > > DLSw Local MAC address reachability cache list
> > > > Mac Addr status Loc. port rif
> > > > 4000.3745.0001 FOUND LOCAL TokenRing0 0630.1F94.12D0
> > > >
> > > > DLSw Remote MAC address reachability cache list
> > > > Mac Addr status Loc. peer
> > > > 4000.1010.0001 FOUND REMOTE 64.10.1.1(2065)
> > > >
> > > > DLSw Local NetBIOS Name reachability cache list
> > > > NetBIOS Name status Loc. port rif
> > > >
> > > > DLSw Remote NetBIOS Name reachability cache list
> > > > NetBIOS Name status Loc. peer
> > > >
> > > > -------------------------------
> > > > (r2)
> > > >
> > > > !
> > > > source-bridge ring-group 505
> > > > dlsw local-peer peer-id 64.10.1.1
> > > > dlsw remote-peer 0 tcp 150.100.20.1
> > > > !
> > > > !
> > > > interface TokenRing0/0
> > > > mtu 4464
> > > > ip address 64.10.1.1 255.255.0.0
> > > > ipx network 123
> > > > ring-speed 16
> > > > source-bridge 80 2 505
> > > >
> > > > Verify the results:
> > > >
> > > > ad-c3620-2-9#sh dlsw peer
> > > > Peers: state pkts_rx pkts_tx type drops ckts
> TCP
> > > > uptime
> > > > TCP 150.100.20.1 CONNECT 98 101 conf 0 1
> 0
> > > > 00:44:54
> > > > Total number of connected peers: 1
> > > > Total number of connections: 1
> > > >
> > > > ad-c3620-2-9#sh dlsw cir det
> > > > Index local addr(lsap) remote addr(dsap) state
> > > > uptime
> > > > 1056964608 4000.1010.0001(04) 4000.3745.0001(04) CONNECTED
> > > > 00:29:31
> > > > PCEP: 62CB6F24 UCEP: 62CF5B4C
> > > > Port:To0/0 peer 150.100.20.1(2065)
> > > > Flow-Control-Tx CW:20, Permitted:19; Rx CW:20,
> > > > Granted:39; Op: Repeat
> > > > Congestion: Low(02), Flow Op: Half: 0/0 Reset 0/0
> > > > RIF = 06B0.0502.1F90
> > > > Bytes: 229/18 Info-frames: 1/1
> > > > XID-frames: 4/2 UInfo-frames: 0/0
> > > > Total number of circuits connected: 1
> > > >
> > > > ad-c3620-2-9#sh dlsw reach
> > > > DLSw Local MAC address reachability cache list
> > > > Mac Addr status Loc. port rif
> > > > 4000.1010.0001 FOUND LOCAL TokenRing0/0 06B0.0502.1F90
> > > >
> > > > DLSw Remote MAC address reachability cache list
> > > > Mac Addr status Loc. peer
> > > > 4000.3745.0001 FOUND REMOTE 150.100.20.1(2065) max-lf(4472)
> > > >
> > > > DLSw Local NetBIOS Name reachability cache list
> > > > NetBIOS Name status Loc. port rif
> > > >
> > > > DLSw Remote NetBIOS Name reachability cache list
> > > > NetBIOS Name status Loc. peer
> > > >
> > > >
> > > > -------------------------------
> > > > (dspu pu)
> > > >
> > > > Here you define who you'll try and contact by MAC address
> > > >
> > > > dspu host TOK2 xid-snd 01010101 rmac 4000.3745.0001 rsap 4 lsap 4
> > > > !
> > > > interface TokenRing0
> > > > mac-address 4000.1010.0001
> > > > ring-speed 16
> > > > dspu enable-host lsap 4
> > > > dspu start TOK2
> > > > !
> > > >
> > > > Verify the results:
> > > >
> > > > ad-c2504-2-3#sh dspu pu TOK2
> > > > dspu host TOK2 TokenRing0 PU STATUS Active
> > > > RMAC 4000.3745.0001 RSAP 4 LSAP 4
> > > > XID 01010101 RETRIES 255 RETRY_TIMEOUT 30
> > > > WINDOW 7 MAXIFRAME 1472
> > > > ACT BUFFERS 0 SAP ACT BUFFERS 0
> > > > FRAMES RECEIVED 1 FRAMES SENT 1
> > > > LUs USED BY DSPU 0 LUs ACTIVE 0
> > > > LUs USED BY API 0 LUs ACTIVE 0
> > > > LUs ACTIVATED BY HOST BUT NOT USED 0
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:47 GMT-3