Cisco SVO Admin Plane

This chapter describes the admin plane that used in Cisco NCS 2000 SVO and its related tasks.

Table 1. Feature History

Feature Name

Release Information

Feature Description

Admin Plane UI Enhancements

Cisco NCS 2000 Release 12.2

The following admin plane UI enhancements are done to improve the user experience:

  • Flexible memory reservation replaces memory profiles. This enhancement allows the user to assign desired memory for an SVO instance.

  • IP Assignment Policy page replaces IP Filtering page. This change enables the user to modify IP addresses in the allowed list and denied list. In case of conflicting entries, the allowed IP address is preferred.

  • SVO Runtime Status page simplifies troubleshooting and allows the user to extract detailed information about the runtime environment of both the local and remote SVO instances.

  • Admin Plane Restart button replaces Reset to Factory Default button in the Utilities page. This enhancement enables the user to restart the admin plane when required.

  • Certificates page is introduced to check the details of SVO admin plane. The Renew Certificate button can be used to extend the lifetime of self-signed admin plane certificates by five years.

Admin Plane UI Enhancements

Cisco NCS 2000 Release 12.3

The following admin plane UI enhancements are done to improve the user experience:

  • Statistics menu is introduced to present the memory details of the SVO instances in a table. The SVO Instances Statistics page contains SVO Instance Memory Statistics icon to view the memory details and Download Memory Statistics icon to download the memory details.

  • SVO Instance Details page is updated with Restart SVO Container, Force local SVO Container, and Delete SVO Container icons to troubleshoot both the local and remote SVO instances.

  • Certificates page is updated with Upload Certificate button. The Upload Certificate button can be used to upload a customized certificate by providing Key and Certificate files in .PEM format.

  • Scripts menu is introduced to upload custom scripts provided by Cisco. The custom scripts provide access to a few object models of the application.

Admin Plane UI Enhancements

Cisco NCS 2000 Release 12.3.1

The following admin plane UI enhancements are done to improve the user experience:

  • SVO containers now have the limit memory besides the reseved memory. The limit memory is a threshold that is set by the Admin Plane at 2 GB higher than the reserved memory. When you configure the reserved memory, the Admin Plane automatically assigns the limit memory that is shared by the SVO containers. The limit memory acts a buffer to absorb the temporary peak memory requirements.

  • In IP Assignment Policy page, you can enter multiple IP addresses using Range, List, and Wildcard inputs. This approach reduces the tedious and error-prone task of manually typing multiple IP addresses.

  • Troubleshooting menu is introduced to perform on-demand health checks on the network infrastructure and identify the common misconfiguration. You can view the report in the Network Troubleshooting page.

  • The new Properties menu enables you to easily modify and customize multiple admin plane properties. This menu reduces the task of manually editing each property file in the local system.

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.

—

Log into the Cisco SVO Admin Plane

Use this task to log in to the Cisco SVO admin plane.

Procedure

Step 1

In the browser URL field, enter the IP address of the admin plane (https://IP_address/login).

The login page appears.

Step 2

Enter the username and password.

In an SVO card system, only the superuser is allowed to log in to the Cisco SVO admin plane.

Step 3

Click Login.

The SVO Instances page is displayed.

SVO Admin Plane Home Page

Table 2. Feature History

Feature Name

Release Information

Feature Description

Device Synchronization and Alarm Status Icon

Cisco NCS 2000 Release 12.3

The device synchronization and alarm status icon indicates the status of the device and alarm synchronization with varying colors. The colors in the synchronization status icon are:

  • Green

  • Orange

  • Red

Side Menu Items

In the SVO Admin Plane home page, the menu items are present in the left panel. The menu items allow you to monitor and troubleshoot SVO instances, view certificates, and restart admin plane. The following list describes the menu items.

  • Instances—Instances menu enables you to create, edit, and monitor SVO instances.

  • Diagnostics—Diagnostics menu allows you to download log files to troubleshoot SVO instances.

  • Networks—Networks menu enables you to configure networks and assign IP addresses.

  • Certificates—Certificates menu enables you to view and renew the self-signed admin plane certificates.

  • Utilities—Utilities menu allows you to restart the admin plane.

Device Synchronization and Alarm Status Icon

The device synchronization and alarm status are indicated as a summary icon with changing colors close to the bell icon.


Note

The icon appears only when you synchronize a device.

The icon indicates the device synchronization and alarm status with respective colors. The icon color changes from lower to a higher priority. The icon statuses are:

  • Green—All the defined devices are connected and synchronized. The device status is alarm-synchronised.

  • Orange—One or more devices are disconnected or locked by the user. The device status changes as sync-not-started, sync-configuration, and sync-operational.

  • Red—One or more devices have sync-error, sync-not-completed, or out-of-sync-alarms.

Router Icon (BGP Status)

Each Admin Plane constantly monitors its BGP daemon, exchanging information with its peer about the BGP service and neighbor relationship status.


Note

The icon appears only when SVO is installed with management interconnection at Layer 3.

A router icon with two colored dots over it indicate the neighbor relationship status of the servers or VMs with the core router. The first dot represents the local status, and the second dot represents the remote status. The dots statuses are:

  • Green—Server or VM has established BGP connection.

  • Red—Server or VM has lost or not yet established BGP connection.

Bell Icon (HA Status)

The icon on the top right of the SVO home page indicates the status of high availability network (primary link) and devices network (secondary link). The icon statuses are:

  • Green—Both the primary and secondary links are up. High availability is working successfully.

  • Yellow—A warning that the primary link is up but the secondary link is down.

  • Red—There are two cases:

    • Small red icon—The primary link is down but the admin planes are able to communicate because the secondary link is up.

    • Large red icon—Both the primary and secondary links are down and the server is functioning in standalone mode.

User Profile Icon

The user profile icon displays the username and the log out option for the user to exit the current SVO session.

SVO Instances

An SVO instance is a software virtualization of the physical NCS 2000 node that has been configured to manage. SVO instances are of types—ROADM, OLA, DGE, and TXP. In an SVO card model, you can configure a maximum of one ROADM SVO instance and up to 30 OLA DGE, or TXP SVO instances.

In an external server model, you can configure any number of ROADM, OLA, DGE, or TXP SVO instances.

You can create, update and delete SVO instances using the admin plane. Each SVO instance runs as an active instance on one server and as a standby instance on the other server. It is also possible to manually switch the roles of the SVO instance between active and standby.

The peer admin planes that are running on the local and remote server respectively have two intercommunication links, one through the HA network (primary link) and the other through the devices network (secondary link).

The table displays the SVO instances that were created. Each row has two entries relating to the local and remote SVO card or server. In each row, the first entry is the local instance and the second entry is the remote instance. The details are:

  • Name—Name of the SVO instance.

  • IP Address—The IP address of the SVO instance. It is IPv4 for the SVO card model, and IPv6 or IPv4 for the external server model.

  • SW version—SW version on the server.

  • State—State of the SVO instance.

  • App State—State of the SVO application that is running on the SVO instance.

    • During a manual switching process, the App State field displays different statuses such as SWITCHING, SWITCH_DONE, or UP.

    • The App State field displays ACTIVATING or ACTIVATE_RESTART only after the SVO web UI has requested the admin plane to orchestrate the activation process.

  • Role —Role of the SVO instance. The roles are ACTIVE, STANDBY, NONE, and UNKNOWN. In case of issues or specific SVO states, special tags are displayed such as NOT_RESPONDING, STARTING,STOPPED, or BAD_CLUSTER.


    Note

    The green icon indicates the reachability of the SVO instance to the connected NCS 2000 device. If the active SVO instance is unable to reach the NCS 2000 device due to a network segregation, it performs an auto-switch.

  • Up Time—Up time of the SVO instance.

  • Type—Label for the SVO instance.

  • Action—A set of actions can be performed on the SVO instance:

    • Details of the SVO instance—Click this icon to view the summary of the local and remote SVO instance.

    • Edit SVO Instance—Click this icon to edit the memory size of the SVO instance.

    • Switch SVO Instance—Click this icon to manually switch the SVO instance between servers.


      Note

      A switch operation is possible only if both the SVO instances are up and running and the role of the instances are Active and Standby.

    • Delete SVO Instance—Click this icon to delete an SVO instance.


      Note

      This icon is disabled when a switch operation is in progress.

Create an SVO Instance

Use this task to configure an SVO instance.

Before you begin

Log into the Cisco SVO Admin Plane

Procedure

Step 1

Click the + button at the top-left of the SVO Instances page.

The SVO Instance Configuration page appears.

Step 2

In the General Info area, perform these steps:

  1. Enter the name for the new SVO instance in the Name field.

    The name is mandatory and must be unique among the SVO instances managed by the admin plane. It can contain a minimum of two characters and a maximum of 64 characters. It can include numbers, uppercase letters, lowercase letters, dashes (-), or underscores (_).

  2. Choose the version from the Software Version drop-down list.

  3. Choose the type of the SVO instance from the TDM Terminology drop-down list.

    The two options are ANSI and ETSI.

  4. Choose the label of the SVO instance from the Type drop-down list.

    The four options are ROADM, OLA, DGE, and TXP. The type indicates the role of the SVO instance in the network.

    Note

     

    When Type is selected, a default value for memory size is displayed in the Reserved Memory GB field.

  5. Choose the memory size to be allocated to the SVO instance from the Reserved Memory GB field.

    The user is allowed to reserve the SVO container memory in steps of 0.1GB. This value is visible and summarized at server level in the SVO instances table.

    Note

     
    In addition to the reserved memory, SVO container allocates the Limit Memory. SVO solution automatically sets the Limit Memory with a threshold value of 2 GB higher than the configured Reserved Memory. This threshold acts as a buffer to absorb the temporary peak memory requirements. Docker engine kills the operations that cross the Limit Memory threshold due to Out-of-Memory (OOM).

    If the reserved memory is alloted more than the server or VM memory, the docker engine fails the allocation. Allocate only up to 80 percent of the server or VM memory for the Reserved Memory.

Step 3

In the Admin User area, perform these steps:

  1. Enter the username in the Username field.

    The values "admin," "oper," "private," or, "public" cannot be used as the admin username.

  2. Enter the password in the Password field.

    The password must be a minimum of eight characters. The password must contain at least an uppercase letter a number, and a special character. The special characters supported are ! $ % ^ ( ) [ ] _ - ~ { } . +

  3. Enter the password again in the Retype Password field.

Step 4

In the Management Network area, the system suggests the management subnets to be used in the IPv4 Address or the IPv6 Address fields, depending on the type of addressing defined during the installation. The system checks for constraints defined in the network configuration file and ensures that the IP addresses that are assigned are not in use.

  1. Enter the IPv4 Address in the IPv4 Address field in a SVO card model.

    or

  2. Enter the IPv4 or the IPv6 Address in the IPv4 Address or IPv6 Address field respectively in an external server model.

Step 5

Click Create.

Step 6

A message is displayed indicating the creation of the SVO instance.

Step 7

Click OK.

The SVO Instances page appears. The table displays the new SVO instance.

The SVO instance can now be accessed through a web browser.

View Details of an SVO Instance

Use this task to view the details of an SVO instance.

Before you begin

Log into the Cisco SVO Admin Plane

Procedure

Step 1

Choose the SVO instance you want to view.

Step 2

Click Details of SVO Instance.

The SVO Instance Details page is displayed. See SVO Instance Details.

Edit Reserved Memory of an SVO Instance

Use this task to edit the memory size of the SVO instance.

Before you begin

Log into the Cisco SVO Admin Plane

Procedure

Step 1

Choose the SVO instance that you want to edit.

Step 2

Click Edit SVO Instance.

The SVO Instance Edit page is displayed.

Step 3

Choose the memory size to allocate to the SVO instance from the Reserved Memory GB field.

Note

 
After upgrading the SVO solution to R12.31, you should adjust the containers memory to default 2.1GB. Allocate only up to 80 percent of the server or VM memory for the Reserved Memory. Enough free Host memory must be available to set the Limit Memory.

Step 4

Click Edit.

Switch SVO Instances

Use this task to manually switch between active and standby SVO instances.

Before you begin

Log into the Cisco SVO Admin Plane

Procedure

Step 1

Choose the SVO instance you want to switch.

Step 2

Click Switch SVO Instances.

A dialog box is displayed asking for confirmation.

Step 3

Click Confirm.

During the switching process, the App State field displays different statuses such as SWITCHING, SWITCH_DONE, and UP. The Role field displays NONE, ACTIVE, and STANDBY.

Delete an SVO Instance

Use this task to delete an SVO instance.

Before you begin

Log into the Cisco SVO Admin Plane

Procedure

Step 1

Choose the SVO instance you want to delete.

Step 2

Click Delete SVO Instances.

A dialog box is displayed asking for confirmation of deletion.

Step 3

Click Confirm.

SVO Instance Details

The SVO Instance Details page provides information on the various properties of both local and remote SVO instances. The Admin & Troubleshooting property includes a set of action icons for both SVO instances. The action icons enable you to troubleshoot the SVO instances. The actions are:

  • Get local SVO Runtime Status—Click this icon to extract detailed information about the runtime status of both local and remote SVO applications.

  • Restart Container—Click this icon to restart the target SVO container.

  • Delete local SVO container—Click this icon to delete the target SVO container.

  • Force as Active the local SVO container—Click this icon to force the local SVO container to become the active instance.

Retrieve SVO Runtime Status

Use this task to retrieve the runtime information of local or remote SVO instances.

Procedure

Step 1

Click the heartbeat icon next to the required instance.

The SVO Runtime Status page is displayed.

Step 2

Expand the related sections to view the details of the SVO instances.

The sections are NCS Status, HA Agent, and NCS Launcher.

Step 3

Click the hyperlink above the expandable sections to view the details in separate window as plain text.

Restart SVO Container

Use this task to restart the required SVO instance.

Procedure

Click the reload icon next to the desired instance.

You are redirected to the SVO Instances page.

The SVO instance reloads.

Delete SVO Container

Use this task to delete the required SVO instance.

Procedure

Step 1

Click the trashcan icon next to the required instance.

A warning dialog box appears.

Step 2

Click Confirm.

Success message appears.

Step 3

Click OK.

You are redirected to the SVO Instances page.

Force Active the Local SVO Container

Use this task to force a local SVO instance as ACTIVE. This action must be performed only when the admin plane fails to assign a role to the local instance.

Procedure

Click the go-forward icon next to the local instance.

You are redirected to the SVO Instances page.

The status of the local SVO instance changes from NONE to ACTIVE.

IP Assignment Policy

The IP Assignment Policy page displays two sets of IP addresses:

  • Allowed List—Contains a list of available IP addresses.

  • Denied List—Contains a list of blocked IP addresses.

The list of allowed and denied IP addresses displayed on this page are stored in two separate files on the file system of the local and remote server.

The IP lists are applicable only to the devices network. During the creation of the SVO instance, the denied list prevents the admin plane from selecting any IP address that is on the list for the IPv4 and IPv6 addresses whereas the allowed list permits the admin plane to select any IP address that is in the list.

The IP list can be modified on this page at runtime.

To view these IP addresses in the admin plane:

Before you begin

Log into the Cisco SVO Admin Plane.

Procedure

Step 1

Click Networks in the left panel and choose IP Assignment Policy.

Step 2

Enter the needed IP addresses in the Allowed IP addresses list and Denied IP addresses list columns.

Use one of the following methods to enter multiple IP addresses:

  • List—For Example, 192.168.1.1,4 becomes [192.168.1.1, 192.168.1.4].

    Use comma to enter a list of IP addresses.

  • Range—For example, 192.168.1.1-4 becomes [192.168.1.1, 192.168.1.2, 192.168.1.3, 192.168.1.4].

    Use hyphen to define a range of IP addresses.

  • Wildcard—For example, 192.168.1.* becomes [192.168.1.1,..... , 192.168.1.255].

    Use asterisk to enter all the possible IP addresses in the subnet.

Step 3

Click Apply.

When you apply the changes, all the shortcuts expand and join into the final list.

Note

 

If conflicting entries exist, the allowed IP address has the precedence.

Restart Admin Plane

Use this task to restart the SVO admin plane.

Before you begin

Log into the Cisco SVO Admin Plane

Procedure

Step 1

Click Utilities in the left panel.

The Utilities page appears.

Step 2

Click Restart Admin Plane.

All the SVO instances and configurations available on the SVO card are restarted.

A Warning! dialog box appears.

Step 3

Click Confirm.

Warning

 

Proceeding with confirmation may interrupt any running procedure.

Manage Certificate

Certificates are required to enable security protocols for the SVO application. Use this task to generate a self-signed certificate or upload your own certificate for the admin plane.

Before you begin

Log into the Cisco SVO Admin Plane.

Procedure

Step 1

Click Certificates in the left panel.

The Certificates page displays the certificate details.

Step 2

To manage the certificates, perform one of the following actions:

  • In the case of a self-signed certificate, click Generate Selfsigned Certificate.

  • In the case of an own certificate, perform the following steps:

    1. Click Upload Certificate.

      The Custom Certificate Configuration dialog box appears.

    2. In Key file, click the Add icon to upload the key file in .pem format.

    3. In Certificate file, click the Add icon to upload the certificate file in .pem format.

    4. Click Generate Certificate.

      Your certificate is uploaded.

SVO Instances Statistics

SVO instances statistics table is a collection of memory resource details for each SVO instance. The table periodically collects details such as allocation and consumption of memory for each SVO instance. The statistics table is similar to the SVO instances table with a Memory column.

You can view and download the statistical data of the SVO instances using the icons in the Actions column. Each SVO instance runs as an active instance on one server and as a standby instance on the other server.

The table displays the created SVO instances and the associated memory details. Each row has two entries relating to the local and remote SVO card or server. In each row, the first entry is the local instance and the second entry is the remote instance. The details are:

  • Name—Name of the SVO instance.

  • IP Address—The IP address of the SVO instance. It is IPv4 for the SVO card model, and IPv6 or IPv4 for the external server model.

  • SW version—SW version on the server.

  • Role—Role of the SVO instance.


    Note

    The green icon indicates the reachability of the SVO instance to the connected NCS 2000 device. If the active SVO instance is unable to reach the NCS 2000 device due to a network segregation, it performs an auto-switch.

  • Type—Label for the SVO instance.

  • Memory (GB) Min/Max/Actual—Minimum and maximum memory allocated for each instance and actual memory utilized by each instance.

  • Actions—A set of actions performed on the SVO instance. The actions are:

    • Memory Statistics Graph—Click this icon to view the summary of the local and remote SVO instance.

    • Download Local Statistics File—Click this icon to download all the statistics files of the local SVO instance as a zip package.

View Memory Statistics Graphical Summary

Use this task to view the memory details of local and remote SVO instances in graphical format.

Before you begin

Log into the Cisco SVO Admin Plane

Procedure

Step 1

Click Statistics in the left panel.

The Statistics page appears.

Step 2

Click Memory Statistics Graph for an SVO instance.

The SVO Instance Memory Statistics page appears displaying memory statistics for both local and remote instances.

Note

 

The Memory Statistics graph displays a fine-grained collection of memory usage of the SVO instance in the last few days. Memory limits defined at creation time are also displayed for reference. The Historical Daily Statistics graph displays the daily memory details such as average memory usage and maximum memory usage of the SVO instances since creation.

Step 3

(Optional) Click the calender icon to view the statistics for the required period.

Step 4

Click the table icon to export the data as plain text in a new window.

Download Local SVO Instances Memory Files

Use this task to download the local SVO instances memory files.

Before you begin

Log into the Cisco SVO Admin Plane

Procedure

Step 1

Click Statistics in the left panel.

The Statistics page appears.

Step 2

Click Download Local Statistics File for an SVO instance.

A confirmation message appears.

Step 3

Click OK.

The statistics files for the local SVO instance downloads as a zip package.

Download Diagnostic Log Files

Use this task to download the diagnostic log files.

Before you begin

Log into the Cisco SVO Admin Plane

Procedure

Step 1

Click Diagnostic in the left panel.

The Diagnostic page appears.

Step 2

Click Download Log Files.

A zip file that contains the admin plane logs is downloaded.

Custom Scripts

Custom scripts are quick solutions that are specific to each feature. The scripts provide access to the full application object model to extend the capabilities of the admin plane at runtime

The custom scripts let you do the following actions and more:

  • Add UI- and REST-based custom actions

  • Define in a declarative way web input forms for action parameters

  • Export data in different text formats

  • Add custom validation logic, for example, when creating a new SVO instance

  • Perform custom tasks on application events, for example, when the HA role changes

  • Define scripted HA services that can communicate through the Admin Plane GRPC channels

The scripts table displays the added scripts and the relevant script details. The following list describes the table items.

  • Name—Name of the custom script

  • Type—Type of the custom script

  • Target—Target GUI of the SVO admin plane

  • Status—Status of the custom script

  • Version—Version of the custom script added

  • Lifetime—Duration of the script in the admin plane in dd:hh:mm:ss format

  • Action—Action to delete the added script

Add Custom Scripts

Use this task to add custom scripts to the SVO admin plane, for example, importInstancesCSV file.

Before you begin

Log into the Cisco SVO Admin Plane

Procedure

Step 1

Click Scripts in the left panel.

The Scripts page appears.

Step 2

Click Add new SVO script.

An explorer window opens.

Step 3

Select a custom script and click Open, for example, importInstancesCSV file.

A Success message appears.

Step 4

Click OK.

The importInstancesCSV script is added to the scripts table.

Step 5

Check the SVO Instances table in the admin plane for the Import CSV button.

The Import CSV button allows you to import the SVO instances using a CSV file.

Modify Admin Plane Properties

Admin plane is customizable through several configuration properties. A few of the admin plane properties are useful in particular contexts or for troubleshooting. From Release 12.31, some “expert only” settings are modifiable directly from the Admin Plane web UI.

Use this task to modify the admin plane properties.

Before you begin

Log into the Cisco SVO Admin Plane

Procedure

Step 1

Click Tools in the left panel and choose Properties.

The Properties page appears to display the admin plane properties, current values, and edited values.

Table 3. Properties Table

Label

Description

Property

Displays the customizable admin plane properties

Current Value

Displays the current values of each admin plane property

Edited Value

This field is editable. Enter the values for the admin plane properties.

Step 2

To modify the values for the admin plane properties, perform one of the following actions:

Tip

 
When you hover over a property, a tooltip appears to explain the property purpose.

  • In Edited Value, enter the needed values for the properties that you want to customize.

  • Click Reset to default to restore the default settings for all the properties.

Step 3

Click Apply to apply the modified values.

A Warning! message appears.

Step 4

Click Continue.

A Success! message appears.

Step 5

Click OK.

Step 6

Restart the admin plane to commit the modified values in the properties files. See Restart Admin Plane.

Remember

 
Modified properties are not automatically propagated to the peer server. Make the same changes on the peer server to align the properties files with the host server.

Troubleshoot Networks

SVO requires proper configurations of management, high availability, and devices networks. The Networks Troubleshooting page allows performing general health-checks and identifying some common misconfiguration in the network infrastructure. It performs extra reachability checks when you specify an optional device IP address of any relevant network device.

Use this task to initiate the troubleshooting report of the network infrastructure or a target device.

Before you begin

Log into the Cisco SVO Admin Plane

Procedure

Step 1

Click Networks in the left panel and choose Troubleshooting.

The Networks Troubleshooting page appears.

Step 2

Click Troubleshooting to initiate checks on the network infrastructure.

Network troubleshooting report appears in the pane below the Troubleshooting button.

Step 3

(Optional) In Device IP address: field, enter the IP address of the device and click Troubleshooting.

Note

 
Enter only the IP address of a device that is reachable without adding any IP route.

Troubleshooting report for the target device appears in the pane below the Troubleshooting button.