Displaying MRP information
You can display the following MRP information:
- Topology group configuration information
- Ring configuration information and statistics
Topology group configuration information
To display topology group information, enter the following command.
Syntax: show topology-group [group-id]
Refer toDisplaying topology group information for more information.
To display ring information, enter the following command.
device#show metro
Metro Ring 1
=============
Ring State Ring Master Topo Hello Prefwing
id role vlan group time(ms) time(ms)
2 enabled member 2 not conf 100 300
Ring interfaces Interface role Forwarding state Active interface Interface Type
ethernet 1/1/1 primary disabled none Regular
ethernet 1/1/2 secondary forwarding ethernet 2 Tunnel
RHPs sent RHPs rcvd TC RHPs rcvd State changes
3 0 0 4
Syntax: show metro [ ring-id ]
This display shows the following information.
Field |
Description |
---|---|
Ring id |
The ring ID |
State |
The state of MRP. The state can be one of the following:
|
Ring role |
Whether this node is the master for the ring. The role can be one of the following:
|
Master vlan |
The ID of the master VLAN in the topology group used by this ring. If a topology group is used by MRP, the master VLAN controls the MRP settings for all VLANs in the topology group. NOTE The topology group ID is 0 if the MRP VLAN is not the master VLAN in a topology group. Using a topology group for MRP configuration is optional.
|
Topo group |
The topology group ID. |
Hello time |
The interval, in milliseconds, at which the Forwarding port on the ring master node sends Ring Hello Packets (RHPs). |
Prefwing time |
The number of milliseconds an MRP interface that has entered the Preforwarding state will wait before changing to the Forwarding state. If a member port in the Preforwarding state does not receive an RHP within the Preforwarding time (Prefwing time), the port assumes that a topology change has occurred and changes to the Forwarding state. The secondary port on the Master node changes to Blocking if it receives an RHP, but changes to Forwarding if the port does not receive an RHP before the preforwarding time expires. NOTE A member node Preforwarding interface also changes from Preforwarding to Forwarding if it receives an RHP whose forwarding bit is on.
|
Ring interfaces |
The device two interfaces with the ring. NOTE If the interfaces are trunk groups, only the primary ports of the groups are listed.
|
Interface role |
The interface role can be one of the following:
|
Forwarding state |
Whether MRP Forwarding is enabled on the interface. The forwarding state can be one of the following:
|
Active interface |
The physical interfaces that are sending and receiving RHPs. NOTE If a port is disabled, its state is shown as "disabled".
NOTE If an interface is a trunk group, the member port which comes up first is listed.
|
Interface Type |
Shows if the interface is a regular port or a tunnel port. |
RHPs sent |
The number of RHPs sent on the interface. NOTE This field applies only to the master node. On non-master nodes, this field contains 0. This is because the RHPs are forwarded in hardware on the non-master nodes.
|
RHPs rcvd |
The number of RHPs received on the interface. NOTE On most
Ruckus devices, this field applies only to the master node. On non-master nodes, this field contains 0. This is because the RHPs are forwarded in hardware on the non-master nodes. However, on the
FastIron devices, the RHP received counter on non-master MRP nodes increment. This is because, on
FastIron devices, the CPU receives a copy of the RHPs forwarded in hardware.
|
TC RHPs rcvd |
The number of Topology Change RHPs received on the interface. A Topology Change RHP indicates that the ring topology has changed. |
State changes |
The number of MRP interface state changes that have occurred. The state can be one of the states listed in the Forwarding state field. |
Interface Type |
Shows if the interface is a regular port or a tunnel port. |