Ports
This section describes 7210 SAS ports.
Port types
The following table describes the port types supported on the 7210 SAS platforms.
|
7210 SAS platform |
Fixed copper ports (10/100/1000 Base-T) |
Ethernet SFP ports |
10 Gigabit XFP/SFP+ ports |
100 Gigabit QSFP28 ports |
|---|---|---|---|---|
|
7210 SAS-T |
✓ |
✓ |
✓ 1 |
|
|
7210 SAS-R6 |
✓ 2 |
✓ |
✓ 3 |
✓ |
|
7210 SAS-R12 |
✓ 2 |
✓ |
✓ 3 |
✓ |
|
7210 SAS-Mxp |
✓ |
✓ |
✓ 4 |
|
|
7210 SAS-Sx/S 1/10GE |
✓ |
✓ |
✓ 4 |
|
|
7210 SAS-Sx 10/100GE |
✓ 4 |
✓ 4 |
✓ 4 |
✓ |
The following support guidelines apply to the supported Ethernet port types described in the preceding table:
10/100/1000 Base-T copper SFPs can be used in any of the SFP ports.
Copper SFPs with speeds of 10 Mb/s and full-duplex are supported on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-T. Copper SFPs with speeds of 10 Mb/s and half-duplex mode are supported only on the 7210 SAS-T.
Fixed copper ports on the 7210 SAS-Sx/S 1/10GE 24-port and 48-port copper variants, including PoE variants, support speeds of 10 Mb/s and 100 Mb/s with full-duplex mode. They do not support half-duplex mode.
Combination ports on the 7210 SAS-Mxp and 7210 SAS-Sx 1/10GE support speeds of 10 Mb/s with full-duplex mode when the copper port is used.
Fixed copper ports on the 16 x 10/100/1000 Base-T (RJ.5) IMMv2 card on the 7210 SAS-R6 and 7210 SAS-R12 support speeds of 10 Mb/s with full-duplex mode. They do not support speeds of 10 Mb/s with half-duplex mode.
Fixed copper ports on the 7210 SAS-T support speeds of 10 Mb/s with full-duplex and half duplex modes.
On the 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE, the user can select the fiber interface slot or the copper interfaces slot of the combination port using the following command.
configure port ethernet connection-typeBy default, the combination port connection-type is set to auto. The auto option allows the software to automatically detect the connection type based on the link availability of the media inserted into the port and set the operational value to either ‟copper” or ‟fiber”.
-
The 7210 SAS-Sx 1/10GE (48-port fiber) supports the use of copper SFP in the SFP slot for combo ports.
Note: Nokia recommends that the user should not plug in the connector for the copper connection while using the SFP port (the opposite also applies). That is, at any point in time, only a single connector must be used. The SFP+ ports on the 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE allow the use of 1 GE fiber-optic SFPs or copper SFPs in SFP+ interface slots. Before using the 1 GE SFP, you must configure a speed of 1000 Mb/s on the SFP+ ports using the following command.
configure port ethernet speedOnly a speed of 1 Gb/s is supported for copper SFPs; that is, speeds of 10 Mb/s and 100 Mb/s are not supported.
-
The SFP+ ports on the 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE allow the use of 1 GE fiber-optic SFPs or copper SFPs in SFP+ interface slots. Before using the 1 GE SFP, you must configure a speed of 1000 Mb/s on the SFP+ ports using the config port ethernet speed command. Only a speed of 1 Gb/s is supported for copper SFPs; that is, 10 Mb/s and 100 Mb/s speeds are not supported.
-
The ports on the 7210 SAS-Sx 10/100GE 64SFP+ 4QSFP28 front panel are named 1/1/1 to 1/1/64 for the 64 SFP+ ports and 1/1/c1, 1/1/c2, 1/1/c3, and 1/1/c4 for the 100GE 4QSFP28 ports.
Port modes
In 7210 SAS devices, port must be configured as either access, access uplink or network. The following paragraphs describe the significance of the different port modes and the support available on different platforms.
access ports
Configured for customer facing traffic on which services are configured. If a Service Access Port (SAP) is to be configured on the port, it must be configured as an access port. When a port is configured for access mode, the appropriate encapsulation type must be configured to distinguish the services on the port. After a port has been configured for access mode, one or more services can be configured on the port depending on the encapsulation value. Access ports can be configured on all the 7210 SAS platforms.
access-uplink ports
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. This is the default mode when a node is operating in access-uplink mode.
network ports
Configured for network facing traffic. These ports participate in the service provider transport or infrastructure network. Dot1q is supported on network ports. This is default for nodes operating in network mode.
hybrid ports
Configured for access and network facing traffic. While the default mode of an Ethernet port remains network, the mode of a port cannot be changed between the access/network/hybrid values unless the port is shut down and the configured SAPs or interfaces are deleted. Hybrid ports allow a single port to operate in both access and network modes. MTU of port in hybrid mode is the same as in network mode except for the 10/100 MDA. The default encap for hybrid port mode is dot1q, it also supports QinQ encapsulation on the port level. Null hybrid port mode is not supported.
After the port is changed to hybrid, the default MTU of the port is changed to match the value of 9212 bytes currently used in network mode (higher than an access port); this is to ensure that both SAP and network VLANs can be accommodated.
The only exception is when the port is a 10/100 fast Ethernet. In those cases, the MTU in hybrid mode is set to 1522 bytes, which corresponds to the default access MTU with QinQ, which is larger than the network dot1q MTU or access dot1q MTU for this type of Ethernet port. The configuration of all parameters in access and network contexts will continue to be done within the port using the same CLI hierarchy as in existing implementation. The difference is that a port configured in mode hybrid allows both ingress and egress contexts to be configured concurrently.
An Ethernet port configured in hybrid mode can have two values of encapsulation type: dot1q and QinQ. The NULL value is not supported because a single SAP is allowed, and can be achieved by configuring the port in the access mode, or a single network IP interface is allowed, which can be achieved by configuring the port in network mode. Hybrid mode can be enabled on a LAG port when the port is part of a single chassis LAG configuration. When the port is part of a multi-chassis LAG configuration, it can only be configured to access mode as MC-LAG is not supported on a network port and consequently is not supported on a hybrid port.
The following table describes the port modes that are supported on each 7210 SAS platform.
Table 2. 7210 SAS platforms supporting port modes Port mode platforms
Access
Network
Hybrid
Access-uplink
7210 SAS-T
Yes
Yes 5
Yes 6
Yes 7
7210 SAS-R6 IMM-b (IMMv2)
Yes
Yes
Yes
No
7210 SAS-R6 IMM-c 100GE (IMM-c 1QSFP28)
Yes
Yes
No
No
7210 SAS-R12 IMM-b
Yes
Yes
Yes
No
7210 SAS-R12 IMM-c 100GE (IMM-c 1QSFP28)
Yes
Yes
No
No
7210 SAS-Mxp
Yes
Yes
Yes
No
7210 SAS-Sx/S 1/10GE
Yes
Yes
Yes
No
7210 SAS-Sx 10/100GE
Yes
Yes
Yes
No
Port dot1q VLAN Etype
7210 SAS supports an option to allow the user to use a different dot1q VLAN Ethernet Type (Etype). It allows for interoperability with third-party switches that use some pre-standard (other than 0x8100) dot1q VLAN etype.
Configuration guidelines for dot1q-etype
The following are the configuration guidelines for dot1q-etype configured for dot1q encap port:
Dot1q-etype configuration is supported for all ports - Access, Hybrid and Network ports.
Dot1q-preserve SAPs cannot be configured on dot1q encap ports configured to use ethertype other than 0x8100.
Priority tagged packet received with etype 0x8100 on a dot1q port configured with etype 0x9100 are classified as priority tagged packet and mapped to a dot1q :0 SAP (if configured) and the priority tag is removed.
Priority tagged packets received with etype 0x6666 (any value other than 0x8100) on a dot1q port configured with etype 0x9100 is classified as null-tagged packet and mapped to a dot1q :0 SAP (if configured) and the priority tag is retained and forwarded.
The dot1q-etype is modified only for the dot1q encap port (access/hybrid port). The dot1q-etype cannot be modified on Network ports.
During the non-default dot1q-rvpls and qinq-rvpls, the extra tagged packets is dropped even for an 0x8100 packets on an RVPLS SAP, this is applicable only for network mode (and not access-uplink mode).
Support for Power over Ethernet
Power over Ethernet (PoE) is supported only on the 7210 SAS-Mxp ETR, 7210 SAS-Sx/S 1/10GE operating in standalone mode, and 7210 SAS-T ETR.
The 7210 SAS-Mxp ETR, 7210 SAS-Sx/S 1/10GE PoE variants, and 7210 SAS-T ETR support PoE in accordance with the 802.3af and 802.3at standards. This feature allows these platforms to supply power to connected PoE devices, such as telephones, CCTV cameras, and other PoE standard compliant devices.
The 7210 SAS-Sx 1/10GE supports two PoE variants:
24Tp 4SFP+ PoE
48Tp 4SFP+ PoE
In addition to the PoE variants, the following 7210 SAS-Sx 1/10GE fiber variants support two PoE/PoE+ ports:
22F 2C 4SFP+
46F 2C 4SFP+
The 7210 SAS-S 1/10GE supports two PoE variants:
24Tp 4SFP+ AC PoE
48Tp 4SFP+ AC PoE
The following PoE functionalities are available:
The 7210 SAS supports both 802.3af (PoE) and 802.3at (PoE+) on all ports. The ports can be used to connect either PoE or PoE+ devices, or a combination of both simultaneously, as long as the power drawn is within the device system limits.
Only Alternative A, as described in the 802.3af and 802.3at standards, is supported on the 7210 SAS.
The 7210 SAS supports classification of both Type 1 and Type 2 PoE devices (PDs) using the physical layer classification mechanism (using the 1-event physical layer classification mechanism for Type 1 PD and 2-event physical layer classification mechanism for Type 2 PD).
The 7210 SAS supports the class-based power allocation method, which allocates power based on the identified class using a physical layer classification mechanism. The 802.3af and 802.3at standards define the power that can be allocated or requested by a particular class. The standards define four classes: Class 1, Class 2, Class 3, and Class 4. These classes are used to allow PoE devices to request power based on their needs. If there is not enough power available to supply the identified class, power is denied to the connected PoE device. Each 7210 SAS device has a limit on the maximum amount of power it can provide. If the total power requested by the PDs connected to PoE-enabled ports exceeds this threshold, the 7210 SAS device denies power to the other PD. When power is denied to the PD, the port is operationally up, even though power is not supplied to the port. If power is applied successfully or denied to the port, the system logs an event.
Only DC power is supplied to connected PDs. It is supported for PDs that use injectors where an AC/DC wall device is used to power a remote PoE device.
The software monitors the PoE port, detects faults and events, and raises traps. The software displays this information in the status report. The following events and faults are detected and notify the user:
supplying power event
This event is generated when power is supplied to a connected PoE device after successful detection and classification.
denied power event
This event is generated when power is denied to a connected PoE device after successful detection and classification.
disconnect event
This event is generated when a connected PoE device is disconnected from the port and stops drawing power from the node.
fault events
These events are generated for overload, short-circuit, and other events. Software clears the fault when the fault no longer exists.
If a port enabled for PoE is shut down, the power supplied to the port is disabled. It restores power when the no shutdown command is executed, if the request does not exceed the power budget.
PoE configuration notes
The following configuration notes apply for PoE:
On the 7210 SAS-T ETR, up to four fixed copper ports are available to connect PoE/PoE+ devices. The 7210 SAS-T ETR can supply a maximum of 60 W.
On the 7210 SAS-Mxp ETR, up to 2 ports are available to connect PoE/PoE+ devices. The 7210 SAS-Mxp ETR can supply a maximum of 60 W.
On the 7210 SAS-T ETR and 7210 SAS-Mxp ETR, the maximum available power must be shared among all PoE/PoE+ devices connected to the node. That is, the node can support a mix of PoE devices (using 15 W) and PoE+ devices (using 30 W) as long as the total power drawn is within the system limits.
The 7210 SAS-Sx 1/10GE 24-port and 48-port fiber variants provide two PoE/PoE+ capable combo ports: 1/1/1 and 1/1/2. To use PoE/PoE+, these combo ports must be configured to use the copper interface and can draw maximum of 60 W. The ports can be used for either PoE or PoE+ devices, or a combination.
On the 7210 SAS-Sx 1/10GE and 7210 SAS-S 1/10GE, the 24-port and 48-port copper PoE variants support PoE/PoE+ on all fixed copper ports. On both variants, the PoE ports can draw maximum of 720 W. On the 24-port PoE variant, each port can draw up to 15 W for PoE or up to 25 W for PoE+. On the 48-port PoE variant, each port can draw up to 15 W for PoE or up to 25 W for PoE+, or a combination of PoE and PoE+ devices can be connected to the ports, as long as the total power drawn across all ports does not exceed 720 W.