ethernet
config>port
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure access parameters.
This context can only be used when configuring Ethernet LAN ports on an appropriate MDA.
autonegotiate [limited]
no autonegotiate
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document
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. Note that 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
Specifies tht the Ethernet interface will automatically negotiate link parameters with the far end, but will only advertise the speed and duplex mode specified by the Ethernet and commands.
connection-type connection-type
config>port>ethernet
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
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 that will be used.
When configured as SFP port it 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.
When configured as 'auto', software will attempt to detect the type of interface in use based on whether the copper cable is plugged in or the SFP optic is plugged in. It is not allowed to plug in copper cable and SFP optics into the Ethernet combo port at the same time.
When combo port is used for SyncE, the connection type has to be set to either sfp or copper. SyncE is not supported with connection-type as auto.
The combo port can be configured either as a SFP port or a copper port or set for automatic detection. That is, both the interfaces cannot be used simultaneously (even when 'auto' is set, software selects one of the ports based on the interface plugged in).
sfp (7210 SAS-K 2F1C2T)
auto (7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C)
Specifies the type of Ethernet combo port.
crc-monitor
config>port>ethernet
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command configures Ethernet CRC Monitoring parameters.
[no] sd-threshold threshold [multiplier multiplier]
config>port>ethernet>crc-monitor
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
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 return 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
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
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 no form of this command reverts to the default value of 1. If the multiplier keyword is omitted, the multiplier will return to the default value of 1.
no sf-threshold
Specifies the rate of CRC errored Ethernet frames.
Specifies the multiplier used to scale the CRC error ratio.
[no] window-size seconds
config>port>ethernet>crc-monitor
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
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
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command brings 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
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
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 is supported 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.
Specifies the Ethertype to expect, in decimal or hexadecimal format.
duplex {full | half}
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document
This command enables the context for the configuration of the duplex mode of a Fast Ethernet port. 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.
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
This command configures the rate of traffic leaving the network.
The no form of this command reverts to the default value.
For 7210 SAS-D and 7210 SAS-Dxp devices, the max-burst parameter configures a maximum-burst (in kilobits) associated with the egress-rate. This is an optional parameter; if not defined then, by default, it is set to 64 kbits for a 1G port and 98 kbits for a 10G port. The user cannot configure max-burst without configuring egress-rate. 7210 SAS-D devices do not support 10G ports. See the 7210 SAS-D, Dxp Quality of Service Guide for more information.
no egress-rate
The egress rate in Kbps.
Specifies the maximum egress burst in kilobits. This parameter is configurable only on 7210 SAS-D and 7210 SAS-Dxp.
efm-oam
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure EFM-OAM attributes.
[no] accept-remote-loopback
config>port>ethernet>efm-oam
Supported on all 7210 SAS platforms as described in this document
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
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
Specifies that the port has the capability to initiate negotiation and monitoring activities.
Specifies that the port 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
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 is applicable to all platforms except for the 7210 SAS-D. On the 7210 SAS-D, the minimum transmit interval is 500 msec and multiplier is 4.
transmit-interval 10 multiplier 5
Specifies the transmit interval, in 100 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
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
encap-type {dot1q | null | qinq}
no encap-type
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document
This command configures the encapsulation method used to distinguish customer traffic on an Ethernet access port, or different VLANs on a port.
On the 7210 SAS-D ETR, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, the qinq encapsulation type can be configured for both access and access-uplink ports. The null and dot1q encapsulation types can be specified only for access ports.
On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, the null and dot1q encapsulation types can be specified for network ports. The dot1q and qinq encapsulation types can be specified for hybrid ports.
The no form of this command reverts to the default.
encap-type null
Specifies that the ingress frames carry 802.1Q tags where each tag signifies a different service.
Specifies that the 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-K 2F1C2T and 7210 SAS-K 2F6C4T
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-K 2F1C2T and 7210 SAS-K 2F6C4T
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-K 2F1C2T and 7210 SAS-K 2F6C4T
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-K 2F1C2T and 7210 SAS-K 2F6C4T
Commands in this context configure ETH-BN message handling.
[no] receive
config>port>ethernet>eth-cfm>mep>eth-bn
7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T
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-K 2F1C2T and 7210 SAS-K 2F6C4T
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).
frame-based-accounting
no frame-based-accounting
config>port>ethernet
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command configures per port frame-based accounting. It can be enabled or disabled on each port. When enabled, all the shapers rates and queues statistics on that port also account for the Ethernet Layer 1 overhead (of 20 bytes) in both ingress and egress direction. That is all ingress queue shaper rates, egress queue shaper rates and aggregate SAP shaper rate account for the Ethernet overhead.
The no form of this command disables frame-based-accounting.
no frame-based-accounting
hold-time {[up hold-time up] [down hold-time] [seconds | centiseconds]}
no hold-time
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document
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 zero, but if the hold-time down interval is greater than zero, interface down transitions are not advertised to upper layers until the hold-time down interval has expired. Likewise, an interface is immediately advertised as up to the rest of the system if the hold-time up interval is zero, but if the hold-time up interval is greater than zero, up transitions are not advertised until the hold-time up interval has expired.
The no form of this command reverts to the default values.
hold-time up 0 down 0 seconds
Specifies the delay, in seconds or centiseconds, to notify the upper layers after an interface transitions from a down state to an up state.
Specifies the delay, in seconds or centiseconds, to notify the upper layers after an interface transitions from an up state to a down state.
Specifies the units of the hold time in seconds or centiseconds.
[no] lacp-tunnel
config>port>ethernet
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
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
no oper-group
oper-group name
config>port>ethernet
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command associates the context to which it is configured 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.
poe [plus] [plusplus] [hpoe]
no poe
config>port>ethernet
7210 SAS-Dxp 16p and 7210 SAS-Dxp 24p
This command enables PoE on the specified port and allows the user to configure the PoE device (PD) type that can be connected to the port.
This command must be used to enable PoE on a port before connecting a PD to the port. When a PD is connected to an enabled port, the software attempts to detect the type of device (that is, PoE, PoE+, PoE++, or HPoE) and the power it is requesting. If the detection is successful and the power request is within the maximum PoE power budget configured, power is supplied to the connected device. Otherwise, the request is denied and no power is provided to the port.
The user must configure the maximum PoE power budget for the system using the configure system poe max-poe-power-budget command before enabling PoE on any port. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for more information about this command.
The no form of this command disables PoE, PoE+, PoE++, and HPoE capabilities on the specified port. If PoE is disabled, the software does not attempt to detect the characteristics of the connected PD.
poe
Keyword to support PoE+ and allow 802.3at (Type-2) PoE devices to be connected to the port and request up to 30 W.
Keyword to support PoE++ and allow 802.3bt (Type-3) PoE devices to be connected to the port and request up to 60 W.
Keyword to support HPoE and allow 802.3bt (Type-4) PoE devices to be connected to the port and request up to 90 W.
qinq-etype value
no qinq-etype
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document
This command configures the Ethertype used for Q-in-Q encapsulation.
When the qinq-etype is configured to a value other than the default value on a port, the outermost tag in the received packet is matched against the configured value and the inner tag's etype is matched against the default value. If there is a match, 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 is supported 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 reverse 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 value. The default value is not user configurable.
0x8100
Specifies the qinq-etype to expect, in hexadecimal or decimal notation.
statistics
config>port>ethernet
7210 SAS-D, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Commands in this context configure the counters associated with the egress port.
egress
config>port>ethernet>statistics
7210 SAS-D, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Commands in this context configure egress per queue statistics counter, which counts the total number of packets forwarded.
port-clock {master | slave | automatic}
config>port>ethernet
7210 SAS-D ETR, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command forces the copper port to be a master or slave or set it for automatic detection. 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 autonegotiation of the link parameters and is automated; there is no management intervention in this process. When 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.
For copper ports, when port-clock is set to automatic, the Ethernet interface will automatically negotiate clock mastership along with other link parameters with the far end. Depending upon the capabilities of the two ends, one will be master the other will be slave for clocking.
This command is ignored for all ports, other than copper ports that support SyncE.
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 this command is used.
The following conditions must be met before using SyncE on the fixed port copper ports:
Autonegotiation (or autonegotiation 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 port clock must be set to slave, if the port is used as a source-port for any reference. On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C platform, when using combo ports, the connection-type must be set to copper. The port-clock parameter is ignored if the connection-type is set to sfp or auto.
automatic
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.
Specifies that the Ethernet interface will automatically negotiate clock mastership along with other link parameters with the far end. Depending upon the capabilities of the two ends, one will be master the other will be slave for clocking.
speed {10 | 100 | 1000}
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document
This command configures the port speed of a fast Ethernet port when autonegotiation is disabled. If the port is configured to autonegotiate, the speed parameter is ignored. Speed cannot be configured for ports that are part of a LAG.
On the 7210 SAS-Dxp, the 10 Mb/s port speed is not supported for an SFP port using a copper SFP.
speed 100
Keyword to set the link to 10 Mb/s.
Keyword to set the link to 100 Mb/s.
Keyword to set the link to 1000 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
This configures simple port loopback and port loopback with MAC swap. When the optional parameter internal is specified, it provides the port loopback without the mac-swap functionality. It enables physical layer loopback of the packets that egress on the SAPs created on an 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 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C only support port loopback without MAC swap (that is, only the config>port>ethernet> loopback internal command applies). Port loopback with MAC swap is not supported on these platforms.
This 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 is 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 SAS platforms.
The following information describes guidelines 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 caused by 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 loopback 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 loopback command is enabled, ensure that Ethernet parameters such as speed, duplex, autonegotiation and so on are not modified.
The following information describes guidelines 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 caused by 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 as the forwarding of these packets after loopback can potentially cause network wide problems.
For loopback 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 loopback is enabled, ensure that Ethernet parameters such as, speed, duplex, autonegotiation 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 because 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 caused by MAC movement and flooding issues in other services/SAPs, since the whole port is in loopback.
When the port is in loopback, software disable learning and aging on the specified SAP. When 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 loopback command is not saved in the configuration file across a reboot.
The following list is the recommended sequence of commands to be executed to perform loopback:
Disable the port, execute the config>port>shutdown command.
Enable loopback, execute the config>port>ethernet>loopback internal command
Enable the port, execute the config>port>no shutdown command.
Perform the required tests.
Disable the port, execute the config>port>shutdown command.
Disable loopback, execute the config>port>ethernet>no loopback internal command
Enable the port, execute the command config>port> no shutdown.Enable the required services. The following list is the recommended sequence of commands to be executed to perform loopback 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 config>port>no shutdown command.
Disable the port and execute the config>port>shutdown command. Enable loopback and execute the config>port>ethernet>loopback internal command.
Enable the port and execute the config>port>no shutdown command.Perform the required tests.
Disable the port and execute the config>port>shutdown command. Disable loopback and execute the config>port>ethernet>no loopback internal command.
Enable the port and execute the config>port>no shutdown command.Enable the required services.
The following list is the sequence of commands to be executed to perform loopback when SFP or XFPs are changed:
Disable the port, execute the config>port>shutdown command.
Insert the new SFP or XFP.
Enable the port and execute the config>port>no shutdown command. Disable the port and execute the config>port>shutdown command. Enable loopback and execute the config>port>ethernet>loopback internal command.
Enable the port and execute the config>port>no shutdown command.
Perform the required tests.
Disable the port and execute the config>port>shutdown command.
Disable loopback and execute the config>port>ethernet>no loopback internal command.
Enable the port and execute the config>port>no shutdown command.
Enable the required services.
Enable loopback and execute the config>port>ethernet>loopback internal command.
Perform the required tests.
Disable loopback and execute the config>port>ethernet>no loopback internal command.
Enable the required services.
Sets the associated port or channel into a internal loopback mode. A internal loopback loops the frames from the local router back at the framer.
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
7210 SAS-D ETR, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command enables Ethernet Synchronous Status Message (SSM) capability on a synchronous Ethernet port. Synchronous Ethernet must be enabled on the MDA (using the sync-e command) before SSM can be enabled.
code-type [sonet | sdh]
config>port>ethernet>ssm
7210 SAS-D ETR, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
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 (not supported on 7210 SAS-Dxp)
7210 SAS-D ETR, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command forces 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 for timing purposes from the 7210 SAS.
no tx-dus