From: Sam Munzani (sam@xxxxxxxxxxx)
Date: Fri Nov 03 2000 - 11:10:41 GMT-3
I don't know if this is true but have read somewhere a note from Jeff
telling they stick with DLSW for SNA stuff. I haven't seen anybody talking
about RSRB on group either. It may not be there at all.
Sam
> source-bridge remote-peer should be include itself.
>
> ----- Original Message -----
> From: Jack Heney <jheneyccie@hotmail.com>
> To: <ccielab@groupstudy.com>
> Sent: Friday, November 03, 2000 6:23 AM
> Subject: Re: RSRB
>
>
> > Okay...Now I have 2 routers running the same version (12.07t) and it
still
> > doesn't work...Here's the config:
> >
> > RtrA-(e0/0)----(f0/0)-RtrB-(s0/0)----(s0/0)-RtrC-(f0/0)----(e0/0)-RtrD
> >
> > RtrA:
> > source-bridge ring-group 10
> > source-bridge remote-peer 10 tcp 10.2.2.254
> > interface ethernet 0/0
> > ip address 10.1.2.254 255.255.255.0
> > interface tokenring 0/0
> > source-bridge 1 1 10
> > source-bridge spanning
> > router rip
> > version 2
> > network 10.0.0.0
> >
> > RtrB:
> > interface fastethernet 0/0
> > ip address 10.1.2.253 255.255.255.0
> > interface serial 0/0
> > ip address 10.10.1.1 255.255.255.0
> > encapsulation frame-relay
> > router rip
> > version 2
> > network 10.0.0.0
> >
> > RtrC:
> > interface fastethernet 0/0
> > ip address 10.2.2.253 255.255.255.0
> > interface serial 0/0
> > ip address 10.10.1.2 255.255.255.0
> > encapsulation frame-relay
> > router rip
> > version 2
> > network 10.0.0.0
> >
> > RtrD:
> > source-bridge ring-group 10
> > source-bridge remote-peer 10 tcp 10.1.2.254
> > interface ethernet 0/0
> > ip address 10.2.2.254 255.255.255.0
> > interface tokenring 0/0
> > source-bridge 2 1 10
> > source-bridge spanning
> > router rip
> > version 2
> > network 10.0.0.0
> >
> > I don't think it gets much simpler, but it doesn't work...Here's the
debug
> > output for RtrD:
> >
> > 01:08:50: RSRB: peer 10/10.1.2.254/1996 dead -> closed (809DE22C)
> > 01:08:50: RSRB: remote explorer to 10/10.3.2.254/1996 srn 2
> > [C830.0021.00A0.0000]
> > 01:08:50: RSRB: peer 10/10.1.2.254/1996 closed -> opening (809D9A84)
> > 01:08:50: RSRB: CONN: no peername set, aborting (tcpd)
> > 01:08:50: RSRB: peer 10/10.1.2.254/1996 opening -> openwait (809D57A4)
> > 01:08:50: RSRB: CONN: no peername set, aborting (tcpd)
> > 01:08:50: RSRB: peer 10/10.1.2.254/1996 openwait -> dead (809D5854)
> > 01:08:50: RSRB: CONN: connector terminating
> > 01:08:50: SRB0: explorer enqueued (srn 2 bn 1 trn 10)
> > 01:08:50: RSRB TCPD: wrong state to keep, 10/10.1.2.254/1996 dead
EXPLORER
> > 01:08:50: RSRB: send explorer to peer 10/10.1.2.254/1996 failed
> >
> >
> > Anyone have any ideas?
> > Thanks,
> > Jack
> >
> > >From: "Jack Heney" <jheneyccie@hotmail.com>
> > >Reply-To: "Jack Heney" <jheneyccie@hotmail.com>
> > >To: ccielab@groupstudy.com
> > >Subject: RSRB
> > >Date: Thu, 02 Nov 2000 21:39:12 GMT
> > >
> > >Are there any issues with configuring RSRB between routers running
> > >different
> > >IOS versions? I have a very basic RSRB configuration between 2 routers
> > >across an ethernet link. One is using 12.07t, the other 11.3.
> > >When I debug source bridge, I keep getting a message that says "RSRB
TCPD:
> > >wrong state to keep". Any body ever seen this before?
> > >I'm positive my configuration is right...I set up the mosty basic of
> > >configs
> > >with a source-bridge ring-group, a source-bridge remote-peer, and a
> > >source-bridge command on the token ring interface. When I show
> > >source-bridge, the remote peer shows up as dead. I can ping on router
to
> > >the other, so I know it isn't the underlying IP network. Any help
would be
> > >greatly appreciated.
> > >Thanks,
> > >Jack
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:41 GMT-3