A question on RSRB using TCP encapsulation

[ten]

We have chosen to encapsulate our Remote Source-Route Bridging traffic in TCP. the routers are peered by using the "source-bridge remote-peer 1010 tcp " statments.

This method is working well, but I have noticed that when the central site router is rebooted and I issue the "show source-bridge" command and look at the state of the peers, some of the peers can take 4 or 5 minutes before they enter the "open" state.

My question is: " What initiates the TCP session for RSRB between the routers?

Are they supposed to come up right away or do they wait for traffic to set up the sessions?

Also is there a way to "jump start" a session?

Thanks

[vmiller]

I would strongly suggest getting over to dlsw. This issue will go away with

dlsw. Actually 4 or 5 minues isn't bad, I have seen 20 minutes on older systems. Peer connectivity is a function of:

1. how many remote peers

2. WAN link speed

3. processing horsepower in the headend router.