As we know, EOBC is a bus-based Ethernet. In a shared-medium bus like EOBC, we expect to see some type of errors, such as CRC errors, sometimes. As long as the number of errors does not increase very quickly in a short period of time, we do not need to be concerned. There is no impact on the operation of the router when we observe a CRC errors because the protocols on the EOBC have a retry mechanism.
When several keep-alives are missed, it means communication is lost between the Application-Specific Integrated Circuits (ASICs) and the supervisor. In order to prevent this, the code contains a workaround that resets the EOBC when it sees that the messages do not increment constantly.
EOBC is a half-duplex out of band channel which is used for backplane communication between SP/RP and line cards. These errors are mostly benign, as deferred implies packet is ready but the media to send it on is busy. The reason for this is that the EOBC is a half-duplex interface, and the fact that there are deferred simply means that we are receiving when we attempt to transmit. With a half-duplex interface we cannot do that, so we defer the packet, and wait. Likewise, on a half-duplex interface collisions happen, and are part of normal operation.
[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...