The bridges look for the lowest Root Bridge Identifier (BID), an eight-byte field composed of a Bridge Priority and a Media Access Control (MAC) address. This allows the entire bridged network to elect a single Root Bridge.
Is the case same for port ID i.e. MAC+Priority? If a tie occurs between 2 ports on a segment in a STP process how is the designated port selected between these two ports is it by lowest MAC+Priority of the port?
Port ID (a unique index value for every port in a bridge or switch) is evaluated if all three of the previous criteria tie. I can not find what exactly makes up the index value, but I would assume the MAC has something to do with it.
The port ID is a 16 bit integer made using the same scheme as the bridge ID, but using a port number instead of a mac address. The port number is (currently) a 12 bit integer, identifying with no ambiguity the port on a given bridge. The 4 bits with the highest weight in the port ID are the port priority, settable by the user.
There is no need for a mac address in the port ID because the mac address of the bridge on which the port is located was already included in the sender bridge ID (one of the 3 fields that are taken into account before using the port ID as a tie breaker).
Sorry, I don't understand the question. What do you mean by converted?
0x8002 is a 16 bit integer. The 4 highest bits are the priority and the 12 lowest ones are the port number
So priority 0x8, port number is 0x002
The trick is that the priority is generally expressed as a byte (it used to be 8 bits priority and 8 bits of port number before 802.1t changed all this to 4 and 12 bits respectively). So in Cisco's CLI, the priority that you see on this port will be 0x80 = 128 decimal. That's the default priority.
[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...