Cisco SVO Admin Plane Overview
Cisco SVO admin plane is responsible for turning up the shelf virtualization orchestration services for the network elements (NE). It is a web user interface that facilitates the installation of the SVO software and configures the NE instances and orchestrates high availability (HA) services.
The admin plane is supported both on the external server and the SVO card. The admin plane allows you to create, update, manage, and delete SVO NE instances.
To achieve high availability for the exernal server, the SVO software is installed on two servers in local and remote locations. In the case of the SVO card, two SVO line cards are installed in two different chassis of the ROADM node. The two external servers or two SVO cards are connected by two intercommunication links—through the HA network (primary link) and through the devices network (secondary link). Both links are used for the communication between the admin planes. The primary link is also responsible for replicating all the configuration transactions that are performed on each active SVO instance to the related standby SVO instance.
All the networking configuration data required by the admin plane is present in a file shared by both the SVO cards or external servers. When creating a new SVO instance, you can configure the management interface address, while the other parameters are automatically selected by the admin plane based on the constraints defined in the configuration file.
The admin planes coordinate to automatically assign active and standby roles to the SVO instances. The admin planes can also perform an automatic switchover that promotes the standby instance to active when software or hardware faults affect the active instance.
The Cisco SVO admin plane allows you to:
-
Create the super user for the SVO card model or the admin user for the external server model.
-
Create, update, or delete SVO instances of type ROADM, OLA, DGE, or TXP. You can also view the details of the SVO instances.
Note
The first SVO instance created on the SVO card is always a ROADM instance. Subsequent SVO instances can be OLA, DGE, or TXP.
-
Control, monitor, and performs health checks of the SVO instances.
-
Auto switch SVO instances during a software or hardware fault in the SVO cards or servers.
-
Force a manual switch between the active and standby SVO instances.
-
View parameters of the network configuration file.
-
View a list of allowed and blocked IP addresses
-
Troubleshoot using diagnostics. A zip file containing the log files from the admin plane can be downloaded.
-
Reset the SVO card to factory defaults. This action erases all containers and configurations on the SVO card.
The following table highlights the differences between the two types of system installation.
SVO Card Model |
External Server Model |
---|---|
The super user must be created to log in to the admin plane. |
The admin user must be created to log in to the admin plane. |
Only IPv4 addresses can be configured. |
IPv4 or IPv6 addresses can be configured independently for the three networks (Management, HA, and Devices) during the installation. |
Only one ROADM SVO instance can be created. Subsequent instances must be of type OLA, DGE, or TXP. |
Any number of ROADM, OLA, DGE, or TXP SVO can be created. |
The SVO card can be reset to its default values. |
— |