2.14. Configuring Physical Ports with CLI
This section provides information to configure ports.
2.15. Preprovisioning Guidelines
The 7210 SAS platforms have a console port to connect terminals to the device. The Ethernet management port is supported.
Configure parameters from a system console connected to a console port, using Telnet to access the device remotely or SSH to open a secure shell connection.
2.15.1. Predefining Entities
On 7210 SAS platforms, where cards/MDAs are not auto-provisioned, to initialize a card, the chassis slot, line card type, and MDA type must match the preprovisioned parameters. In this context, preprovisioning means to configure the entity type (such as the line card type, MDA type, port, and interface) that is planned for a chassis slot, line card, or MDA. Preprovisioned entities can be installed but not enabled or the slots can be configured but remain empty until populated. Provisioning means that the preprovisioned entity is installed and enabled.
You can:
- provision the chassis to accept specific IMM cards on the 7210 SAS-R6 and 7210 SAS-R12
- preprovision ports and interfaces after the line card and MDA types are specified.
- install line cards in slots with no preconfiguration parameters specified. When the card is installed, the card and MDA types must be specified. This is required on 7210 SAS chassis-based platforms (7210 SAS-R6 and 7210 SAS-R12) or those platforms that support expansion slots (7210 SAS-M). On 7210 SAS platforms that do not support any removable cards and/or MDAs, the cards are preprovisioned for fixed ports.
- install a line card in a slot provisioned for a different card type (the card will not initialize). The existing card and MDA configuration must be deleted and replaced with the current information. This is required on 7210 SAS chassis-based platforms (7210 SAS-R6 and 7210 SAS-R12) or those platforms that support expansion slots (7210 SAS-M). On 7210 SAS platforms that do not support any removable cards and/or MDAs, the MDAs are preprovisioned for all fixed ports.
2.15.2. Preprovisioning a Port
On 7210 SAS chassis-based platforms (7210 SAS-R6 and 7210 SAS-R12) or those that provide an expansion slot (7210 SAS-M), before a port can be configured, the slot must be preprovisioned with an allowed card type and/or the MDA must be preprovisioned with an allowed MDA type.
Some recommendations to configure a port include:
- Ethernet
- Configure an access port for customer facing traffic on which services are configured.An encapsulation type may be specified to distinguish services on the port or channel. Encapsulation types are not required for network ports.To configure an Ethernet access port, refer to Ethernet Access Port.
- Configure a network port to participate in the service provider transport or infrastructure network.To configure an Ethernet network port, refer to Ethernet Network Port.Accounting policies can only be associated with network ports and Service Access Points (SAPs). Accounting policies are configured in the config>log>accounting-policy context.
When ports are preprovisioned, Link Aggregation Groups (LAGs) can be configured to increase the bandwidth available between two nodes. All physical links in a specific LAG combine to form one logical connection. A LAG also provides redundancy in case one or more links that participate in the LAG fail. For command syntax, see Configuring LAG Parameters.
2.16. Basic Configuration
7210 SAS platforms that do not support any removable cards and/or MDAs (7210 SAS-M (if expansion slot is not used), 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE), the card and MDA is auto-provisioned and operators can directly start with identifying and configuring the ports as follows. If the operators intends to use the expansion slot on the 7210 SAS-M, then they must start with the step in identifying and configuring the MDA slot.
On 7210 SAS chassis-based platforms, (7210 SAS-R6 and 7210 SAS-R12), the card type must be provisioned and operators need to start from identifying the chassis slot and configuration of the slot and card type, as shown below.
The most basic configuration must have the following:
- identify chassis slot (if applicable)
- specify line card type (must be an allowed card type).
- identify MDA slot (if applicable)
- specify MDA (must be an allowed MDA type) – if applicable
- identify specific port to configure
2.16.1. Configuring Cards and MDAs
Card configurations include a chassis slot designation.
The following is a sample of card configuration output for the 7210 SAS-R6.
The following is a sample of MDA configuration output for the 7210 SAS-M.
2.16.2. Configuration Notes for Provisioning of Cards
The following provisioning guidelines and caveats apply.
- On 7210 SAS systems that require provisioning of the card type (7210 SAS-R6 and 7210 SAS-R12), if a card or MDA type is installed in a slot provisioned for a different type, the card will not initialize.
- On 7210 SAS systems that require provisioning of a card (7210 SAS-R6 and 7210 SAS-R12) and MDA (7210 SAS-M), if the card or MDA is installed in an unprovisioned slot, it will remain administratively and operationally down until the card type and MDA is specified.
- Ports cannot be provisioned until the slot, card, and MDA type are specified, on systems that require provisioning of the card and MDA. Ports can be provisioned on bootup on systems that auto-provision the cards and MDAs (7210 SAS-T, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE and fixed ports on the 7210 SAS-M).
2.16.2.1. Configuration Notes for Provisioning of 7210 SAS-R6 IMMv2 (IMM-b) Cards
The 7210 SAS-R6 platform supports IMM version-2 cards (imm-sas-b variants). The IMM version-1 cards (IMMs whose family is displayed as imm-sas-r) and IMM version-2 cards (IMMs whose family is imm-sas-r-b) cannot coexist in a single chassis. The 7210 SAS-R6 chassis can operate with all IMMv1 or all IMMv2 cards. A mix of IMMv1 cards and IMMv2 cards in the same chassis is not allowed. If the user is currently using IMMv1 cards, the user can continue using them without any changes.
From release 7.0R4 by default, the system allows only IMMv1 cards to be provisioned and equipped in the chassis. To use IMMv2 cards, you must provision the chassis using the config>system>chassis>allow-imm-family CLI command as shown below. This command lets the software know which version of cards will be used in the system and allows it to initialize the system appropriately with the correct set of parameters. A change to this value requires a reboot of the chassis.
where:
imm-family = imm-sas-r | imm-sas-r-b | imm-sas-r-c
- imm-sas-r: use for IMMv1
- imm-sas-r-b: use for IMMv2
- imm-sas-r-c: use for IMM-c
For the list of IMMs supported in a particular release, refer to the release notes.
The user can change the value of allow-imm-family at any time. It does not change the operational state of the chassis. For the value to take effect, the user must reboot. If the software detects a mismatch in the cards specified by allow-imm-family and the IMM cards provisioned/equipped in the chassis, it will generate an error as shown below.
Use the following command to display a list of supported cards per family.
Use the following command to display the list of IMM cards allowed in the chassis based on the configured value of allow-imm-family.
 | Note: For more information about upgrading the chassis to use IMMv2 cards, see the 7210 SAS-R6 Chassis Installation Guide. |
2.16.2.2. Configuration Notes for Provisioning of 7210 SAS-R6 IMM-c Cards
The user has the option to aggregate 1G and 10G customer services to 100GE uplinks to meet the increasing bandwidth needs in access networks by provisioning 7210 SAS-R6 IMM-c cards. Both the QSFP28 (named imm-sas-c-1qsfp28) and CFP4 (named imm-sas-c-1cfp4) variants are supported, providing the flexibility of using optics based on needs.
The 100GE IMM cards support only network ports, allowing the ports to be used as network uplinks when the 7210 SAS-R6 is deployed as an IP/MPLS router with MPLS LER and LSR functionality.
Before using the card, the command config>system>chassis>allow-imm-family imm-sas-r-c must be used, followed by a reboot of the node to allow the system to initialize correctly when using the new card.
On both the 7210 SAS-R6 and 7210 SAS-R12, imm-b and imm-c can be used simultaneously (that is, some slots can be populated with imm-b and some slots can be populated with imm-c). To achieve that, configure both imm-sas-r-b and imm-sas-r-c using the CLI command config>system>chassis>allow-imm-family. The system scaling of the functions supported when a mix of IMM-b and IMM-c are in use in the chassis is the lower of the scaling supported by each of the cards. Refer to the scaling guide or contact your Nokia representative for more information.
where:
imm-family = imm-sas-r | imm-sas-r-b | imm-sas-r-c
- imm-sas-r: use for IMMv1
- imm-sas-r-b: use for IMMv2
- imm-sas-r-c: use for IMM-c
The following guidelines and caveats apply.
- IMM-c supports hot-swapping (after one-time configuration of the node).
- On the 7210 SAS-R6, only two 100GE IMM-c cards in specified slots can be used. On the 7210 SAS-R12, all slots can be populated with 100GE IMM-c cards.
- SyncE (as a reference and for distribution of frequency) and PTP (IEEE default and G.8265.1 profile) are available for use with the 100GE port.
- Supports eight egress queues per network port for egress queuing and scheduling, along with MPLS EXP based marking, for prioritizing service traffic on network uplinks. Supports network port ingress classification with policing and network IP interface ingress classification with policing to differentiate and prioritize service traffic.
- 100GE QSFP28 IMM-c variant does not provide a breakout option.
- Hybrid ports are not supported with IMM-c cards.
2.17. Common Configuration Tasks
This section describes common configuration tasks.
2.17.1. Configuring Ports
2.17.1.1. Configuring Ethernet Port Parameters
This section describes Ethernet port configuration.
2.17.1.1.1. Ethernet Network Port
A network port is network-facing and participates in the service provider transport or infrastructure network processes.
The following is a sample network port configuration output.
2.17.1.1.2. Ethernet Access-uplink Port
Access-uplink ports are network-facing and transport customer services. Only QinQ encapsulation can be used.
The following is a sample access-uplink port configuration output.
2.17.1.1.3. Ethernet Access Port
Services are configured on access ports used for customer-facing traffic. If a SAP is to be configured on a port, it must be configured in access mode. When a port is configured for access mode, the appropriate encapsulation type can be specified to distinguish the services on the port. When a port has been configured for access mode, multiple services may be configured on the port.
The following is a sample Ethernet access port configuration output.
2.17.1.1.4. Configuring 802.1x Authentication Port Parameters
The following is a sample 802.1x port configuration output.
2.17.1.1.5. Configuring MAC Authentication Port Parameters
| Note: MAC authentication is only supported on 7210 SAS-M, 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-T. |
The 7210 SAS supports a fallback MAC authentication mechanism for client devices (for example, PCs and cameras) on an Ethernet network that do not support 802.1x EAP.
MAC authentication provides protection against unauthorized access by forcing the device connected to the 7210 SAS to have its MAC address authenticated by a RADIUS server before the device is able to transmit packets through the 7210 SAS.
Use the following CLI syntax to configure MAC authentication for an Ethernet port.
The following example shows the command usage to configure MAC authentication for an Ethernet port.
Use the info detail command to display port configuration information. The following is a sample port configuration output.
2.17.1.1.6. Configuring VLAN Authentication Port Parameters
| Note: VLAN authentication is only supported on 7210 SAS-M, 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-T. |
The 7210 SAS supports VLAN authentication for client devices (for example, PCs and STBs) on an Ethernet network.
VLAN authentication provides protection against unauthorized access by forcing the device connected to the 7210 SAS to be authenticated by a RADIUS server before the device is able to transmit packets through the 7210 SAS.
Use the following CLI syntax to configure VLAN authentication for an Ethernet port.
The following example shows the command usage to configure VLAN authentication for an Ethernet port.
Use the info detail command to display port configuration information. The following is a sample port configuration output.
2.17.1.2. Configuring Channelized Ports
| Note: The Circuit Emulation Services (CES) MDA is only supported on the 7210 SAS-M platform (network mode). |
This section describes the configuration of the CES MDA that supports 4 x T1/E1 ports.
To configure channelized ports, the port ID syntax varies depending on the MDA type and level of channelization. Ethernet ports cannot be channelized.
2.17.1.2.1. Configuring a Channelized DS1 Card
The 7210 SAS-M supports a CES MDA that supports 4-port channelized DS-1 cards. The channelization is as follows:
- N*DS0 in DS1 port{1 to 24}
- N*DS0 in E1 port {1 to 32}
To ensure that the MDA is channel-capable, verify the MDA type using the show mda slot-id command.
In the following example, MDA 2 shows a channelized DS1 MDA.
In the TDM E1 context, configure DS0 channel groups and their parameters. For a DS1 channel group, up to 24 timeslots can be assigned (numbered 1 to 24). For an E1 channel group, up to 31 timeslots can be assigned (numbered 2 to 32). Only CES services (that is, CESoPSN and SAToP) are supported with a CES MDA on the 7210 SAS-M in network mode.
Configuration examples follow:
Services can now be applied to the configured channelized ports.
2.17.2. Configuring LAG Parameters
The following guidelines and caveats apply for LAG configurations.
- LAG configurations must include at least two ports.
- Up to eight ports can be included in a LAG, depending on the platform. All ports in the LAG must share the same characteristics (speed, duplex, hold-timer, and so on). The port characteristics are inherited from the primary port.
- Autonegotiation must be disabled or set to limited mode for ports that are part of a LAG to guarantee a specific port speed.
- Ports in a LAG must be configured as full duplex.
- The 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12 support IP DSCP table-based classification for LAG. Refer to “Service Ingress QoS Policies” in the 7210 SAS-M, T, Mxp, Sx, S Quality of Service Guide and the 7210 SAS-R6, R12 Quality of Service Guide for more information.
The following is a sample LAG configuration output.
2.17.2.1. Configuring BFD Over LAG Links
After the LAG and associated links are configured, you can configure BFD in the LAG context to create and establish the micro-BFD session per link. Before micro-BFD can be established, an IP interface must be associated with the LAG or a VLAN within the LAG, if dot1q encapsulation is used.
Perform the following to enable and configure BFD over individual LAG links.
- Within the lag context, enter the bfd context and enable BFD.
- Configure the address family for the micro-BFD sessions. Only one address family per LAG can be configured. On the 7210 SAS-T, 7210 SAS-R6, and 7210 SAS-R12, only the IPv4 address family can be configured.
- Configure the local IP address for the BFD sessions.
- Configure the remote IP address for the BFD sessions.
When configuring the local and remote IP address for the BFD over LAG link sessions, ensure that the local-ip parameter should always match an IP address associated with the IP interface to which the LAG is bound. In addition, the remote-ip parameter must match an IP address on the remote system and should also be in the same subnet as the local-ip address. If the LAG bundle is reassociated with a different IP interface, modify the local-ip and remote-ip parameters to match the new IP subnet. The local-ip and remote-ip values do not have to match a configured interface in the case of tagged LAG or ports.
The following optional parameters can be configured for BFD over LAG links:
- transmit interval
- receive interval
- multiplier
- max-wait-for-up-time — This parameter controls how long a link will remain active if BFD is enabled after the LAG and associated links are active and in a forwarding state.
- max-time-admin-down — This parameter controls how long the system will wait before bringing the associated link out of service if an admin down message is received from the far end.
The following is a sample configuration output.
2.17.3. Configuring Access Egress Queue Overrides
Queue override support on an access port in the egress direction allows users to override queue parameters such as adaptation rule, percent CIR and PIR rates, queue management policy, queue mode, CIR and PIR rates, and queue weight.
When the queue override feature is not used, queue parameters for the port are taken from the access egress QoS policy assigned to the port.
The following is a sample queue override configuration output.
2.17.4. CRC Error Monitoring
This feature allows the user to track CRC (cyclic redundancy check) errors received on a specific port. The detection mechanism is based around a configurable threshold specified by the administrator. Two thresholds are configurable, one for CRC degrade and one for CRC signal fail. The first threshold crossing generates an alarm, log entry, and trap, but does not bring the physical port down, while the second (signal fail) threshold crossing logs an alarm, generates a trap, and brings the port operationally down.
The thresholds are configurable with the CLI command config>port>ethernet crc-monitor.
| Note: This behavior is enabled on a per-port basis. By default, the command and functionality is disabled for signal degrade and signal fail. |
The user can configure different values for the sf-threshold and the sd-threshold. However, the sf-threshold value must be less than or equal to the sd-threshold value.
The values provided by the user for threshold and multiplier are used to compute the error ratio as (multiplier * (10 ^ - (threshold value)). Port statistics are collected once per second and accumulated over the configured window size. Each second, the oldest sample is discarded and the new sample is added to a running total. If the error ratio exceeds the configured threshold (as computed previously) over the window size for 2 consecutive seconds, appropriate actions are taken as follows.
- If the number of CRC errors exceeds the signal degrade threshold value, a log warning message, syslog event and SNMP trap with the message “CRC errors in excess of the configured degrade threshold <M>*10e-<N> Set” is raised.
- If the CRC error rate increases further and exceeds the configured signal fail threshold value, an alarm log message, syslog event, and SNMP trap are raised, and the port is brought operationally down.
When the condition is cleared, a SNMP trap message to clear the event is generated.
2.18. Service Management Tasks
This section describes the service management tasks.
2.18.1. Modifying or Deleting an MDA
To change an MDA type already provisioned for a specific slot/card, the slot/MDA/port configuration must be shut down and then the MDA must be deleted from the configuration. Modify and delete operations can be performed only on the MDAs that are not auto-equipped or auto-provisioned.
Use the following syntax to modify an MDA.
2.18.2. Modifying a Card Type
The modify operation cannot be performed on an IOM card that is auto-equipped and auto-provisioned during bootup and is fixed.
2.18.3. Deleting a Card
The delete operation cannot be performed on an IOM card that is auto-equipped and auto-provisioned during bootup and is fixed.
2.18.4. Deleting Port Parameters
Use the following syntax to delete a port provisioned for a specific card.