Problems of implementation of the basic Spanning Tree (802.1d) Catalyst 2960 SI
I have a problem of implementation of Cisco Catalyst 2960 switches in relation to the Spanning Tree (802.1d) in the current topology of the network that currently contains other switches from different manufacturers as HP3COM
When Using Spanning Tree implementations with Cisco switches and HP3COM in the same topology switches feature Cisco malfunction accusing looping in the network where there is no such problem
I'm studying hard in order to implement the Spanning Tree network
The network topology is somewhat large and complex
Currently the network is undergoing a change in every line of active elements for which the topology has only elements of Cisco
In this moment it is still necessary the coexistence of two manufacturers in the topology (HP3COM and Cisco)
Someone could at least spend some idea of compatibility between the operation of Spanning Tree (802.1d) of Cisco switches and other manufacturers?
[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...