port port-id
no port port-id
config
Supported on all 7210 SAS platforms as described in this document.
This command configures ports. Before a port can be configured, the chassis slot must be provisioned with a valid card type and the MDA parameter must be provisioned with a valid MDA type. (See card and mda commands.)
Specifies the physical port ID in the slot/mda/port format.
dwdm
config>port
Supported on all 7210 SAS platforms as described in this document.
This command configures the Dense Wavelength Division Multiplexing (DWDM) parameters.
channel channel
config>port>dwdm
Supported on all 7210 SAS platforms as described in this document.
This command configures the Dense Wavelength Division Multiplexing (DWDM) ITU channel at which a tunable MDA optical interface will be configured to operate. It is expressed in a form that is derived from the laser's operational frequency. For example, 193.40 THz corresponds to DWDM ITU channel 34 in the 100 GHz grid and 193.45 THz corresponds to DWDM ITU channel 345 in the 50 GHz grid. A provisioned MDA type must have DWDM tunable optics (m1-10gb-dwdm-tun).
The DWDM channel must set to a non-zero value before the port is set to no shutdown.
The port must be shut down before changing the DWDM channel.
The DWDM channel must be on a physical port.
Specifies the channel.
enable-dei
no enable-dei
config>port>ethernet
config>lag
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command enables DEI based classification on access ports, network ports, access-uplink or hybrid ports.
If enabled, DEI value in the Ethernet packet header is used to determine the initial profile/color of the packet when the meter/policer used to police the FC is configured in color-aware mode. If the meter used to police the FC is configured in color-blind mode, then the DEI value of the packet has no effect. When in color-aware mode, DEI value of 0 is interpreted as in-profile or green packet and DEI value of 1 is interpreted as out-of-profile or yellow packet. In color-aware mode, the following behavior is accorded to packets classified with initial profile/color as in-profile/green and out-of-profile/yellow:
If a green packet is received and the color-aware meter is within the CIR rate, then packet is assigned a final profile of green and it is assigned a final profile of yellow if the meter exceeds the CIR rate and is within the PIR rate.
If a yellow packet is received and the color-aware meter is above the CIR rate and within the PIR rate, then the packet is assigned a final profile of yellow.
That is, in color-aware mode, yellow/out-of-profile packets cannot eat into the CIR bandwidth. It is exclusively reserved for green/in-profile packets.
The final profile assigned at ingress is used by egress to determine the WRED slope to use. The WRED slope determines whether the packet is eligible to be assigned a buffer and can be queued up on egress queue for transmission.
For more information, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide.
no enable-dei
egress-scheduler-policy port-scheduler-policy-name
no egress-scheduler-policy
config>port>ethernet
7210 SAS-T, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-Sx 10/100GE
This command enables the provisioning of an existing port-scheduler-policy to a port or channel.
The default scheduling done for a port is strict scheduling. When a port-scheduler-policy is applied to the port, the scheduling behavior changes to the one specified in the policy (Strict, RR, WRR, WDRR, WRR/WDRR + Strict).
The no form of this command removes the associated default port scheduler policy from an egress port.
Specifies an existing port-scheduler-policy configured in the config>qos context.
mode {access [uplink]| network | hybrid}
no mode
config>port>ethernet
config>lag
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Access: An access port is used for customer facing traffic on which services are configured. A Service Access Point (SAP) can only be configured on an access port. When a port is configured for access mode, the appropriate encap-type must be specified to distinguish the services on the port. Once an Ethernet port has been configured for access mode, multiple services can be configured on the Ethernet port.
Access-uplink: Access-uplink ports are used to provide native Ethernet connectivity in service provider transport or infrastructure network. This can be achieved by configuring port mode as access uplink. With this option, the encap-type can be configured to only qinq. Access-uplink SAPs, which are QinQ SAPs, can only be configured on an access uplink port to allow the operator to differentiate multiple services being carried over a single access uplink port. It is supported only on 7210 SAS-T configured in access-uplink mode.
Network: A network port participates in the service provider transport or infrastructure network when a network mode is selected. When the network option is configured, the encap-type can be configured to either null or dot1q.
Hybrid: A hybrid Ethernet port allows the combination of network and access modes of operation on a per-VLAN basis and must be configured as either dot1q or QinQ encapsulation. When the hybrid port is configured to the dot1q encapsulation, the user configures a SAP inside a service by providing the SAP ID which must include the port-id value of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. A SAP of format <port-id>:* is also supported. The user configures a network IP interface under config>router>interface>port by providing the port name which consists of the port-id of the hybrid mode port and an unused VLAN tag value. The format is <portid>:qtag1.
The user must explicitly enter a valid value for qtag1. The <port-id>:* value is not supported on a network IP interface. The 4096 VLAN tag space on the port is shared among VLAN SAPs and VLAN network IP interfaces. When the hybrid port is configured to QinQ encapsulation, the user configures a SAP inside a service by providing the SAP ID which must include the port-id value of the hybrid mode port and the outer and inner VLAN tag values.
The format is <port-id>:qtag1.qtag2. A SAP of format <port-id>: qtag1.* is also supported. The outer VLAN tag value must not have been used to create an IP network interface on this port. In addition, the qtag1.qtag2 value combination must not have been used by another SAP on this port. The user configures a network IP interface under config>router>interface>port by providing the port name which consists of the port-id of the hybrid mode port and a VLAN tag value. The format is <portid>:qtag1.*. An outer VLAN tag qtag2 of * is used to create an IP network interface. In addition, the qtag1.qtag2 value combination must not have been used on another SAP or IP network interface on this port.
The no form of this command reverts to the default.
network
Specifies that the Ethernet port is configured as service access (available only in network mode).
Specifies that the Ethernet port is configured for transport network use.
Specifies that the Ethernet port is configured for transport (Ethernet uplinks available only in access-uplink mode).
Specifies that the Ethernet port is configured for hybrid use (available only in network mode).
monitor-oper-group name
no monitor-oper-group
config>port>ethernet
7210 SAS-T (access-uplink), 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured in the config>system context before its name is referenced in this command.
The no form of this command removes the association from the configuration.
no monitor-oper-group
Specifies a character string of maximum 32 ASCII characters identifying the existing group instance.
mac ieee-address
no mac
config>port>ethernet
config>lag
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command assigns a specific MAC address to an Ethernet port, Link Aggregation Group (LAG), or Ethernet tunnel.
Only one MAC address can be assigned to a port. When multiple mac commands are entered, the last command overwrites the previous command. When the command is issued while the port is operational, IP will issue an ARP, if appropriate, and BPDUs are sent with the new MAC address.
The no form of this command reverts the MAC address to the default value.
a default MAC address is assigned by the system from the chassis MAC address pool
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.
mtu mtu-bytes
no mtu
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the maximum payload MTU size for an Ethernet port. The Ethernet port level MTU parameter indirectly defines the largest physical packet the port can transmit or the far-end Ethernet port can receive. Packets received larger than the MTU will be discarded. Packets that cannot be fragmented at egress and exceed the MTU are discarded.
The value specified for the MTU includes the destination MAC address, source MAC address, the Ethertype or Length field and the complete Ethernet payload. The MTU value does not include the preamble, start of frame delimiter or the trailing CRC.
The no form of this command reverts to the default values.
The default MTU value depends on the (sub-)port type, mode, and encapsulation. Table: Default MTU values lists the default MTU values.
Type |
Mode |
Encap type |
Default (bytes) |
|---|---|---|---|
10/100, Gig, or 10GigE |
Access |
null |
1514 |
10/100, Gig, or 10GigE |
Access |
dot1q |
1518 |
10/100, Gig, or 10GigE |
Access |
q-in-q |
1522 |
10/100 or 100FX Ethernet |
Network |
null |
1514 |
10/100 or 100FX Ethernet |
Network |
dot1q |
1518 |
Sets the maximum allowable size of the MTU, expressed as an integer.
multicast-egress {l2-switch | l3-fwd}
no multicast-egress
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document
This command configures Layer 2 or Layer 3 multicast egress replication on a port. That is, with RVPLS IGMPv3 snooping-based multicast, a port on which receivers are present can be configured to do either Layer 2 multicast replication—where IP TTL is not decremented and the source MAC address is not replaced with the 7210 SAS chassis MAC or IP interface MAC address—or Layer 3 multicast replication—where IP TTL is decremented and the source MAC address is replaced.
This command is supported in network mode
All SAPs on the specified port have the same behavior, therefore the reference to port instead of SAP in the following behavior description:
If the l3-fwd keyword is used, then for both IP multicast and RVPLS IGMP snooping multicast traffic forwarded out of the specified port, the following processing is done:
For IP multicast traffic processed in the context of RVPLS service, the source MAC address is replaced with the chassis MAC address if no IP interface is associated with the RVPLS service. If there is an IES IP interface associated with RVPLS service, the IES interface MAC address is used. In addition, the IP TTL value is decremented by one.
For IP multicast traffic processed in the context of IES or VPRN IP interface, the source MAC address is replaced with the MAC address of the IP interface. In addition, the IP TTL value is decremented by 1. If the IP TTL is not greater than 0, the packet is dropped.
If the l2-switch keyword is used, then for both IP multicast and RVPLS IGMP snooping multicast traffic forwarded out of the specified port, the following processing is done:
For IP multicast traffic processed in the context of RVPLS service, the source MAC address is not replaced. Instead, the original MAC address in the packet is retained. In addition, the IP TTL value is not decremented.
Users must not enable IP multicast on this port.
l3-fwd
Specifies that IGMP snooping on the port (egress) with Layer 2 multicast lookup is enabled.
Specifies that IP multicast (Layer 3) lookups on the port (egress) is enabled.
multicast-ingress {l2-mc | ip-mc}
no multicast-ingress
config>port>ethernet
Supported on all 7210 SAS platforms as described in this document.
This command turns on either IP multicast or IGMP snooping on a port. The l2-mc and ip-mc options are mutually exclusive.On 7210 SAS port ingress, either IGMP snooping Layer 2 multicast lookup can be enabled or IP multicast Layer 3 multicast lookup can be enabled.
The ip-mc keyword must be enabled on ports where multicast sources are located and an RVPLS SAP is configured to receive the multicast streams.
The restriction of either configuring a VPLS SAP as a receiver for processing Layer 2 multicast traffic on ingress or configuring an IP interface as a receiver for processing Layer 3 multicast traffic on ingress (on a port) does not restrict the ability to configure both a VPLS SAP and an IP interface on a port with receivers connected downstream (that is, in the egress direction). Typically, the ports used for ingress and the ports used for egress are not the same.
l2-mc
Specifies that IGMP snooping on the port (ingress) with Layer 2 multicast lookup is enabled.
Specifies that IP multicast (Layer-3) lookups on the port (ingress) is enabled. This parameter is not supported on 7210 SAS-Sx 10/100GE platforms.
[no] ptp-hw-timestamp
config>port
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx 1/10GE, and 7210 SAS-Sx 10/100GE
This command enables Precision Time Protocol (PTP) port-based hardware timestamping on the port in both egress and ingress directions. For more information about PTP port-based hardware timestamping, including configuration guidelines, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide.
The no version of this command disables PTP port-based hardware timestamping on the port.
ptp-hw-timestamp