From: Bernard Dunn (dunn@xxxxxxxxx)
Date: Sat Feb 03 2001 - 04:08:43 GMT-3
Maybe your igmp looks like an explorer, and brought up the circuit.
Think the mac layer looks about the same.
Regards
Bernard.
On Sat, 3 Feb 2001, David Ankers wrote:
> Errmm.. I had a bit of a think about this and as it's not the PCs, something
> did jump out at me.
>
> > interface FastEthernet0/0
> > ip address 144.16.11.1 255.255.255.0
> > no ip directed-broadcast
> > ip pim sparse-mode
> > ip igmp join-group 224.10.10.10
> > duplex auto
> > speed auto
> > bridge-group 1
>
> What's the reason for not using IRB with this config, personally I would, if
> this was given to me on the lab, IRB would be in there. Now the chances of me
> passing this lab are very remote so take that with a grain of salt.
>
> !
> bridge irb
> !
> bridge 1 protocol ieee
> bridge 1 route ip
> no bridge 1 bridge ip
> !
>
> Something in the back of my mind is telling me that this is only needed if
> you want to bridge routable protocols but something else is telling me to
> bridge and route on the same interface needs IRB. I wonder which bit is
> correct?
>
> David.
>
>
> On Saturday 03 February 2001 03:51, you wrote:
> > They are win95 machines and I turned off master browser. I am concerned
> > that it is a windows/netbios issue but even with pc unplugged the problem
> > remains. Thanks for the input,
> > Kyle
> >
>
> >To me the config of the DLSw bits looks good (although its a weak subject),
> >what does a sniffer on the lan segment say. It could be that the NT stations
> >are actually sending some data (master browser stuff?). Its just an idea
> that
> >its worth checking that it's not NT.... Again it's a weak subject but seems
> >that nobody else replied a fresh idea might help?
> >
> >David.
> >
> >
> >On Friday 02 February 2001 23:37, you wrote:
> >> I could use another set of eyes on this.
> >>
> >> I have configure two dynamic dlsw peers. R1 is one peer and r8 is anothe
r
> >> peer. R3 is an intermediate router that connects to r1 via frame and r8
> >> via ISDN. I have OSPF as the routing protocol with ip ospf demand betwee
n
> >> R3 and R8. I am running netbios from Win95 machines on the ethernet
> >> segments on r1 and r8. The routers peer fine and by using "find computer
"
> >> on the win95 PCs I can get a DLSW circuit established.
> >>
> >> So it looks like this
> >> PC----ether---R8---isdn---R3----f/r------R1---ether--PC
> >>
> >>
> >> The problem is my isdn link stays up (it shouldn't) after the circuit goes
> >> down. OSPF hellos or LSAs are not the problem. It looks like a DLSW tcp
> >> (2065) session keepalive is keeping the session up but I've configure kee
p
> >> of 0 on both peers.
> >>
> >> Any thoughts?
> >> Kyle
> >>
> >> Config and Debugs follow.
> >>
> >> r8#sho dlsw cir (this is normal)
> >> Index local addr(lsap) remote addr(dsap) state
> >> uptime 1342177382 0003.f20e.0277(F0) 0003.f226.652c(F0) CONNECTED
> >> 00:00:19 Total number of circuits connected: 1
> >>
> >> r8#sho dlsw peer (this is normal)
> >> Peers: state pkts_rx pkts_tx type drops ckts TCP
> >> uptime
> >>
> >> TCP 144.16.1.1 CONNECT 90 72 dynam 0 1 0 00:02:4
7
> >> Total number of connected peers: 1
> >>
> >>
> >>
> >> *******************
> >> selected parts on r8s config
> >> r8
> >> dlsw local-peer peer-id 144.16.1.8
> >> dlsw remote-peer 0 tcp 144.16.1.1 keepalive 0 timeout 90 dynamic (this
> >> should stop keeps)
> >> dlsw bridge-group 1
> >> !
> >> !
> >> interface FastEthernet2/0
> >> ip address 144.16.8.8 255.255.255.0
> >> no ip directed-broadcast
> >> bridge-group 1
> >> !
> >> bridge 1 protocol ieee
> >>
> >> ************************
> >> Selected parts of r1s config
> >> !
> >> dlsw local-peer peer-id 144.16.1.1
> >> dlsw remote-peer 0 tcp 144.16.1.2 priority cost 5
> >> dlsw remote-peer 0 tcp 144.16.1.8 keepalive 0 timeout 90 dynamic no-llc 1
> >> dlsw bridge-group 1
> >> !
> >> interface FastEthernet0/0
> >> ip address 144.16.11.1 255.255.255.0
> >> no ip directed-broadcast
> >> ip pim sparse-mode
> >> ip igmp join-group 224.10.10.10
> >> duplex auto
> >> speed auto
> >> bridge-group 1
> >> !
> >> bridge 1 protocol ieee
> >>
> >> ***********************
> >>
> >> r8#sho tcp bri (this tcp session should drop but does not)
> >> TCB Local Address Foreign Address (state)
> >> 61101228 144.16.1.8.11128 144.16.1.1.2065 ESTAB
> >>
> >> r8# debug dialer pack This shows dlsw is keeping dialer up but why?
> >> 06:47:16: IP: s=144.16.1.8 (local), d=144.16.1.1 (Dialer0), len 40, sendin
g
> >> 06:47:16: TCP src=2065, dst=11324, seq=3966165290, ack=0, win=20004 RS
T
> >> 06:47:16: IP: s=144.16.1.1 (Dialer0), d=144.16.1.8, len 40, rcvd 4
> >> 06:47:16: TCP src=2065, dst=11128, seq=3847272988, ack=3966124550,
> >> win=20102 ACK
> >>
> >> r8#sho dlsw pee (after circuit drops connect stays up 120 seconds then
> >> drops then reestablsihes
> >> repeatedly???? This connection should stay down until needed.
> >> Peers: state pkts_rx pkts_tx type drops ckts TCP
> >> uptime
> >>
> >> TCP 144.16.1.1 CONNECT 17 14 dynam 0 0 0 00:00:5
7
> >> Total number of connected peers: 1
> >> Total number of connection
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:34 GMT-3