ethernet
config>port
This command enables access to the context to configure Ethernet port attributes on all cards, modules, and chassis that support Ethernet. For the Packet Microwave Adapter card, this command does not apply to ports that support microwave awareness.
access
config>port>ethernet
This command enables access to the context to configure access mode parameters.
egress
config>port>ethernet>access
This command enables access to the context to configure the CIR rate for the aggregate of all the unshaped 4-priority SAPs on the port and to configure the shaper policy.
shaper-policy name
no shaper-policy
config>port>ethernet>access>egress
This command assigns a shaper policy to the specified hybrid port.
For hybrid ports, the shaper policy is independently assigned to access or network egress traffic. When the Ethernet port mode is changed to hybrid mode, the default policy is assigned to access and network traffic. To change an access or network policy, use the commands config>port>ethernet> access>egress>shaper-policy and config>port>ethernet> network>egress>shaper-policy.
For access egress per-customer aggregate shaping, the shaper policy is assigned to a port and SAPs on that port must be bound to a shaper group within the shaper policy bound to that port.
The shaper policy defines shaper parameters such as shaper group, and PIR and CIR rates. The shaper policy is defined in the config>qos>shaper-policy context. Refer to the 7705 SAR Quality of Service Guide, ‟QoS for Hybrid Ports” and ‟Per-Customer Aggregate shapers (Multiservice Site)”, for more information.
The port shaper rate applies to the bulk of access and network traffic. Thus, once the configured egress shaper rate is reached, both the access and network traffic scheduling pauses.
For hybrid ports, there can be a single shaper policy on access egress and a single shaper policy on network egress. Therefore, all the SAP traffic and all the network traffic is each bound to its own shaper group in the shaper policy (access and network shaper policy, respectively). In other words, shaped SAPs and the bulk/aggregate of unshaped SAPs are shaped together as per the shaper policy assigned to the access egress. A similar behavior applies to network traffic, where the shaped interfaces and the bulk/aggregate of unshaped interfaces are shaped together as per the shaper policy assigned to the network egress.
The no form of this command reverts to the default.
‟default”
specifies an existing shaper policy name
unshaped-sap-cir cir-rate
no unshaped-sap-cir
config>port>ethernet>access>egress
This command sets the CIR rate for the aggregate of all the unshaped 4-priority SAPs on the port. The default cir-rate is 0 kb/s. When the cir-rate is set to max, the CIR rate adopts the maximum rate of the port, which is set using the egress-rate sub-rate command.
If the cir-rate is higher than the sub-rate, the cir-rate is stored in the configuration database but the sub-rate limit is used.
On a Gen-3-based port, this command can be set for mix-and-match LAG SAP purposes, but is not applied to the Gen-3-based port. See LAG Support on Mixed-Generation Hardware for more information.
The no form of the command sets the unshaped-sap-cir CIR rate to 0 kb/s.
no unshaped-sap-cir
the CIR rate for the aggregate of all the unshaped 4-priority SAPs on the port
autonegotiate [limited]
no autonegotiate
config>port>ethernet
This command enables speed autonegotiation and duplex autonegotiation on Ethernet ports.
The 8-port Gigabit Ethernet Adapter card, 10-port 1GigE/1-port 10GigE X-Adapter card in x10-1gb-sfp mode, and Packet Microwave Adapter card support speed autonegotiation and duplex autonegotiation on all SFP ports. Each port can run in full-duplex mode or in half-duplex mode at 10 or 100 Mb/s.
The 6-port Ethernet 10Gbps Adapter card and the 7705 SAR-X support speed autonegotiation and duplex autonegotiation on all SFP ports; SFP+ ports do not support autonegotiation. Each SFP port can run in full-duplex mode or half-duplex mode at 10 Mb/s or 100 Mb/s, and in full-duplex mode at 1 Gb/s. Each SFP+ port can run in full-duplex mode at 10 Gb/s.
Speed autonegotiation takes place automatically — all ports are configured for speed autonegotiation by default. Speed autonegotiation might need to be disabled (for example, if a port must be forced to a certain speed or to avoid speed negotiation loops between the Ethernet Adapter card and other devices). To turn off speed autonegotiation for a port, the user configures the port speed manually.
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. Also, when autonegotiation is disabled, the tx and rx pauses are enabled automatically (the tx and rx pauses are negotiated with the far end if autonegotiation is enabled).
If the autonegotiate limited keyword option is specified, the port will autonegotiate but will only advertise a specific speed and duplex mode. The speed and duplex mode advertised are the 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.
The no form of this command disables autonegotiation on this port.
Autonegotiation must not be disabled on an Ethernet port if the port is connected to an MPR-e radio.
For fiber SFP-based Gigabit Ethernet ports, it is recommended that autonegotiation be enabled. If autonegotiation is disabled and the configured speed does not correctly match the capability of the SFP, then the operational state of the link will remain down. Attempting to configure a speed and duplex mode to 1000 Mb/s, half-duplex, is an invalid combination and will be blocked from CLI.
For RJ-45 interfaces, autonegotiation is mandatory for 1000Base-T operation (if disabled, the behavior is undefined).
If autonegotiation is turned off, the reception and transmission of IEEE 802.3x flow control frames is enabled by default and cannot be disabled. For more information, see Flow Control on Ethernet Ports.
Ports belonging to a microwave link must have limited autonegotiation enabled before the link can be added to a LAG.
autonegotiate
cfm-loopback priority {low | high | dot1p} [match-vlan {vlan-range | none}]
no cfm-loopback
config>port>ethernet
This command enables the port to respond to Loopback Messages (LBMs) and sets the queuing and scheduling conditions for handling CFM LBM frames. The user selects the desired QoS treatment by enabling the CFM loopback and including the high or low priority with the high or low keyword. The queue parameters and scheduler mappings associated with the high and low keywords are preconfigured and cannot be altered by the user.
The priority dot1p and match-vlan keywords apply only to physical ring ports on the 2-port 10GigE (Ethernet) Adapter card and 2-port 10GigE (Ethernet) module.
The parameters and mappings have the following settings:
for network egress, where profiled scheduling is the choice of scheduling:
high-priority: either cir = port_speed, which applies to all frames that are scheduled via an in-profile scheduler, or round-robin (RR) for all other (network egress queue) frames that are in-profile
low-priority: either cir = 0, pir = port_speed, which applies to all frames that are scheduled as out-of-profile, or RR for all other frames that are out-of-profile
for network egress or access egress, where 4-priority scheduling is enabled:
high-priority: either cir = port_speed, which applies to all frames that are scheduled via an expedited in-profile scheduler, or RR for all other (network egress queue) frames that reside in expedited queues and are in an in-profile state
low-priority: either cir = 0, pir = port_speed, which applies to all frames that are scheduled via a best effort out-of-profile scheduler, or RR for all other frames that reside in best-effort queues and are in an out-of-profile state
for the 8-port Gigabit Ethernet Adapter card, the 10-port 1GigE/1-port 10GigE X-Adapter card, and for the v-port on the 2-port 10GigE (Ethernet) Adapter card and 2-port 10GigE (Ethernet) module, for network egress, where 16-priority scheduling is enabled:
high-priority: has higher priority than any user frames
low-priority: has lower priority than any user frames
for the physical ring ports on the 2-port 10GigE (Ethernet) Adapter card or 2-port 10GigE (Ethernet) module, which can only operate as network egress, the priority of the LBR frame is derived from the dot1p setting of the received LBM frame. Based on the assigned ring-type network queue policy, dot1p-to-queue mapping is handled using the same mapping rule that applies to all other user frames.
CFM loopback support on a physical ring port on the 2-port 10GigE (Ethernet) Adapter card or 2-port 10GigE (Ethernet) module differs from other Ethernet ports. For these ports, cfm-loopback is configured using dot1p and an optional list of up to 16 VLANs. The null VLAN is always applied. The CFM Loopback Message will be processed if it does not contain a VLAN header, or if it contains a VLAN header with a VLAN ID that matches one in the configured match-vlan list.
The no form of the command disables the handling of CFM loopback frames.
no cfm-loopback
sets the queue parameters and scheduler mappings, as described above
sets the queue parameters and scheduler mappings, as described above
sets the queue parameters and scheduler mappings on a physical ring port, as described above
sets the matching VLAN IDs that will allow a CFM loopback on a physical ring port when priority is set to dot1p, as described above
crc-monitor
config>port>ethernet
This command enables the context to configure Ethernet CRC monitoring parameters.
sd-threshold threshold [multiplier multiplier]
no sd-threshold
config>port>ethernet>crc-monitor
This command configures the error rate threshold at which the signal degrade condition is declared on an Ethernet interface. The error rate threshold value is the ratio of errored frames over total frames received, which is calculated as an average over the time set by the sliding window. The value is calculated as M ✕ 10E-N, where M is the optional multiplier used to increase the error ratio, and N is the rate of errored frames allowed (threshold). For example, 3 ✕ 10E-3 sets the error rate threshold at 3 errored frames per 1000 total frames received. If no window-size is configured, a default of 10-s is used. The CRC errors on the interface are sampled once per second.
The multiplier keyword is optional. If the multiplier keyword is omitted, the default value of 1 is used.
The no form of the command disables sd-threshold monitoring.
no sd-threshold
specifies the threshold value
specifies the multiplier value
sf-threshold threshold [multiplier multiplier]
no sf-threshold
config>port>ethernet>crc-monitor
This command configures the error rate threshold at which the signal fail condition is declared on an Ethernet interface. The error rate threshold value is the ratio of errored frames over total frames received, which is calculated as an average over the time set by the sliding window. The value is calculated as M ✕ 10E-N, where M is the optional multiplier used to increase the error ratio, and N is the rate of errored frames allowed (threshold). For example, 3 ✕ 10E-3 sets the error rate threshold at 3 errored frames per 1000 total frames received. If no window-size is configured, a default of 10-s is used. The CRC errors on the interface are sampled once per second.
The multiplier keyword is optional. If the multiplier keyword is omitted, the default value of 1 is used.
The no form of the command disables sf-threshold monitoring.
no sf-threshold
specifies the threshold value
specifies the multiplier value
window-size seconds
no window-size
config>port>ethernet>crc-monitor
This command configures the 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 sd-threshold and the sf-threshold commands.
A sliding window (window-size) is used to calculate a statistical average of CRC error statistics collected every second. Each second, the oldest statistics are dropped from the calculation. For example, if the default 10-s sliding window is configured, at the 11th second the oldest second of statistical data is dropped and the 11th second is included. This sliding average is compared against the configured SD and SF thresholds to determine if the error rate over the window exceeds one or both of the thresholds, which will generate an alarm and log event.
The no form of the command disables window-size monitoring.
10
specifies the size of the sliding window over which the errors are measured
dot1q-etype 0x0600 to 0xffff
no dot1q-etype
config>port>ethernet
This command specifies the Ethertype expected when the port’s encapsulation type is dot1q.
IEEE 802.1q (also known as VLAN tagging) defines a process to channelize a single Ethernet port or v-port into VLANs. Each VLAN can represent a customer or an application. Up to 4096 VLANs can be configured per port. For more information on VLANs and VLAN tagging, refer to ‟VLL Services” in the 7705 SAR Services Guide.
The Ethertype specifies the protocol being carried in an Ethernet frame. In 802.1q, the Ethertype is set to the Tag Protocol Identifier (TPID) value of 0x8100, which identifies the frame as an IEE 802.1Q-tagged frame. As well, 2 bytes of Tag Control Information (TCI), followed by 2 bytes containing the frame’s original Ethertype are added to the frame. Together, the TPID and TCI make up the VLAN tag.
For Ethernet ports, when the port encap-type is qinq, the dot1q-etype value sets the Ethertype for the inner VLAN tag. The qinq encapsulation type is not supported by v-ports.
Network ports do not allow dot1q-etype settings.
The no form of this command resets the dot1q-etype value to the default.
0x8100
specifies the Ethertype to expect
down-when-looped
config>port>ethernet
This command enables the down-when-looped feature on Ethernet ports or v-ports. When the down-when-looped feature is activated, a keepalive loop PDU is transmitted periodically toward the network. The port listens for returning keepalive loop PDUs. A loop is detected if any of the received PDUs have an Ethertype value of 9000 and the source and destination MAC addresses are identical to the MAC address of the port. When a loop is detected, the port is immediately brought down.
Ethernet port-layer line loopbacks and Ethernet port-layer internal loopbacks can be enabled on the same port with the down-when-looped feature. EFM OAM cannot be enabled on the same port with the down-when-looped feature.
keep-alive timer
no keep-alive
config>port>ethernet>down-when-looped
This command configures the time interval between the keepalive PDUs transmitted toward the network during loop detection by the down-when-looped feature.
10 s
the interval between keepalive PDUs
retry-timeout timer
no retry-timeout
config>port>ethernet>down-when-looped
This command configures the minimum wait time before re-enabling the Ethernet port or v-port after it is brought down due to a loop detection.
120
the minimum wait time before re-enabling the Ethernet port or v-port
[no] use-broadcast-address
config>port>ethernet>down-when-looped
This command configures the down-when-looped feature to declare a loop when the destination MAC address matches the broadcast MAC address instead of the MAC address of the Ethernet port or v-port.
duplex {full | half}
config>port>ethernet
This command configures the duplex mode of an Ethernet or Fast Ethernet port when autonegotiation is disabled.
The 10-port 1GigE/1-port 10GigE X-Adapter card must be in x10-1gb-sfp mode to support this command.
SFP slots hosting Ethernet or Fast Ethernet SFPs can be configured to full-duplex or half-duplex mode when autonegotiation is disabled. Duplex autonegotiation is automatically turned off when the user sets the mode with this command. SFP slots hosting optical GigE SFPs only support full-duplex mode; duplex autonegotiation is not supported.
On 10 Gb/s ports, the mode is always full duplex and cannot be changed. This includes the ring Ethernet XFP ports and the v-port on the 2-port 10GigE (Ethernet) Adapter card and 2-port 10GigE (Ethernet) module.
full
efm-oam
config>port>ethernet
This command configures EFM-OAM attributes.
[no] accept-remote-loopback
config>port>ethernet>efm-oam
This command enables reactions to loopback control OAMPDUs from peers.
The no form of this command disables reactions to loopback control OAMPDUs.
no accept-remote-loopback
hold-time time-value
no hold-time
config>port>ethernet>efm-oam
This command sets the amount of time that EFM-OAM will wait before going from a non-operational state to an operational state.
If EFM-OAM goes from an operational state to a non-operational state (other than link-fault), it enters the hold-time period. During this time, EFM-OAM continues to negotiate with the peer if possible, but will not transition to the ‟up” state until the hold time has expired.
If EFM-OAM goes down due to a lower-level fault (for example, the port goes down and EFM-OAM enters the link-fault state), the hold timer is not triggered. When the lower-level fault is cleared, EFM-OAM immediately starts running on the port and transitions to the operational state as soon as possible.
If EFM-OAM goes down because the user administratively disables the protocol, EFM-OAM immediately transitions to the disabled state. When the user re-enables EFM-OAM, the protocol enters the hold time period and EFM-OAM is not operational until the hold time expires.
A hold-time value of 0 indicates that EFM-OAM returns to the operational state without delay.
The hold time affects only the transition from a non-operational state to an operational state; it does not apply to a transition from an operational state to a non-operational state.
no hold-time
the number of seconds that EFM-OAM will wait before returning to an operational state from a non-operational state
[no] ignore-efm-state
config>port>ethernet>efm-oam
This command decouples the EFM OAM protocol from the port state and operational state.
When this command is configured on the port, any failure in the EFM protocol state (discovery, configuration, time-out, loops, and so on) does not affect the port. Only a protocol warning message is raised to indicate issues with the protocol.
When the command is not configured on a port, the port state is affected by any EFM OAM protocol fault or clear condition.
If the port is a member of a microwave link, the ignore-efm-state command must be enabled before the EFM OAM protocol can be activated. This restriction is required because EFM OAM is not compatible with microwave links.
no ignore-efm-state
mode {active | passive}
config>port>ethernet>efm-oam
This command configures the mode of OAM operation for this Ethernet port.
Active mode causes the port to initiate the negotiation process and continually send out efm-oam information PDUs. 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
[no] transmit-interval interval [multiplier multiplier]
config>port>ethernet>efm-oam
This command configures the transmit interval of OAMPDUs.
interval 10, multiplier 5
specifies the transmit interval
specifies the multiplier for the transmit-interval to set the local link down timer
[no] tunneling
config>port>ethernet>efm-oam
This command enables EFM OAMPDU tunneling. OAMPDU tunneling is required when a loopback is initiated from a router end and must be transported over the existing network infrastructure to the other end. Enabling tunneling will allow the PDUs to be mapped to Epipes so that the OAM frames can be tunneled over MPLS to the far end.
To enable Ethernet EFM OAM 802.3ah on the port, use the efm-oam>no shutdown command.
The no form of the command disables tunneling.
no tunneling
egress-rate sub-rate [include-fcs] [allow-eth-bn-rate-changes] [hold-time hold-time]
no egress-rate
config>port>ethernet
This command configures the rate of traffic leaving the network.
With the include-fcs option, the egress rate limit is applied to the traffic rate egressing the port with the 4-byte Ethernet FCS field included. If this option is not configured, the egress rate limit is applied to the traffic rate egressing the port without the 4-byte Ethernet FCS field included, and the actual rate of packets leaving the port is slightly higher than the configured egress rate value.
The include-fcs option is not supported on the 7705 SAR-A Fast Ethernet ports (ports 9 to 12) or 4-port SAR-H Fast Ethernet module. On the 6-port SAR-M Ethernet module, the include-fcs option is always on and cannot be disabled to compensate for the 4-byte FCS.
The allow-eth-bn-rate-changes option enables the Y.1731 ETH-BN client MEP option on the port. In applications such as a point-to-point microwave link, where degradation on the line can result in reduced link bandwidth, the egress rate can be dynamically changed based on the available bandwidth on the link as indicated by the ETH-BN server. When enabled, the received rate overrides the configured sub-rate for the port. For information on ETH-BN, including which Ethernet ports support this functionality, refer to the 7705 SAR OAM and Diagnostics Guide, ‟ITU-T Y.1731 Ethernet Bandwidth Notification (ETH-BN)”.
The bandwidth indicated by the ETH-BN server includes the FCS; therefore, the include-fcs option must be selected if the allow-eth-bn-rate-changes option is selected or the dynamically changed bandwidth will not match the intended rate.
The hold-time is used to limit the number of bandwidth changes as requested by the ETH-BN server. After a rate change occurs based on a Bandwidth Notification Message (BNM), any BMN received before the hold timer expires will be ignored.
The no form of this command returns the value to the default.
no egress-rate
the egress rate in kb/s
the egress rate limit is applied to the traffic rate egressing the port with the 4-byte Ethernet FCS field included. This option must be selected if the allow-eth-bn-rate-changes option is selected; otherwise, the dynamically changed bandwidth will not match the intended rate.
enables the Y.1731 ETH-BN client MEP option on the port. The egress rate will be dynamically changed to the bandwidth indicated in messages received from an ETH-BN server MEP. When enabled, the received rate overrides the configured sub-rate for the port.
configures the hold time for egress rate bandwidth changes based on a received BNM, in seconds
encap-type {dot1q | null | qinq}
no encap-type
config>port>ethernet
This command configures the encapsulation method used to distinguish customer traffic on an Ethernet access port, network v-port, or different VLANs on a network port.
Before an MPR-e radio can be configured on an MWA port (see radio), the port must have an encapsulation type of dot1q.
The qinq encapsulation type is not supported by v-ports.
The no form of this command restores the default.
See also dot1q-etype and qinq-etype for information on tagging and encapsulation.
null
ingress frames carry 802.1Q tags, where each tag signifies a different service
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.
ingress frames carry two stacked tags, where the outer tag is the service provider tag and the inner tag is the customer service tag as defined in 802.1ad
[no] group-encryption
config>port>ethernet
This command enables network group encryption (NGE) on the Ethernet port. When NGE is enabled on the port, all received Layer 2 IS-IS and LLDP packets are considered to be NGE packets and must be encrypted using a valid set of keys from any preconfigured key group on the system.
The no form of the command disables NGE on the Ethernet port. NGE cannot be disabled unless all key groups and IP exception filters are removed.
no group-encryption
encryption-keygroup keygroup-id direction {inbound | outbound}
no encryption-keygroup direction {inbound | outbound}
config>port>ethernet>group-encryption
This command is used to bind a key group to an Ethernet port for inbound or outbound packet processing. When configured in the outbound direction, packets egressing the router use the active-outbound-sa associated with the configured key group. When configured in the inbound direction, received packets must be encrypted using one of the valid security associations configured for the key group.
The no form of the command removes the key group from the Ethernet port in the specified direction.
no encryption-keygroup direction inbound
no encryption-keygroup direction outbound
the ID number of the key group being configured
binds the key group in the inbound direction
binds the key group in the outbound direction
hold-time {[up hold-time-up] [down hold-time-down]}
no hold-time
config>port>ethernet
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, 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, interface up transitions are not advertised until the hold-time-up interval has expired.
If the hold-time-down or hold-time-up value is 0, interface down and interface up transitions are immediately reported to upper layer protocols.
The no form of this command reverts to the default values.
down 0 or up 0 — no port link dampening is enabled; link transitions are immediately reported to upper layer protocols
the interval, in seconds, before an interface transition from a down state to an up state is reported to upper layer protocols
the interval, in seconds, before an interface transition from an up state to a down state is reported to upper layer protocols
ingress-rate ingress-rate cbs size [bytes | kilobytes]
no ingress-rate
config>port>ethernet
This command configures a policing action to rate-limit the ingress traffic. Ingress-rate enforcement uses dedicated hardware for rate limiting, however software configuration is required at the port level (ingress-rate limiter) to ensure that the network processor or adapter card or port never receives more traffic than they are optimized for.
The configured ingress rate ensures that the network processor does not receive traffic greater than this configured value on a per-port basis. Once the ingress-rate value is reached, all subsequent frames are dropped. The ingress-rate limiter drops excess traffic without classifying whether the traffic has a higher or lower priority.
Similar to the egress-rate configuration, the ingress-rate configuration survives port mode changes. If a port mode is changed (for example, from access to network mode), the ingress rate and configured CBS still remain when the port comes back up.
The no form of this command returns the value to the default.
no ingress-rate
the ingress rate in Mb/s
specifies the committed burst size that the hard policer can accept while complying with the configured ingress rate. Set the cbs value to at least two times the ingress packet size so that the datapath can make a proper policing and forwarding decision.
CBS is integrated with the ingress-rate command and you must always specify the CBS size every time you configure the ingress rate. If you use the default CBS size, then explicitly indicate that it is the CBS default.
specifies the committed burst size in bytes or kilobytes. If configured in bytes, the committed burst size must be a multiple of 256 bytes and must include the bytes parameter. If configured in kilobytes, the maximum value is 127 and must include the kilobytes parameter. If configured as default, the value is set to 130816 bytes.
src-pause
no src-pause
config>port>ethernet>ingress-rate
This command sends a notification to slow down the transmission rate when it exceeds the bandwidth limit.
If incoming traffic exceeds the configured ingress rate, an src-pause frame is sent to the far end to hold transmission (src-pause delay timer). When the src-pause delay timer expires, the far end resumes transmission. The src-pause delay timer varies based on the difference between the incoming traffic rate and the configured ingress rate on the port. If the difference is large, then the far end must wait for a longer period before resuming transmission. The src-pause frame helps to prioritize far-end traffic so that the ingress-rate limiter does not drop high-priority traffic.
The ingress-rate limiter can be configured with or without src-pause; however, src-pause is disabled whenever the ingress-rate limiter is disabled.
The no form of this command disables the src-pause feature.
This command is blocked for the 6-port SAR-M Ethernet module.
no src-pause
lacp-tunnel
no lacp-tunnel
config>port>ethernet
This command enables LACP packet tunneling for the Ethernet port. When tunneling is enabled, the port does not process any LACP packets, but tunnels them instead. A port with LACP packet tunneling enabled cannot be added as a member of a Link Aggregation Group (LAG).
The no form of this command disables LACP packet tunneling for the Ethernet port.
no lacp-tunnel
loopback {line | internal} {timer {0 | 30 .. 86400} | persistent} [swap-src-dst-mac]
no loopback
config>port>ethernet
This command configures timed line loopbacks on Ethernet network and access ports, timed line loopbacks on ring Ethernet network ports, untimed line loopbacks on Ethernet access ports, and timed and untimed internal loopbacks on Ethernet ports.
For Ethernet ports, a line loopback loops frames received on the corresponding port back towards the transmit (egress) direction inside the network processor. Line loopbacks are supported on ports configured in network or access mode.
You can swap the source and destination MAC addresses of the received frames using the swap-src-dst-mac keyword. The swap-src-dst-mac keyword is not supported on ring Ethernet ports.
An internal loopback loops the frames that are coming in an egress direction from the fabric towards the framer, back to the fabric. This type of loopback is usually referred to as an equipment loopback. Internal loopbacks are supported on ports configured in access mode.
Loopback timers can be configured for 30 s to 86400 s. All non-zero timed loopbacks are turned off under the following conditions: an adapter card reset, an activity switch, or timer expiry. Line or internal loopbacks can also be configured as a latched loopback by setting the timer to 0 s, or as a persistent loopback with the persistent keyword.
Latched and persistent loopbacks are enabled indefinitely until turned off by the user. Latched loopbacks survive adapter card resets and activity switches, but are lost if there is a system restart. Persistent loopbacks survive adapter card resets and activity switches and can survive a system restart if the admin-save or admin-save-detail command was executed prior to the restart. Latched (untimed) persistent loopbacks can be enabled only on Ethernet access ports.
If a loopback exists on a port, it must be disabled or the timer must expire before another loopback can be configured on the same port. An Ethernet loopback cannot be configured on a port that has EFM-OAM enabled on it; EFM-OAM cannot be enabled on a port that has an Ethernet loopback enabled on it.
Persistent loopbacks are the only Ethernet loopbacks saved to the database by the admin-save and admin-save-detail commands.
The no form of this command disables the specified type of loopback.
places the associated Ethernet port or ring Ethernet port into line loopback mode
places the associated Ethernet access port into internal loopback mode; not supported on ring Ethernet ports
places the associated Ethernet access port or ring Ethernet port into persistent loopback mode
swaps source and destination MAC addresses for Ethernet line loopbacks; not supported on ring Ethernet ports
the timer set for Ethernet loopbacks, in seconds
mac ieee-address
no mac
config>port>ethernet
This command assigns a specific MAC address to an Ethernet port, ring Ethernet port, or v-port. 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 returns the MAC address to the default value.
a default MAC address is assigned by the system
specifies the 48-bit MAC address in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee, and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC, and non-IEEE reserved MAC addresses.
mode {access | network | hybrid}
no mode
config>port>ethernet
This command configures an Ethernet port for access, network, or hybrid mode operation, or configures a ring Ethernet port or v-port for network mode. On ring Ethernet ports and the v-port, the mode is always network and cannot be changed.
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 or channel. Once an Ethernet port has been configured for access mode, multiple services can be configured on it.
A network port participates in the service provider transport or infrastructure network when network mode is selected.
A hybrid Ethernet port allows the combination of network and access modes of operation on a per-VLAN basis and must be configured for either dot1q or qinq encapsulation.
A hybrid port must use dot1q encapsulation to be configured as a network IP interface. Binding a network IP interface to a qinq encapsulation is blocked. In hybrid mode, qinq encapsulation is for access mode use only.
If the hybrid port is configured for dot1q encapsulation, the user configures a SAP inside a service or a network IP interface as follows:
configure a SAP under config>service by providing the SAP ID, which must include the port-id value of the hybrid port and an unused VLAN tag value. The format is port-id:qtag1. A SAP of format port-id:* is also supported.
configure a network IP interface under config>router>if>port by providing the port-name, which consists of the port-id of the hybrid port and an unused VLAN tag value. The format is port-id:qtag1. The user must explicitly enter a valid value for qtag1. The port-id:* value is not supported on a network IP interface. The VLAN tag space on the port (range of 0 to 4094) is shared among VLAN SAPs and VLAN network IP interfaces.
If the hybrid port is configured for qinq encapsulation, the user configures a SAP inside a service as follows:
configure a SAP under config>service by providing the SAP ID, which must include the port-id value of the hybrid 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 no form of this command restores the default.
access (except as listed below)
network
10-port 1GigE/1-port 10GigE X-Adapter card (in 1-port 10GigE mode, the port operates in network mode only)
2-port 10GigE (Ethernet) Adapter card
2-port 10GigE (Ethernet) module
configures the port as service access
configures the port for transport network use
configures the port for hybrid use (transport network and service access per VLAN)
mtu mtu-bytes
no mtu
config>port>ethernet
This command configures the maximum payload MTU size for an Ethernet port or a v-port on an Ethernet Ring adapter card (for ring Ethernet ports, the MTU value is fixed at 9728 bytes).
The port-level MTU parameter indirectly defines the largest physical packet the port can transmit or the far-end Ethernet port can receive. Packets to be transmitted over a given port that are larger than the MTU of the port will be fragmented or discarded, depending on whether the DF bit is set in the packet header.
If the port mode or encapsulation type is changed, the MTU assumes the default values of the new mode or encapsulation type.
The no form of this command restores the default values.
The default MTU value depends on the port type, mode, and encapsulation as listed in Table: Port MTU Default and Maximum Values .
sets the maximum allowable size of the MTU, expressed as an integer (see Table: Port MTU Default and Maximum Values )
[no] phy-tx-clock {auto-pref-master | auto-pref-slave | slave | master}
config>port>ethernet
This command configures the 1000Base-T physical layer transmit clock. The mode affects the establishment of the master-slave relationship between two ports sharing a link segment during auto-negotiation. The master port uses a local clock to determine the timing of transmitter operations. The slave port recovers the clock from the signal it receives and uses the signal to determine the timing of transmitter operations. For ports that do not support 1000Base-T, the value defaults to N/A and cannot be changed.
The phy-tx-clock configuration is supported on SFP ports whether or not the SFP is inserted. The phy-tx-clock command applies only to copper-based RJ-45 synchronous Ethernet ports. The command can be used on an SFP port that supports fiber and copper, but the command has no effect if a fiber SFP is installed.
The proper value must be set to ensure that the synchronous Ethernet clock relay is correctly configured. See the 7705 SAR Basic System Configuration Guide for more information about synchronous Ethernet.
The default value for the MWA 1000Base-T Ethernet ports on the Packet Microwave Adapter card is master. On other adapter cards, the default value is auto-pref-slave for ports that support 1000Base-T Ethernet connections. The default value is n/a for ports that do not support 1000Base-T Ethernet connections.
prefers to be master during autonegotiation
prefers to be slave during autonegotiation
forces the port to be the slave clocking source
forces the port to be the master clocking source
poe [plus]
no poe
config>port>ethernet
The poe command enables an RJ-45 or RJ point five port that is Power over Ethernet (PoE) capable to deliver power to a ‟Powered Device” at levels compatible with the IEEE 802.3af standard.
The poe plus command enables an RJ-45 or RJ point five port that is PoE+ capable to deliver power to a ‟Powered Device” at levels compatible with the IEEE 802.3at standard.
On the 7705 SAR-H, 7705 SAR-Hc, and 6-port SAR-M Ethernet module, a PoE-capable port can be configured for PoE and PoE+. On the 7705 SAR-Wx, a PoE-capable port only supports PoE+ and can only be enabled using the poe plus command.
On the 7705 SAR-H, before a port can be configured for either PoE or PoE+, the PoE power source option must first be configured as either internal or external using the config>system>poe-power-source command; refer to the 7705 SAR Basic System Configuration Guide, ‟System Command Reference”, for information.
When the 7705 SAR-H is configured for the internal power source option, PoE capability is allowed on ports 5 and 6 only. Port 5 can be configured for PoE+ but in that case, port 6 cannot support PoE. When the system is configured for the external power source option, a mix of PoE and PoE+ is allowed on ports 5, 6, 7, and 8. PoE+ is supported only on ports 5 and 7. Table: Supported PoE/PoE+ Combinations on the 7705 SAR-H describes the allowed mix of PoE and PoE+ ports on the 7705 SAR-H.
PoE Power Supply Source |
Port 5 |
Port 6 |
Port 7 |
Port 8 |
Supported PoE/PoE+ Combinations |
---|---|---|---|---|---|
Internal |
PoE |
PoE |
No PoE |
No PoE |
Two PoE ports |
Internal |
PoE+ |
No PoE |
No PoE |
No PoE |
One PoE+ port |
External |
PoE |
PoE |
PoE |
PoE |
Four PoE ports |
External |
PoE |
PoE |
PoE+ |
PoE |
Three PoE ports and one PoE+ port |
External |
PoE+ |
No PoE |
PoE+ |
PoE |
One PoE port and two PoE+ ports |
On the 6-port SAR-M Ethernet module, ports 5 and 6 on the module can each support PoE. Port 5 can also support PoE+, but if it is configured for PoE+, then port 6 cannot support PoE power.
On the 7705 SAR-Hc, ports 5 and 6 each support PoE and PoE+. If configured for PoE, both ports can be used for PoE simultaneously. Both ports are also capable of supporting PoE+ but not simultaneously; if one port is configured for PoE+, the other port can only be configured for PoE. Ports 5 and 6 can also operate in non-PoE mode.
On the 7705 SAR-Wx, port 5 (the RJ-45 port labeled PoE) supports PoE+. The port can also operate in non-PoE+ mode.
To disable PoE/PoE+ on a port and prevent it from delivering power, use the no form of the command. Performing a shutdown command on the port does not disable PoE/PoE+ on the port.
n/a
enables PoE+ on the 7705 SAR-H, 7705 SAR-Hc, 7705 SAR-Wx, and 6-port SAR-M Ethernet module
ptp-asymmetry ptp-asymmetry
no ptp-asymmetry
config>port>ethernet
This command configures the PTP asymmetry delay delta on an Ethernet port. The command corrects for known asymmetry for time of day/phase recovery of PTP packets on both local and downstream PTP slave clocks as well as on end-to-end transparent clocks.
the value in nanoseconds that the forward path delay varies from the mean path delay; the value can be a negative number
qinq-etype 0x0600 to 0xffff
no qinq-etype
config>port>ethernet
This command specifies the Ethertype expected when the port’s encapsulation type is qinq. The qinq-etype value sets the Ethertype for the outer VLAN tag when qinq encapsulation is used.
IEEE 802.1ad (also known as VLAN stacking) defines a process to channelize a single Ethernet port or v-port into double-tagged VLANs. Each VLAN can represent a customer or an application. Each tag allows for up to 4096 VLANs to be configured on a port (4096 ✕ 4096 total). For more information on VLANs and VLAN tagging, refer to ‟VLL Services” in the 7705 SAR Services Guide.
The Ethertype specifies the protocol being carried in an Ethernet frame. In 802.1q, the Ethertype is set to the Tag Protocol Identifier (TPID) value of 0x8100, which identifies the frame as an IEEE 802.1Q-tagged frame. As well, 2 bytes of Tag Control Information (TCI), followed by 2 bytes containing the frame’s original Ethertype are added to the frame for each tag (4 bytes total). Together, the TPID and TCI make up a VLAN tag.
The qinq-etype command is not supported by v-ports.
Network ports do not allow qinq-etype settings.
The no form of this command resets the qinq-etype value to the default.
0x8100
specifies the Ethertype to expect
[no] report-alarm [signal-fail] [remote] [local] [no-frame-lock] [high-ber]
config>port>ethernet
This command specifies when and if to generate alarms and alarm clear notifications for this port.
The command applies only to the physical 10GigE ports on the 7705 SAR-X, 6-port Ethernet 10Gbps Adapter card, 2-port 10GigE (Ethernet) Adapter card, and 2-port 10GigE (Ethernet) module, and on the 10-port 1GigE/1-port 10GigE X-Adapter card in 1-port 10GigE mode (select x1-10GigE-sf+ with the mda-mode command).
reports an Ethernet signal lost alarm
reports remote faults
reports local faults
reports a ‟not locked on the ethernet framing sequence” alarm
reports a high bit error rate alarm
speed {10 | 100 | 1000 | 2500 | 10000}
config>port>ethernet
This command configures the port speed of an Ethernet port, ring Ethernet port, or v-port when autonegotiation is disabled.
100 (for Fast Ethernet ports on the 7705 SAR-A (ports 9 to 12), 7705 SAR-Hc (ports 3 and 4), 4-port SAR-H Fast Ethernet module, and 6-port SAR-M Ethernet module (ports 1 and 2))
1000 (for Gigabit Ethernet ports on all adapter cards, modules, and fixed platforms)
2500 on a v-port (this default cannot be changed)
10000 (for the 10-port 1GigE/1-port 10GigE X-Adapter card in 1-port 10GigE mode, 2-port 10GigE (Ethernet) Adapter card, 2-port 10GigE (Ethernet) module, 6-port Ethernet 10Gbps Adapter card (ports 5 and 6), 7705 SAR-X (ports 1/2/7 and 1/3/7)
sets the link speed to 10 Mb/s
sets the Ethernet port speed to 100 Mb/s
sets the Ethernet port speed to 1000 Mb/s (only supported on GigE SFPs)
sets the v-port speed to 2500 Mb/s (only supported on a v-port)
sets the ring Ethernet port speed (only supported on GigE XFPs) and the SFP+ ports speed on the 6-port Ethernet 10Gbps Adapter card or the 7705 SAR-X to 10 000 Mb/s
ssm
config>port>ethernet
This command enables the Ethernet Synchronization Message Channel (ESMC) capability on a synchronous Ethernet port on the following:
2-port 10GigE (Ethernet) Adapter card
2-port 10GigE (Ethernet) module
6-port Ethernet 10Gbps Adapter card
8-port Gigabit Ethernet Adapter card
10-port 1GigE/1-port 10GigE X-Adapter card
Packet Microwave Adapter card
4-port SAR-H Fast Ethernet module
7705 SAR-A
7705 SAR-Ax
7705 SAR-H
7705 SAR-Hc
7705 SAR-M
7705 SAR-Wx
7705 SAR-X
The ssm command is enabled and disabled using the no shutdown and shutdown commands.
On the 2-port 10GigE (Ethernet) Adapter card and 2-port 10GigE (Ethernet) module, SSM frames received on the ring Ethernet ports are extracted for processing through the v-port. Therefore, the v-port must be active (that is, in no shutdown mode) in order for SSM to function. The v-port must also be active in order for the 2-port 10GigE (Ethernet) Adapter card or 2-port 10GigE (Ethernet) module to transmit SSM frames. No additional interface or IP configuration is required on the v-port for SSM.
shutdown
code-type {sonet | sdh}
config>port>ethernet>ssm
This command specifies whether to use SDH or SONET values for the encoding of synchronous status messages on a:
synchronous ring Ethernet port on the 2-port 10GigE (Ethernet) Adapter card
synchronous ring Ethernet port on the 2-port 10GigE (Ethernet) module
synchronous Ethernet port on the 6-port Ethernet 10Gbps Adapter card
synchronous Ethernet port on the 8-port Gigabit Ethernet Adapter card
synchronous Ethernet port on the 10-port 1GigE/1-port 10GigE X-Adapter card
synchronous Ethernet port on the Packet Microwave Adapter card
synchronous Ethernet port on the 4-port SAR-H Fast Ethernet module
synchronous Ethernet port on the 7705 SAR-A
synchronous Ethernet port on the 7705 SAR-Ax
synchronous Ethernet port on the 7705 SAR-H
synchronous Ethernet port on the 7705 SAR-Hc
synchronous Ethernet port on the 7705 SAR-M
synchronous Ethernet port on the 7705 SAR-Wx
synchronous Ethernet port on the 7705 SAR-X
sdh
specifies the values used on a G.781 option 1 compliant network
specifies the values used on a G.782 option 1 compliant network
[no] tx-dus
config>port>ssm
config>port>ethernet>ssm
This command sets the quality level value transmitted from the Synchronization Status Messaging (SSM) channel of the following ports to QL-DUS/QL-DNU (do not use for synchronization for timing purposes):
synchronous Ethernet port on the 2-port 10GigE (Ethernet) Adapter card
synchronous Ethernet port on the 2-port 10GigE (Ethernet) module
synchronous Ethernet port on the 6-port Ethernet 10Gbps Adapter card
synchronous Ethernet port on the 8-port Gigabit Ethernet Adapter card
synchronous Ethernet port on the 10-port 1GigE/1-port 10GigE X-Adapter card
synchronous Ethernet port on the Packet Microwave Adapter card
synchronous Ethernet port on the 4-port SAR-H Fast Ethernet module
synchronous Ethernet port on the 7705 SAR-A
synchronous Ethernet port on the 7705 SAR-Ax
synchronous Ethernet port on the 7705 SAR-H
synchronous Ethernet port on the 7705 SAR-Hc
synchronous Ethernet port on the 7705 SAR-M
synchronous Ethernet port on the 7705 SAR-Wx
synchronous Ethernet port on the 7705 SAR-X
enabled for fiber ports
disabled (no tx-dus) for copper ports
util-stats-interval seconds
config>port>ethernet
This command configures the interval over which to calculate and display an average percentage of the maximum possible port utilization for an Ethernet port.
300
the utilization statistics calculation interval in seconds
[no] vlan-filter filter-id
config>port>ethernet
This command associates a VLAN filter policy with an ingress ring port on the 2-port 10GigE (Ethernet) Adapter card or 2-port 10GigE (Ethernet) module.
Filter policies control the forwarding and dropping of packets based on matching criteria. Only one filter policy can be applied to a ring port at a time. The same filter policy can be applied to both ring ports.
The filter-id must already be defined before the vlan-filter command is executed. If the filter policy does not exist, the operation will fail and an error message will be displayed.
The no form of the command removes any configured filter-id association with the ring port. The filter policy cannot be deleted until it is removed from all ring ports where it is applied.
n/a
the VLAN filter policy ID number or filter name
xgig {lan | wan}
config>port>ethernet
This command configures the specified 10-Gb/s interface in LAN or WAN mode. When configuring the port for WAN mode, you can change some SONET/SDH parameters to reflect the SONET/SDH requirements for this port. When you configure a port for LAN mode, all SONET/SDH parameters are predetermined and not configurable. The command is supported on the 7705 SAR-X, 6-port Ethernet 10Gbps Adapter card, 10-port 1GigE/1-port 10GigE X-Adapter card, 2-port 10GigE (Ethernet) Adapter card, and 2-port 10GigE (Ethernet) module.
On the 6-port Ethernet 10Gbps Adapter card, both 10-Gb/s interfaces (ports 5 and 6) operate in the same xgig mode, either LAN mode or WAN mode. Setting the xgig mode for either port sets the mode for both ports.
lan
specifies that the port operates in LAN mode
specifies that the port operates in WAN mode
xor-mode {rj45 | rjp5 | sfp}
config>port>ethernet
This command configures the operational mode of Ethernet XOR combination ports. Ethernet XOR ports on the 7705 SAR-A, 7705 SAR-Ax, 7705 SAR-H, and 7705 SAR-X can be configured to operate as either RJ-45 ports or SFP ports. Ethernet XOR ports on the 6-port SAR-M Ethernet module can be configured to operate as either RJ point five ports or SFP ports. The mode can be configured on each port independently. Refer to the individual hardware installation guides for more information.
rj45 (for applicable 7705 SAR chassis); rjp5 (for 6-port SAR-M Ethernet module)
specifies that the port operate as a 10/100/1000Base-T electrical RJ-45 port (applicable 7705 SAR chassis only)
specifies that the port operate as a 10/100/1000Base-T electrical RJ point five port (6-port SAR-M Ethernet module only)
specifies that the port operate as an SFP port