Card, Adapter Card, and Port Command Reference

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

The no form of this command removes any description string from the context. For the serial context, the no form of this command restores the default value.

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

The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they can be deleted.

When used with the ethernet>efm-oam command, shutdown enables tunneling on the port (see tunneling), and no shutdown enables Ethernet EFM OAM 802.3ah.

The no form of this command administratively enables an entity.

Note: The config>port> shutdown command does not remove power on RJ-45 ports that are Power over Ethernet (PoE/PoE+) capable. You must use the config>port>ethernet>no poe command to turn the power off; see poe for more information.

This mandatory command is the first step in activating the IOM software: designating it a slot position in the chassis. On the 7705 SAR, the slot number is always 1. The IOM software must be activated before the adapter cards and ports can be configured. The no form of this command removes the card from the configuration. All associated ports, services, and adapter cards must be shut down.

This mandatory command is the second step in activating the IOM software: designating the card type. The card type can be preprovisioned, meaning that the card does not need to be installed in the chassis. On the 7705 SAR, the card type is always iom-sar.

A card must be provisioned (configured) before an adapter card or port can be configured.

A card can only be provisioned in a slot that is vacant, which means that no other card can be provisioned for that particular slot. To reconfigure a slot position, use the no form of this command to remove the current information. Port and adapter card information must be shut down.

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

The no form of this command removes the card from the configuration. This operation requires that the card be administratively shut down. All dependencies to ports on this card must be shut down and removed from the configuration before issuing the no card-type command.

This mandatory command enables access to a card’s MDA CLI context to configure adapter cards.

This command enables the 7705 SAR to interoperate with SDH networks that use subnetwork connection protection (SNCP). When ais-propagation is enabled, the 7705 SAR can use SDH signaling to make pseudowire switching decisions on Cpipes configured for redundancy.

For more information about 7705 SAR interoperation with SDH SNCP, refer to the 7705 SAR OS Services Guide, “AIS Fault Propagation” section.

This command defines the clocking mode and the associated timestamp frequency (if differential or dcr-acr clocking mode is configured).

All clock modes are supported on the following:

Only adaptive mode is supported on the following chassis and cards:

Only differential mode is supported on the following cards:

This command enables the fabric port statistics counter to count egress traffic toward a specified adapter card. The CSM allows the collection of fabric statistics from only one fabric port at any given time. To change the port statistics counter to a different adapter card, turn off statistics collection on the assigned adapter card by using no fabric-stats-enabled and then enabling statistics collection on another adapter card.

This command configures the set of software services that are enabled for a specific adapter card.

The cem-atm-ppp and cem-fr-hdlc-ppp parameter values are used to configure the appropriate encapsulation methods that are required to support pseudowire services. These values apply to the following adapter cards:

The card-level encapsulation capabilities must be configured before the encap-type parameter is configured at the port level.

The x10-1gb-sfp and x1-10gb-sf+ parameter values are used for the 10-port 1GigE/1-port 10GigE X-Adapter card to define whether the card operates in 10-port 1GigE mode or 1-port 10GigE mode.

The no form of this command sets the mda-mode back to the card’s default mode. For the 10-port 1GigE/1-port 10GigE X-Adapter card, the default mode is x1-10gb-sf+. For the T1/E1 ASAP adapter cards and 4-port DS3/E3 Adapter card, the default mode is cem-atm-ppp. All service and port/channel configurations associated with the adapter card must be removed before the mda-mode can be changed.

This mandatory command provisions a specific adapter card or module type to the device configuration for the slot. The adapter card or module can be preprovisioned, but it must be provisioned before ports can be configured. Ports can be configured once the adapter card or module is properly provisioned.

A maximum of 6 adapter cards can be installed in a 7705 SAR-8 chassis, and a maximum of 12 adapter cards and 4 XMDA adapter cards can be installed in a 7705 SAR-18 chassis. One module can be installed in 7705 SAR-M variants that support modules. A maximum of two modules can be installed in a 7705 SAR-H chassis. Only one adapter card or module can be provisioned per MDA or module slot. To modify an MDA or module slot, shut down all port associations.

A medium severity alarm is generated if an adapter card or module is inserted that does not match the adapter card or module type configured for the slot. This alarm is cleared when the correct adapter card or module is inserted or the configuration is modified. A high severity alarm is raised if an administratively enabled adapter card or module is removed from the chassis. This alarm is cleared if either the correct adapter card or module type is inserted or the configuration is modified. A low severity trap is issued if an administratively disabled adapter card or module is removed.

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

The no form of this command deletes the adapter card or module from the configuration. The adapter card or module must be administratively shut down before it can be deleted from the configuration. Before an adapter card or module can be shut down, all port associations with this adapter card or module, for example SAPs and IP interfaces, must be shut down first.

This command enables the context to configure voice parameters on the 6-port E&M Adapter card, 8-port Voice & Teleprotection card, 8-port FXO Adapter card, and 6-port FXS Adapter card.

This command specifies the companding law to be used on the 6-port E&M Adapter card, 8-port Voice & Teleprotection card, 8-port FXO Adapter card, and 6-port FXS Adapter card.

To change this parameter, all ports associated with the card must be in shutdown mode and no channels can be defined on the card. A change in the companding law results in a corresponding change to the signaling-type default. The signaling-type applies only to the 6-port E&M Adapter card.

This command specifies the signaling type to be used on the 6-port E&M Adapter card.

To change this parameter, all ports associated with the 6-port E&M Adapter card must be in shutdown mode and no channels can be defined on the card.

The signaling type is selectable on a per-card basis depending on companding type. When A-Law companding is configured, the signaling type is automatically type V. When Mu-Law companding is configured, all signaling types can be selected; however, the only supported configurations are both ends of the connection operating in the same mode (for example, Type I to Type I) or one end operating in Type I mode and the other in Type V mode.

This command enables the access context to configure QoS policy parameters for the specified adapter card.

This command enables the network context to configure QoS policy parameters for the specified adapter card.

This command enables the context to configure the QoS policy parameters for ingress traffic, in either an access or network context, for the specified adapter card.

This command configures (applies) the ingress fabric policy, in either an access or network context, for the specified adapter card.

Fabric profiles do not apply to the Auxiliary Alarm card.

The no form of this command reverts the fabric-policy-id to the default value.

This command specifies the network ingress queue policy that defines queue parameters such as CBS, high-priority-only burst size, MBS, CIR, and PIR rates, as well as forwarding class-to-queue mappings. The network queue policy is defined in the config>qos>network-queue context. Refer to the 7705 SAR OS Quality of Service Guide, “Network Queue QoS Policies”, for more information.

The no form of this command reverts to the default.

This command specifies the QoS policy parameters for ring traffic in a network, for the 2-port 10GigE (Ethernet) Adapter card or 2-port 10GigE (Ethernet) module.

This command specifies the network queue policy to be applied to the add/drop port on the bridging domain side of a ring adapter card. The network queue policy is defined in the config>qos>network-queue context. Refer to the 7705 SAR OS Quality of Service Guide, “Network Queue QoS Policies”, for more information.

The ring ports and the add/drop port cannot use the same non-default network queue policy that is being used by the v-port and any other port on other cards.

This command specifies the network QoS policy for the ring. Only a ring type network QoS policy can be assigned to a port on the bridging domain side of a ring adapter card.

This command enables access to the context to configure external alarm attributes on 7705 SAR Ethernet ports (supported on all platforms with Ethernet ports), on the Auxiliary Alarm card and on the four alarm inputs on the fan module (for the 7705 SAR-8), alarm connector (for the 7705 SAR-F, 7705 SAR-M (all variants), 7705 SAR-H, and 7705 SAR-Hc), and alarm module (for the 7705 SAR-18).

When configuring custom alarms for an Ethernet port, the port must be configured for 100 Base-Tx operation with autonegotiation disabled.

This command creates or removes alarms.

The no form of this command disables the alarm attributes for the specified alarm. The alarm must be in the shutdown state before the no form of the command can be performed.

This command generates output to chassis alarm relays and LEDs for the specified alarm.

The no form of this command disables the generation of output to chassis alarm relays and LEDs.

This command generates raise/clear log events for the specified alarm and controls SNMP trap generation for the raise/clear log events.

The no form of this command disables the generation of raise/clear log events.

This command configures the severity level for the specified alarm.

The alarm must be disabled before the severity level can be modified.

If the alarm generates raise/clear log events and SNMP traps (enabled by the log command), the severity of the raise log events and SNMP traps is controlled by this configuration. The severity level of the clear log events and SNMP traps is warning.

If the alarm generates output to chassis alarm relays and LEDs (enabled by the chassis-alarming command), the severity level of the alarm output is controlled by this configuration. For chassis relay alarms, only the critical, major and minor levels of severity apply. (There are three LEDs that represent each of them.)

This command provides the context to configure the thresholds for the specified alarm.

This command provides the context to configure analog trigger thresholds for the specified alarm.

This command configures the analog voltage level thresholds for the specified alarm.

The analog input level threshold cannot be changed from no level when there are no analog inputs configured as triggers. When all analog inputs are removed from the trigger list, the level is automatically changed to no level. The analog input level threshold cannot be changed to no level when there is analog input in the trigger list. When the first analog input is added to the alarm trigger, the level is automatically changed to gt 0.

The no form of this command removes the analog voltage level threshold.

This command configures the inputs that will trigger the alarm. An alarm can be configured to trigger on any configured input or only when all enabled configured inputs are active. Administratively disabled inputs are ignored for alarm triggering.

Digital inputs are considered normally open. This means that a digital input becomes active only if it closes. Analog inputs have a customizable voltage threshold. This threshold can be configured using the thresholds command. Analog inputs become active when this threshold is crossed.

The no form of this command removes the trigger.

This command provides the context to configure the external alarm inputs on 7705 SAR Ethernet ports, on the Auxiliary Alarm card and on the four alarm inputs on the fan module (for the 7705 SAR-8), alarm connector (for the 7705 SAR-F and 7705 SAR-M (all variants), 7705 SAR-H, and 7705 SAR-Hc), alarm module (for the 7705 SAR-18).

An alarm input must be associated with an alarm in order for the input to be triggered. See the trigger command. An input can be associated with up to four alarms.

This command configures the debounce time associated with detecting and clearing an alarm input. Debounce time is not supported on alarm inputs on Ethernet ports.

The no debounce form of the command sets both the detect time and clear time to 0.

This command provides the context to configure the external alarm output relays.

This command configures a name for the alarm input or output relay. The configured name must be unique within the external alarms context; therefore, it must not be the same as an alarm-input name configured for the trigger or input command, or an alarm-output name configured for the output command. For example, alarm-1/3.d-1 or doorOpen1 cannot be used as a name for any alarm input, and relay-1/3.d-5 or doorHolder5 cannot be used as a name for any output relay.

The no form of this command does not associate a name with the alarm input or output relay.

This command configures the normal condition of the digital input – either normally open or normally closed. You cannot configure the normal condition on alarm inputs on Ethernet ports.

This command enables access to the context to configure APS on SONET/SDH ports and assigns an APS group ID. Both working and protection circuits must be configured with the same APS group ID on either the same 7705 SAR node (SC-APS) or on two 7705 SAR nodes (MC-APS).

This command configures APS on SONET/SDH ports. An APS group contains a working and protection circuit with the same APS group ID on either a single 7705 SAR node (SC-APS) or on two 7705 SAR nodes (MC-APS).

The working circuit must be connected to the peer working circuit, and the protection circuit must be connected to the peer protection circuit.

The aps command is only available for APS groups, not for physical ports.

This command specifies the time interval, in 100s of milliseconds, between “I am operational” messages sent by the protection and working circuits to their neighbor in an MC-APS group. The advertise-interval value is valid only for an MC-APS.

This command specifies how much time can pass without the node receiving an advertise packet from its neighbor before the MC-APS signaling link is considered operationally down.The hold time is in 100s of milliseconds and is usually the advertise-interval value multiplied by 3.

This command configures hold-down timers to debounce signal failure conditions (lais, b2err-sf) and signal degrade conditions (b2err-sd) for 1+1 unidirectional SC-APS switching mode. If the signal fail or signal degrade conditions exceed the configured hold-down time, APS is activated.

This command specifies the neighbor's IP address in an MC-APS group. If the value of the neighbor IP address is set to 0.0.0.0, or not set, this implies that the APS group is configured as an SC-APS group.The route to the neighbor must not traverse the MC-APS member (working or protection) circuits. It is recommended that the neighbor IP address configured be on a shared network between the routers that own the working and protection circuits. The node should be connected with a direct interface to ensure optimum failover time.By default, no neighbor address is configured and both the working and protection circuits should be configured on the same router as an SC-APS group.

This command configures a physical port that will act as the protection circuit for this APS group.

The protection circuit port must contain only the default configuration and cannot belong to another APS group. The protection circuit port must be of the same type as the working circuit (SONET/SDH) for the APS group; if it is not, the command will return an error.

A protection circuit can only be added if the working circuit already exists. The protection circuit must be removed from the configuration before the working circuit can be removed.

When a port is a protection circuit of an APS group, the configuration options available in the config>port port-id>sonet-sdh context are not allowed for that port unless they are in the following exception list:

When a port is configured as a protection circuit of an APS group, the configurations listed above and all service configurations related to the APS port are operationally inherited by the protection circuit. If the protection circuit cannot inherit the configurations (due to resource limitations), the configuration attempt fails and an error is returned to the user.

The protection circuit must be shut down before it can be removed from the APS group port. The inherited configuration for the circuit and APS operational commands for that circuit are not preserved when the circuit is removed from the APS group.

The no form of this command removes the protection circuit.

This command configures how RDI alarms (line, path, section) are generated on physical circuits of an APS port. The command is only supported in 1+1 unidirectional SC-APS mode. When you configure RDI alarms on a port on the 2-port OC3/STM1 Channelized Adapter card, the second port is automatically configured with a matching RDI alarms setting. As a consequence, both ports will then support only 1+1 unidirectional SC-APS mode.

This command configures how long the 7705 SAR waits before switching back to the working circuit after it has been restored to service.

If the minutes value is changed, it takes effect at the next initiation of the wait-to-restore (WTR) timer.

This command does not modify the length of a WTR timer that has already been started. The WTR timer of a non-revertive switch can be assumed to be infinite.

The no form of this command restores the default (non-revertive) mode – the switch back does not occur unless the protection circuit fails or it is manually switched by the operator.

This command configures the switching mode for the APS port. SC-APS supports both bi-directional and uni-1plus1; MC-APS supports only bi-directional switching mode.

This command configures a physical port that will act as the working circuit for this APS group.

The working circuit port must contain only the default configuration and cannot be part of another APS group. The working circuit must be created before the protection circuit.

When a port is a working circuit of an APS group, the configuration options available in the config>port port-id>sonet-sdh context are not allowed for that port unless they are in the following exception list:

When a port is configured as a working circuit of an APS group, the configurations listed above and all service configurations related to the APS port are operationally inherited by the working circuit from the APS group ID. If the working circuit cannot inherit that configuration (for example, due to resource limitations), the configuration attempt fails and an error is returned to the user.

The working circuit must be shut down before it can be removed from an APS group. The inherited configuration for the circuit and APS operational commands for that circuit are not preserved when the circuit is removed from the APS group.

All configurations for the APS group under the config>port context and its submenus and all configuration for services that use this APS group ID are preserved as a non-activated configuration since the APS group no longer has any physical circuits assigned.

The no form of this command removes the working circuit. The working circuit can only be removed from the configuration after the protection circuit has been removed.

This command configure a microwave link on a 7705 SAR-8 or 7705 SAR-18.

The no form of this command removes the microwave link configuration.

This command enables the context to configure microwave link parameters.

This command configures dampening timers on a microwave link. Dampening timers guard against excessive link transitions reported to upper layer protocols.

The no form of this command removes the dampening timers configuration.

This command enables or disables peer discovery on the microwave link.

Peer discovery is used to discover the IP addresses of remote routers over the microwave link, as well as the physical ports of the remote routers corresponding to the primary radios for the microwave link.

Ports with peer discovery disabled do not send peer discovery packets and ignore any received peer discovery packets. The CLI does not display the IP address of peers when peer discovery is disabled.

This command enables protection switching on a microwave link.

The no form of this command removes the protection switching on a microwave link.

This command configures an MPR-e radio for a microwave link.

The no form of this command removes an MPR-e spare radio from the specified port

Note: You cannot remove an MPR-e main radio that is associated with a microwave link. The microwave link must be deleted and then re-configured with the desired MPR-e radio.

This command configures the filename of the MPR-e radio database.

The no form of this command removes the MPR-e radio database configuration.

This command specifies a name to be associated with an MPR-e radio.

The no form of this command removes the name configured for the MPR-e radio.

This command configures the MPR-e radio to operate in standalone mode.

The no form of this command removes the standalone designation and sets the MPR-e radio in MWA mode.

This command mutes the transmitter on the radio MPR-e radio.

The no form of this command disables the mute configuration.

This command configures the type of revertive switching on the microwave link. Revertive switching occurs when the MPR-e radio operation switches from the spare radio back to the main radio after a fault condition is cleared.

The no form of this command removes the revertive switching configuration.

This command enables access to the context to configure ports, multilink bundles, and IMA groups. Before a port can be configured, the chassis slot must be provisioned with a valid card type and the adapter card slot must be provisioned with a valid adapter card type. (See the card and mda commands.)

This command enables or disables digital diagnostic monitoring (DDM) events for the port. DDM is supported on Ethernet SFP ports, OC3 SONET SFP ports, and v-ports.

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

This command configures the DWDM ITU channel for a tunable adapter card optical interface. The channel is expressed in a form that is derived from the laser's operational frequency. For example, 193.40 THz corresponds to DWDM ITU channel 34 in the 100 GHz grid and 193.45 THz corresponds to DWDM ITU channel 345 in the 50 GHz grid. The provisioned adapter card type must have DWDM tunable optics (2-port 10GigE (Ethernet) Adapter card or 2-port 10GigE (Ethernet) module).

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

The port must be shut down before changing the DWDM channel, and the port must be a physical port to set the DWDM channel.

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).

This command enables access to the context to configure access mode parameters.

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.

This command assigns a shaper policy to the specified hybrid 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 OS Quality of Service Guide, “QoS for Hybrid Ports”, for more information.

Note: 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 Release 6.2 support 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.

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 the 6-port Ethernet 10Gbps Adapter Card for more information..

The no form of the command sets the unshaped-sap-cir CIR rate to 0 kb/s.

For the 8-port Ethernet Adapter card, this command enables speed autonegotiation and duplex autonegotiation on Ethernet 10/100Base-T RJ-45 ports. The command enables speed autonegotiation on the two SFP ports (10, 100, or 1000 Mb/s). Duplex autonegotiation is only supported on SFP ports using 100 Mb/s fiber SFPs or 10/100/1000Base-T copper SFPs. Duplex autonegotiation is not supported on optical Gigabit Ethernet SFPs; the mode is always full duplex.

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 supports 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.

Caution: 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).

Note: 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.

This command enables the port to respond to LBM messages 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:

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.

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 OS 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 a v-port, or by DSL or GPON modules on the 7705 SAR-M. However, qinq encapsulation is supported by the DSL block on the 7705 SAR-Wx.

Network ports do not allow dot1q-etype settings.

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

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.

This command configures the time interval between the keepalive PDUs transmitted toward the network during loop detection by the down-when-looped feature.

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.

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. You must enable use-broadcast-address if down-when-looped is enabled on DSL or GPON module ports.

For the 8-port Ethernet Adapter card, the 6-port Ethernet 10Gbps Adapter card, and the 10-port 1GigE/1-port 10GigE X-Adapter card in x10-1gb-sfp mode, this command configures the duplex mode of an Ethernet or Fast Ethernet port when autonegotiation is disabled. 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.

For the 8-port Gigabit Ethernet Adapter card, the 6-port Ethernet 10Gbps Adapter card, the 10-port 1GigE/1-port 10GigE X-Adapter card in x10-1gb-sfp mode, and the Packet Microwave Adapter card, this command configures the duplex mode of an Ethernet, Fast Ethernet, or Gigabit Ethernet port when autonegotiation is disabled. On the 2-port 10GigE (Ethernet) Adapter card and 2-port 10GigE (Ethernet) module, ring Ethernet XFP ports and the v-port are set to full-duplex mode by default and cannot be changed. On the other cards, SFP slots can be configured for full-duplex mode or for half-duplex mode on ports configured for speeds of 10 or 100 Mb/s when autonegotiation is disabled. Duplex autonegotiation is automatically turned off when the user sets the mode with this command. All SFP slots support duplex autonegotiation.

Note: On the 10-Gb/s ports of the 6-port Ethernet 10Gbps Adapter card (ports 5 and 6), the mode is always full duplex and cannot be changed.

This command configures EFM-OAM attributes.

This command enables reactions to loopback control OAMPDUs from peers.

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

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.

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.

This command configures the transmit interval of OAMPDUs.

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.

This command configures the rate of traffic leaving the network.

On the 7705 SAR-M GPON module and the 7705 SAR-W using a GPON SFP interface, this command configures the rate of traffic leaving the GPON port. The egress-rate for the GPON port must be configured to match the traffic management parameters provisioned across the PON. These parameters can be viewed via TL1 on the OLT.

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

This command configures the encapsulation method used to distinguish customer traffic on an Ethernet or DSL access port, network v-port, GPON 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 a v-port, or by DSL or GPON modules on the 7705 SAR-M. However, qinq encapsulation is supported by the DSL block on the 7705 SAR-Wx.

The no form of this command restores the default.

See also dot1q-etype and qinq-etype for information on tagging and encapsulation.

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. Likewise, 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.

Note that 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.

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.

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 enables LACP packet tunneling for the Ethernet port, DSL port, or GPON 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, DSL port, or GPON port.

This command configures timed line loopbacks on Ethernet and GPON network and access ports, timed line loopbacks on ring Ethernet network ports, untimed line loopbacks on Ethernet and GPON access ports, and timed and untimed internal loopbacks on Ethernet ports, DSL ports, and GPON ports.

For Ethernet and GPON 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, GPON ports or DSL 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, DSL module reset, GPON module 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. The persistent keyword is not supported on GPON ports or DSL ports.

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 or DSL 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. EFM-OAM is not supported on GPON ports.

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.

This command assigns a specific MAC address to an Ethernet port, ring Ethernet port, v-port, DSL port, or GPON 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.

This command configures an Ethernet port, DSL port, or GPON 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, DSL, or GPON 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:

If the hybrid port is configured for qinq encapsulation, the user configures a SAP inside a service as follows:

The no form of this command restores the default.

This command configures the maximum payload MTU size for an Ethernet port, v-port on Ethernet Ring adapter card, DSL, or GPON port (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.

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 OS Basic System Configuration Guide for more information about synchronous Ethernet.

The poe command enables an RJ-45 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 port that is PoE+ capable to deliver power to a “Powered Device” at levels compatible with the IEEE 802.3at standard.