From: steven.j.nelson@xxxxxx
Date: Tue Aug 13 2002 - 05:11:21 GMT-3
Raj
It's quite simple.
The reachability cache tells you what remote devices are accessible by the
DLSw peer whether they are local to the box, i.e attached to an interface
participating in DLSw (Token ring with SRB, Ethernet TB etc etc) or remote,
i.e accessible by via another configured peer whether the peer be POD,
configured or Promiscuous. You will not see your TR switch as it is not an
end station and as such is not participating in the DLSw process.
You need end stations to create either SNA traffic or Netbios traffic to
generate entries in the reachability cache or DLSw circuits to test your
configs. The easiest way to do this is to connect 2 Windoze machines to
either DLSw peer and install Netbeui then browse the network for the remote
computer name. This will start a Netbios spanning tree explorer frame and
the peers should have the netbios names in their cache, then a circuit
(CANUREACH, ICANREACH, XID etc etc) can be established.
If you have another 2 spare routers try looking in the archives for the DPSU
commands, I think Yakout Esmat posted some good stuff a while back, maybe
you can find that.
HTH
Steve
-----Original Message-----
From: Raj [mailto:raj.bahad@totalise.co.uk]
Sent: 13 August 2002 08:45
To: Jason Sinclair; Glenn Johnson; ccielab
Subject: RE: DLSW Reachability Cache problems
Jason,
Thanks for your input. However, I am confused when you state "In your case
you do not have a
remote address as the peer does not count". A remote address? would that
mean I have to setup a static RIF pointing to it?
Thanks,
Raj.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Jason Sinclair
Sent: 13 August 2002 00:51
To: 'Raj'; Glenn Johnson; ccielab@groupstudy.com
Subject: RE: DLSW Reachability Cache problems
Raj,
A couple of points - firstly the reachability cache is used to determine
which peers can reach a remote address. In your case you do not have a
remote address as the peer does not count. Secondly, if you want to simulate
traffic you can use the Cisco DSPU feature. I will need to look into the
exact reason why you get reachability info for ether, however this appears
to me normal behaviour. Try using DSPU and if you need some help please let
me know.
Regards,
Jason Sinclair CCIE #9100
Manager, Network Control Centre
POWERTEL
55 Clarence Street,
SYDNEY NSW 2000
AUSTRALIA
office: + 61 2 8264 3820
mobile: + 61 416 105 858
email: sinclairj@powertel.com.au
-----Original Message-----
From: Raj [mailto:raj.bahad@totalise.co.uk]
Sent: Tuesday, 13 August 2002 04:56
To: Glenn Johnson; ccielab@groupstudy.com
Subject: RE: DLSW Reachability Cache problems
Glenn,
Do you think it may be an issue with the fact that both token ring
interfaces are not in the same trcrf ? Also I have configured both trcrf's
to belong to different trbrf's.
Looking at some of the archives, it states that SRB needs RIF's when
attempting to SRB packets from Tokenring to interfaces which have been
assigned different ring numbers/vlans but are attached to the same bridge.
Whereas, if both tokenring interfaces were on the same vlan and sharing the
same bridge, RIF's would not be required because the local explorer sent
would be resolved.
Raj.
-----Original Message-----
From: Glenn Johnson [mailto:glennjohnson@attbi.com]
Sent: 12 August 2002 19:44
To: 'Raj'
Subject: RE: DLSW Reachability Cache problems
Perhaps this will be of some use --
http://www.cisco.com/warp/public/697/ibm3.htm
-----Original Message-----
From: Raj [mailto:raj.bahad@totalise.co.uk]
Sent: Monday, August 12, 2002 2:40 PM
To: Glenn Johnson; ccielab@groupstudy.com
Subject: RE: DLSW Reachability Cache problems
Yep,
They can see each other without any problems. I think it may be an issue
of traffic being generated using SRB inh order for the RIF to be built.
Without the RIF, Tokenring cannot reach its destination.
However, this still does not answer my question about why the mac
address associated with my local token ring interface refuses to show in
the dlsw local reachability cache even though it has been attached to
the virtual ring?
Ethernet always shows up in the local cache regardless of whether wan
traffic traversing is going across the dlsw connection. Also, if i
decide to include ethernet interfaces as part of the DLSW configuration
(using the dlsw bridge group X statement in addition to the bridge group
interface command), DLSW sees both the local and remote mac addresses.
Is is just that without any traffic traversing between the two tokenring
peers, the interfaces mac-address will not show up?
-----Original Message-----
From: Glenn Johnson [mailto:glennjohnson@attbi.com]
Sent: 12 August 2002 19:30
To: 'Raj'
Subject: RE: DLSW Reachability Cache problems
Is sh dlsw capabilities working? Can the routers see each other?
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Raj
Sent: Monday, August 12, 2002 2:15 PM
To: ccielab@groupstudy.com
Subject: RE: DLSW Reachability Cache problems
Guys,
Please could you enlighten me into what I may be doing wrong?
-----Original Message-----
From: Glenn Johnson [mailto:glennjohnson@attbi.com]
Sent: 12 August 2002 19:10
To: 'Raj'
Subject: RE: DLSW Reachability Cache problems
I am not aware of one, but that does not mean it does not exist.
I purchased a few old token ring cards for a few dollars to hang off of
my 3920 because I was having similar problems.
-----Original Message-----
From: Raj [mailto:raj.bahad@totalise.co.uk]
Sent: Monday, August 12, 2002 2:05 PM
To: Glenn Johnson
Cc: ccielab@groupstudy.com
Subject: RE: DLSW Reachability Cache problems
The problem is that i do not have any devices attached to the end of
each token ring interface (even though they are connected to a cat3920
using seperate vlans).
Would you have a method of generating traffic to bring up this circuit?
-----Original Message-----
From: Glenn Johnson [mailto:glennjohnson@attbi.com]
Sent: 12 August 2002 18:58
To: 'Raj'
Subject: RE: DLSW Reachability Cache problems
Did you actually push any traffic through from ring to ring first?
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Raj
Sent: Monday, August 12, 2002 1:43 PM
To: ccielab@groupstudy.com
Subject: DLSW Reachability Cache problems
Hi Group,
I have a simple scenario where to routers (A & B) both have token ring
interfaces attached to them. I am using DLSW+ to connect both peers
using TCP. The problem is that even though the virtual rings have been
setup, The reachability cache does not contain the mac-address for
either the local or remote dlsw peer.
I've racked my brains and have been unable to resolve this. Using the
same config between Ethernet is not a problem.
Config:
Router A
Source bridge ring-group 1000
dlsw local peer peer-id 10.10.10.1
dlsw remote peer 0 tcp 10.10.10.2
interface tokenring0
ip address 10.10.20.1 255.255.255.0
ring-speed 16
source bridge 1 1 1000
source bridge spanning
multiring all
Router B:
Source bridge ring-group 1000
dlsw local peer peer-id 10.10.10.2
dlsw remote peer 0 tcp 10.10.10.1
interface tokenring0
ip address 10.10.30.1 255.255.255.0
ring-speed 16
source bridge 10 1 1000
source bridge spanning
multiring all
Can anyone help?
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:24 GMT-3