This command displays multicast path management bandwidth policy information.
The following output displays an example of multicast management bandwidth policy information.
7450 ESS, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR
Displays basic information about the service ID including service type, description, SAPs and SDPs.
The following output is an example of base service ID information, and Table 50 describes the output fields.
Label | Description |
Service Id | The service identifier. |
Vpn Id | Specifies the VPN ID assigned to the service. |
Service Type | The type of service: Epipe, Apipe, Fpipe, Ipipe, VPLS, IES, VPRN. |
Description | Generic information about the service. |
Customer Id | The customer identifier. |
Last Mgmt Change | The date and time of the most recent management-initiated change to this customer. |
Adm | The desired state of the service. |
Oper | The operating state of the service. |
Mtu | The largest frame size (in octets) that the service can handle. |
SAP Count | The number of SAPs defined on the service. |
SDP Bind Count | The number of SDPs bound to the service. |
Identifier | Specifies the service access (SAP) and destination (SDP) points. |
Type | Specifies the signaling protocol used to obtain the ingress and egress labels used in frames transmitted and received on the SDP. |
AdmMTU | Specifies the desired largest service frame size (in octets) that can be transmitted through this SDP to the far-end ESR, without requiring the packet to be fragmented. |
PBB Tunnel Point | Specifies the endpoint in the B-VPLS environment where the Epipe terminates. |
Admin MTU | Specifies the B-VPLS admin MTU. |
Backbone-Flooding | Specifies whether or not the traffic is flooded in the B-VPLS for the destination instead of unicast. If the backbone destination MAC is in the B-VPLS FDB, then it will be unicast. |
ISID | The 24 bit field carrying the service instance identifier associated with the frame. It is used at the destination PE as a demultiplexor field. |
All
This command displays basic MLD snooping information.
All
This command displays SPB base information.
The following output is an example of service SPB base information.
All
The show qos bcg command outputs the current and historical visitation time associated with the specified BCG name.
A Burst Control Group (BCG) represents a list of queues that share the same non-scheduling PIR and CIR bucket target update interval. When a queue’s scheduled rate bursts above its PIR bucket depth, the queue is removed from its scheduling context. The system uses a BCG in order to visit the queues PIR bucket to periodically drain an appropriate amount from the bucket. When the bucket has been drained below the PIR bucket threshold, the queue is allowed back onto its scheduling context. The amount decremented from the bucket is a function of the amount of time that has elapsed since the last bucket update and the queue’s shaping rate (PIR). If the queue’s shaping rate is configured as 1 Mb/s and 1 ms has elapsed since the last bucket update, the system decrements the PIR bucket by 125 bytes. One caveat is that the bucket cannot be decremented past a depth of 0. This fact drives how the system chooses which BCG is used to manage the queue bucket update interval.
If a queue’s shaping rate is 1 Mb/s and the threshold (burst limit) is set to 10 kbytes, the maximum amount of time that can expire before the queue is updated without resulting in a negative bucket depth is 81.92 ms. This can be calculated by taking the number of bits represented by the bucket depth (10 kbytes = 10 * 1,024 * 8 = 81,920 bits) and dividing it by the rate (81,920 bits / 1,000,000 bits per second = 81.92 ms). The queue is not removed from the scheduler until the PIR bucket depth has equaled or exceeded the configured burst threshold, so the bucket is at least 10 kbytes deep. If the system visits the queue PIR bucket within 81.92 ms, the resulting decrement operation leaves the bucket. If the system takes longer than 81.92 ms, the decrement result will be greater than 10 kbytes and part of the decrement result is lost. The net result is that, because of less than timely updates, the queue will not be returned to the scheduler context fast enough and some shaping bandwidth for the queue will be lost (underrun the shaping rate).
Each FP2- and FP3-based Q-chip maintains eight BCGs, each targeting a certain queue bucket visitation time. A 1 s, 40 ms, 20 ms, 10 ms, 5 ms, 1 ms, 500 µs, and 100 µs BCG is supported. An FP4-based Q-chip has an additional four BCGs with target visitation times of 50 μs, 10 μs, 5 μs, and 1 μs. By default, queues are placed in a BCG based on shaping rate and the queue’s burst limit (PIR threshold depth) is set based on the BCG visitation time and the queue’s specified shaping rate.
When explicit burst-limit threshold values are defined for a shaping queue, the system picks an appropriate BCG based on the queue’s configured shaping rate and the explicit threshold to find a BCG with the best target visitation time that results in worst-case decrement values that are less than the configured threshold. However, when a queue is placed on a ‘faster’ BCG, more visitation resources are consumed and it is possible that the system will not meet a queue’s decrement constraints.
The show qos bcg command allows visibility into a BCG’s historic and current visitation time. The system samples the amount of time it takes each list to visit each of its associated queues once each second and stores the last 10 samples. It also keeps the longest visitation time seen since the last time the BCG statistics were cleared, the longest visitation time for the current queue-to-BCG lists associations, calculated longest visitation time based on maximum scheduling bandwidth, and the longest visitation time for an optionally defined scheduling rate.
With each sample, the system indirectly calculates the amount of scheduling bandwidth based on how many Q-chip resources were diverted from BCG visitation processing. This calculated scheduling bandwidth is used to evaluate the worst-case visitation times for each BCG. The calculated scheduling bandwidth value is stored with the longest-seen-visitation time and the longest-seen-visitation time with the current queue-to-BCG mappings. This is not applicable to an FP4-based Q-chip, so the exp-util-bw parameter is not applicable to an FP4-based Q-chip.
All
This command displays information for the specified HLE bridge. If no bridge is specified, then all domains are listed.
The following output is an example of HLE bridge information.
7750 SR, 7750 SR-e, 7750 SR-s, VSR
7750 SR, 7750 SR-e, 7750 SR-s, VSR
All
The following output is an example of BFD information.
All
All
This command displays BFD template information.
The following output is an example of BFD template information.
All
This command indicates the named BFD templates that are configured for use by LSP BFD for LDP.
All
This command displays BGP-related information for the service.
The following is an example of BGP-related output.
All
This command clears or resets the route damping information for received routes.
All
All
This command displays all the traffic statistics of the SR policy specified by its color and end-point.
The following output is an example of traffic statistics of the SR policy.
All
This command displays BGP auto route distinguisher (RD) information.
The following shows an example of BGP auto route distinguisher (RD) information
All
This command displays the bgp-evpn configured parameters for a specified service, including the admin status of VXLAN, the configuration for mac-advertisement and unknown-mac-route, as well as the mac-duplication parameters. The command shows the duplicate MAC addresses that mac-duplication has detected.
This command also shows whether the ip-route-advertisement command (and the incl-host parameter) is enabled. If the service is BGP-EVPN MPLS, the command also shows the parameters corresponding to EVPN-MPLS.
The following is an example of BGP EVPN information.
All
The following output is an example of service system BGP EVPN information, and Table 51 describes the output fields.
Label | Description |
Eth Seg Route Dist | Specifies the ES Route Distinguisher. |
Eth Seg Oper Route Dist | Specifies the operational ES Route Distinguisher. |
Eth Seg Oper Route Dist Type | Specifies the operational ES Route Distinguisher type. |
Ad Per ES Route Target | Specifies the AD per-ES route target. |
Leaf Label | Specifies the leaf label. |
Alloc Leaf Label | Specifies the allocated leaf label. |
Leaf Label Value | Specifies the leaf label value. |
Mcast Leave Sync Prop | Specifies the multicast leave synchronization propagation time. |
Attribute Uniform Prop | Specifies the attribute uniform propagation configuration. |
BGP Path Selection | Specifies the configuration of the BGP Path Selection. |
All
All
This command shows the information related to the EVPN global timers.
All
This command displays the BGP operational route-distinguishers used by all the bgp-enabled services in the system. The information can be filtered by service: VPRN, VPLS. or Epipe. The output can also be filtered to show only the relevant route-distinguisher information related to services (svc), or the EVPN Auto-Discovery routes (ad-evi-rt-set), or the system route-distinguishers (system).
The following is an example of service BGP auto route distinguisher (RD) information.
All
This command displays BGP VPWS related information for the service.
The following output is an example of BGP VPWS information.
All
All
All
Show the configuration data for one or all OAM Performance Monitoring bin groups.
The following is an example of OAM-PM bin group information.
All
Show the list of sessions configured against one or all OAM Performance Monitoring bin groups.
The following is an example of OAM-PM bin group session information.
All
This command displays the MPLS forwarding policy binding label information.
Table 52 describes MPLS binding label output fields.
Label | Description |
Label | Specifies the label number. |
Preference | Specifies the preference. |
Oper State | Specifies the operational state (up | down). |
Policy Name | Specifies the MPLS forwarding policies binding label name. |
No. of Binding Labels | Specifies the number of binding labels. |
OperDown Reason | Specifies the reason for being operationally down. |
Down Time | Specifies the downtime date and time. |
NumNextHopGrps | Specifies the number of next-hop groups. |
Ingress Stats | Specifies if ingress stats are enabled for collection (disabled | enabled). |
IngOperState | Specifies the ingress operational state (up | down) |
Revert Timer | Specifies the revert timer value. |
Retry Count | Specifies the retry count. |
Next Retry In | Specifies the next retry value. |
Next-hop Group | Specifies the next-hop group. |
Resolution Type | Specifies the resolution type (direct | indirect). |
Num Revert | Specifies the number of reverts. |
Num Failover | Specifies the number of failovers. |
Next Revert In | Specifies the next revert interval. |
Primary nexthop | Specifies the IP address of the primary next-hop. |
Resolved | Specifies the resolved status (false | true). |
NHopDownReason | Specifies the reason for the next-hop down. |
Backup nexthop | Specifies the IP address of the backup next-hop. |
StatsOperState | Specifies if a statistic index is allocated to the next-hop. |
EgrStatsState | Specifies if all next-hops have a statistic index allocated. |
All
This command lists all the DHCP bindings of the local pool associated with the specified BRG. If the MAC attribute is specified, only the binding for that MAC address is displayed.
The following output is an example of BRG gateway binding information.
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
This command displays LDP bindings information.
The following output is an example of LDP bindings information.
All
This command displays detailed information about the Bluetooth configuration on the CPM or chassis.
The following is an example of Bluetooth configuration information. Table 53 describes the output fields.
Label | Description |
Passkey | The Bluetooth passkey in use by the system. |
Advertising Timeout | The amount of time the Bluetooth will advertise that it is ready to pair. |
Power State | The operating mode for Bluetooth. |
Pairing Button | Displays whether the pairing button is enabled for use. |
Device | The MAC address of the Bluetooth device. |
Description | The customer-entered description for the Bluetooth device. |
Module | Displays which CPM module contains the Bluetooth device. |
Connected Device | Displays if there is a device actively paired to the module. |
Device MAC | The MAC address of the Bluetooth device connected to the module. |
Device Description | The description associated with the connected Bluetooth device. |
Configured Identifier | The customer-defined Bluetooth identifier for the module. |
Operational Identifier | The Bluetooth identifier in use for the module. |
7750 SR-1, 7750 SR-s
7750 SR-1, 7750 SR-s
All
Commands in this context display BGP related information.
All
This command displays the Boot Option File (BOF) executed on last system boot or on the specified device.
If no device is specified, the BOF used in the last system boot displays. If the BOF has been modified since the system boot, a message displays.
The following output is an example of BOF, and Table 54 describes the output fields.
Label | Description |
primary-image | The primary location of the directory that contains the runtime images of both CPM and XCM/IOM. |
primary-config | The primary location of the file that contains the configuration. |
primary-dns | The primary DNS server for resolution of host names to IP addresses. |
secondary-image | The secondary location of the directory that contains the runtime images of both CPM and XCM/IOM. |
secondary-config | The secondary location of the file that contains the configuration. |
secondary-dns | The secondary DNS server for resolution of host names to IP addresses. |
tertiary-image | The tertiary location of the directory that contains the runtime images of both CPM and XCM/IOM. |
tertiary-config | The tertiary location of the file that contains the configuration. |
address | The IP address and mask associated with the CPM Ethernet port or the secondary CPM port. |
tertiary-dns | The tertiary DNS server for resolution of host names to IP addresses. |
persist | on — Persistent indexes between system reboots is enabled. off — Persistent indexes between system reboots is disabled. |
wait | The time configured for the boot to pause while waiting for console input. |
autonegotiate | no autonegotiate — Autonegotiate not enabled. autonegotiate — Autonegotiate is enabled. |
duplex | half — Specifies that the system uses half duplex. full — Specifies that the system uses full duplex. |
speed | The speed of the CPM Ethernet interface. |
console speed | The console port baud rate. |
dns domain | The domain name used when performing DNS address resolution. |
uplinkA-address | Displays the Uplink-A IP address. |
uplinkA-port | Displays the primary port to be used for auto-boot. |
uplinkA-route | Displays the static route associated with Uplink-A. |
uplinkA-vlan | Displays the VLAN ID to be used on Uplink-A. |
uplinkB-address | Displays the Uplink-B IP address. |
uplinkB-port | Displays the secondary port to be used for auto-boot. |
uplinkB-route | Displays the static route associated with Uplink-B. |
uplinkB-vlan | Displays the VLAN ID to be used on Uplink-B. |
uplink-mode | Displays the uplink mode of the device. |
no-service-ports | Displays the ports on which service traffic is not processed. |
use-expansion-card-type | The expansion card type. |
system-profile | The system profile used by the system when it is rebooted. |
All
This command displays an overview of active bonding contexts and the associated access connections.
When a bonding ID is specified, only information for that specific context is displayed.
The following is an example of bonding information.
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
This command enables the tools used for hybrid access bonding.
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
This command displays boot messages generated during the last system boot.
The following output is an example of a boot-message.
All
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
This command clears BRG data.
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
This command enables tools for controlling BRGs.
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
This command displays operational information for connected BRGs and related hosts.
The following output is an example of subscriber management BRG host information.
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
This command displays BRG profile information.
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
This command displays L2TP MLPPP bundle statistics.
The following output is an example of L2TP MLPPP bundle statistics information.
The following is an example with one MLPPP bundle (using two links).
The following is an example with two MLPPP bundles (using two links)
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
If fast reroute is enabled on an LSP and the facility method is selected, instead of creating a separate LSP for every LSP that is to be backed up, a single LSP is created which serves as a backup for a set of LSPs. Such an LSP tunnel is called a bypass tunnel.
The following output is an example of MPLS bypass tunnel information.
Table 55 describes MPLS bypass tunnel output fields.
Label | Description |
To | The IP address of the egress router. |
State | The LSP’s administrative state. |
Out I/F | Specifies the name of the network IP interface. |
Out Label | Specifies the incoming MPLS label on which to match. |
Reserved BW (kb/s) | Specifies the amount of bandwidth in Mb/s reserved for the LSP. |
All
This command displays information about the MPLS bypass tunnel.
All