EasyManua.ls Logo

Nokia 7210 SAS-Mxp - Virtual Chassis; Overview

Nokia 7210 SAS-Mxp
736 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
Virtual chassis
software module keeps track of the shortest path from a specific source IMM to a destination IMM and
uses it to forward packets through the stack using the stacking ports.
A VC can operate as a Layer 2 device, where only VLANs are used for uplink connectivity, or as a full-
fledged IP/MPLS platform with support for IP/MPLS-based Layer 2 and Layer 3 VPNs.
Note:
The following functionality is currently not supported on VCs:
Synchronous Ethernet network synchronization
1588v2 PTP network synchronization
5.1.1 Node roles in the VC
Note:
Contact a Nokia technical support representative for scaling information about the minimum and
maximum number of nodes supported in the VC.
The nodes in a VC are modeled in software as either CPM nodes or IMM nodes. The CPMs and the IMMs
are interconnected through stacking ports.
In a VC, CPMs perform a dual role and will also act as IMMs. Consequently, a CPM is referred to as a
CPM-IMM node and the IMM is referred to as an IMM-only node. Nodes in a VC are IMM-only nodes by
default, but an IMM-only node is not mandatory in a VC.
If only one node is configured in the VC (minimum requirement), it must be a CPM-IMM node. A maximum
of two CPM-IMM nodes can be configured on the VC to provide control plane redundancy. In this case,
the remaining nodes must be IMM nodes. If more than two CPM-IMM nodes are configured, the software
logs an error. The user can also configure a VC with one CPM-IMM and one IMM-only node; however, this
configuration does not provide control-plane redundancy.
During the boot process, the system designates one of the configured CPM-IMM nodes as the active and
the other as the standby CPM-IMM. If the active CPM-IMM fails, the standby CPM-IMM takes over the
active role. It is possible to upgrade an existing IMM-only node to be a CPM-IMM node so that if an existing
CPM-IMM node fails, another node can take on its role. See Configuration guidelines for upgrading,
adding, or removing a VC node for more information about upgrading an IMM-only node to a CPM-IMM
node. It is also possible to add a new node to the VC as a CPM-IMM node in the event that an existing
CPM-IMM node must be replaced; however, there are restrictions. See Permitted platform combinations
in a VC for more information. For information about adding and removing nodes in different scenarios, see
VC boot scenarios.
5.1.2 Permitted platform combinations in a VC
Not all combinations of 7210 SAS-Sx 1/10GE and 7210 SAS-S 1/10GE platform variants can be configured
as CPM-IMM nodes and assume the role of the active and standby CPM in a VC. Only platforms with
similar capabilities can be configured as CPM-IMM nodes.
This restriction does not apply to nodes acting as IMM-only nodes. Any 7210 SAS-Sx 1/10GE variant or
7210 SAS-S 1/10GE variant (PoE and non-PoE, fiber and copper) can be configured as an IMM-only node
to operate with any of the supported combinations of CPM-IMM nodes.
The following table lists the supported combinations of 7210 SAS-Sx 1/10GE and 7210 SAS-S 1/10GE
variants that can be configured as CPM-IMM nodes.
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
223
SPACER TEXT

Table of Contents

Related product manuals