2.19. Card, MDA, and Port Command Reference

This command creates a text description for a configuration context to help identify the content in the configuration file.

The no form of this command removes any description string from the context.

Note: The config>port>tdm>e1>channel-group and config>port>tdm>ds1>channel-group contexts are only supported on 7210 SAS-M (network operating mode).

This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.

The operational state of the entity is disabled as well as the operational state of any entities contained within.

The no form of this command administratively enables an entity.

Note: The config>port>tdm>e1>channel-group and config>port>tdm>ds1>channel-group contexts are only supported on 7210 SAS-M (network operating mode).

This mandatory command enables the chassis card Input/Output Module (IOM), slot, and MDA CLI context.

The no form of this command cannot be used on fixed IOM and MDA cards that are auto equipped and auto provisioned.

This command configures the card slot. The card type can be preprovisioned, meaning that the card does not need to be installed in the chassis.

A card must be provisioned before an MDA or port can be configured.

A card can only be provisioned in a slot that is vacant, meaning no other card can be provisioned (configured) for that particular slot.

A card can only be provisioned in a slot if the card type is allowed in the slot. An error message is generated if an attempt is made to provision a card type that is not allowed.

A high severity alarm is raised if an administratively enabled card is removed from the chassis. The alarm is cleared when the correct card type is installed or the configuration is modified. A low severity trap is issued when a card is removed that is administratively disabled.

An appropriate alarm is raised if a partial or complete card failure is detected. The alarm is cleared when the error condition ceases.

Note: This command is not required for 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE (standalone), 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp devices as the cards are preprovisioned.

In a virtual chassis (VC), when the TiMOS image boots up on the CPM-IMM and the IMM-only cards/nodes, users must provision the card type on each member node so that the software knows which hardware platforms are members of the VC. The software can then determine the logical IMM types that are part of the VC. Provisioning the card type is a mandatory step in the bring up of virtual chassis system in order for all the member nodes to be fully functional.

The no form of this command cannot be used as the IOM card is fixed.

This command enables the context to attach the system resource-profile policy. The system resource profile parameters are defined as a policy. The user must configure the system resource profile policy and associate it with the IMM card. The software reads the configured policy and allocates resources appropriately per IMM card. It allows users to allocate resources to different features per IMM card.

Note: On 7210 SAS-R6 and 7210 SAS-R12, some of the system resource profile parameters are applicable to the entire node and not per IMM card.

For more information about the CLI descriptions for System Resource Profile parameters, refer to the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System Configuration Guide.

This command enables the MDA CLI context to configure MDAs.

Note: The mda command is only required to be configured on 7210 SAS-M when using the T1/E1 CES MDA or 2x10GE MDA. All other 7210 SAS platforms auto-provision MDAs and do not require this command to be configured.

This command enables the context to configure a specific MDA type to the device configuration for the slot. The MDA can be preprovisioned but an MDA must be provisioned before ports can be configured. Ports can be configured once the MDA is correctly provisioned.

All 7210 SAS platforms (unless noted otherwise) support a fixed MDA. The fixed MDA (addressed as mda 1) is auto-equipped and auto-provisioned on boot up. It cannot be deleted. An error message is shown in case a no mda-type command is executed on a fixed MDA.

All 7210 SAS-M platform variants supports an expansion slot which can accept supported MDA types. The MDA in the expansion slot is addressed as mda 2. Users must use this command to configure the MDA slot appropriately based on the supported MDA cards they plan to use. To modify an MDA slot, shut down all port associations. An alarm is raised if partial or complete MDA failure is detected. The alarm is cleared when the error condition ceases.

Note: The mda-type command is only required to be configured on 7210 SAS-M when using the T1/E1 CES MDA or 2x10GE MDA. All other 7210 SAS platforms auto-provision MDAs and do not require this command to be configured.

The no form of this command deletes the MDA from the configuration. The MDA must be administratively shut down before it can be deleted from the configuration.

This command enables Synchronous Ethernet on the Ethernet ports that support Synchronous Ethernet. When Synchronous Ethernet is enabled, the timing information is derived from the Ethernet ports.

Synchronous Ethernet is supported for both Ethernet SFP ports and fixed copper ports. It is highly recommended to use copper port only for distribution of synchronous Ethernet and not as a reference.

Refer to the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System Configuration Guide for more information about Synchronous Ethernet.

The no form of this command disables Synchronous Ethernet on the MDA.

This command enables the context to configure egress and ingress pool policy parameters.

This command enables the context to configure egress and ingress pool policy parameters.

This command enables the context to configure access pool parameters.

This command enables the context to specify the slope policy that is configured in the config>qos>slope-policy context.

This command configures Ethernet access ingress port QoS parameters.

This command enables the context to configure the slope policy for the queues associated with this port.

Note: The config>port>access>uplink>pool context is only supported on 7210 SAS platforms operating in the access-uplink mode.

This command specifies an existing slope policy which defines high and low priority RED slope parameters and the time average factor. The policy is defined in the config>qos>slope-policy context.

This command associates a access-egress QoS policy to the access port.

On 7210 SAS-M and 7210 SAS-T in access uplink mode, this policy is used to enable port-based marking and configuring port-based queue parameters. For more information, refer to the 7210 SAS-M, T, Mxp, Sx, S Quality of Service Guide.

On 7210 SAS-M and 7210 SAS-T in network mode, this policy is used to enable port-based marking and configuring port-based queue parameters. For more information, refer to the 7210 SAS-M, T, Mxp, Sx, S Quality of Service Guide.

On 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, when SAP based egress queuing is configured, this policy is to used configure only marking values for packets sent out of access ports. For more information, refer to the 7210 SAS-M, T, Mxp, Sx, S Quality of Service Guide and the 7210 SAS-R6, R12 Quality of Service Guide.

On 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, when port-based queues are used on access ports, this policy is used to configure marking values and to configure the port-based queue parameters. For more information, refer to the 7210 SAS-M, T, Mxp, Sx, S Quality of Service Guide and the 7210 SAS-R6, R12 Quality of Service Guide.

On 7210 SAS-Sx/S 1/10GE(standalone and standalone-VC) and 7210 SAS-Sx 10/100GE, this policy is used to enable port-based marking and configuring port-based queue parameters. For more information, refer to the 7210 SAS-M, T, Mxp, Sx, S Quality of Service Guide.

The no form of this command removes the explicit association of a user configured QoS policy and associates a default QoS policy with the port.

This command associates a network QoS policy to the access-uplink port.

On 7210 SAS-M and 7210 SAS-T in access uplink mode, this policy is used to enable marking on egress and classification and metering/policing on port ingress. For more information, refer to the 7210 SAS-M, T, Mxp, Sx, S Quality of Service Guide.

The no form of this command removes the explicit association of a user configured QoS policy and associates a default QoS policy with the port.

This command associates a network QoS policy to a network port.

This command enables the context to configure override values for the specified queue. These values will override the values specified in the associated access egress QoS policy.

The no form of this command removes all existing queue override commands.

This command enables the context to modify the queue parameters associated with a particular queue.

The no form of this command removes the queue override commands for this queue.

This command enables the context to override the adaptation-rule CIR and PIR values defined in the access egress QoS policy assigned to the port.

This command defines the method used by the system to derive the operational CIR and PIR settings when the queue is provisioned in hardware. For the CIR and PIR parameters individually, the system attempts to derive the best operational rate depending on the defined constraint.

The no form of this command removes adaptation-rule override parameters on the queue and applies the adaptation-rule defined for the queue in the access egress QoS policy.

This command enables the context to override the percent-rate or rate CIR and PIR values defined in the access egress QoS policy assigned to the port.

The percent-rate command enables support for configuring a queue PIR and CIR as a percentage of the egress port line rate (that is, the port limit). When the rates are expressed as a port limit, the actual rates used per instance of the queue will vary based on the port speed or the configured port egress rate. For example, when the same QoS policy is used on a 1 Gigabit and a 10 Gigabit Ethernet port, the queue rates will be 10 times greater on the 10 Gigabit port due to the difference in port speeds.

If the port speed changes after the queue is created, the queue PIR and CIR will be recalculated based on the defined percentage value.

The rate and percent-rate commands override one another. If the current rate for a queue is defined using the percent-rate command and the rate command is executed, the percent-rate values are deleted. Similarly, the percent-rate command causes any rate command values to be deleted. A queue rate may dynamically be changed back and forth from a percentage to an explicit rate at anytime.

The no form of this command, when defined within an egress queue-override command, reverts to the defined PIR and CIR within the access egress QoS policy associated with the queue.

This command enables the context to override the queue management policy defined in the access egress QoS policy assigned to the port.

This command associates the specified queue management policy with this queue.

The queue management policy specifies the queue buffer parameters and queue slope policy parameters.

The no form of this command associates the queue management policy for this queue as defined in the access egress QoS policy.

This command enables the context to override the queue mode defined in the access egress QoS policy assigned to the port.

This command determines whether the queue operates in strict or weighted mode.

The no form of this command associates the queue-mode for this queue as defined in access egress QoS policy.

This command enables the context to override the CIR and PIR values defined in the access egress QoS policy assigned to the port.

This command defines the administrative PIR and the administrative CIR parameters for the queue. The PIR defines the maximum rate at which the queue can transmit packets through the port. Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth. The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth.

The rate command can be executed at anytime, altering the PIR and CIR for all queues created on the access ports.

The rate and percent-rate commands override one another. If the current rate for a queue is defined using the percent-rate command and the rate command is executed, the percent-rate values are deleted. Similarly, the percent-rate command causes any rate command values to be deleted. A queue rate may dynamically be changed back and forth from a percentage to an explicit rate at anytime.

The no form of this command removes the queue-override parameter and applies the rate or percent-rate as specified for the queue in access egress QoS policy.

This command enables the context to override the weight defined in the access egress QoS policy assigned to the port.

For queues configured with queue-mode in weighted mode, weight values are considered only in the PIR loop. That is, in the CIR loop the CIR of the queues are met if bandwidth is available, and in the PIR loop the configured weight values determine the proportion of available bandwidth allocated to this queue relative to other queues configured in weighted mode.

The no form of this command removes the configured queue-override weight value and applies the weight value as defined in access-egress QoS policy for that queue.

This command associates a dot1p classification policy with an Ethernet port.

The dot1p classification policy is applicable only when table-based classification is enabled on the access port. It is used to classify only bridged packets received on this port and processed in the context of an RVPLS service with a SAP configured on this port. The dot1p classification policy defines the mapping of IP dot1p values to forwarding class (FC) and profile (in-profile or out-profile).

The no form of this command removes the dot1p classification policy from its association with the Ethernet port.

This command associates a DSCP classification policy with an Ethernet port.

The DSCP classification policy is applicable only when table-based classification is enabled on the access port. It is used to classify only bridged packets received on this port and processed in the context of an RVPLS service with a SAP configured on this port. The DSCP classification policy defines the mapping of IP DSCP values to forwarding class (FC) and profile (in-profile or out-profile).

The no form of this command removes the DSCP classification policy from its association with the Ethernet port.

This command assigns a default FC and profile to non-IP Ethernet packets received on this port and processed in the context of an RVPLS service that has a SAP configured on this port.

Non-IP tagged and untagged packets are assigned the untagged-fc fc because they do not have a DSCP field available to match in the DSCP classification policy.

Note: All tagged bridged non-IP packets received on this port are processed in the context of an RVPLS service with a SAP configured on this port. FC is assigned as per the value configured using this command and profile is assigned using the DEI bit in the packet. Untagged bridged traffic will also match the untagged-fc fc and are treated as out of profile.

The no form of this command reverts the assigned FC to the default value.

This command associates an access ingress policy with an access port configured to use the port-mode option in the configure port ethernet access-ingress-qos-mode command.

The qos command is ignored if the configure port ethernet access-ingress-qos-mode command is configured to use the sap-mode option.

The no form of this command reverts to the default value.

This command enables the context to configure ports. Before a port can be configured, the chassis slot must be provisioned with a valid card type and the MDA parameter must be provisioned with a valid MDA type. (See card and mda commands.)

This command configures the Dense Wavelength Division Multiplexing (DWDM) parameters.

This command configures the Dense Wavelength Division Multiplexing (DWDM) ITU channel at which a tunable MDA optical interface will be configured to operate. It is expressed in a form that is derived from the laser's operational frequency. For example, 193.40 THz corresponds to DWDM ITU channel 34 in the 100 GHz grid and 193.45 THz corresponds to DWDM ITU channel 345 in the 50 GHz grid. A provisioned MDA type must have DWDM tunable optics (m1-10gb-dwdm-tun).

The DWDM channel must set to a non-zero value before the port is set to no shutdown.

The port must be shut down before changing the DWDM channel.

The DWDM channel must be on a physical port.

This command enables DEI based classification on access ports, network ports, access-uplink or hybrid ports.

If enabled, DEI value in the Ethernet packet header is used to determine the initial profile/color of the packet when the meter/policer used to police the FC is configured in color-aware mode. If the meter used to police the FC is configured in color-blind mode, then the DEI value of the packet has no effect. When in color-aware mode, DEI value of 0 is interpreted as in-profile or green packet and DEI value of 1 is interpreted as out-of-profile or yellow packet. In color-aware mode, the following behavior is accorded to packets classified with initial profile/color as in-profile/green and out-of-profile/yellow:

That is, in color-aware mode, yellow/out-of-profile packets cannot eat into the CIR bandwidth. It is exclusively reserved for green/in-profile packets.

The final profile assigned at ingress is used by egress to determine the WRED slope to use. The WRED slope determines whether the packet is eligible to be assigned a buffer and can be queued up on egress queue for transmission.

For more information, see the 7210 SAS-R6, R12 Quality of Service Guide.

This command enables the provisioning of an existing port-scheduler-policy to a port or channel.

The default scheduling done for a port is strict scheduling. When a port-scheduler-policy is applied to the port, the scheduling behavior changes to the one specified in the policy (Strict, RR, WRR, WDRR, WRR/WDRR + Strict).

The no form of this command removes the associated default port scheduler policy from an egress port.

Access: An access port is used for customer facing traffic on which services are configured. A Service Access Point (SAP) can only be configured on an access port. When a port is configured for access mode, the appropriate encap-type must be specified to distinguish the services on the port. Once an Ethernet port has been configured for access mode, multiple services can be configured on the Ethernet port.

Access-uplink: Access-uplink ports are used to provide native Ethernet connectivity in service provider transport or infrastructure network. This can be achieved by configuring port mode as access uplink. With this option, the encap-type can be configured to only qinq. Access-uplink SAPs, which are QinQ SAPs, can only be configured on an access uplink port to allow the operator to differentiate multiple services being carried over a single access uplink port. It is supported only on 7210 SAS-M and 7210 SAS-T configured in access-uplink mode.

Network: A network port participates in the service provider transport or infrastructure network when a network mode is selected. When the network option is configured, the encap-type can be configured to either null or dot1q.

Hybrid: A hybrid Ethernet port allows the combination of network and access modes of operation on a per-VLAN basis and must be configured as either dot1q or QinQ encapsulation. When the hybrid port is configured to the dot1q encapsulation, the user configures a SAP inside a service by providing the SAP ID which must include the port-id value of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. A SAP of format <port-id>:* is also supported. The user configures a network IP interface under config>router>interface>port by providing the port name which consists of the port-id of the hybrid mode port and an unused VLAN tag value. The format is <portid>:qtag1.

The user must explicitly enter a valid value for qtag1. The <port-id>:* value is not supported on a network IP interface. The 4096 VLAN tag space on the port is shared among VLAN SAPs and VLAN network IP interfaces. When the hybrid port is configured to QinQ encapsulation, the user configures a SAP inside a service by providing the SAP ID which must include the port-id value of the hybrid mode port and the outer and inner VLAN tag values.

The format is <port-id>:qtag1.qtag2. A SAP of format <port-id>: qtag1.* is also supported. The outer VLAN tag value must not have been used to create an IP network interface on this port. In addition, the qtag1.qtag2 value combination must not have been used by another SAP on this port. The user configures a network IP interface under config>router>interface>port by providing the port name which consists of the port-id of the hybrid mode port and a VLAN tag value. The format is <portid>:qtag1.*. An outer VLAN tag qtag2 of * is used to create an IP network interface. In addition, the qtag1.qtag2 value combination must not have been used on another SAP or IP network interface on this port.

The no form of this command reverts to the default.

This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>system context before its name is referenced in this command.

The no form of this command removes the association from the configuration.

This command assigns a specific MAC address to an Ethernet port, Link Aggregation Group (LAG), or Ethernet tunnel.

Only one MAC address can be assigned to a port. When multiple mac commands are entered, the last command overwrites the previous command. When the command is issued while the port is operational, IP will issue an ARP, if appropriate, and BPDUs are sent with the new MAC address.

The no form of this command reverts the MAC address to the default value.

This command configures the maximum payload MTU size for an Ethernet port. The Ethernet port level MTU parameter indirectly defines the largest physical packet the port can transmit or the far-end Ethernet port can receive. Packets received larger than the MTU will be discarded. Packets that cannot be fragmented at egress and exceed the MTU are discarded.

The value specified for the MTU includes the destination MAC address, source MAC address, the Ethertype or Length field and the complete Ethernet payload. The MTU value does not include the preamble, start of frame delimiter or the trailing CRC.

The no form of this command reverts to the default values.

This command enables the context to configure Layer 2 or Layer 3 multicast egress replication on a port. That is, with RVPLS IGMPv3 snooping-based multicast, a port on which receivers are present can be configured to do either Layer 2 multicast replication—where IP TTL is not decremented and the source MAC address is not replaced with the 7210 SAS chassis MAC or IP interface MAC address—or Layer 3 multicast replication—where IP TTL is decremented and the source MAC address is replaced.

This command is supported in network mode

All SAPs on the specified port have the same behavior, therefore the reference to port instead of SAP in the following behavior description:

This command enables the context to turn on either IP multicast or IGMP snooping on a port. The l2-mc and ip-mc options are mutually exclusive.On 7210 SAS port ingress, either IGMP snooping Layer 2 multicast lookup can be enabled or IP multicast Layer 3 multicast lookup can be enabled.

The ip-mc keyword must be enabled on ports where multicast sources are located and an RVPLS SAP is configured to receive the multicast streams.

Note: The restriction of either configuring a VPLS SAP as a receiver for processing Layer 2 multicast traffic on ingress or configuring an IP interface as a receiver for processing Layer 3 multicast traffic on ingress (on a port) does not restrict the ability to configure both a VPLS SAP and an IP interface on a port with receivers connected downstream (that is, in the egress direction). Typically, the ports used for ingress and the ports used for egress are not the same.

This command enables Precision Time Protocol (PTP) port-based hardware timestamping on the port in both egress and ingress directions. For more information about PTP port-based hardware timestamping, including configuration guidelines, see the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System Configuration Guide.

The no version of this command disables PTP port-based hardware timestamping on the port.

Note: The p2mpbud p2mpbud-port-id parameter is supported only on the 7210 SAS-R6 and 7210 SAS-R12. It reserves a loopback port for use with the NG-MVPN P2MP LSP feature.

This command specifies the port to assign for system use when using port loopback with the following tools: mac-swap, mirroring, testhead OAM, and NG-MVPN, when the node is acting as a P2MP bud router on the 7210 SAS-R6 or 7210 SAS-R12. When configured, the system uses the resources of the port, and the port is not available for configuring services.

A single port cannot be shared among these tools simultaneously. The system displays an error if users attempt to configure the same port for use with multiple OAM tools or use the tool without first configuring the port resources for the tool.

To use these OAM tools simultaneously, this command must be executed once for each OAM tool with a different port ID. For example, users can dedicate two ports for use by executing the loopback-no-svc-port mirror 1/1/1 command for use with the mirroring OAM tool, followed by the loopback-no-svc-port mac-swap 1/1/2 command for use by the mac-swap OAM tool.

Alternatively, users can dedicate two ports by executing the loopback-no-svc-port testhead 1/1/1 command for use by the testhead OAM tool, followed by executing the loopback-no-svc-port mac-swap 1/1/2 command for use by the mac-swap OAM tool.

The system verifies whether any services are configured on the port specified using this command; if services are configured, the command fails.

The no form of this command disables the use of this port by the specified OAM tool.

Note: On the 7210 SAS-M 24F 2XFP(ETR and non-ETR variants), one of the ports configured under the BOF no-service-ports command can be used with the mac-swap, mirroring, or testhead OAM tool. To use the OAM tools simultaneously, an additional front-panel port must be configured for use with each of the tools. On the 7210 SAS-M 24F, the internal port 1/1/25 can be used with either the mac-swap or mirroring OAM tool. To use the OAM tools simultaneously, an additional front-panel port must be configured for use with each of the tools. On the 7210 SAS-T, the two available internal ports (that is, port 1/1/27 and 1/1/28) can be used with the mac-swap, mirroring, or testhead OAM tool. To use the OAM tools simultaneously, an additional front-panel port must be configured for use with each of the tools. On the 7210 SAS-R6 and 7210 SAS-R12, a fixed number of internal ports are available for use with OAM tools (such as, the testhead, mac-swap, and dot1q or remote mirroring OAM tool) that need the resources of a loopback port. The number of internal virtual port resources that are available on different types of IMMs can be obtained using the show system internal-loopback-ports detail command. If all the internal port resources are in use, users might need to configure the resources of a front-panel port for use with OAM tools that need loopback port resources. To use the OAM tools simultaneously, an additional front-panel port must be configured for use with each of the tools. When configuring internal port resources or front-panel port resources for testhead and mac-swap OAM tools, the port must be on the same IMM as the test SAP. On the 7210 SAS-Mxp, one internal port (that is, port 1/1/29) is available for use with the mac-swap, mirroring, or testhead OAM tool. To use the OAM tools simultaneously, an additional front-panel port must be configured for use with each of the tools.

This command enables the context to configure Ethernet port attributes.

This context can only be used when configuring Fast Ethernet, gigabit, or 10Gig Ethernet LAN ports on an appropriate MDA.

This command configures an Ethernet port for access, network, or hybrid mode of operation. It also configures a TDM channel or SONET/SDH path (sub-port) for access or network mode operation.

An access port or channel is used for customer facing traffic on which services are configured. A Service Access Point (SAP) can only be configured on an access port or channel. When a port is configured for access mode, the appropriate encap-type must be specified to distinguish the services on the port or SONET path. Once an Ethernet port, a TDM channel or a SONET path has been configured for access mode, multiple services can be configured on the Ethernet port, a TDM channel or SONET path.

Note: ATM, frame relay, and cHDLC port parameters can only be configured in the access mode.

A network port or channel participates in the service provider transport or infrastructure network when a network mode is selected. When the network option is configured, the encap-type cannot be configured for the port/channel.

When network mode is selected on a SONET/SDH path, the appropriate control protocols are activated when the need arises. For example, configuring an IP interface on the SONET path activates IPCP while the removal of the IP interface causes the IPCP to be removed. The same applies for MPLS, MPLSCP, and OSICP. When configuring a SONET/SDH port, the mode command must be entered in the channel context or an error message is generated.

The no form of this command reverts to the default.

Note: For tdm>ds1 and tdm>e1 only access mode is supported. Network and hybrid is not supported.

This command enables the context to use either a per-SAP ingress QoS policy or a per-port access ingress QoS policy on the access port.

This command is supported only in the high SAP scale mode, which is configured using the config>system>resource-profile>sap-scale-mode high command on the 7210 SAS-Mxp and the config>system>global-res-profile>sap-scale-mode high command on the 7210 SAS-R6 and 7210 SAS-R12.

When the access-ingress-qos-mode command is configured on the access port with the sap-mode option specified, per-SAP ingress QoS policies are used for SAPs configured on the port. Attempts to attach an access ingress QoS policy fail.

When the access-ingress-qos-mode command is configured with the port-mode option specified, access ingress QoS policies associated with the port are used for ingress classification and metering and policing. If a user-defined access ingress QoS policy is associated with the port, the user must reset the access ingress policy ID to 1 before changing access-ingress-qos-mode to sap-mode; otherwise, the change fails.

When the user enables the access-ingress-qos-mode command with the port-mode option, the IP DSCP and dot1p classification policies configured in the context of the access port ingress QoS are used. Refer to the 7210 SAS-M, T, Mxp, Sx, S Quality of Service Guide and 7210 SAS-R6, R12 Quality of Service Guide for more information about the config qos access-ingress command.

LAG member ports can be configured to use either the sap-mode or port-mode; a mix of the two modes is not allowed. When operating in port-mode, all LAG members have the same access ingress QoS policy as the primary LAG member. The policy defines the classification and policing rates for all traffic received on all ports of the LAG. For example, if the user configures the classification entry dot1p 7 to FC nc and the meter 1 CIR and PIR to 100 Mb/s and 2 Gb/s respectively, traffic received on the LAG member ports with a dot1p value of 7 are assigned FC nc at ingress and are rate-limited to 2 Gb/s. For inter-card LAG scenarios, each card is programmed separately for 2 Gb/s.

A node can have a mix of ports configured as access, hybrid, and network ports, where some access ports are configured to use sap-mode access ingress QoS and other access ports are configured to use port-mode access ingress QoS.

SAPs configured on ports in hybrid port mode cannot be configured to use per-port access ingress QoS policies.

Before configuring the access-ingress-qos-mode command with the port-mode option specified, use the configure system resource-profile ingress-internal-tcam qos-access-port-ingress-resource command to allocate the appropriate resources from the ingress-internal-tcam resource pool for use by the access ingress QoS policies. If no resources are allocated, changing the existing access ingress QoS mode to port-mode will fail. In addition, if access ports are currently configured to use port-mode access ingress QoS, setting the qos-access-port-ingress-resource command to 0 is not allowed.

In addition, before executing this command, the user must ensure that access port scheduling is configured using the configure system resource-profile qos port-scheduler-mode command on the 7210 SAS-Mxp and the configure system global-res-profile qos port-scheduler-mode command on the 7210 SAS-R6 and 7210 SAS-R12, after which high SAP scale mode can be configured using the sap-scale-mode high command. This is a per-node configuration and requires a node reboot for the change to take effect. The node must be rebooted in the high SAP scale mode and qos-access-port-ingress-resource must have enough resources to change the access-ingress-qos-mode command to port-mode.

Note: The user must change the access-ingress-qos-mode command to sap-mode before changing the sap-scale-mode command to low. Otherwise, the configuration will fail on reboot and the saved configuration will attempt to change the access-ingress-qos-mode to port-mode while in low SAP scale mode When the port-scheduler-mode command and high SAP scale mode are configured, use either per-access SAP ingress QoS policies or per-access port ingress QoS policies for the access port.

This command configures Ethernet access port QoS parameters.

This command configures Ethernet access egress port QoS parameters.

This command enables speed and duplex autonegotiation on Fast Ethernet ports and enables far-end fault indicator support on Gigabit ports.

There are three possible settings for autonegotiation:

When autonegotiation is enabled on a port, the link attempts to automatically negotiate the link speed and duplex parameters. If autonegotiation is enabled, the configured duplex and speed parameters are ignored.

When autonegotiation is disabled on a port, the port does not attempt to autonegotiate and will only operate at the speed and duplex settings configured for the port.

Note: Disabling autonegotiation on gigabit ports is not allowed as the IEEE 802.3 specification for gigabit Ethernet requires autonegotiation be enabled for far end fault indication.

If the autonegotiate limited keyword option is specified the port will autonegotiate but will only advertise a specific speed and duplex. The speed and duplex advertised are the speed and duplex settings configured for the port. One use for limited mode is for multispeed gigabit ports to force gigabit operation while keeping autonegotiation enabled for compliance with IEEE 801.3.

7210 SAS requires that autonegotiation be disabled or limited for ports in a Link Aggregation Group to guarantee a specific port speed.

The no form of this command disables autonegotiation on this port.

This command configures the connection type on the Ethernet combo port. The combo port provides two physical interface options to the user, SFP or copper. This command lets the user specify the physical interface that will be used.

When configured as an SFP port, the combo port allows for fiber based connectivity with the flexibility of using suitable optics for longer reach. When configured as a fixed copper port, it provides cheaper connectivity for shorter reach. The SFP port support 100/1000 speeds and the copper port can support 10/100/1000Mbps speed.

The combo port can be configured either as an SFP port or a copper port. That is, both the interfaces cannot be used simultaneously.

This command configures Ethernet CRC Monitoring parameters.

This command specifies the error rate at which to declare the Signal Failure condition on an Ethernet interface.

The value represents a ratio of errored frames over total frames received over seconds of the sliding window. The CRC errors on the interface are sampled once per second. A default of 10 seconds is used when there is no additional window-size configured. The multiplier keyword is optional.

The no form of this command reverts to the default value of 1. If the multiplier keyword is omitted, the multiplier will revert to the default value of 1.

This command specifies the error rate at which to declare the Signal Degrade condition on an Ethernet interface.

The value represents a ratio of errored frames over total frames received over seconds of the sliding window. The CRC errors on the interface are sampled once per second. A default of 10 seconds is used when there is no additional window-size configured. The multiplier keyword is optional.

The no form of this command reverts to the default value of 1. If the multiplier keyword is omitted, the multiplier will revert to the default value of 1.

This command specifies sliding window size over which the Ethernet frames are sampled to detect signal fail or signal degrade conditions. The command is used jointly with the sf-threshold and the sd-threshold to configure the sliding window size.

This command configures the system to allow to bring a port operationally down in the event the systems has detected internal max transmit errors.

This command specifies the Ethertype expected when the port's encapsulation type is dot1q. Dot1q encapsulation is supported only on Ethernet interfaces.

When the dot1-etype is configured to a value other than 0x8100 (the default value) on a port, the outermost tag in the received packet is matched against the configured value and if there is a match then it is treated as a Dot1q packet and the VLAN ID is used to match against the configured Dot1q SAPs on the port to find the Dot1q SAP the packet should be matched to.

Note: This command does not change the etype used to match the inner tag for a QinQ SAP. The 7210 SAS devices always uses 0x8100 for matching the inner tag etype. That is, if this command is configured on a port configured for QinQ encapsulation, then it is ignored and 0x8100 is used always. This command takes effect only for access ports and hybrid ports. On hybrid ports, it applies to all traffic (that is, traffic mapped to SAPs and network IP interfaces). It is not supported for network ports. Dot1q-preserve SAPs cannot be configured on dot1q encap ports configured to use Ethertype other than 0x8100. Priority tagged packet received with etype 0x8100 on a dot1q port configured with etype 0x9100 is classified as a priority tagged packet and mapped to a dot1q:0 SAP (if configured) and the priority tag is removed. Priority tagged packets received with etype 0x6666 (any value other than 0x8100) on a dot1q port configured with etype 0x9100 is classified as null-tagged packet and mapped to a dot1q:0 SAP (if configured) and the priority tag is retained and forwarded as expected. The maximum number of unique dot1q-etypes configurable per node is limited. The resources needed for configuration of dot1q-etype is shared by the default dot1q-etype, default qinq-etype and user configured values for qinq-etype. That is, the number of unique dot1q-etypes allowed decreases, if the number of unique qinq-etype configured is more. The converse is also true.

The no form of this command reverts the dot1q-etype value to the default.

This command configures the duplex of a Fast Ethernet port when autonegotiation is disabled. If the port is configured to autonegotiate this parameter is ignored.

This command configures EFM-OAM attributes.

This command enables reactions to loopback control OAM PDUs from peers.

The no form of this command disables reactions to loopback control OAM PDUs.

This command configures the mode of OAM operation for this Ethernet port. These two modes differ in that active mode causes the port to continually send out efm-oam info PDUs while passive mode waits for the peer to initiate the negotiation process. A passive mode port cannot initiate monitoring activities (such as loopback) with the peer.

This command configures the transmit interval of OAM PDUs.

The minimum efm-oam session time-out value supported is 300 milliseconds. That is, user can configure "transmit-interval 1 multiplier 3" as the minimum value.

This command enables EFM OAM PDU tunneling. Enabling tunneling will allow a port mode Epipe SAP to pass OAM frames through the pipe to the far end.

The no form of this command disables tunneling.

This command configures the rate of traffic leaving the network.

The no form of this command reverts the value to the default.

Note: The max-burst keyword configures a maximum-burst (in kilobits) associated with the egress-rate. This is an optional parameter and if not explicitly configured then by default it is set to 64 kbits for both 1G and 10G ports. Users cannot configure max-burst without configuring egress-rate. The value should be between 32 and 16384, or default. For more information, see the 7210 SAS-R6, R12 Quality of Service Guide.

This command enables the context to use a table-based IP DSCP classification policy to assign FC and profile to RVPLS bridged IP packets received on access port ingress. This command works in conjunction with the SAP ingress QoS policy associated with the RVPLS service. The match-criteria entries from the RVPLS SAP ingress policy are ignored and instead the IP DSCP classification is used to assign the FC and profile. Only meters from the SAP ingress policy are used to rate-limit the traffic mapped to different FCs.

The DSCP classification policy that is enabled by the enable-table-classification command is specified in the config>port>ethernet>access>ingress context, using the dscp-classification command.

Note: The enable-table-classification command—as well as the DSCP classification policy—takes effect only if enable-table-classification is enabled in the respective RVPLS SAP and in the context of the IP interface associated with the RVPLS service.

This command has no effect on a network port.

The no form of this command disables the use of a DSCP classification policy for RVPLS bridged packets.

This command configures the encapsulation method used to distinguish customer traffic on an Ethernet access port, or different VLANs on a network port.

The no form of this command reverts to the default.

This command allows rate changes received in ETH-BN messages on a port-based MEP to update the egress rate used on the port. The egress rate is capped by the minimum of the configured egress-rate and the maximum port rate.

The no form of this command reverts to the default value.

This command enables the context to configure 802.1ag CFM parameters.

This command provisions the maintenance endpoint (MEP).

The no form of this command removes the configuration.

This command enables the context to configure ETH-BN message handling.

This command enables the reception and processing of eth-bn messages, and the retrieval and processing of the current bandwidth field for inclusion in dynamic egress rate adjustments.

The received rate is a Layer 2 rate, and is expected to be in Mb/s. If this rate is a link rate (including preamble, start frame delimiter, and inter-frame gap), it requires the configuration of frame-based accounting in the config>port>ethernet context.

The no form of this command disables the reception and processing of ETH-BN messages.

This command sets the pace for update messages to and from the eth-cfm subsystem to the QoS subsystem. The most recent update messages are held by the ETH-CFM subsystem, but the most recent update is held until the expiration of the pacing timer.

This command configures port link dampening timers, which reduce the number of link transitions reported to upper layer protocols. The hold-time value is used to dampen interface transitions.

When an interface transitions from an up state to a down state, it is immediately advertised to the rest of the system if the hold-time down interval is 0, but if the hold-time down interval is greater than 0, interface down transitions are not advertised to upper layers until the hold-time down interval has expired. When an interface transitions from a down state to an up state, it immediately advertised to the rest of the system if the hold-time up interval is 0, but if the hold-time up interval is greater than 0 interface, up transitions are not advertised until the hold-time up interval has expired.

The no form of this command reverts to the default values.

This command enables LACP packet tunneling for the Ethernet port. When tunneling is enabled, the port will not process any LACP packets but will tunnel them instead. The port cannot be added as a member to a LAG group.

The no form of this command disables LACP packet tunneling for the Ethernet port.

This command enables PoE on this port and allows only 802.3af (Type 1) low-power devices to be connected to the port.

Using the plus parameter enables users to connect Type 2 devices (that is, high-powered devices) compliant to 802.3at standards to the port.

This command must be used to enable PoE on a port before connecting a PoE device to the port. Once a port is enabled for PoE, software attempts to detect the type of PoE device (that is, PoE or PoE+ device) connected to the port and the power it is requesting when a PoE device is connected to the port. If the detection is successful and the power request is within the budget that the platform supports, then power is supplied to the connected device. If not, power is not supplied to the port.

The no form of this command disables PoE and PoE+ on this port. If PoE is disabled, the software does not attempt to detect the characteristics of the PoE device connected to the port and not supply power to the port.

This command associates the context to the operational group specified in the group-name. The oper-group group-name must be already configured under config>system context before its name is referenced in this command.

The no form of this command removes the association.

This command configures the Ethertype used for Q-in-Q encapsulation.

When the qinq-etype is configured on a port with a value other than the default, the outermost tag in the received packet is matched against the configured value and the inner tag's etype is matched against the default. If there is a match then it is treated as a QinQ packet and the outer VLAN ID and inner VLAN ID is used to match against the configured Q1.Q2 SAPs on the port to find the QinQ SAP the packet should be matched to. If only the outermost tag's etype matches the qinq-etype configured on the port and the VLAN ID matches any of the Q1.* SAP configured on the port, the packet is processed in the context of that SAP. If the outermost tag's etype does not match the configured qinq-etype, then the packet is considered to be a untagged packet.

Note: This command takes effect only for access ports and hybrid ports. On hybrid ports, it applies to all traffic (that is, traffic mapped to SAPs and network IP interfaces). It is not supported for network ports. The maximum number of unique qinq-etypes configurable per node is limited. The resources needed for configuration of qinq-etype is shared by the default dot1q-etype, default qinq-etype and user configured values for qinq-etype. That is, the number of unique dot1q-etypes allowed decreases if the number of unique qinq-etype configured is more. The converse is also true. The qinq-etype change is not allowed on hybrid port, if there is an interface or a SAP configured on the port.

The no form of this command reverts the qinq-etype value to the default. The default value is not user configurable.

This command enables Reed–Solomon Forward Error Correction (RS-FEC) on the Ethernet port.

The no form of this command disables RS-FEC.

This command specifies when and if to generate alarms and alarm clear notifications for this port.

Note: The report-alarm command is only supported for 10G ports on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-R6, and 7210 SAS-R12.

This command enables the context to force the copper port to be a master or slave. Using a value of master ensures that the local node is the syncE master. A syncE master port, distributes the system timing over the copper port to the remote peer node. Using a value of slave ensures that the local node is a syncE slave. A syncE slave port uses the incoming timing information.

With copper ports using 1G speed, the nodes need to determine who will be the master and slave with respect to clock used for transmission and reception. The master-slave relationship between the two ports of the nodes is determined during auto-negotiation of the link parameters and is automated; there is no management intervention in this process. Once this process is complete, the master port transmit clock will be used for receiving the packets on the slave port. However, when syncE is in use, to maintain clock distribution hierarchy (for example, master will be synchronized to a stable reference and will distribute this clock to the slave) one needs to make sure that one of the ports behave as a master while the remote port of the ink in question behaves as a slave.

The following conditions must be met before using syncE on the fixed port copper ports:

The no form of this command allows the node to automatically determine the master or slave status for the copper port based on the nodes capabilities exchanged during auto-negotiation. That is, depending on the peer setting, the local end could end up as either a master or a slave when the no form of the command is used.

Note: For 7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), the user must first configure the combo port connection-type to copper before using the port-clock command. The port-clock command cannot be configured without first configuring connection-type copper.

This command configures the port speed of an Ethernet port when autonegotiation is disabled. If the port is configured to autonegotiate, this parameter is ignored.

Speed cannot be configured for ports that are part of a Link Aggregation Group (LAG).

Supported values depend on the speed of the Ethernet interface supported on the platform.

On the 7210 SAS-S 1/10GE and 7210 SAS-Sx 1/10GE (copper variants), and on the 7210 SAS-Sx 10/100GE, if 1GE fiber-optic SFPs are used in SFP+ ports, the SFP+ ports must be set to 1000 Mb/s.

SFP+ ports that support SFPs do not support speeds of 10 Mb/s or 100 Mb/s.

This command enables the context to configure simple port loopback and port loopback with MAC swap. The command when the optional parameter 'internal' is specified, provides the port loopback without the mac-swap functionality. It enables physical layer loopback of the packets that egress on the SAPs created on a Ethernet port. The packets that egress are looped back into the node instead of being transmitted on to the line. After loopback, the packets ingress the system and are mapped to the same SAP from which they were egressed. The packets that are looped back are processed as per the service configuration of the SAP.

The command when used with service-id and MAC address, provides the port loopback with mac-swap functionality. It enables a physical layer loopback, so that packets which egress on the SAPs created on an Ethernet port are looped back into the system. After loopback, on ingress to the system, the MAC addresses in the Ethernet header are swapped (that is, the source MAC address and destination MAC address is exchanged with each other) by the system before being processed as per the service configuration of the SAP.

On 7210 SAS platforms, use of port loopback with mac-swap, requires resources of another port to be assigned for system use. Users need to assign the resources of either internal virtual port or the resource of the front panel port for use with this OAM tool using the command configure> system> loopback-no-svc-port {mirror | mac-swap| testhead} port-id. The number of internal virtual port resources available for use in different for different platforms and can be obtained using the command show> system> internal-loopback-ports detail. Based on the number of internal virtual port resources and the use of other OAM tool that require the resources of another port, the user might need to assign the resources of a front-panel port if the internal virtual port resources are not available.

Note: On 7210 SAS-M 24F 2XFP, the user can configure the second port specified in the no-service-ports configured in the BOF parameter as the assigned port in the command configure> system> loopback-no-svc-port. Port loopback without mac-swap does not require another port to be assigned for system use on any of the 7210 platforms.

Physical layer loopback is used with external third-party Ethernet test devices to diagnose provisioning issues and test end-to-end performance metrics of a service.

For Port loopback without mac-swap:

For port loopback with mac-swap:

The recommended procedure for using port loopback with mac-swap is:

The no form of this command disables physical layer loopback on the Ethernet port.

Note: The loop back command is not saved in the configuration file across a reboot.

Listed below is the recommended sequence of commands to be executed to perform loop back:

Listed below is the recommended sequence of commands to be executed to perform loop back when SFP or XFPs are inserted into the device:

Listed below is the sequence of commands to be executed to perform loop back when SFP or XFPs are changed:

This command enables Ethernet Synchronous Status Message (SSM).

This command configures the encoding of synchronous status messages, that is, to select either SDH or SONET set of values. Configuring the code-type is only applicable to Synchronous Ethernet ports. It is not configurable on TDM ports. For the code-type, SDH refers to ITU-T G.781 Option-1,while SONET refers to G.781 Option 2 (equivalent to Telcordia GR-253-CORE).

This command configures the QL value, transmitted from the SSM channel of the SONET/SDH port or the Synchronous Ethernet port, to be set to QL-DUS/QL-DNU. This capability is provided to block the use of the interface from the SR/ESS for timing purposes.

This command enables the context to configure port-specific 802.1x authentication attributes. This context can only be used when configuring a Fast Ethernet, Gigabit or 10Gig Ethernet or Gigabit Ethernet LAN ports on an appropriate MDA.

This command enables MAC-based authentication. To use MAC-based authentication, 802.1x authentication must first be enabled using the port-control auto command.

When MAC-based authentication is enabled, and the mac-auth-wait timer expires, the 7210 SAS begins listening on the port for valid Ethernet frames. The source MAC address of a received frame is used for MAC-based authentication.

MAC authentication and Dot1x authentication or VLAN authentication are mutually exclusive and cannot be configured on the same port.

The no form of this command disables MAC-based authentication.

This command configures the delay period before MAC authentication is activated.

The no form of this command disables the delay and allows MAC authentication to be used immediately.

This command configures the maximum number of times that the 7210 SAS will send an access request RADIUS message to the RADIUS server. If a reply is not received from the RADIUS server after the specified number of attempts, the 802.1x authentication procedure is considered to have failed.

This command configures the 802.1x authentication mode.

The no form of this command reverts the value to the default.

This command configures the period between two authentication sessions during which no EAPOL frames are sent by the 7210 SAS.

The no form of this command reverts the value to the default.

This command configures the RADIUS policy to be used for 802.1x authentication. An 802.1x RADIUS policy must be configured (under config>security>dot1x) before it can be associated to a port. If the RADIUS policy-id does not exist, an error is returned. Only one 802.1x RADIUS policy can be associated with a port at a time.

The no form of this command removes the RADIUS policy association.

This command configures the period after which re-authentication is performed. This value is only relevant if re-authentication is enabled.

The no form of this command reverts the value to the default.

This command enables and disables periodic 802.1x reauthentication.

When re-authentication is enabled, the 7210 SAS will reauthenticate clients on the port every re-auth-period seconds.

The no form of this command reverts the value to the default.

This command configures the period during which the 7210 SAS waits for the RADIUS server to responds to its access request message. When this timer expires, the 7210 SAS will resend the access request message, up to the specified number times.

The no form of this command reverts the value to the default.

This command configures the period during which the 7210 SAS waits for a client to respond to its EAPOL messages. When the supplicant-timeout expires, the 802.1x authentication session is considered to have failed.

The no form of this command reverts the value to the default.

This command configures the period after which the 7210 SAS sends a new EAPOL request message.

The no form of this command reverts the value to the default.

This command enables the tunneling of dot1x frames. With dot1x tunneling enabled, dot1x frames received on the port are transparently forwarded to the remote end of the service. To forwards dot1x frames transparently, the port on which tunneling is enabled must be configured with NULL SAP and the NULL SAP must be configured in an Epipe service. Tunneling is not supported for any other port encapsulation or when using any other service.

Additionally, dot1x protocol must be disabled on the port (using the configure>port>ethernet>dot1x>port-control force-auth command) before dot1x tunneling can be enabled using this command. If dot1x is configured to use either force-unauath or auto, then dot1x tunneling cannot be enabled. Conversely, if dot1x tunneling is enabled, then port-control force-unauth or port-control auto cannot be configured.

The no form of this command disables dot1x tunneling.

This command enables VLAN-based authentication. To use VLAN-based authentication, 802.1x authentication must first be enabled using the port-control auto command.

When VLAN-based authentication is enabled, all traffic for all VLANs on the port is blocked. VLAN-tagged EAPOL messages are forwarded to the RADIUS server for authentication. If authentication is successful, the VLAN corresponding to the successfully authenticated VLAN-tagged EAPOL message is unblocked and traffic is processed for the configured service. If authentication fails, the VLAN continues to be blocked.

VLAN authentication and MAC authentication are mutually exclusive and cannot be configured on the same port.

The no form of this command disables VLAN-based authentication.

This command configures Ethernet loop detection attributes.

This command configures the time interval between keep-alive PDUs.

This command configures the minimum wait time before reenabling port after loop detection.

This command enables the context to configure Link Layer Discovery Protocol (LLDP) parameters on the specified port.

This command enables the context to configure tunneling for LLDP frames that use the nearest-bridge-dest-mac as destination MAC address. If enabled using the command tunnel-nearest-bridge-dest-mac, all frames received with the appropriate destination mac address are forwarded transparently to the remote end of the service. To forward these frames transparently, the port on which tunneling is enabled must be configured with NULL SAP and the NULL SAP must be configured in an Epipe service. Tunneling is not supported for any other port encapsulation or when using any other service.

Additionally, before enabling tunneling, admin status for LLDP dest-mac nearest-bridge must be set to disabled or Tx only, using the command admin-status available under configure> port>ethernet>lldp>dest-mac nearest-bridge. If admin-status for dest-mac nearest-bridge is set to receive and process nearest-bridge LLDPDUs (that is, if either rx or tx-rx is set) then it overrides the tunnel-nearest-bridge-dest-mac command.

Table 24 lists the behavior for LLDP with different values set in use for admin-status and when tunneling is enabled or disabled:

Note: Transparent forwarding of LLDP frames can be achieved using the standard defined mechanism when using the either nearest-non-tmpr or the nearest-customer as the destination MAC address in the LLDP frames. Nokia recommends that the customers use these MAC address where possible to conform to standards. This command allows legacy LLDP implementations that do not support these additional destinations MAC addresses to tunnel LLDP frames that use the nearest-bridge destination MAC address.

The no form of this command disable LLDP tunneling for frames using nearest-bridge destination MAC address.

This command configures destination MAC address parameters.

This command specifies the desired administrative status of the local LLDP agent.

This command creates the context to configure the administrative status of the local LLDP-MED agent.

This command configures the administrative status of the local LLDP-MED agent.

The no form of this command disables the ability to specify the administrative status of the local LLDP-MED agent.

This command configures the network policy information that the node transmits in the Network Policy TLV.

Up to four policies can be configured, as long as the configured application-type for each policy is different. The system includes multiple Network Policy TLVs (if multiple policies are configured), with the policy for each application-type included in its own Network Policy TLV. The Network Policy TLV order in the LLDP message will match the policy order configured in the CLI. If the system cannot fit all configured Network Policy TLVs into the LLDP frame because of size constraints, a log message is generated for the last network policy that exceeds the frame size. The error notification allows the user to adjust the configuration appropriately.

The user must explicitly configure a network policy (with values assigned to the endpoint device) before the transmission and reception of LLDP-MED TLVs on the port is allowed. If a port is configured to transmit the LLDP-MED Network Policy TLV but the user has not configured a network policy, the node will not transmit the Network Policy TLV. The node processes the received Network Policy TLV and displays the TLV values in the LLDP message received from the peer provided that the LLDP-MED receiving processing and Network Policy TLV processing is enabled, regardless of whether network-policy is configured.

The no form of this command removes the association of all network policies with the port.

This command configures the specific transmit TLV from the network connectivity TLV set to be transmitted on the port if LLDP-MED TLV transmission is enabled on the port.

The no form of this command removes the configuration.

This command enables LLDP notifications.

The no form of this command disables LLDP notifications.

This command specifies how to encode the PortID TLV transmit to the peer. Some releases of SAM require the PortID value require the default if-Alias to correctly build the Layer Two topology map using LLDP. Selecting a different option will impact SAM ability to build those Layer Two topologies.

This command specifies which management address to transmit. The operator can choose to send the system IPv4 IP Address, the system IPv6 address or both.

Note: The system address will only be sent once. When both options are configured both system addresses are sent. The system address must be configured for the specific version of the protocol to sent the management address.

This command specifies which LLDP TLVs to transmit.

The no form of this command reverts the value to the default.

no tx-tlvs

This command enables the context to configure network port parameters.

This command enables the context to configure access uplink port parameters.

This command configures an accounting policy that can apply to an interface.

An accounting policy must be configured before it can be associated to an interface. If the accounting policy-id does not exist, an error is returned.

Accounting policies associated with service billing can only be applied to SAPs. Accounting policies associated with network ports can only be associated with interfaces. Only one accounting policy can be associated with an interface at a time.

The no form of this command removes the accounting policy association from the network interface, and the accounting policy reverts to the default.

This command enables the collection of accounting and statistical data for the network interface. When applying accounting policies, the data, by default, is collected in the appropriate records and written to the designated billing file.

The no form of this command ensures that the statistics are still accumulated by the cards, however, the CPU does not obtain the results and write them to the billing file. If the collect-stats command is issued again (enabled), then the counters written to the billing file will include the traffic collected while the no collect-stats command was in effect.

This command associates a network queue policy with access-uplink port in access-uplink mode or a network port or hybrid port in network mode of operation.

This command specifies the existing network queue policy which defines queue parameters such as CIR and PIR rates, as well as forwarding-class to queue mappings. The network-queue policy is defined in the config>qos>network-queue context.

This command enables the context to configure DS-1/E-1 parameters for a port on a CES MDA.

TDM is a mechanism to divide the bandwidth of a stream into separate channels or time slots by assigning each stream a different time slot in a set. TDM repeatedly transmits a fixed sequence of time slots over a single transmission channel. Each individual data stream is reassembled at the receiving end based on the timing.

This command enables the context to configure digital signal level 1 (DS-1) frame parameters on a T1/E1 CES MDA.

T-1 transmits DS-1-formatted data at 1.544 Mbps through the network. If channel has been configured for DS1 on a T1/E1 CES MDA, all ports on that card can be configured for DS1. A combination of DS1 and E1 channels cannot exist on the same card.

The no form of this command disables DS-1 capabilities.

This command enables the context to configure E1 parameters on a T1/E1 CES MDA. E1 is a basic time division multiplexing scheme used to carry digital circuits. It is also a standard WAN digital communication format designed to operate over copper facilities at a rate of 2.048 Mbps.

If the channel has been configured for E1 on a T1/E1 CES MDA, all ports on that card can be configured for E1. A combination of DS1 and E1 channels cannot exist on the same card.

The no form of this command disables E1 capabilities.

This command initiates or restarts a Bit Error Rate Test (BERT) on the associated DS1/E1 circuit.

The associated DS1 or E1 must be in a shutdown (admin down) state to initiate this test.

The no form of this command terminates the BERT test if it has not yet completed.

Note: This command is not saved in the router configuration between boots. The 4-port OC-3/STM-1 and the 1-port OC-12/STM-4 ASAP MDA supports up to 28 concurrent BERT tests per MDA. An attempt to configure more BERT tests can result in an error indicating an operation failure due to resource exhaustion. If the ASAP MDA BERT error insertion rate command is executed when tests are running, it will not take effect until test is restarted.

This command specifies line buildout (cable length) for physical DS-1 interfaces on the T1/E1 CES MDA.

This command configures the number of decibels the transmission signal decreases over the line. This command applies only to a DS-1 port configured with a 'short' buildout (see the buildout command).

This command configures the line length for the physical DS1 port on the T1/E1 card.

This command configures the line impedance of a port. Line impedance is set on a per-port basis and ports on the same card can have different values. Before changing the line impedance of a port, the port must be shut down.

This command creates DS0 channel groups in a channelized DS1 or E1 circuit. Channel groups cannot be further subdivided.

The no form of this command deletes the specified DS1 or E1 channel.

This command specifies the clock source to be used for the link transmit timing. Adaptive timing is supported only on T1/E1 CES MDA card ports used for TDM pseudowires.

This command configures the encapsulation method used to on the specified port, path, or channel for the port on the T1/E1 CES MDA. This parameter can be set on access ports. For access mode, only cem encapsulation is supported.

This command specifies the DS1 framing to be used for the port. The ds1-unframed parameter allows the configuration of an unstructured DS1 channel on a T1/E1 MDA. If a DS1 unframed channel is shut down, the channel sends an AIS pattern to the far-end DS1. If the far-end DS1 is configured as unframed, it does not react to the AIS pattern. If the far-end DS1 is configured as framed, the far end declares the AIS pattern. The operational status remains up and no alarms are generated when the near end is operationally down. This is normal behavior for unframed G.703 mode.

This command specifies the E-1 framing to be used for the port.

This command configures the value that the HDLC TDM DS-0, E-1, E-3, DS-1, or DS-3 interface transmits during idle cycles. For ATM ports/channels/channel-groups, the configuration does not apply and only the no form is accepted.

The no form of this command reverts the idle cycle flag to the default value.

This command defines the data pattern to be transmitted when the circuit emulation service is not operational or temporarily experiences under-run conditions.This command is only valid for cesopsn services.

See the 7210 SAS-M, T, Mxp, Sx, S Services Guide for more information about CESoPSN services.

This command defines the signaling pattern to be transmitted (4-bit value) when the circuit emulation service is not operational or temporarily experiences underrun conditions. This command is only valid for CES with CAS.

See the 7210 SAS-M, T, Mxp, Sx, S Services Guide for more information about CESoPSN services.

This command configures the specified port or channel so that it is in a loopback mode. A line loopback loops frames received on the corresponding port or channel back toward the transmit (egress) direction before reaching the framer. The bit stream is not reframed. The electrical signal is regenerated by the Tx line interface unit (LIU) and the timing is provided by the Rx LIU.

An internal loopback, loops the frames from the local router back to the framer. This is usually referred to as an equipment loopback. The Tx signal is looped back and received by the interface.

The no form of this command disables the specified type of loopback.

Note: The loopback command is not saved to the system configuration. The fdl-ansi, fdl-bellcore and payload-ansi options can only be configured if DS1 framing is set to ESF. Only line and internal options are supported for "e1".

This command configures a TDM channel for access mode operation. An access port or channel is used for customer-facing traffic on which services are configured. A Service Access Point (SAP) can only be configured on an access port or channel. When a port is configured for access mode, the encap-type cem must be specified to distinguish the services on the port.

The no form of this command reverts to the default.

This command configures the DS1 channel response to remote loop backs. When enabled, the channel responds to remote loop backs; when disabled, the channel does not respond.

This command enables logging of DS-1 or E-1 alarms for DS-1 or E-1 ports or channels.

The no form of this command disables logging of the specified alarms.

This command activates the signal mode on the channel.

When enabled, control signals (such as those for synchronizing and bounding frames) are carried in the same channels as voice and data signals. Configure the signal mode before configuring the Cpipe service to support T1 or E1 with CAS.

Refer to the 7210 SAS-M, T, Mxp, Sx, S Services Guide, “Creating a Cpipe Service”, for information about configuring a Cpipe service.

This command is valid when:

Note: On the 7210 SAS, CAS is enabled at the port level, rather than at the 64 kb/s channel level. This means that control signals and voice and data signals are all carried in the same channels. However, T1 and E1 links with a mix of voice and data channels cannot be transported directly across a 7210 SAS network. For a workaround, contact your Nokia technical service representatives.

This limitation does not apply to Serial Data Interface card and E&M card traffic transported over MPLS as the signaling is transported in individual pseudowires.

This command defines the list of DS-0 timeslots to be used in the DS-1 or E-1 channel-group. The timeslots need not be consecutive.

The no form of this command removes DS-0 timeslots from a channel group.

This command enables the context to configure Link Aggregation Group (LAG) attributes.

A LAG can be used to group two or more ports into one logical link. The number of ports supported in a LAG depends on the platform. The aggregation of multiple physical links allows for load sharing and provides seamless redundancy. If one of the links fails, traffic is redistributed over the remaining links.

The no form of this command deletes the LAG from the configuration. Deleting a LAG is only allowed while the LAG is administratively shut down. Any dependencies, such as IP interface configurations, must be removed from the configuration before the no lag command can be issued.

This command enables the bfd context and enables BFD over the associated LAG links.

This command enables BFD over LAG links; additional parameter configuration is required to make the links operational.

BFD session timers are automatically extended during soft-reset operation on the IOMs and IMMs to avoid BFD sessions timing out and causing protocol events. However, in some cases this behavior is not desired as it can delay fast reroute transitions if they are in place. The optional disable-soft-reset-extension keyword disables the behavior so that the BFD timers are not automatically extended.

This command specifies the address family for the micro-BFD session over the associated LAG links.

This command specifies that the micro-BFD sessions to links in LACP state distributing will be restricted.

The no form of this command disables restricting micro-BFD sessions.

This command specifies the IPv4 address of the BFD source.

The no form of this command removes this address from the configuration.

This command specifies the maximum amount of time the router will continue to forward traffic over a link after the micro-BFD sessions have transitioned to a Down state because the router received an ADMIN-DOWN state from the far end. The timer provides the administrator the configured amount of time to disable or deprovision the micro-BFD session on the local node before forwarding is halted over the associated link or links.

The no form of this command removes the time interval from the configuration.

This command specifies the maximum amount of time the router will forward traffic over a link that has transitioned from Standby to Active, before the micro-BFD session must be fully established (Up state).

The no form of this command reverts the up-interval to the default, which indicates that forwarding will not start until the BFD session is established.

This command specifies the detect multiplier used for a micro-BFD session over the associated LAG links. The session is declared administratively Down if a BFD control packet is not received for a period determined by the following equation:

multiplier × receive-interval

The no form of this command removes the multiplier from the configuration.

This command specifies the receive timer used for micro-BFD sessions over the associated LAG links.

The no form of this command removes the receive timer from the configuration.

This command specifies the IPv4 address of the BFD destination.

The no form of this command removes this address from the configuration.

This command disables micro-BFD sessions for this address family.

The no form of this command reenables micro-BFD sessions for this address family.

This command specifies the transmit timer used for micro-BFD session over the associated LAG links.

The no form of this command removes the transmit timer from the configuration.

This command enables OSPF costing of a Link Aggregation Group (LAG) based on the available aggregated, operational bandwidth.

The path cost is dynamically calculated based on the interface bandwidth. OSPF path cost can be changed through the interface metric or the reference bandwidth.

If dynamic cost is configured, then costing is applied based on the total number of links configured and the cost advertised is inversely proportional to the number of links available at the time. This is provided that the number of links that are up exceeds the configured LAG threshold value at which time the configured threshold action determines if, and at what cost, this LAG will be advertised.

For example:

Assume a physical link in OSPF has a cost associated with it of 100, and the LAG consists of four physical links. The cost associated with the logical link is 25. If one link fails then the cost would automatically be adjusted to 33.

If dynamic cost is not configured and OSPF autocost is configured, then costing is applied based on the total number of links configured. This cost will remain static provided the number of links that are up exceeds the configured LAG threshold value at which time the configured threshold action determines if and at what cost this LAG will be advertised.

If dynamic-cost is configured and OSPF autocost is not configured, the cost is determined by the cost configured on the OSPF metric provided the number of links available exceeds the configured LAG threshold value at which time the configured threshold action determines if this LAG will be advertised.

If neither dynamic-cost nor OSPF autocost are configured, the cost advertised is determined by the cost configured on the OSPF metric. This is provided that the number of links available exceeds the configured LAG threshold value, at which time the configured threshold action determines if this LAG will be advertised.

The no form of this command removes dynamic costing from the LAG.

This command configures the encapsulation method used to distinguish customer traffic on a LAG. The encapsulation type is configurable on a LAG port. The LAG port and the port member encapsulation types must match when adding a port member.

If the encapsulation type of the LAG port is changed, the encapsulation type on all the port members will also change. The encapsulation type can be changed on the LAG port only if there is no interface associated with it. If the MTU is set to a non default value, it will be reset to the default value when the encap type is changed.All traffic on the port belongs to a single service or VLAN.

The no form of this command reverts to the default.

This command specifies the timer, in tenths of seconds, which controls the delay between detecting that a LAG is down (all active ports are down) and reporting it to the higher levels.

A non-zero value can be configured, for example, when active/standby signaling is used in a 1:1 fashion to avoid informing higher levels during the small time interval between detecting that the LAG is down and the time needed to activate the standby link.

This command specifies the Link Aggregation Control Protocol (LACP) mode for aggregated Ethernet interfaces only. Per the IEEE 802.3ax standard (formerly 802.3ad), the LACP provides a standardized means for exchanging information between Partner Systems on a link. This allow their Link Aggregation Control instances to reach agreement on the identity of the Link Aggregation Group to which the link belongs, move the link to that Link Aggregation Group, and enable its transmission and reception functions in an orderly manner.

This command specifies the interval signaled to the peer and tells the peer at which rate it should transmit.

This command enables LACP message transmission on standby links.

The no form of this command disables LACP message transmission. This command should be disabled for compatibility when using active/standby groups. This forces a timeout of the standby links by the peer. Use the no form if the peer does not implement the correct behavior regarding the lacp sync bit.

This command provides an option per LAG to select the load-balancing hash function to use. For more details about the packet header fields used when the hash function is set to one of these values, see LAG and ECMP Hashing.

Note: For non-unicast traffic, the hashing parameters are used as an input to the hash-2 algorithm regardless of the setting for this value on platforms that support use of packet fields and perform hash computation in hardware.