We currently have DLSW as we are still running SNA in a couple of our remote sites.
Yesterday we connected a new Cisco 2950 to a remote site and it brought down the network at 2 other sites (the 2 other sites had cisco switches).
Looking at the problem is looks like spanning tree but I don't know where to start. I can't afford to plug the switch in for the networks to go down again. The networks in all 3 remote sites use VLAN1 and portfast is enabled on the port connected to the router at all 3 sites
Portfast should only be configured on single host ports and NOT on ports connected to any other network device. Portfast eliminates the first stages of the Spanning Tree algorithm and places the port in forwarding state with no regard for the topology of the network.
Portfast enabled ports will not send Topology change notifications (TCN) when the state of the port changes, (which is useful for end user devices as you dont really need notifications every time someone reboots a PC) - but not much use when the topology of your bridged network changes.
I advise you remove portfast from the switch ports that connect to your routers (and to any other switches) at all sites.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...