ethernet
config>port
Supported on all 7210 SAS platforms as described in this document.
Commands in this context configure Ethernet port attributes.
This context can only be used when configuring Fast Ethernet, gigabit, or 10Gig Ethernet LAN ports on an appropriate MDA.
mode {access | network | hybrid}
no mode
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document.
This command configures an Ethernet port for access, network, or hybrid mode of 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. Once an Ethernet port has been configured for access mode, multiple services can be configured on the Ethernet port.
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.
network
Specifies that the Ethernet port is configured as service access.
Specifies that the Ethernet port is configured for transport network use.
Specifies that the Ethernet port is configured for hybrid use.
access-ingress-qos-mode {sap-mode | port-mode}
config>port>ethernet
config>lag
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
This command configures 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, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE, 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. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide and 7210 SAS-Mxp, R6, R12, S, Sx, T 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.
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
On the 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12, when the port-scheduler-mode command and high SAP scale mode are configured, the user has the option to use either per-access SAP ingress QoS policies or per-access port ingress QoS policies for the access port.
access-ingress-qos-mode sap-mode
Keyword to enable the access ingress QoS SAP mode; that is, per-SAP ingress QoS policies are used for SAPs configured on the access port.
Keyword to enable the access ingress QoS port mode; that is, access ingress QoS policies associated with the access port are used for ingress classification and metering and policing.
access
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document.
This command configures Ethernet access port QoS parameters.
egress
config>port>ethernet>access
Supported on all 7210 SAS platforms as described in this document.
This command configures Ethernet access egress port QoS parameters.
autonegotiate [limited]
[no] autonegotiate
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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:
‟on” or enabled with full port capabilities advertised
‟off” or disabled where there are no autonegotiation advertisements
‟limited” where a single speed/duplex is advertised.
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.
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.
autonegotiate
connection-type connection-type
config>port>ethernet
7210 SAS-Mxp and 7210 SAS-Sx 1/10GE (fiber variants only)
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 allows the user specify the physical interface to use.
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 supports speeds of 100/1000 Mb/s and the copper port can support speeds of 10/100/1000 Mb/s.
The combo port can be configured either as an SFP port or a copper port. That is, both the interfaces cannot be used simultaneously.
connection-type sfp
Specifies the type of Ethernet combo port.
crc-monitor
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures Ethernet CRC Monitoring parameters.
[no] sd-threshold threshold [multiplier multiplier]
config>port>ethernet>crc-monitor
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
no sd-threshold
Specifies the rate of CRC errored Ethernet frames.
Specifies the multiplier used to scale the CRC error ratio.
[no] sf-threshold threshold [multiplier multiplier]
config>port>ethernet>crc-monitor
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
no sf-threshold
Represents the rate of CRC errored Ethernet frames.
Represents the multiplier used to scale the CRC error ratio.
[no] window-size seconds
config>port>ethernet>crc-monitor
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
10
Specifies the size of the sliding window in seconds over which the errors are measured.
[no] down-on-internal-error
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the system to allow to bring a port operationally down in the event the systems has detected internal max transmit errors.
no down-on-internal-error
dot1q-etype value
no dot1q-etype
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document.
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.
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.
0x8100
Specifies the Ethertype to expect.
duplex {full | half}
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
full
Sets the link to full duplex mode
Sets the link to half duplex mode
efm-oam
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures EFM-OAM attributes.
[no] accept-remote-loopback
config>port>ethernet>efm-oam
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command enables reactions to loopback control OAM PDUs from peers.
The no form of this command disables reactions to loopback control OAM PDUs.
no accept-remote-loopback
mode {active | passive}
config>port>ethernet>efm-oam
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
active
Provides capability to initiate negotiation and monitoring activities.
Relies on peer to initiate negotiation and monitoring activities.
[no] transmit-interval interval [multiplier multiplier]
config>port>ethernet>efm-oam
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
transmit-interval 10 multiplier 5
Specifies the transmit interval in 100s of milliseconds.
Specifies the multiplier for transmit-interval to set local link down timer.
[no] tunneling
config>port>ethernet>efm-oam
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
no tunneling
egress-rate sub-rate [max-burst size-in-kbits]
no egress-rate
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the rate of traffic leaving the network.
The no form of this command reverts the value to the default.
The max-burst size in kbits 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 size in kbits without configuring egress-rate. The value should be between 32 and 16384, or default. For more information, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide.
no egress-rate
Specifies the egress rate, in kilobits per second (kbps).
Specifies the maximum egress burst, in kilobits (Kbits).
[no] enable-table-classification
config>port>ethernet
config>lag
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12.
This command enables the use of 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.
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.
no enable-table-classification
encap-type {dot1q | null|qinq}
no encap-type
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
null
Specifies that ingress frames carry 802.1Q tags where each tag signifies a different service.
Specifies that ingress frames will not use any tags to delineate a service. As a result, only one service can be configured on a port with a null encapsulation type.
Specifies QinQ encapsulation for QinQ access SAPs.
[no] eth-bn-egress-rate-changes
config>port>ethernet
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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.
no eth-bn-egress-rate-changes
eth-cfm
config>port>ethernet
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
Commands in this context configure 802.1ag CFM parameters.
[no] mep mep-id domain md-index association ma-index
config>port>ethernet>eth-cfm
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command provisions the maintenance endpoint (MEP).
The no form of this command removes the configuration.
no mep
Specifies the maintenance association endpoint identifier.
Specifies the maintenance domain (MD) index value.
Specifies the MA index value.
eth-bn
config>port>ethernet>eth-cfm>mep
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
Commands in this context configure ETH-BN message handling.
[no] receive
config>port>ethernet>eth-cfm>mep>eth-bn
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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.
no receive
rx-update-pacing seconds
config>port>ethernet>eth-cfm>mep>eth-bn
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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.
rx-update-pacing 5
Specifies the time to wait before sending subsequent updates (in seconds).
hold-time {[up hold-time up] [down hold-time down] [seconds | centiseconds]}
no hold-time
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
down 0 seconds — No port link down dampening is enabled, link down transitions are immediately reported to upper layer protocols
up 0 seconds — No port link up dampening is enabled, link up transitions are immediately reported to upper layer protocols
Specifies the interval, in seconds or centiseconds, before an interface transitions from a down state to an up state is reported to upper layer protocols.
Specifies the interval, in seconds or centiseconds, before an interface transitions from an up state to a down state is reported to upper layer protocols.
Specifies the unit of measurement for the hold time.
[no] lacp-tunnel
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
no lacp-tunnel
poe [plus]
no poe
config>port>ethernet
7210 SAS-T ETR, 7210 SAS-Mxp, 7210 SAS-Sx 1/10GE fiber variants (standalone mode), and 7210 SAS-Sx/S 1/10GE copper PoE variants (standalone mode)
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. After 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.
Specifies the parameter poe-plus to allow support of 802.3at (Type-2) high power devices to be connected to the port.
oper-group name
no oper-group
config>port>ethernet
config>lag
Only supported on 7210 SAS platforms configured in the access-uplink operating mode
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.
Specifies a character string of maximum 32 ASCII characters identifying the group instance.
qinq-etype value
no qinq-etype
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
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.
0x8100
Specifies the qinq-etype to expect.
rs-fec-mode rs-fec-mode
no rs-fec-mode
config>port>ethernet
7210 SAS-R6 and 7210 SAS-R12 with IMM-c QSFP28 card, and 7210 SAS-Sx 10/100GE QSFP28
This command enables Reed–Solomon Forward Error Correction (RS-FEC) on the Ethernet port.
The no form of this command disables RS-FEC.
no rs-fec-mode
Specifies the RS-FEC mode to support.
[no] report-alarm [signal-fail] [remote] [local]
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command specifies when and if to generate alarms and alarm clear notifications for this port.
The report-alarm command is only supported for 10G ports on applicable platforms.
Specifies an Ethernet signal lost alarm.
Specifies remote faults.
Specifies local faults.
port-clock {master | slave | automatic}
config>port>ethernet
7210 SAS-T (network and access-uplink), 7210 SAS-R6 and 7210 SAS-R12 (16-port copper IMM-sas-r-b (IMMv2), Combo ports of 7210 SAS-Mxp, Combo ports on 7210 SAS-Sx 1/10GE fiber variant (standalone), and all copper variants of 7210 SAS-Sx/S 1/10GE (standalone)
This command forces 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 link in question behaves as a slave.
The following conditions must be met before using syncE on the fixed port copper ports:
Auto-negotiation (or auto-negotiation limited) must be turned on.
This command is required only when the copper port speed is set to 1Gbps.
This CLI command is not supported for fiber ports or for fiber ports that use Copper SFPs.
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.
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.
Specifies that the local node is the synchronous Ethernet master. A synchronous Ethernet master port distributes the system timing over the copper port to the remote peer node.
Specifies that the local node is a synchronous Ethernet slave. A synchronous Ethernet slave port uses the incoming timing information.
speed {10 | 100 | 1000 | 10000}
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
varies depending on platform
Sets the link to 10 Mb/s.
Sets the link to 100 Mb/s.
Sets the link to 1000 Mb/s.
Sets the link to 10 000 Mb/s.
[no] loopback {internal} [service svc-id sap sap-id src-mac SA dst-mac DA]
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures 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 may need to assign the resources of a front-panel port if the internal virtual port resources are not available.
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:
Use this command for testing VLL services.
Enabling this command for testing VPLS services leads to rapid MAC address movement to another port, as source or destination MAC address swap is not performed.
This command affects all services provisioned on the port.
Before enabling this command, turn off all layer 2 and IP control protocols (such as LACP, EFM, 802.1x and so on) on the device and its peer to prevent errors such as protocol flaps resulting from timeout and so on.When port loopback feature is to be used for multicast traffic with IGMP snooping enabled in the service, the corresponding datapath has to be statically created using static IGMP groups.
For loop back to be functional, the following are not required:
SFP or XFPs need not be inserted into the device.
Ethernet cables need not be plugged in for copper ports.
When the loop back command is enabled, ensure that Ethernet parameters such as, speed, duplex, auto-negotiation and so on are not modified.
For port loopback with mac-swap:
This command is available for testing VLL services and VPLS services only.
When enabled, the command affects all services provisioned on the port.
Before enabling this command, turn off all layer 2 and IP control protocols (such as LACP, EFM, 802.1x and so on) on the device and its peer to prevent errors such as protocol flaps because of timeout and so on.When port loopback feature is to be used for multicast traffic with IGMP snooping enabled in the service, the corresponding datapath has to be statically created using static IGMP groups.
When using port loopback with mac-swap enabled, for unicast and unknown-unicast packets, if the packet matches the configured source and destination MAC address it will be swapped and looped back in the service. For broadcast and multicast packets, if the packet matches the configured source MAC address, its source MAC address will be used as the destination MAC address and the system MAC address will be the source MAC address. The packet is looped back in the service as a unicast packet. All other packets sent to the loopback port will be dropped since forwarding of these packets after loopback can potentially cause network wide problems.
For loop back to be functional, the following are not required:
SFP or XFPs need not be inserted into the device.
Ethernet cables need not be plugged in for copper ports.
When the loop back is enabled, ensure that Ethernet parameters such as, speed, duplex, auto-negotiation and so on are not modified.
When the loopback is enabled, ensure that service parameter and attributes such as ingress qos policy, accounting records, ingress/egress ACLs, and so on are not modified.
With port loopback in use, the SAP ingress ACLs with IP-criteria is not recommended for use, since only MAC addresses are swapped.
The recommended procedure for using port loopback with mac-swap is:
Configure the service and SAP on which loopback is to be enabled.
Configure the assigned loopback port to be used.
Send bidirectional learning frames on the SAP under test and spoke or uplink from a traffic tester or one can install static MAC for this purpose. Installing a static MAC is highly recommended because the recommended procedure for enabling port loopback is to shutdown the port –> enable loopback and then execute no shutdown the port.
Enable port loopback and specify the service, SAP, and the source MAC address (SA) and the destination MAC address (DA). All packets with source MAC matching SA are the only ones processed in the context of the SAP on ingress after the loopback. Any other traffic is dropped on ingress to avoid issues resulting from MAC movement and flooding issues in other services/SAPs because the whole port is in loopback.
When the port is in loopback, software disable learning and aging on the specified SAP. After the loopback configuration is removed for the port, then the software enables learning and aging for specified SAP. Therefore, port loopback with mac-swap cannot be used for learning or aging.
It is not recommend to change the service parameters for the SAP and the service when loopback is active. Additionally use of commands which clears the FDB, and so on is highly discouraged.
Remove the loopback on the SAP port to bring the sap out of MAC swap with loopback mode
The no form of this command disables physical layer loopback on the Ethernet port.
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:
Disable the port, execute the command config>port>shutdown.
Enable loop back, execute the command config>port>ethernet>loopback internal
Enable the port, execute the command config>port>no shutdown.
Perform the required tests.
Disable the port, execute the command config>port>shutdown.
Disable loop back, execute the command config>port>ethernet>no loopback internal
Enable the port, execute the command config>port>no shutdown.
Enable the required services.
Listed below is the recommended sequence of commands to be executed to perform loop back when SFP or XFPs are inserted into the device:
Insert SFP or XFPs. SFP or XFPs are not required in case of fixed copper ports.
Enable the port and execute the command config>port>[no] shutdown.
Disable the port and execute the command config>port>shutdown.
Enable loop back and execute the command config>port>ethernet>loopback internal.
Enable the port and execute the command config>port>no shutdown.
Perform the required tests.
Disable the port and execute the command config>port>shutdown.
Disable loop back and execute the command config>port>ethernet>no loopback internal
Enable the port and execute the command config>port>no shutdown.
Enable the required services.
Listed below is the sequence of commands to be executed to perform loop back when SFP or XFPs are changed:
Disable the port, execute the command config>port>shutdown.
Insert the new SFP or XFP.
Enable the port and execute the command config>port>no shutdown.
Disable the port and execute the command config>port>shutdown.
Enable loop back and execute the command config>port>ethernet>loopback internal.
Enable the port and execute the command config>port>no shutdown.
Perform the required tests.
Disable the port and execute the command config>port>shutdown.
Disable loop back and execute the command config>port>ethernet>no loopback internal.
Enable the port and execute the command config>port>no shutdown.
Enable the required services.
Specifies the unique service identification number or string 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 on which this service is defined.
Specifies the physical port identifier portion of the SAP.
Specifies the source MAC address.
Specifies the destination MAC address.
ssm
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command enables Ethernet Synchronous Status Message (SSM).
code-type [sonet | sdh]
config>port>ethernet>ssm
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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. 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).
sdh
Specifies the values used on a G.781 Option 1 compliant network.
Specifies the values used on a G.781 Option 2 compliant network.
[no] tx-dus
config>port>ethernet>ssm
config>port>sonet-sdh
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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.
no tx-dus