0% found this document useful (0 votes)
228 views3 pages

OmniVista Cirrus Switch Setup Guide

To add switches to OmniVista Cirrus, you must first prepare the environment by ensuring the switches have internet access and firewall rules allow communication. Then, you either power on a new switch to trigger activation, or reboot an existing switch. For switches already in use, you can log in via CLI and run commands to disable and re-enable the cloud agent to trigger activation.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
228 views3 pages

OmniVista Cirrus Switch Setup Guide

To add switches to OmniVista Cirrus, you must first prepare the environment by ensuring the switches have internet access and firewall rules allow communication. Then, you either power on a new switch to trigger activation, or reboot an existing switch. For switches already in use, you can log in via CLI and run commands to disable and re-enable the cloud agent to trigger activation.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

20/5/22, 17:37 Artículo de Knowledge

How manage switch in OmniVista Cirrus


Información

Título How manage switch in OmniVista Cirrus


Nombre de URL 000053073
Resumen Procedure for adding the switches in OVC.
Número de artículo 000053073
Fecha de la última modificación 31/03/2020 8:27
Description

Topology

Detailed Description

Environment
Product name: OVC
Product release: 3.1.0

Scenario

Need to add Omniswitch both 6x and 8x switches to OmniVista Cirrus


Version Build 3.1.0
Resolution

Resolution Analysis

The switches should have internet access and firewall should all the traffic to the activation server.
 
https://activation.myovcloud.com

Solution

Step 1: Prepare the environment to accept the switch.


Step 2: Make the switch contact OmniVista Cirrus server for activation.

Step 1:

a. Upgrade the switch to the right software version and setup the network to allow the switch to connect to OmniVista cirrus (DHCP config ex: option 43 sub-option 1, Firewall config)
b. Add the switch serial numbers in the Device Catalog application and wait for the “Device Status” to reach either “Waiting for First Contact” or “Registered” state.

https://alcatel-lucent-enterprise.secure.force.com/knowledgebp/articles/Customer_Care_Article/000053073/p?pubstatus=o 1/3
20/5/22, 17:37 Artículo de Knowledge

a. If aiming for full management of the switch from OmniVista Cirrus, click on Assign License to the devices in the Device Catalog application.
b. OV provides a default pre-provisioning template for AOS switches starting from build 44 and so there is NO need for setting up Pre-provisioning for AOS.

Step 2 depends on how fresh the switch is:


 

a. If the switch is fresh out of the box with only factory config and NEVER powered-on before, then simply power-on the switch. The switch should reach “OV Managed” Device Status in the
Device Catalog.
b. If the switch was already connected to the network, then simply reboot the switch to trigger it to contact OV Cirrus.  If a reboot of the switch is not feasible because it is doing a critical
function in the network, then it means we are in a BROWN FIELD usecase, where the switch was being configured via CLI. So, there should be no problem for the customer to log into the
CLI and type the following commands:
https://alcatel-lucent-enterprise.secure.force.com/knowledgebp/articles/Customer_Care_Article/000053073/p?pubstatus=o 2/3
20/5/22, 17:37 Artículo de Knowledge
cloud-agent admin-state disable force

cloud-agent admin-state enable

please verify the status with


show cloud-agent status

 
Attachment  

https://alcatel-lucent-enterprise.secure.force.com/knowledgebp/articles/Customer_Care_Article/000053073/p?pubstatus=o 3/3

You might also like