IEEE 802.1ah Provider Backbone Bridging (PBB)
Provider Backbone Bridging (PBB) is supported only on the 7210 SAS-T operating in the network mode.
This chapter provides information about PBB, process overview, and implementation notes.
IEEE 802.1ah PBB overview
IEEE 802.1ah draft standard (IEEE802.1ah), also known as Provider Backbone Bridges (PBB), defines an architecture and bridge protocols for interconnection of multiple Provider Bridge Networks (PBNs - IEEE802.1ad QinQ networks). PBB is defined in IEEE as a connectionless technology based on multipoint VLAN tunnels. IEEE 802.1ah employs Provider MSTP as the core control plane for loop avoidance and load balancing. As a result, the coverage of the solution is limited by STP scale in the core of large service provider networks. The 7210 SAS-T in network mode supports a native PBB Ethernet backbone deployment.
The IEEE model for PBB is organized around a B-component handling the provider backbone layer and an I-component concerned with the mapping of Customer or Provider Bridge (QinQ) domain (for example, MACs, VLANs) to the provider backbone (for example, B-MACs, B-VLANs), that is, the I-component contains the boundary between the Customer and Backbone MAC domains. PBB encapsulates customer payload in a provider backbone Ethernet header, providing for Customer MAC hiding capabilities. With PBB, 7210 SAS platforms can be used for tier-1/2 aggregation, encapsulating customer service frames in PBB, allowing the PE-rs devices deployed in the metro core to be aware of only provider MAC addresses and for metro service scaling.
7210 SAS platforms fully support only native PBB deployment. They do not support the integrated PBB VPLS model. In particular, 7210 SAS platforms do not support use of SDPs in PBB services.
PBB features
Integrated PBB-VPLS solution
H-VPLS introduced a service-aware device in a central core location to provide efficient replication and controlled interaction at domain boundaries. The core network facing provider edge (N-PE) devices have knowledge of all VPLS services and customer MAC addresses for local and related remote regions resulting in potential scalability issues as shown in the following figure.
In a large VPLS deployment, it is important to improve the stability of the overall solution and to speed up service delivery. These goals are achieved by reducing the load on the N-PEs and respectively minimizing the number of provisioning touches on the N-PEs.
The integrated PBB-VPLS model provides an additional PBB hierarchy in the VPLS network to address these goals, as shown in the following figure.
PBB encapsulation is added at the user facing PE (U-PE) to hide the customer MAC addressing and topology from the N-PE devices. The core N-PEs need to only handle backbone MAC addressing and do not need to have visibility of each customer VPN. As a result, the integrated PBB-VPLS solution decreases the load in the N-PEs and improves the overall stability of the backbone.
In the preceding figure, 7210 devices can only be used as U-PEs supporting only native Ethernet PBB services.
PBB technology
IEEE 802.1ah specification encapsulates the customer or QinQ payload in a provider header as shown in the following figure.
PBB adds a regular Ethernet header where the B-DA and B-SA are the backbone destination and respectively, source MACs of the edge U-PEs. The backbone MACs (B-MACs) are used by the core N-PE devices to switch the frame through the backbone.
A special group MAC is used for the backbone destination MAC (B-DA) when handling an unknown unicast, multicast or broadcast frame. This backbone group MAC is derived from the I-service instance identifier (ISID) using the rule: a standard group OUI (01-1E-83) followed by the 24 bit ISID coded in the last three bytes of the MAC address.
The BVID (backbone VLAN ID) field is a regular DOT1Q tag and controls the size of the backbone broadcast domain.
The following ITAG (standard Ether-type value of 0x88E7) has the role of identifying the customer VPN to which the frame is addressed through the 24 bit ISID.
PBB mapping to existing VPLS configurations
The IEEE model for PBB is organized around a B-component handling the provider backbone layer and an I-component concerned with the mapping of the customer/provider bridge (QinQ) domain (MACs, VLANs) to the provider backbone (B-MACs, B-VLANs). For example, the I-component contains the boundary between the customer and backbone MAC domains.
The Nokia implementation is extending the IEEE model for PBB to allow support for MPLS pseudowires using a chain of two VPLS context linked together as shown in the following figure.
7210 SAS does not support MPLS pseudowires in a PBB B-component and PBB I-component.
I-PW and B-PW are not supported on 7210 SAS platforms.
A VPLS context is used to provide the backbone switching component. The white circle marked B, referred to as backbone-VPLS (B-VPLS) operates on backbone MAC addresses providing a core multipoint infrastructure that may be used for one or multiple customer VPNs. The Nokia B-VPLS implementation allows the use of native PBB infrastructures.
7210 SAS implementation allows the use of only native PBB over Ethernet infrastructures.
Another VPLS context (I-VPLS) can be used to provide the multipoint I-component functionality emulating the ELAN service (refer to the triangle marked ‟I” in the preceding figure). Similar to B-VPLS, I-VPLS inherits from the regular VPLS and native Ethernet (SAPs) hand-offs accommodating this way different types of access: for example, direct customer link, QinQ or H-VPLS.
To support PBB ELINE (point-to-point service), the use of an Epipe as I-component is allowed. All Ethernet SAPs supported by a regular Epipe are also supported in the PBB Epipe.
SAP support
This section contains information about the following topics:
PBB B-VPLS
SAPs
Ethernet dot1q is supported - this is applicable to most PBB use cases, for example, one backbone VLAN ID used for native Ethernet tunneling
Ethernet null is supported - this is supported for a direct connection between PBB PEs, for example, no BVID is required
Default SAP types are blocked in the CLI for the B-VPLS SAP.
The following rules apply to the SAP processing of PBB frames:
For ‟transit frames” (not destined to a local BMAC), there is no need to process the ITAG component of the PBB Frames. Regular Ethernet SAP processing is applied to the backbone header (BMACs and BVID).
If a local I-VPLS instance is associated with the B-VPLS, ‟local frames” originated/terminated on local I-VPLSes are PBB encapsulated/de-encapsulated using the pbb-etype = 0x88e7.
PBB I-VPLS
Port Level
All existing Ethernet encapsulation types are supported (for example, null, dot1q, qinq).
SAPs
The I-VPLS SAPs can coexist on the same port with SAPs for other business services, for example, VLL, VPLS SAPs.
All existing Ethernet encapsulation are supported: null, dot1q, qinq.
Existing SAP processing rules still apply for the I-VPLS case; the SAP encapsulation definition on Ethernet ingress ports defines which VLAN tags are used to determine the service that the packet belongs to:
null encap defined on ingress
Any VLAN tags are ignored and the packet goes to a default service for the SAP.
dot1q encap defined on ingress
Only first VLAN tag is considered.
QinQ encap defined on ingress
Both VLAN tags are considered; wildcard support for the inner VLAN tag.
For dot1q/qinq encapsulations, traffic encapsulated with VLAN tags for which there is no definition is discarded.
Note that any VLAN tag used for service selection on the I-SAP is stripped before the PBB encapsulation is added. Appropriate VLAN tags are added at the remote PBB PE when sending the packet out on the egress SAP.
PBB packet walk-through
This section describes the walk-through for a packet that traverses the B-VPLS and I-VPLS instances using the example of a unicast frame between two customer stations as shown in the following network diagram in the following figure.
The station with CMAC (customer MAC) X needs to send a unicast frame to CMAC Y through the PBB-VPLS network. A customer frame arriving at PBB-VPLS U-PE1 is encapsulated with the PBB header. The local I-VPLS FIB on U-PE1 is consulted to determine the destination BMAC of the egress U-PE for CMAC Y. In our example, B2 is assumed to be known as the B-DA for Y. If CMAC Y is not present in the U-PE1 forwarding database, the PBB packet is sent in the B-VPLS using the standard group MAC address for the ISID associated with the customer VPN.
Next, only the Backbone Header in green is used to switch the frame through the green B-VPLS/VPLS instances in the N-PEs. At the receiving U-PE2, the CMAC X is learned as being behind BMAC B1; then the PBB encapsulation is removed and the lookup for CMAC Y is performed.
PBB ELINE service
ELINE service is defined in PBB (IEEE 802.1ah) as a point-to-point service over the B-component infrastructure. The Nokia implementation provides support for PBB ELINE through the mapping of multiple Epipe services to a Backbone VPLS infrastructure.
The use of Epipe scales the ELINE services as no MAC switching, learning or replication is required to deliver the point-to-point service.
All packets ingressing the customer SAP are PBB encapsulated and unicasted through the B-VPLS ‟tunnel” using the backbone destination MAC of the remote PBB PE.
All the packets ingressing the B-VPLS destined for the Epipe are PBB de-encapsulated and forwarded to the customer SAP.
PBB resiliency for PBB Epipe service
The PBB Epipe service can be protected using G.8032 (the G8032 instance is created to protect the PBB B-VPLS service). For more information and for an example see Overview of G.8032 operation.
PBB resiliency for B-VPLS
The following VPLS resiliency mechanisms are also supported in PBB VPLS:
Native Ethernet resiliency supported in both I-VPLS and B-VPLS contexts.
Distributed LAG, MC-LAG, RSTP.
MSTP in a management VPLS monitoring (B- or I-) SAPs.
The G.8032 is supported for B-VPLS service. The G.8032 support is used only with PBB Epipe service from the current releases and cannot be used with PBB I-VPLS service.
Access multi-homing for native PBB (B-VPLS over SAP infrastructure)
The Nokia PBB implementation allows the operator to use a native Ethernet infrastructure as the PBB core. Native Ethernet tunneling can be emulated using Ethernet SAPs to interconnect the related B-VPLS instances. This kind of solution might fit certain operational environments where Ethernet services was provided in the past using QinQ solution. The drawback is that no LDP signaling is available to provide support for Access Multi-homing for Epipe (pseudowire Active/Standby status) or I-VPLS services (LDP MAC Withdraw). An alternate solution is required.
A PBB network using Native Ethernet core is shown in the following figure. MC-LAG is used to multi-home a number of edge switches running QinQ to PBB BEBs.
The interrupted line from the MC-LAG represents the standby, inactive link; the solid line is the active link. The BEBs are dual-homed to two core switches BCB1 and BCB2 using native Ethernet SAPs on the B-VPLS side. Multi-point B-VPLS with MSTP for loop avoidance can be used as the PBB core tunneling.
PBB QoS
The following QoS processing rules apply for PBB B-VPLS SAPs:
B-VPLS SAP ingress
If dot1p classification is enabled, the BTAG fields will be used by default to evaluate the internal forwarding class (fc) and discard profile if there is a BTAG field.
If dot1p classification is not explicitly enabled or the packets are untagged then the default fc and profile is assigned.
B-VPLS SAP egress
If the access port based policy contains FC and profile to dot1p mapping, this entry is used to mark the dot1p bits in the B-TAG of the frame going out of the SAP. The I-Tag of the frame is not modified in any case.
If no explicit mapping exists, the related dot1p DE bits are set to zero on both ITAG and BTAG if the frame is originated locally from an I-VPLS. If the frame is transiting the B-VPLS the ITAG stays unchanged, the BTAG is set according to the type of ingress SAP.
If the ingress SAP is tagged, the values of the dot1p, DE bits are preserved in the BTAG going out on the egress SAP.
If the ingress SAP is untagged, the dot1p, DE bits are set to zero in the BTAG going out on the egress SAP.
I-SAP Ingress
SAP ingress classification using mac-criteria or IP DSCP is supported.
I-SAP Egress
Access port based marking is supported for I-SAPs (dot1q and QinQ SAPs).
PBB ACL support
Filter policies are supported for ingress and egress of PBB I-SAP in both PBB Epipe and PBB VPLS service.
Only MAC criteria Filter policies is available for use with PBB B-SAPs on ingress with the following functionality:
For PBB B-VPLS B-SAPs, the MAC filter matches the outer MAC header fields (that is, B-DA, B-SA, B-Tag) for traffic received on a B-SAP and forwarded to another B-SAP in the system.
For PBB B-VPLS B-SAPs, the MAC filter matches the inner MAC header fields (that is, the customer MAC DA, SA and VLAN tags) for traffic received on a B-SAP and forwarded out of an I-SAP in the system.
Only MAC criteria filter policies is available for use with PBB B-SAPs on egress. This filter policy only matches the BCB traffic. BEB traffic (that is, PBB originated traffic) cannot be matched using the egress filter policy attached to PBB B-SAP.
Configuration guidelines
Listed as follows are the configuration guidelines for a PBB service:
PBB services are supported only on 7210 SAS devices configured in network mode.
A PBB service instance (identified by the ISID) cannot be used to encapsulate customer payloads with additional VLAN tags, if that service instance is being used to transport frames received on a QinQ access SAP. If a particular service instance is in use by a QinQ access SAP, then the system drops the packets that are received with additional tags on all the SAPs (NULL or Dot1q) using the same instance. Packets received with one or more tags on a NULL SAP, more than one tag on a Dot1q SAP, and more than two tags on a QinQ SAP are classified as packets with additional VLAN tags.
Service MTU is not available for use.
Port-based SHG is available for use with I-VPLS and B-VPLS service. Service based SHG is not available for use in an I-VPLS and a B-VPLS service.
The system uses the internal loopback to flood/replicate BUM traffic received on the B-SAP, to create an additional copy for processing in the I-VPLS context. The system also uses the internal loopback to for egress port mirroring.
The user needs to ensure that aggregate amount of mirrored traffic in the system and the BUM traffic received on a B-SAP does not exceed the available internal loopback bandwidth. Ingress meters can be used to limit the amount of BUM received and processed from a B-SAP and user can limit the number of ports setup for port egress mirroring to control the maximum amount of traffic that needs to be circulated for two pass processing using the internal loopback. NOTE: If only PBB Epipe is used (no I-VPLS service is configured for use), then egress port mirroring can be enabled without affecting PBB traffic, since PBB Epipe traffic does not use the two-pass approach.
Multiple B-SAPs on the same port cannot be part of the same B-VPLS service. Two B-SAPs on the same port need to be configured in two different services.
Processing rules for packets received with multiple B-tags on a SAP:
If the B-Tag header has two tags, the packet is processed and forwarded appropriately and sent out of an I-SID service or another B-VPLS B-SAP.
If the node is acting as a pure BCB (with no ISID/service termination), then the packets are flooded and switched appropriately and if the node is acting as a BCB + BEB, then the packets are flooded and switched appropriately on the B-SAPs, but they will not switched or flooded to a I-SAPs (both VPLS and Epipe I-SAPs).
PBB I-tag etype is not configurable, it is set to 0x88e7.
PBB B-tag etype is not configurable; it is set to 0x8100.
PBB packets received from a destination MAC address other than the one configured in the Epipe service is not accepted by 7210 devices.
In the current release, PBB packets with UCA bit set are dropped.
Aging of MAC addresses learned in the B-domain - As long as a Customer MAC (C-MAC) or an Epipe service is associated with an B-SA/B-MAC, do not age out the B-SA. When the last customer MAC ages out or the last Epipe service using the particular B-SA MAC is removed, remove the corresponding B-SA entry. This means that as long as an Epipe service is associated with a particular PBB destination MAC address, the corresponding B-MAC will not age out and will occupy an entry in the Layer 2 learning table. Note, that if only I-VPLS is in use, then aging out of C-MAC will automatically trigger aging out B-MAC, when the last C-MAC associated with the B-MAC is aged out.
Configuration guidelines for the 7210 SAS-T
The following configuration guidelines are specific to the 7210 SAS-T operating in the network mode.
When ‟discard-unknown” is enabled on a B-VPLS, the following behavior can be observed:
Unknown unicast (B-DA) packets arriving on a B-SAP are dropped.
Unknown unicast (C-DA) packets arriving on a B-SAP are processed in the I-VPLS, if the B-DA is not unknown unicast.
Unknown unicast (C-DA) packets arriving on an I-SAP are not dropped and are flooded in the B-VPLS, because B-DA is equal to the ‟Group Mcast MAC” and is a known value
Port based SHG is available for use with both I-VPLS and B-VPLS service. Service based SHG is not available in both.
Configuration examples
Use the CLI syntax displayed to configure PBB.
PBB ELAN and ELINE
Use the following syntax to bring up PBB B-VPLS - common to both ELAN and ELINE services.
— config>service# vpls 200 customer 1 b-vpls create
— description ‟This is a B-VPLS.”
— sap 3/1/3:33 create
— description ‟B-VPLS SAP”
Use the following syntax to bring up PBB ELAN.
— config>service# vpls 2000 customer 6 i-vpls create
— description ‟This is an I-VPLS.”
— sap 4/1/3:20 create
— description ‟I-VPLS SAP”
— backbone-vpls 200
Use the following syntax to bring up PBB ELINE.
— config>service# epipe 1000 customer 10 create pbb-epipe
— description ‟This is an Epipe.”
— sap 4/1/3:20 create
— description ‟Epipe SAP”
— pbb-tunnel 200 backbone-dest-mac 00-01-10-1E-C6-67 isid 752
MC-LAG multi-homing for native PBB
This section describes a configuration example for BEB C configuration with the following assumptions:
BEB C and BEB D are MC-LAG peers
B-VPLS 100 on BEB C and BEB D
VPLS 1000 on BEB C and BEB D
MC-LAG 1 on BEB C and BEB D
— service pbb
— source-bmac ab-ac-ad-ef-00-00
— port 1/1/1
— ethernet
— encap-type qinq
— lag 1
— port 1/1/1 priority 20
— lacp active administrative-key 32768
— redundancy
— multi-chassis
— peer 1.1.1.3 create
— source-address 10.1.1.1
— mc-lag
— lag 1 lacp-key 1 system-id 00:00:00:01:01:01 system-priority 100
— source-bmac-lsb use-lacp-key
— service vpls 100 bvpls
— sap 2/2/2:100 // bvid 100
— mac-notification
— no shutdown
—
— service vpls 101 bvpls
— sap 2/2/2:101 // bvid 101
— mac-notification
— no shutdown
— // no per BVPLS source-bmac configuration, the chassis one (ab-ac-ad-ef-00-00) is used
—
— service vpls 1000 ivpls
— backbone-vpls 100
— sap lag-1:1000 //automatically associates the SAP with ab-ac-ad-ef-00-01 (first 36 bits from BVPLS 100 sbmac+16bit source-bmac-lsb)
—
— service vpls 1001 ivpls
— backbone-vpls 101
— sap lag-1:1001 //automatically associates the SAP with ab-ac-ad-ef-00-01(first 36 bits from BVPLS 101 sbmac+16bit source-bmac-lsb)
PBB command reference
PBB CLI commands are supported only on 7210 SAS-T operating in network mode.
Command hierarchies
PBB service commands
config
- service
- pbb
- mac-name name ieee-address
- no mac-name
- source-bmac ieee-address
- no source-bmac
config
- service
- vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
- no vpls service-id
- pbb
- backbone-vpls service-id [isid isid]
- no backbone-vpls
- source-bmac ieee-address
- no source-bmac
config
- service
- [no] epipe service-id [customer customer-id] [create] [vpn vpn-id] svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [pbb-epipe]
- pbb
- tunnel service-id backbone-dest-mac mac-name isid ISID
- tunnel service-id backbone-dest-mac ieee-address isid ISID
- no tunnel
Show commands
show
- eth-cfm
- association [ma-index] [detail]
- cfm-stack-table [port port-id [vlan qtag[.qtag]] | sdp sdp-id[:vc-id] [level 0..7] [direction up | down]
- domain [md-index] [association ma-index | all-associations [detail]]
- mep mep-id domain md-index association ma-index [loopback] [linktrace]
- mip
- service
- id service-id
- i-vpls
- epipe
- all
- base
- fdb {info | mac ieee-address | sap sap-id | detail | endpoint endpoint} [expiry] [pbb]
- stp [detail]
- isid-using [ISID]
- pbb
- mac-name [detail]
- service-using [b-vpls] [i-vpls]
Clear commands
clear
- service
- id service-id
- fdb {all | mac ieee-address | sap sap-id}
- stp
- detected-protocols [all | sap sap-id]
- statistics
- id service-id
- counters
- stp
- sap sap-id {all | counters | stp}
Debug commands
debug
- service
- id service-id
- [no] event-type {config-change | svc-oper-status-change | sap-oper-statuschange}
- [no] sap sap-id
- stp
- all-events
- [no] bpdu
- [no] core-connectivity
- [no] exception
- [no] fsm-state-changes
- [no] fsm-timers
- [no] port-role
- [no] port-state
- [no] sap sap-id
Command descriptions
PBB service configuration commands
pbb
Syntax
pbb
Context
config>service
config>service>epipe
config>service>vpls
Platforms
7210 SAS-T (network operating mode)
Description
Commands in this context configure the parameters related to Provider Backbone Bridging (PBB).
mac-name
Syntax
mac-name name ieee-address
no mac-name name
Context
config>service>pbb
Platforms
7210 SAS-T (network operating mode)
Description
This command configures the MAC name for the MAC address. It associates an ASCII name with an IEEE MAC to improve the PBB Epipe configuration. It can also change the dest-BMAC in one place instead of thousands of Epipes.
Parameters
- name
Specifies the MAC name up to 32 characters.
- ieee-address
Specifies the MAC address assigned to the MAC name. The value should be input in either a xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx format.
source-bmac
Syntax
source-bmac ieee-address
no source-bmac
Context
config>service>pbb
config>service>vpls>pbb
Platforms
7210 SAS-T (network operating mode)
Description
This command configures the base source BMAC for the B-VPLS. The first 32 bits must be the same as those configured in the MC-LAG peer. If the base source BMAC under VPLS is not configured, it inherits the chassis-level BMAC.
Parameters
- ieee-address
Specifies the MAC address assigned to the BMAC. The value should be input in either a xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx format.
tunnel
Syntax
tunnel service-id backbone-dest-mac mac-name isid ISID
tunnel service-id backbone-dest-mac ieee-mac isid ISID
no tunnel
Context
config>service>epipe>pbb
Platforms
7210 SAS-T (network operating mode)
Description
This command configures a PBB tunnel with Backbone VPLS (B-VPLS) service information.
Parameters
- service-id
Specifies the B-VPLS service for the PBB tunnel associated with this service.
- backbone-dest-mac {mac-name | ieee-mac}
Specifies the backbone destination MAC-address for PBB packets.
- isid ISID
Specifies a 24 bit service instance identifier for the PBB tunnel associated with this service. As part of the PBB frames, it is used at the destination PE as a demultiplexor field.
vpls
Syntax
vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
no vpls service-id
Context
config>service
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Description
This command creates or edits a virtual private LAN services (VPLS) instance. The vpls command is used to create or maintain a VPLS service. If the service-id does not exist, a context for the service is created. If the service-id exists, the context for editing the service is entered.
A VPLS service connects multiple customer sites, acting like a zero-hop Layer 2 switched domain. A VPLS is always a logical full mesh.
When a service is created, the create keyword must be specified if the create command is enabled in the environment context. When a service is created, the customer keyword and customer-id parameter must be specified to associate the service with a customer. The customer-id value must already exist, having been created using the customer command in the service context. When a service has been created with a customer association, it is not possible to edit the customer association. The service must be deleted and recreated with a new customer association.
When a service is created, the use of the customer customer-id command is optional for navigating into the service configuration context. Editing a service with the incorrect customer-id value specified results in an error.
More than one VPLS service may be created for a single customer ID.
By default, no VPLS instances exist until they are explicitly created.
The no form of this command deletes the VPLS service instance with the specified service-id. The service cannot be deleted until all SAPs and SDPs defined within the service ID have been shut down and deleted, and the service has been shut down.
Parameters
- service-id
Specifies the unique service identification number identifying the service in the service domain. This ID must be unique to this service and may not be used for any other service of any type. The service-id must be the same number used for every 7210 SAS on which this service is defined.
- customer customer-id
Specifies the customer ID number to be associated with the service. This parameter is required on service creation and optional for service editing or deleting.
- m-vpls
Keyword to create a management VPLS.
- b-vpls
Keyword to create a PBB backbone-VPLS service, which can only be configured with SAPs. This keyword is supported only on 7210 SAS-T operating in network mode.
- i-vpls
Keyword to create a PBB I-VPLS service, which can only be configured with SAPs. This keyword is only supported when the svc-sap-type value any is configured. This keyword is supported only on 7210 SAS-T operating in network mode.
- create
Keyword that is mandatory when creating a VPLS service instance. The create keyword requirement can be enabled or disabled in the environment>create context.
- svc-sap-type
Specifies the type of service and allowed SAPs in the service.
- b-vid vid
Specifies the VLAN ID to use when the svc-sap-type value is set to dot1q-preserve. This parameter is supported only when the b-vpls keyword and svc-sap-type value dot1q-preserve are configured.
- r-vpls
Keyword that allows the VPLS instance to be associated with an IP interface to provide routed VPLS (RVPLS) functionality. When configured with the svc-sap-type values null-star, dot1q-preserve, and any, this keyword instantiates an RVPLS service that can be configured only with SAPs.
Note:The r-vpls keyword is not supported in access-uplink mode (that is, in access-uplink mode, routed VPLS service can be configured without using this parameter).
backbone-vpls
Syntax
backbone-vpls service-id [isid isid]
no backbone-vpls
Context
config>service>vpls>pbb
Platforms
7210 SAS-T (network operating mode)
Description
This command configures B-VPLS service associated with the I-VPLS.
Parameters
- service-id
Specifies the service ID.
- isid
Specifies the ISID.
PBB show commands
eth-cfm
Syntax
eth-cfm
Context
show
Platforms
7210 SAS-T (network operating mode)
Description
This command displays 802.1ag CFM information.
association
Syntax
association [ma-index] [detail]
Context
show>eth-cfm
Platforms
7210 SAS-T (network operating mode)
Description
This command displays association information.
Parameters
- ma-index
Specifies the MA index value.
- detail
Displays all association detail.
Output
The following output is an example of Ethernet CFM associations information, and Output fields: ETH-CFM associations describes the output fields.
Sample output*A:alcag1-R6# show eth-cfm association
======================================================================
CFM Association Table
======================================================================
Md-index Ma-index Name CCM-interval Bridge-id
----------------------------------------------------------------------
1 1 ivpls 1 5000
======================================================================
*A:alcag1-R6#
|
Label |
Description |
|---|---|
|
Md-index |
Displays the MD index |
|
Ma-index |
Displays the MA index |
|
Name |
Displays the name of the MA |
|
CCM-interval |
Displays the CCM interval (in seconds) |
|
Bridge-id |
Displays the bridge ID for the MA. The bridge ID is the same value as the service ID of the service to which the MEP belongs. |
cfm-stack-table
Syntax
cfm-stack-table
cfm-stack-table port [port-id> [vlan qtag[.qtag]] [level 0..7] [direction up | down]
cfm-stack-table sdp [sdp-id[:vc-id]>] [level 0..7]] [direction up | down]
cfm-stack-table virtual [service-id] [level 0..7]
Context
show>eth-cfm
Platforms
7210 SAS-T (network operating mode)
Description
This command summarizes all MEPs or MIPs.
Parameters
- port-id
Displays information about the specified port.
- sdp-id[:vc-id]
Specfies an existing SDP and VC ID.
- qtag
Specifies the qtag value.
- level
Specifies the level.
- direction up | down
Indicates the direction in which the maintenance association (MEP or MIP) faces on the bridge port.
down — Displays continuity check information configured away from the MAC relay entity.
up — Displays continuity check information configured toward the MAC relay entity.
- service-id
Specifies information about the specified service ID.
Output
The following output is an example of Ethernet CFM stack-table information, and Output fields: ETH-CFM stack table describes the output fields.
Sample output*A:alcag1-R6# show eth-cfm cfm-stack-table
========================================================================
CFM SAP Stack Table
========================================================================
Sap Level Dir Md-index Ma-index Mep-id Mac-address
------------------------------------------------------------------------
1/2/9:5 4 Up 1 1 51 00:ae:ae:ae:ae:ae
========================================================================
CFM SDP Stack Table
========================================================================
Sdp Level Dir Md-index Ma-index Mep-id Mac-address
------------------------------------------------------------------------
No Matching Entries
========================================================================
*A:alcag1-R6#
|
Label |
Description |
|---|---|
|
Sap |
Displays the SAP identifier. |
|
Sdp |
Displays the spoke SDP identifier. |
|
Level |
Displays the MD level of the domain. |
|
Dir (direction) |
Displays the direction of OAMPDU transmission. |
|
Md-index |
Displays the MD index of the domain. |
|
Ma-index |
Displays the MA index of the domain. |
|
Mep-id |
Displays the MEP identifier. |
|
Mac-address |
Displays the MAC address of the MEP. |
domain
Syntax
domain [md-index] [association ma-index | all-associations [detail]]
Context
show>eth-cfm>domain
Platforms
7210 SAS-T (network operating mode)
Description
This command displays domain information.
Parameters
- md-index
Specifies the maintenance domain (MD) index value.
- ma-index
Specifies the MA index value.
- all-associations
Displays information all maintenance associations.
- detail
Displays detailed information.
Output
The following output is an example of Ethernet CFM domain information, and ETH-CFM domain field descriptions describes the output fields.
Sample output*A:alcag1-R6# show eth-cfm domain
==============================================================================
CFM Domain Table
==============================================================================
Md-index Level Name Format
------------------------------------------------------------------------------
1 4 ivpls charString
==============================================================================
*A:alcag1-R6#
*A:alcag1-R6# show eth-cfm mep 51 domain 1 association 1
-------------------------------------------------------------------------------
Mep Information
-------------------------------------------------------------------------------
Md-index : 1 Direction : Up
Ma-index : 1 Admin : Enabled
MepId : 51 CCM-Enable : Enabled
IfIndex : 38043648 PrimaryVid : 5
FngState : fngReset
LowestDefectPri : allDef HighestDefect : none
Defect Flags : None
Mac Address : 00:ae:ae:ae:ae:ae CcmLtmPriority : 7
CcmTx : 775 CcmSequenceErr : 0
CcmLastFailure Frame:
None
XconCcmFailure Frame:
None
*A:alcag1-R6#
|
Label |
Description |
|---|---|
|
Domain |
|
|
Md-index |
Displays the MD index of the domain |
|
Level |
Displays the MD level of the domain |
|
Name |
Displays the name of the MD |
|
Format |
Displays the format for the MD name |
|
Domain Associations |
|
|
Md-index |
Displays the MD index of the domain |
|
Direction |
Displays the direction of OAMPDU transmission |
|
Ma-index |
Displays the MA index of the association |
|
Admin |
Displays the administrative status of the MEP |
|
MepId |
Displays the MEP identifier |
|
CCM-Enable |
Displays the status of the CCM (enabled or disabled) |
|
IfIndex |
Displays the index of the interface |
|
PrimaryVid |
Displays the identifier of the primary VLAN |
|
FngState |
Indicates the different states of the Fault Notification Generator |
|
LowestDefectPri |
Displays the lowest priority defect (a configured value) that is allowed to generate a fault alarm |
|
HighestDefect |
Identifies the highest defect that is present (for example, if defRDICCM and defXconCCM are present, the highest defect is defXconCCM) |
|
Defect Flags |
Displays the number of defect flags |
|
Mac Address |
Displays the MAC address of the MEP |
|
CcmLtmPriority |
Displays the priority value transmitted in the linktrace messages (LTM)s and CCMs for this MEP. The MEP must be configured on a VLAN. |
|
CcmTx |
Displays the number of Continuity Check Messages (CCM) sent. The count is taken from the last polling interval (every 10 s). |
|
CcmSequenceErr |
Displays the number of CCM errors |
|
CcmLastFailure Frame |
Displays the frame that caused the last CCM failure |
|
XconCcmFailure Frame |
Displays the frame that caused the XconCCMFailure |
mep
Syntax
mep mep-id domain md-index association ma-index [loopback] [linktrace]
Context
show>eth-cfm>domain
Platforms
7210 SAS-T (network operating mode)
Description
This command displays Maintenance Endpoint (MEP) information.
Parameters
- mep-id
Specifies the maintenance association end point identifier.
- md-index
Specifies the maintenance domain (MD) index value.
- ma-index
Specifies the MA index value.
- loopback
Displays loopback information for the specified MEP.
- linktrace
Displays linktrace information for specified MEP.
Output
The following output is an example of MEP information, and Output fields: MEP describes the output fields.
Sample output*A:alcag1-R6# oam eth-cfm loopback 00:af:af:af:af:af mep 51 domain 1 association 1
eth-cfm Loopback Test Initiated: Mac-Address: 00:af:af:af:af:af, out sap: 1/2/9:5
Sent 1 packets, received 1 packets [0 out-of-order, 0 Bad Msdu] -- OK
*A:alcag1-R6#
*A:alcag1-R6# oam eth-cfm linktrace 00:af:af:af:af:af mep 51 domain 1 association 1
Index Ingress Mac Egress Mac Relay Action
----- -------------------- -------------------- ---------- ----------
1 00:00:00:00:00:00 00:AF:AF:AF:AF:AF rlyHit terminate
----- -------------------- -------------------- ---------- ----------
No more responses received in the last 5 seconds.
*A:alcag1-R6#
|
Label |
Description |
|---|---|
|
Index |
Displays the index of the domain |
|
Relay |
Displays the value returned in the Relay Action field |
|
IngressMac |
Displays the MAC address returned in the ingress MAC address field |
|
Action |
Displays the value returned in the Action field of the linktrace message |
|
EgressMac |
Displays the MAC address returned in the egress MAC address field |
mip
Syntax
mip
Context
show>eth-cfm>mip
Platforms
7210 SAS-T (network operating mode)
Description
This command displays Maintenance Intermediate Point (MIP) information.
Output
The following output is an example of Ethernet CFM MIP information, and Output fields: MIP describes the output fields.
Sample output*A:7210SAS# show eth-cfm mip
==========================================================================
CFM SAP MIP Table
==========================================================================
Sap Mip-Enabled Mip Mac Address
--------------------------------------------------------------------------
1/1/16 yes 00:a1:b1:c1:d1:e1
==========================================================================
==========================================================================
CFM SDP MIP Table
==========================================================================
Sdp Mip-Enabled Mip Mac Address
--------------------------------------------------------------------------
456:123 yes 00:a2:b2:c2:d2:e2
==========================================================================
*A:7210SAS#
|
Label |
Description |
|---|---|
|
Mip-Enabled |
Displays the state of the MIP service |
|
Mip Mac Address |
Indicates the Mac Address of the MIP |
id
Syntax
id service-id
Context
show>service
Platforms
7210 SAS-T (network operating mode)
Description
This command displays information about a specific service ID.
Parameters
- service-id
The unique service identification number that identifies the service in the service domain.
- all
Displays detailed information about the service.
- base
Displays basic service information.
- fdb
Displays FDB entries.
- epipe
Displays the Epipe services associated with the B-VPLS service.
- i-vpls
Displays the I-VPLS services associated with this B-VPLS service.
- stp
Display STP information.
all
Syntax
all
Context
show>service>id
Platforms
7210 SAS-T (network operating mode)
Description
This command displays detailed information for all aspects of the service.
Output
The following output is an example of detailed information for all aspects of a service, and Output fields: service ID all describes the output fields.
Sample outputSample output for PBB Epipe:
*A:7210-SAS>show>service# id 1000 all
===============================================================================
Service Detailed Information
===============================================================================
Service Id : 1000 Vpn Id : 0
Service Type : Epipe
Description : (Not Specified)
Customer Id : 1
Last Status Change: 04/04/2001 22:18:48
Last Mgmt Change : 04/04/2001 21:28:34
Admin State : Up Oper State : Up
MTU : n/a
MTU Check : n/a
Vc Switching : False
SAP Count : 1 SDP Bind Count : 0
Uplink Type: : MPLS
-------------------------------------------------------------------------------
Service Destination Points(SDPs)
-------------------------------------------------------------------------------
No Matching Entries
-------------------------------------------------------------------------------
Service Access Points
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
SAP 1/1/15:1000
-------------------------------------------------------------------------------
Service Id : 1000
SAP : 1/1/15:1000 Encap : q-tag
Description : (Not Specified)
Admin State : Up Oper State : Up
Flags : None
Last Status Change : 04/04/2001 21:29:23
Last Mgmt Change : 04/04/2001 21:28:34
Dot1Q Ethertype : 0x8100 QinQ Ethertype : 0x8100
Split Horizon Group: (Not Specified)
Admin MTU : 1518 Oper MTU : 1518
Ingr IP Fltr-Id : n/a Egr IP Fltr-Id : n/a
Ingr Mac Fltr-Id : n/a Egr Mac Fltr-Id : n/a
Ingr IPv6 Fltr-Id : n/a Egr IPv6 Fltr-Id : n/a
tod-suite : None
Endpoint : N/A
Acct. Pol : None Collect Stats : Disabled
-------------------------------------------------------------------------------
QOS
-------------------------------------------------------------------------------
Ingress qos-policy : 1
-------------------------------------------------------------------------------
Aggregate Policer
-------------------------------------------------------------------------------
rate : n/a burst : n/a
-------------------------------------------------------------------------------
Ingress QoS Classifier Usage
-------------------------------------------------------------------------------
Classifiers Allocated: 4 Meters Allocated : 2
Classifiers Used : 1 Meters Used : 1
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
Packets Octets
Ingress Stats: 0 0
Egress Stats: 0 0
Ingress Drop Stats: 0 0
Extra-Tag Drop Stats: n/a n/a
-------------------------------------------------------------------------------
Sap per Meter stats (in/out counter mode)
-------------------------------------------------------------------------------
Packets Octets
Ingress Meter 1 (Unicast)
For. InProf : 0 0
For. OutProf : 0 0
-------------------------------------------------------------------------------
PBB Tunnel Point
-------------------------------------------------------------------------------
B-vpls Backbone-dest-MAC Isid AdmMTU OperState Flood Oper-dest-MAC
-------------------------------------------------------------------------------
2 8c:90:d3:79:b2:65 1000 1514 Up Yes 8c:90:d3:79:b2:65
-------------------------------------------------------------------------------
Last Status Change: 04/04/2001 22:18:48
Last Mgmt Change: 04/04/2001 22:18:48
-------------------------------------------------------------------------------
Service Endpoints
-------------------------------------------------------------------------------
No Endpoints found.
===============================================================================
*A:7210-SAS>show>service#
Sample output for I-VPLS:
*A:7210-SAS>show>service# id 200 all
===============================================================================
Service Detailed Information
===============================================================================
Service Id : 200 Vpn Id : 0
Service Type : i-VPLS
Description : (Not Specified)
Customer Id : 1
Last Status Change: 04/04/2001 22:14:30
Last Mgmt Change : 04/04/2001 22:15:06
Admin State : Up Oper State : Up
MTU : n/a
MTU Check : n/a
SAP Count : 1 SDP Bind Count : 0
Snd Flush on Fail : Disabled
Uplink Type: : MPLS
b-Vpls Id : 2 Oper ISID : 200
b-Vpls Status : Up
-------------------------------------------------------------------------------
Split Horizon Group specifics
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Service Destination Points(SDPs)
-------------------------------------------------------------------------------
No Matching Entries
-------------------------------------------------------------------------------
Service Access Points
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
SAP 1/1/15:200
-------------------------------------------------------------------------------
Service Id : 200
SAP : 1/1/15:200 Encap : q-tag
Description : (Not Specified)
Admin State : Up Oper State : Up
Flags : None
Last Status Change : 04/04/2001 22:14:30
Last Mgmt Change : 04/04/2001 22:14:22
Dot1Q Ethertype : 0x8100 QinQ Ethertype : 0x8100
Split Horizon Group: (Not Specified)
Max Nbr of MAC Addr: No Limit Total MAC Addr : 0
Learned MAC Addr : 0 Static MAC Addr : 0
Admin MTU : 1518 Oper MTU : 1518
Ingr IP Fltr-Id : n/a Egr IP Fltr-Id : n/a
Ingr Mac Fltr-Id : n/a Egr Mac Fltr-Id : n/a
Ingr IPv6 Fltr-Id : n/a Egr IPv6 Fltr-Id : n/a
tod-suite : None
Mac Learning : Enabled Discard Unkwn Srce: Disabled
Mac Aging : Enabled Mac Pinning : Disabled
BPDU Translation : Disabled
L2PT Termination : Disabled
Acct. Pol : None Collect Stats : Disabled
-------------------------------------------------------------------------------
Stp Service Access Point specifics
-------------------------------------------------------------------------------
Stp Admin State : Up Stp Oper State : Down
Core Connectivity : Down
Port Role : N/A Port State : Forwarding
Port Number : 2049 Port Priority : 128
Port Path Cost : 10 Auto Edge : Enabled
Admin Edge : Disabled Oper Edge : N/A
Link Type : Pt-pt BPDU Encap : Dot1d
Root Guard : Disabled Active Protocol : N/A
Last BPDU from : N/A
CIST Desig Bridge : N/A Designated Port : N/A
Forward transitions: 0 Bad BPDUs rcvd : 0
Cfg BPDUs rcvd : 0 Cfg BPDUs tx : 0
TCN BPDUs rcvd : 0 TCN BPDUs tx : 0
TC bit BPDUs rcvd : 0 TC bit BPDUs tx : 0
RST BPDUs rcvd : 0 RST BPDUs tx : 0
MST BPDUs rcvd : 0 MST BPDUs tx : 0
-------------------------------------------------------------------------------
ARP host
-------------------------------------------------------------------------------
Admin State : outOfService
Host Limit : 1 Min Auth Interval : 15 minutes
-------------------------------------------------------------------------------
QOS
-------------------------------------------------------------------------------
Ingress qos-policy : 1
-------------------------------------------------------------------------------
Aggregate Policer
-------------------------------------------------------------------------------
rate : n/a burst : n/a
-------------------------------------------------------------------------------
Ingress QoS Classifier Usage
-------------------------------------------------------------------------------
Classifiers Allocated: 4 Meters Allocated : 2
Classifiers Used : 2 Meters Used : 2
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
Packets Octets
Ingress Stats: 0 0
Egress Stats: 0 0
Ingress Drop Stats: 0 0
Extra-Tag Drop Stats: n/a n/a
-------------------------------------------------------------------------------
Sap per Meter stats (in/out counter mode)
-------------------------------------------------------------------------------
Packets Octets
Ingress Meter 1 (Unicast)
For. InProf : 0 0
For. OutProf : 0 0
Ingress Meter 11 (Multipoint)
For. InProf : 0 0
For. OutProf : 0 0
-------------------------------------------------------------------------------
VPLS Spanning Tree Information
-------------------------------------------------------------------------------
VPLS oper state : Up Core Connectivity : Down
Stp Admin State : Down Stp Oper State : Down
Mode : Rstp Vcp Active Prot. : N/A
Bridge Id : 80:00.00:25:ba:08:f6:20 Bridge Instance Id: 0
Bridge Priority : 32768 Tx Hold Count : 6
Topology Change : Inactive Bridge Hello Time : 2
Last Top. Change : 0d 00:00:00 Bridge Max Age : 20
Top. Change Count : 0 Bridge Fwd Delay : 15
Root Bridge : N/A
Primary Bridge : N/A
Root Path Cost : 0 Root Forward Delay: 0
Rcvd Hello Time : 0 Root Max Age : 0
Root Priority : 0 Root Port : N/A
-------------------------------------------------------------------------------
Forwarding Database specifics
-------------------------------------------------------------------------------
Service Id : 200 Mac Move : Disabled
Mac Move Rate : 2 Mac Move Timeout : 10
Mac Move Retries : 3
Table Size : 250 Total Count : 0
Learned Count : 0 Static Count : 0
Remote Age : 900 Local Age : 300
High Watermark : 95% Low Watermark : 90%
Mac Learning : Enabled Discard Unknown : Disabled
Mac Aging : Enabled Relearn Only : False
===============================================================================
Sample output for B-VPLS service:
*A:7210-SAS>show>service# id 2 all
===============================================================================
Service Detailed Information
===============================================================================
Service Id : 2 Vpn Id : 0
Service Type : b-VPLS
Description : (Not Specified)
Customer Id : 1
Last Status Change: 04/04/2001 22:13:57
Last Mgmt Change : 04/04/2001 22:13:57
Admin State : Up Oper State : Up
MTU : n/a
MTU Check : n/a
SAP Count : 1 SDP Bind Count : 0
Snd Flush on Fail : Disabled
Uplink Type: : MPLS
Oper Backbone Src : 00:25:ba:08:f6:20
i-Vpls Count : 1
Epipe Count : 1
-------------------------------------------------------------------------------
Split Horizon Group specifics
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Service Destination Points(SDPs)
-------------------------------------------------------------------------------
No Matching Entries
-------------------------------------------------------------------------------
Service Access Points
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
SAP 1/1/2:2
-------------------------------------------------------------------------------
Service Id : 2
SAP : 1/1/2:2 Encap : q-tag
Description : (Not Specified)
Admin State : Up Oper State : Up
Flags : None
Last Status Change : 04/04/2001 22:13:57
Last Mgmt Change : 04/04/2001 22:13:54
Dot1Q Ethertype : 0x8100 QinQ Ethertype : 0x8100
PBB Ethertype : 0x88e7
Split Horizon Group: (Not Specified)
Max Nbr of MAC Addr: No Limit Total MAC Addr : 0
Learned MAC Addr : 0 Static MAC Addr : 0
Admin MTU : 1518 Oper MTU : 1518
Ingr Mac Fltr-Id : n/a Egr Mac Fltr-Id : n/a
tod-suite : None
Mac Learning : Enabled Discard Unkwn Srce: Disabled
Mac Aging : Enabled Mac Pinning : Disabled
BPDU Translation : Disabled
L2PT Termination : Disabled
Acct. Pol : None Collect Stats : Disabled
-------------------------------------------------------------------------------
Stp Service Access Point specifics
-------------------------------------------------------------------------------
Stp Admin State : Up Stp Oper State : Down
Core Connectivity : Down
Port Role : N/A Port State : Forwarding
Port Number : 2048 Port Priority : 128
Port Path Cost : 10 Auto Edge : Enabled
Admin Edge : Disabled Oper Edge : N/A
Link Type : Pt-pt BPDU Encap : Dot1d
Root Guard : Disabled Active Protocol : N/A
Last BPDU from : N/A
CIST Desig Bridge : N/A Designated Port : N/A
Forward transitions: 0 Bad BPDUs rcvd : 0
Cfg BPDUs rcvd : 0 Cfg BPDUs tx : 0
TCN BPDUs rcvd : 0 TCN BPDUs tx : 0
TC bit BPDUs rcvd : 0 TC bit BPDUs tx : 0
RST BPDUs rcvd : 0 RST BPDUs tx : 0
MST BPDUs rcvd : 0 MST BPDUs tx : 0
-------------------------------------------------------------------------------
ARP host
-------------------------------------------------------------------------------
Admin State : outOfService
Host Limit : 1 Min Auth Interval : 15 minutes
-------------------------------------------------------------------------------
QOS
-------------------------------------------------------------------------------
Ingress qos-policy : 1
-------------------------------------------------------------------------------
Aggregate Policer
-------------------------------------------------------------------------------
rate : n/a burst : n/a
-------------------------------------------------------------------------------
Ingress QoS Classifier Usage
-------------------------------------------------------------------------------
Classifiers Allocated: 4 Meters Allocated : 2
Classifiers Used : 2 Meters Used : 2
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
Packets Octets
Ingress Stats: 0 0
Egress Stats: 0 0
Ingress Drop Stats: 0 0
Extra-Tag Drop Stats: n/a n/a
-------------------------------------------------------------------------------
Sap per Meter stats (in/out counter mode)
-------------------------------------------------------------------------------
Packets Octets
Ingress Meter 1 (Unicast)
For. InProf : 0 0
For. OutProf : 0 0
Ingress Meter 11 (Multipoint)
For. InProf : 0 0
For. OutProf : 0 0
-------------------------------------------------------------------------------
VPLS Spanning Tree Information
-------------------------------------------------------------------------------
VPLS oper state : Up Core Connectivity : Down
Stp Admin State : Down Stp Oper State : Down
Mode : Rstp Vcp Active Prot. : N/A
Bridge Id : 80:00.00:25:ba:08:f6:20 Bridge Instance Id: 0
Bridge Priority : 32768 Tx Hold Count : 6
Topology Change : Inactive Bridge Hello Time : 2
Last Top. Change : 0d 00:00:00 Bridge Max Age : 20
Top. Change Count : 0 Bridge Fwd Delay : 15
Root Bridge : N/A
Primary Bridge : N/A
Root Path Cost : 0 Root Forward Delay: 0
Rcvd Hello Time : 0 Root Max Age : 0
Root Priority : 0 Root Port : N/A
-------------------------------------------------------------------------------
Forwarding Database specifics
-------------------------------------------------------------------------------
Service Id : 2 Mac Move : Disabled
Mac Move Rate : 2 Mac Move Timeout : 10
Mac Move Retries : 3
Table Size : 250 Total Count : 0
Learned Count : 0 Static Count : 0
Remote Age : 900 Local Age : 300
High Watermark : 95% Low Watermark : 90%
Mac Learning : Enabled Discard Unknown : Disabled
Mac Aging : Enabled Relearn Only : False
-------------------------------------------------------------------------------
Related i-Vpls services for b-Vpls service 2
-------------------------------------------------------------------------------
i-Vpls SvcId Oper ISID Admin Oper
-------------------------------------------------------------------------------
200 200 Up Up
-------------------------------------------------------------------------------
Number of Entries : 1
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Related Epipe services for b-Vpls service 2
-------------------------------------------------------------------------------
Epipe SvcId Oper ISID Admin Oper
-------------------------------------------------------------------------------
1000 1000 Up Up
-------------------------------------------------------------------------------
Number of Entries : 1
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Service Endpoints
-------------------------------------------------------------------------------
No Endpoints found.
===============================================================================
*A:7210-SAS>show>service#
|
Label |
Description |
|---|---|
|
|
The service identifier. |
|
|
Specifies the type of service. |
|
|
Generic information about the service. |
|
|
The customer identifier. |
|
|
The date and time of the most recent status change to this customer. |
|
|
The date and time of the most recent management-initiated change to this customer. |
|
|
The administrative state of the service. |
|
|
Displays the status of VC switching. |
|
|
The number of SAPs specified for this service. |
|
|
Displays the mode of the device. |
|
|
The number which identifies the VPN. |
|
|
The operational state of the service. |
|
|
Displays the SAP ID. |
|
|
The value of the label used to identify this SAP on the access port. |
|
|
Displays the configured QinQ Ethertype value. |
|
|
Displays the configured Dot1Q Ethertype value. |
|
|
Displays the split horizon group information. |
|
|
The desired largest service frame size (in octets) that can be transmitted through the port to the far-end router, without requiring the packet to be fragmented. |
|
|
The actual largest service frame size (in octets) that can be transmitted through the port to the far-end router, without requiring the packet to be fragmented. |
|
|
Ingress IP filter ID. |
|
|
Egress IP filter ID. |
|
|
Ingress MAC filter ID. |
|
|
Egress MAC filter ID. |
|
|
Ingress IPv6 filter ID. |
|
|
Egress IPv6 filter ID. |
|
|
Displays the endpoint name. |
|
|
Indicates the accounting policy applied to the SAP. |
|
|
Specifies whether accounting statistics are collected on the SAP. |
|
QoS parameters |
|
|
|
The SAP ingress QoS policy ID. |
|
|
Displays the number of classifiers allocated. |
|
|
Displays the number of classifiers used. |
|
|
Displays the number of meters allocated. |
|
|
Displays the number of meters used. |
|
|
The number of received packets/octets for this SAP. |
|
|
The number of packets/octets forwarded out of this SAP. |
|
PBB Tunnel Point parameters |
|
|
|
Displays the B-VPLS ID. |
|
|
Displays the back bone destination MAC address. |
|
|
Displays the ISID number. |
|
|
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 theB-VPLS FDB, it is unicast. |
|
|
Displays the operational destination MAC address. |
|
|
Displays the count of I-VPLS bound to B-VPLS. |
|
|
Displays the operational state of the B-VPLS service. |
|
|
Displays the count of Epipe bound to B-VPLS. |
base
Syntax
base
Context
show>service>id
Platforms
7210 SAS-T (network operating mode)
Description
This command displays basic information about the service including service type, description and SAPs.
Output
The following output is an example of basic service information, and Output fields: base describes the output fields.
Sample outputSample output for PBB Epipe service:
*A:7210-SAS>show>service# id 1000 base
===============================================================================
Service Basic Information
===============================================================================
Service Id : 1000 Vpn Id : 0
Service Type : Epipe
Description : (Not Specified)
Customer Id : 1
Last Status Change: 04/04/2001 22:18:48
Last Mgmt Change : 04/04/2001 21:28:34
Admin State : Up Oper State : Up
MTU : n/a
MTU Check : n/a
Vc Switching : False
SAP Count : 1 SDP Bind Count : 0
Uplink Type: : MPLS
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/15:1000 q-tag 1518 1518 Up Up
-------------------------------------------------------------------------------
PBB Tunnel Point
-------------------------------------------------------------------------------
B-vpls Backbone-dest-MAC Isid AdmMTU OperState Flood Oper-dest-MAC
-------------------------------------------------------------------------------
2 8c:90:d3:79:b2:65 1000 1514 Up Yes 8c:90:d3:79:b2:65
-------------------------------------------------------------------------------
Last Status Change: 04/04/2001 22:18:48
Last Mgmt Change: 04/04/2001 22:18:48
===============================================================================
*A:7210-SAS>show>service#
Sample output for I-VPLS service:
*A:7210-SAS>show>service# id 200 base
===============================================================================
Service Basic Information
===============================================================================
Service Id : 200 Vpn Id : 0
Service Type : i-VPLS
Description : (Not Specified)
Customer Id : 1
Last Status Change: 04/04/2001 22:14:30
Last Mgmt Change : 04/04/2001 22:15:06
Admin State : Up Oper State : Up
MTU : n/a
MTU Check : n/a
SAP Count : 1 SDP Bind Count : 0
Snd Flush on Fail : Disabled
Uplink Type: : MPLS
b-Vpls Id : 2 Oper ISID : 200
b-Vpls Status : Up
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/15:200 q-tag 1518 1518 Up Up
===============================================================================
*A:7210-SAS>show>service#
Sample output for B-VPLS service:
*A:7210-SAS>show>service# id 2 base
===============================================================================
Service Basic Information
===============================================================================
Service Id : 2 Vpn Id : 0
Service Type : b-VPLS
Description : (Not Specified)
Customer Id : 1
Last Status Change: 04/04/2001 22:13:57
Last Mgmt Change : 04/04/2001 22:13:57
Admin State : Up Oper State : Up
MTU : n/a
MTU Check : n/a
SAP Count : 1 SDP Bind Count : 0
Snd Flush on Fail : Disabled
Uplink Type: : MPLS
Oper Backbone Src : 00:25:ba:08:f6:20
i-Vpls Count : 1
Epipe Count : 1
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:2 q-tag 1518 1518 Up Up
===============================================================================
*A:7210-SAS>show>service#
|
Label |
Description |
|---|---|
|
Service Id |
The service identifier. |
|
Service Type |
Specifies the type of service. |
|
Description |
Generic information about the service. |
|
Customer Id |
The customer identifier. |
|
Last Status Change |
The date and time of the most recent status change to this customer. |
|
Last Mgmt Change |
The date and time of the most recent management-initiated change to this customer. |
|
Admin State |
The administrative state of the service. |
|
Vc Switching |
Displays the status of VC switching. |
|
SAP Count |
The number of SAPs specified for this service. |
|
Uplink Type |
Displays the mode of the device. |
|
Vpn Id |
The number which identifies the VPN. |
|
Oper State |
The operational state of the service. |
|
SAP |
Displays the SAP ID. |
|
Encap |
The value of the label used to identify this SAP on the access port. |
|
Vpn Id |
The number which identifies the VPN. |
|
Oper State |
The operational state of the service. |
|
SAP |
Displays the SAP ID. |
|
PBB Tunnel Point |
|
|
B-vpls |
Displays the B-VPLS ID. |
|
Backbone-dest-MAC |
Displays the back bone destination MAC address. |
|
Isid |
Displays the ISID number. |
|
Flood |
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 theB-VPLS FDB, it is unicast. |
|
b-Vpls Status |
Displays the operational state of the B-VPLS service. |
|
b-Vpls Id |
Displays the B-VPLS ID. |
fdb
Syntax
fdb {info | mac ieee-address | sap sap-id | detail | endpoint endpoint}
[expiry] [pbb]
Context
show>service>id
Platforms
7210 SAS-T (network operating mode)
Description
This command displays FDB entries for a specific MAC address.
Parameters
- sap sap-id
Specifies the physical port identifier portion of the SAP.
- detail
Displays detailed information.
- expiry
Displays time until MAC is aged out.
- endpoint
Displays endpoint information.
- pbb
Displays PBB information.
Output
The following output is an example of FDB entry information, and Output fields: FDB describes the output fields.
Sample output*A:7210-SAS>show>service# id 200 fdb
===============================================================================
Forwarding Database, Service 200
===============================================================================
Service Id : 200 Mac Move : Disabled
Mac Move Rate : 2 Mac Move Timeout : 10
Mac Move Retries : 3
Table Size : 250 Total Count : 0
Learned Count : 0 Static Count : 0
Remote Age : 900 Local Age : 300
High Watermark : 95% Low Watermark : 90%
Mac Learning : Enabled Discard Unknown : Disabled
Mac Aging : Enabled Relearn Only : False
===============================================================================
*A:7210-SAS>show>service#
*A:7210-SAS>show>service# id 2 fdb
===============================================================================
Forwarding Database, Service 2
===============================================================================
Service Id : 2 Mac Move : Disabled
Mac Move Rate : 2 Mac Move Timeout : 10
Mac Move Retries : 3
Table Size : 250 Total Count : 0
Learned Count : 0 Static Count : 0
Remote Age : 900 Local Age : 300
High Watermark : 95% Low Watermark : 90%
Mac Learning : Enabled Discard Unknown : Disabled
Mac Aging : Enabled Relearn Only : False
===============================================================================
*A:7210-SAS>show>service#
|
Label |
Description |
|---|---|
|
Service Id |
Displays the service ID. |
|
Mac Move Rate |
Displays the maximum rate at which MAC's can be relearned in this service, before the SAP where the moving MAC was last seen is automatically disabled to protect the system against undetected loops or duplicate MAs. The rate is computed as the maximum number of relearns allowed in a 5 second interval: for example, the default rate of 2 relearns per second corresponds to 10 relearns in a 5 second period. |
|
Mac Move Retries |
Displays the number of times retries are performed for reenabling the SAP. |
|
Table Size |
Specifies the maximum number of learned and static entries allowed in the FDB of this service. |
|
Learned Count |
Displays the current number of learned entries in the FDB of this service. |
|
Remote Age |
Displays the number of seconds used to age out FDB entries learned on an SAP. These entries correspond to MAC addresses learned on remote SAPs. |
|
High Watermark |
Displays the utilization of the FDB table of this service at which a table full alarm is raised by the agent. |
|
Mac Learning |
Specifies whether the MAC learning process is enabled |
|
Mac Aging |
Indicates whether the MAC aging process is enabled. |
|
Mac Move |
Displays the administrative state of the MAC movement feature associated with this service. |
|
Mac Move Timeout |
Displays the time in seconds to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled. A value of zero indicates that the SAP is automatically re-enabled after being disabled. If after the SAP is re-enabled it is disabled again, the effective retry timeout is doubled to avoid thrashing. |
|
Total Count |
Displays the total number of learned entries in the FDB of this service. |
|
Static Count |
Displays the current number of static entries in the FDB of this service. |
|
Local Age |
Displays the number of seconds used to age out FDB entries learned on local SAPs. |
|
Low Watermark |
Displays the utilization of the FDB table of this service at which a table full alarm is cleared by the agent. |
|
Discard Unknown |
Specifies whether frames received with an unknown destination MAC are discarded. |
|
Relearn Only |
Displays, that when enabled, either the FDB table of this service is full, or that the maximum system-wide number of MAC's supported by the agent has been reached, and therefore MAC learning is temporary disabled, and only MAC relearns can take place. |
stp
Syntax
stp [detail]
Context
show>service>id
Platforms
7210 SAS-T (network operating mode)
Description
This command displays information for the spanning tree protocol (STP) instance for the service.
Parameters
- detail
Displays detailed information.
Output
The following output is an example of service STP information, and Output fields: STP describes the output fields.
Sample output*A:7210-SAS>show>service# id 200 stp
===============================================================================
Stp info, Service 200
===============================================================================
Bridge Id : 80:00.00:25:ba:08:f6:20 Top. Change Count : 0
Root Bridge : N/A Stp Oper State : Down
Primary Bridge : N/A Topology Change : Inactive
Mode : Rstp Last Top. Change : 0d 00:00:00
Vcp Active Prot. : N/A
Root Port : N/A External RPC : 0
===============================================================================
Stp port info
===============================================================================
Sap/Sdp Id Oper- Port- Port- Port- Oper- Link- Active
State Role State Num Edge Type Prot.
-------------------------------------------------------------------------------
Backbone VPLS Up N/A Forward 2048 N/A N/A N/A
1/1/15:200 Up N/A Forward 2049 N/A Pt-pt N/A
===============================================================================
*A:7210-SAS>show>service#
|
Label |
Description |
|---|---|
|
Bridge Id |
Specifies the MAC address used to identify this bridge in the network. |
|
Top. Change Count |
Specifies the total number of topology changes detected by the Spanning Tree Protocol instance associated with this service since the management Entity was last reset or initialized. |
|
Root Bridge |
Specifies the bridge identifier of the root of the spanning tree as determined by the Spanning Tree Protocol instance associated with this service. This value is used as the Root Identifier parameter in all Configuration BPDUs originated by this node. |
|
Stp Oper State |
Displays the operational state of the STP |
|
Primary Bridge |
Specifies the bridge identifier of the root of the spanning tree as determined by the Spanning Tree Protocol instance associated with this service. This value is used as the Root Identifier parameter in all Configuration BPDUs originated by this node. |
|
Topology Change |
Specifies whether a topology change is currently in progress. |
|
Mode |
Displays the mode of the STP |
|
Last Top. Change |
Specifies the time (in hundredths of a second) since the last time a topology change was detected by the Spanning Tree Protocol instance associated with this service. |
|
Root Port |
Specifies the port number of the port which provides the lowest cost path from this bridge to the root bridge. |
|
Backbone VPLS |
Displays the ID of the B-VPLS |
isid-using
Syntax
isid-using [ISID]
Context
show>service
Platforms
7210 SAS-T (network operating mode)
Description
This command displays information about services using ISID.
Parameters
- ISID
Displays the service using the specified I-component Service ID (ISID).
Output
The following output is an example of information about services using ISID, and Output fields: ISID-using describes the output fields.
Sample output*A:7210-SAS>show>service# isid-using
===================================================================
Services
===================================================================
SvcId ISID Type b-Vpls Adm Opr SvcMtu CustId
-------------------------------------------------------------------
100 100 i-VPLS 1 Up Up 1514 1
200 200 i-VPLS 2 Up Up 1514 1
1000 1000 Epipe 2 Up Up 1514 1
3000 3000 Epipe 1 Up Up 1514 1
-------------------------------------------------------------------
Matching Services : 4
-------------------------------------------------------------------
===================================================================
*A:7210-SAS>show>service#
|
Label |
Description |
|---|---|
|
SvcId |
The service identifier. |
|
ISID |
Displays the ISID number. |
|
Type |
Indicates the type of service. |
|
b-Vpls |
Displays the B-VPLS ID. |
|
Adm |
Specifies the operating status of the service. |
|
Opr |
The current status of the service. |
|
SvcMtu |
Indicates the service MTU value. |
|
CustId |
Displays the customer ID. |
i-vpls
Syntax
i-vpls
Context
show>service>id
Platforms
7210 SAS-T (network operating mode)
Description
This command displays I-VPLS services associated with the B-VPLS service. This command only applies when the service is a B-VPLS.
Output
The following output is an example of I-VPLS information, and Output fields: I-VPLS describes the output fields.
Sample output*A:7210-SAS>show>service# id 2 i-vpls
===============================================================================
Related i-Vpls services for b-Vpls service 2
===============================================================================
i-Vpls SvcId Oper ISID Admin Oper
-------------------------------------------------------------------------------
200 200 Up Up
-------------------------------------------------------------------------------
Number of Entries : 1
-------------------------------------------------------------------------------
===============================================================================
*A:7210-SAS>show>service#
|
Label |
Description |
|---|---|
|
i-Vpls SvcId |
Displays the service ID of the I-VPLS service. |
|
Oper ISID |
Displays the ISID number. |
|
Admin |
Specifies the operating status of the service. |
|
Oper |
The current status of the service. |
epipe
Syntax
epipe
Context
show>service>id
Platforms
7210 SAS-T (network operating mode)
Description
This command displays Epipe information for the PBB service.
Output
The following output is an example of Epipe information for a PBB service, and Output fields: service ID Epipe describes the output fields.
Sample output*A:7210-SAS>show>service# id 2 epipe
===============================================================================
Related Epipe services for b-Vpls service 2
===============================================================================
Epipe SvcId Oper ISID Admin Oper
-------------------------------------------------------------------------------
1000 1000 Up Up
-------------------------------------------------------------------------------
Number of Entries : 1
-------------------------------------------------------------------------------
===============================================================================
*A:7210-SAS>show>service# id 200 epipe
|
Label |
Description |
|---|---|
|
Epipe SvcId |
Displays the service ID of the Epipe service bound to the B-VPLS service. |
|
Oper ISID |
Displays the ISID number. |
|
Admin |
Specifies the operating status of the service. |
|
Oper |
The current status of the service. |
isid-using
Syntax
isid-using [ISID]
Context
show>service
Platforms
7210 SAS-T (network operating mode)
Description
This command displays the services using ISID.
Parameters
- ISID
Displays the service using the specified I-component Service ID (ISID).
Output
The following output is an example of information about services using ISID, and Output fields: ISID-using describes the output fields.
Sample output*A:7210-SAS>show>service# isid-using
===================================================================
Services
===================================================================
SvcId ISID Type b-Vpls Adm Opr SvcMtu CustId
-------------------------------------------------------------------
100 100 i-VPLS 1 Up Up 1514 1
200 200 i-VPLS 2 Up Up 1514 1
1000 1000 Epipe 2 Up Up 1514 1
3000 3000 Epipe 1 Up Up 1514 1
-------------------------------------------------------------------
Matching Services : 4
-------------------------------------------------------------------
===================================================================
*A:7210-SAS>show>service#
|
Label |
Description |
|---|---|
|
SvcId |
The service identifier. |
|
ISID |
Displays the ISID number. |
|
Type |
Indicates the type of service. |
|
b-Vpls |
Displays the B-VPLS ID. |
|
Admin |
Specifies the operating status of the service. |
|
Oper |
The current status of the service. |
|
SvcMtu |
Indicates the service MTU value. |
|
Customer Id |
Displays the customer ID. |
service-using
Syntax
service-using [b-vpls] [i-vpls]
Context
show>service
Platforms
7210 SAS-T (network operating mode)
Description
This command displays the services matching certain usage properties. If no optional parameters are specified, all services defined on the system are displayed.
Parameters
- b-vpls
Displays matching Epipe services.
- i-vpls
Displays matching VPLS instances.
Output
The following output is an example of service information, and Output fields: Service-using describes the output fields.
Sample output*A:7210-SAS>show>service# service-using b-vpls
===============================================================================
Services [bvpls]
===============================================================================
ServiceId Type Adm Opr CustomerId Last Mgmt Change
-------------------------------------------------------------------------------
1 b-VPLS Up Up 1 04/04/2001 23:22:12
2 b-VPLS Up Up 1 04/04/2001 22:13:57
-------------------------------------------------------------------------------
Matching Services : 2
-------------------------------------------------------------------------------
===============================================================================
*A:7210-SAS>show>service#
|
Label |
Description |
|---|---|
|
Service Id |
The service identifier. |
|
Type |
Indicates the type of service. |
|
Admin |
Specifies the operating status of the service. |
|
Oper |
The current status of the service. |
|
Customer Id |
Displays the customer ID. |
|
Last Mgmt Change |
The date and time of the most recent management-initiated change to this customer. |
mac-name
Syntax
mac-name [detail]
Context
show>service>pbb
Platforms
7210 SAS-T (network operating mode)
Description
This command displays information about a specific MAC name.
Parameters
- detail
Displays detail information.
Output
The following output is an example of information for a specific MAC name, and Output fields: MAC name describes the output fields.
Sample output*A:7210-SAS>show>service# pbb mac-name test detail
=====================================================================
Services Using MAC name='test' addr='00:25:ba:08:f6:23'
=====================================================================
Svc-Id ISID
---------------------------------------------------------------------
No Matching Entries
=====================================================================
*A:7210-SAS>show>service#
|
Label |
Description |
|---|---|
|
Svc-Id |
The service identifier. |
|
ISID |
Displays the ISID number. |
|
Name |
Displays the MAC name. |
|
Addr |
Displays the MAC address |
PBB clear commands
id
Syntax
id service-id
Context
clear>service
clear>service>statistics
Platforms
7210 SAS-T (network operating mode)
Description
This command clears commands for a specific service.
Parameters
- service-id
Specifies the ID that uniquely identifies a service.
statistics
Syntax
statistics
Context
clear>service>stats
Platforms
7210 SAS-T (network operating mode)
Description
This command clears session statistics for this service.
fdb
Syntax
fdb {all | mac ieee-address | sap sap-id] }
Context
clear>service>id
Platforms
7210 SAS-T (network operating mode)
Description
This command clears FDB entries for the service.
Parameters
- all
Clears all FDB entries.
- mac ieee-address
Clears only FDB entries in the FDB table with the specified 48-bit MAC address. The MAC address can be expressed in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers.
- sap-id
Specifies the physical port identifier portion of the SAP definition.
sap
Syntax
sap service-id
Context
clear>service>statistics
Platforms
7210 SAS-T (network operating mode)
Description
This command clears statistics for the SAP bound to the service.
Parameters
- sap-id
See Common CLI command descriptions for the command syntax.
counters
Syntax
counters
Context
clear>service>statistics>id
Platforms
7210 SAS-T (network operating mode)
Description
This command clears all traffic queue counters associated with the service ID.
stp
Syntax
stp
Context
clear>service>statistics>id
Platforms
7210 SAS-T (network operating mode)
Description
Clears all spanning tree statistics for the service ID.
detected-protocols
Syntax
detected-protocols {all | sap sap-id}
Context
clear>service>id>stp
Platforms
7210 SAS-T (network operating mode)
Description
RSTP automatically falls back to STP mode when it receives an STP BPDU. This command forces the system to revert to the default RSTP mode on the SAP.
Parameters
- all
Clears all detected protocol statistics.
- sap-id
Clears the specified lease state SAP information.
PBB debug commands
Id
Syntax
id service-id
Context
debug>service
Platforms
7210 SAS-T (network operating mode)
Description
This command debugs commands for a specific service.
Parameters
- service-id
The ID that uniquely identifies a service.
event-type
Syntax
[no] event-type {config-change | svc-oper-status-change | sap-oper-status-change}
Context
debug>service>id
Platforms
7210 SAS-T (network operating mode)
Description
This command enables a particular debugging event type. The no form of the command disables the event type debugging.
Parameters
- config-change
Debugs configuration change related events.
- svc-oper-status-change
Debugs service operational status changes.
- sap-oper-status-change
Debugs SAP operational status changes.
sap
Syntax
[no] sap sap-id
Context
debug>service>id
Platforms
7210 SAS-T (network operating mode)
Description
This command enables debugging for a particular SAP.
Parameters
- sap-id
Specifies the SAP ID.
stp
Syntax
stp
Context
debug>service>id
Platforms
7210 SAS-T (network operating mode)
Description
This command enables the context for debugging STP.
all-events
Syntax
all-events
Context
debug>service>id>stp
Platforms
7210 SAS-T (network operating mode)
Description
This command enables STP debugging for all events.
bpdu
Syntax
[no] bpdu
Context
debug>service>id>stp
Platforms
7210 SAS-T (network operating mode)
Description
This command enables STP debugging for received and transmitted BPDUs.
core-connectivity
Syntax
[no] core-connectivity
Context
debug>service>id>stp
Platforms
7210 SAS-T (network operating mode)
Description
This command enables STP debugging for core connectivity.
exception
Syntax
[no] exception
Context
debug>service>id>stp
Platforms
7210 SAS-T (network operating mode)
Description
This command enables STP debugging for exceptions.
fsm-state-changes
Syntax
[no] fsm-state-changes
Context
debug>service>id>stp
Platforms
7210 SAS-T (network operating mode)
Description
This command enables STP debugging for FSM state changes.
fsm-timers
Syntax
[no] fsm-timers
Context
debug>service>id>stp
Platforms
7210 SAS-T (network operating mode)
Description
This command enables STP debugging for FSM timer changes.
port-role
Syntax
[no] port-role
Context
debug>service>id>stp
Platforms
7210 SAS-T (network operating mode)
Description
This command enables STP debugging for changes in port roles.
port-state
Syntax
[no] port-state
Context
debug>service>id>stp
Platforms
7210 SAS-T (network operating mode)
Description
This command enables STP debugging for port states.
sap
Syntax
[no] sap sap-id
Context
debug>service>id>stp
Platforms
7210 SAS-T (network operating mode)
Description
This command enables STP debugging for a specific SAP.
Parameters
- sap-id
Specifies the physical port identifier portion of the SAP definition.