As part of the activation process on licensed LAN devices, OmniVista Cirrus automatically applies an initial configuration (e.g., SNMP version, device login/password) to the device using a pre-configured Default Pre-Provisioning Template. You can customize the Default Pre-Provisioning Template, and can also configure Custom Templates and apply it to a LAN device after its initial activation process.
For APs, pre-provisioning is done through the AP Registration application. Click on the Wireless Pre-Provisioning button to go to the AP Registration application. You should complete wireless pre-provisioning before you start the activation process on the wireless devices.
The Default Pre-Provisioning Template is initially applied to all devices when they are licensed. The Default Template can be customized. You can also create a custom template that can be applied to a switch any time after the initial pre-provisioning process is complete.
Configuring the Default Template
You can edit the Default Pre-Provisioning template by clicking on the Default Template button to bring up the Config Default Template Screen. Any devices you license after customizing the default template will use the new configuration. Complete the fields as described below and click on OK.
- SNMP Version - The SNMP version that OmniVista will use to communicate with the device. The default version for AOS devices is v2, but v3 is also supported.
- Auth & Priv Protocol (SNMP v3 Only) - The authentication protocol OmniVista will use for SNMP communication with the device. Authentication uses a secret key to produce a "fingerprint" of the message. The fingerprint is included within the message. The device that receives the message uses the same secret key to validate that the fingerprint is correct. If it is, and if the message was received in a timely manner, then the message is considered authenticated. Otherwise, the message is discarded. The fingerprint is called a Message Authentication Code, or MAC.
- Timeout - The time period, in milliseconds, that OmniVista will wait for a switch to respond to a connection request before assuming that the request has timed-out (Default = 5,000)
- Retry Count - The number of times that OmniVista will attempt to connect to a switch (Default = 3).
SNMP User Setup
- Username - The SNMP Username. This is the name that OmniVista will use to connect to the device.
- Auth Password - SNMP User Password. This is the Username password that OmniVista will use to connect to the device.
- Confirm Auth Password - Re-enter the Auth Password.
- SNMP Role - Select the SNMP Role OmniVista will have for device management - Read Only or Read/Write (Default).
Other Access Methods
- Use the same Credential as SNMP User Setup - Use the SNMP Username/Password and Role configured above for CLI/FTP access to devices.
- Use a Different Credential - Configure the CLI/FTP Username/Password and Role for CLI/FTP access to the device.
- CLI/FTP User Name - The user name that OmniVista will use to establish CLI/FTP sessions with the discovered devices. The user name specified will be used to auto-login to devices when CLI sessions are established. It will also be used to perform FTP with the device when configuration files are saved and restored (see note below).
- CLI/FTP Password - The password that OmniVista will use to establish CLI/FTP sessions with the discovered devices. The user name specified will be used to auto-login to devices when CLI sessions are established. It will also be used to perform FTP with the device when configuration files are saved and restored (see note below).
- Confirm CLI/FTP Password - Confirm the CLI/FTP Password.
- CLI/FTP Role - Select the CLI/FTP Role OmniVista will have for device management - Read Only or Read/Write (Default).
- Save Config to Certified Directory - Select whether you want the device to save this configuration to the Certified Directory (Yes/No).
Creating a Custom Template
Select a device in the Pre-Provisioning Table and click on the Set Up Chassis button at the top of the table. The Chassis Configuration Screen appears with the "Start From Scratch" radio button selected. Update fields as described above, then click on the Save As New Template button. Enter a name for the template in the Name pop-up and click Save. This new Custom Template will now be available for selection under the "Select a Template" drop-down and can be applied to any switch in the Pre-Provisioning Table.
Applying a Custom Template to a Device
Once a switch has been through the initial Pre-Provisioning process, you can later assign a custom template to the switch. Select the switch(es) and click on the Set Up Chassis button at the top of the table. The Chassis Configurations Screen appears. If you want, you can click on the "Chassis" link at the top of the screen (e.g., "2 Selected Chassis) to view the current configurations of the the selected devices.
Select a template from the "Select a Template" drop-down and click on the Apply to Chassis button. You must restart the activation process on the updated switch(es) for the change to take effect. See the Device Catalog online help for more information on restarting the activation process on a device.
Pre-Provisioning Wireless Devices
Clicking on the Wireless Pre-Provisioning button takes you to the AP Registration application, which is used to manage APs with OmniVista Cirrus. When APs are added to the Device Catalog, validated, and licensed they appear in the Managed AP Tab of the Access Point List and are ready for management. The AP Registration application can be used to assign APs to different AP Groups and configure AP attributes.
Note: The first time you open the AP Registration application, the "Init Registration App" window will appear. This is used to set certain basic pre-provisioning AP parameters (e.g., Country Code, Trust Status). Complete the fields in the window. This pre-provisioning procedure will only have to be done the first time you open the AP Registration application. The configuration will automatically be applied to any subsequent APs you license.
APs must be “trusted” to be managed by OmniVista Cirrus. The “Trust All” field in the Init Registration App" window is enabled by default. This can be convenient when initially adding a large number of APs. If you would like to exercise administrative intervention before accepting new APs, you might want to click on the Trust All" icon (lock in unlocked position) at the top of the Access Points screen to toggle the setting back to “Untrust All” icon (lock in locked position).
See the AP Registration online help for more information on AP configuration, including "Trusted/Untrusted" APs.
The Pre-Provisioning Table displays information for all LAN Devices on your network that have been through the Pre-Provisioning process.
- Serial Number - The serial number of the device.
- MAC Address - The MAC address of the device.
- Device IP - The IP address of the device in your network.
- State - The state of the device:
- Customized - A custom configuration has been applied to the device.
- Default Template - The device is using the Pre-Provisioning Default Template.
- Device Status - The status of the device in the provisioning process (e.g., Waiting for First Contact, Configured Successfully).
- Waiting for First Contact - The device has not made initial contact the OmniVista Cirrus Server, or the user has set up a new configuration for the device and has not restarted the activation process. The activation process needs to be started on the device to apply the configuration to the device.
- Configuring - The device has contacted the OmniVista Cirrus Server and is in the process of configuring the device.
- Writing Memory - The device is writing its configuration to the Certified Directory.
- Configured Successfully - The device was successfully configured by the Pre-Provisioning application.
- Found as Pre-Provisioned - The device has completed pre-provisioning and the configuration has been applied to the device.
- Configuration Failed - Pre-Provisioning failed on the device. The configuration has not been applied to the device.
- Last Contact - The date and time the device last contacted the OmniVista Cirrus Server.