06-08-2004 12:07 AM
Hi all,
we configure the follow
and our wish is to connect a client per netbios with an host (SNA)
Router1 (RSM, 12.0.17))
dlsw local-peer peer-id 192.168.10.200
dlsw remote-peer 0 tcp 192.168.88.1
dlsw bridge-group 1
interface Vlan14
description VLAN Horst
ip address 192.168.10.200 255.255.255.0
no ip redirects
no ip directed-broadcast
no ip route-cache cef
standby priority 120
standby preempt
standby ip 192.168.10.1
bridge-group 1
!
bridge 1 protocol ieee
!
the host is in VLAN 14 per Ethernet connected
Router2 (C2600-DOS-M), Version 12.0(2a)T1
dlsw local-peer peer-id 192.168.88.1
dlsw remote-peer 0 tcp 192.168.10.200
dlsw bridge-group 1
!
interface Ethernet0/0
ip address 192.168.88.1 255.255.255.0 secondary
ip address 194.49.122.129 255.255.255.0
no ip directed-broadcast
bridge-group 1
!
bridge 1 protocol ieee
The peer comes up but I can't see the mac-address of the host with the "show dlsw reach" command on the local-site.
Haye anyone an idea why?
Best regards
Rainer
06-08-2004 01:39 AM
Can you post the ouput from "sh dlsw circuit" and "sh dlsw peer" ?
HTH
06-08-2004 04:13 AM
Hi,
when you say:
and our wish is to connect a client per netbios with an host (SNA)
what does that mean?
Netbios can not talk to SNA. You need some emulator running on the pc to be able to connect to a sna host.
Please provide a one line topology with the mac addresses you are using, i.e.
pc--eth--router1--dlsw--router2----eth--host
also provide:
show dlsw peer
show dlsw cir
show dlsw reach
show span
show bridge
show llc
Preferable from both routers.
as long as you can not see the local mac address in the show reach of the local router nothing will work. If you come in via ethernet and you are using dlsw with a bridge group than you should also see the local mac address in a show bridge.
Please keep in mind that dlsw sees all mac addresses in tokenring format.
So a show bridge and a show dlsw reach or a show dlsw circuit will show the same mac address in two different formats.
If there is no circuit you can also do a
debug dlsw reach verbose
to figure out if the client tries to communicate with the host.
debug dlsw core
gives more information about the circuit establisment but it can be quite a lot of output.
thanks...
Matthias
06-08-2004 05:03 AM
06-08-2004 05:58 AM
In the dlsw debug, we see this:
smac 0003.778b.1c04, dmac c000.0000.0080, ssap F0, dsap F0
This means that mac address is sending to the token-ring functional MAC address that is reserved for token-ring. On ethernet, this should be a broadcast. The SAP are correct-F0 is netbios. We do not see the MAC address that you reference which is the 0050.048f.50e4. So, even though c000.0000.0080 will go across the DLSW, the other NetBios stations will not answer this. And that is why DLSW is not able to start any circuits.
I suggest getting a sniffer and verifying the PC in question is really the MAC address you think it is and to what DMAC address it is sending to.
06-08-2004 06:40 AM
Hi,
netbios has nothing to do with sna!!
The source mac of 0003.778b.1c04 is not the one we are looking for, which is 0050.048f.50e4 (ethernet)
000a.20f1.0a27 (dlsw/tokenring).
c000.0000.0080 bitswaps to 0300.0000.0001 which is a ethernet multicast used by netbios.
SNA is expecting something like this:
client host
test p -->
<--- test final
null xid --->
<---- null xid response
xid --->
xid exchange depends a bit on the pu type
<---- sabme
ua ----->
at that point the dlsw circuit will be in state connected.
Nothing of the above is visible in the debug, nor do we even get to the state of starting a circuit.
thanks...
Matthias
06-08-2004 05:59 AM
Hi,
based on your log file there is no evidence that your end system tries to start to communicate with the host.
The mac address of your pc is neither in the dlsw reachability cache nor in the bridge table.
Which means that the router has not seen any frame from that particular mac address.
Make sure that the pc is on the correct vlan and the router can receive frames from the pc.
If you need additional help in troubleshooting the problem i would advice to open a tac case.
thanks...
Matthias
06-09-2004 10:24 AM
Since the mac is not in the bridge table, I think the PC is either in a wrong Vlan or the physical connection is bad, ie, bad cable or bad NIC. If the PC is also running IP, ping from the same subnet to check the connectivity. Before you open a TAC, it's better to have a sniffer trace ready.
Thanks
Jing
05-22-2016 09:00 AM
Hi RL,
Have u found the solution? I have the same problem. No issue with vlan and other after thousands of checking.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide