Configuration and Discovery

The following sections describe how to configure and discover Cisco Meeting Server for monitoring by SL1 using the Cisco: Meeting Server PowerPack:

Prerequisites for Monitoring Cisco Meeting Server

To monitor the Cisco Meeting Server, you must be able to access both the Cisco Meeting Server Mainboard Management Processor (MMP) and the Cisco Meeting Server API. Accessing the MMP requires an account with admin access. If you wish to create an a new user with admin access, refer to the section "MMP User Account Commands" in the Cisco Meeting Server MMP Command Line Reference document.

You access the Cisco Meeting Server MMP through SSH, while you access the Cisco Meeting Server API through HTTPS.

• If you can reach both of these through the same IP address, you can typically use a single Basic/Snippet credential.
• If the two interfaces have separate IP addresses, or if the API is listening on a port other than 443, you must create two separate credentials. In addition, you should include an SNMP credential as part of discovery to correctly classify the device .

Creating Credentials for Cisco Meeting Server Systems Using a Single IP Address

To monitor Cisco Meeting Server in SL1 in an environment where you can access the Cisco Meeting Server MMP and the Cisco Meeting Server API through the same IP address, you must configure a Basic/Snippet credential and a standard SNMP credential that SL1 can use to discover and communicate with Cisco Meeting Server devices.

To configure the Basic/Snippet credential for Cisco: Meeting Server:

1. Go to the Credential Management page (System > Manage > Credentials).

2. Locate the Cisco Meeting Server Example credential, and then click its wrench icon (). The Edit Basic/Snippet Credential modal page appears.

3. Supply values in the following fields:

• Credential Name. Type a new name for the credential.

• Hostname/IP. Type "%D".
• Port. Type "22".
• Timeout(ms). Type "15000".
• Username. Type the username for the Cisco Meeting Server account with admin access.
• Password. Type the password associated with the admin account.

4. Click the Save As button.

To configure the SNMP credential for Cisco: Meeting Server:

1. Go to the Credential Management page (System > Manage > Credentials).

2. Click the Actions button and select Create SNMP Credential. The Credential Editor page appears.

3. Supply values in the following fields:

• Profile Name. Name of the credential. Can be any combination of alphanumeric characters. This field is required.

• SNMP Version. SNMP version. Choices are SNMP V1, SNMP V2, and SNMP V3. The default value is SNMP V2. This field is required.
• Port. The port SL1 will use to communicate with the external device or application. The default value is 161. This field is required.
• Timeout (ms). Time, in milliseconds, after which SL1 will stop trying to communicate with the SNMP device. The default value is 1500. This field is required.
• Retries. Number of times SL1 will try to authenticate and communicate with the external device. The default value is 1. This field is required.

4. Click the Save button to save the new SNMP credential.

Creating Credentials for Cisco Meeting Server Systems Using More than One IP Address

To monitor Cisco Meeting Server in SL1 in an environment where you access the Cisco Meeting Server MMP and the Cisco Meeting Server API through multiple IP addresses, you must configure a Basic/Snippet credential for each interface and a standard SNMP credential that SL1 can use to discover and communicate with Cisco Meeting Server devices.

You will need to manually align the associated Dynamic Applications with the corresponding Basic/Snippet credentials after discovery is complete.

To configure the Basic/Snippet credential for the system's Mainboard Management Processor (MMP)/SSH interface:

1. Go to the Credential Management page (System > Manage > Credentials).

2. Click the Actions button and select Create Basic/Snippet Credential. The Credential Editor page appears.

3. Supply values in the following fields:

• Credential Name. Type a new name for the credential.

• Hostname/IP. Type the IP address of the SSH interface.
• Port. Type "22". This is the default value, but you can adjust it depending on your environment.
• Timeout(ms). Type "15000".  You can adjust this value depending on your environment.
• Username. Type the username for the Cisco Meeting Server account with admin access.
• Password. Type the password associated with the above account.

4. Click the Save As button.

To configure the Basic/Snippet credential for the API interface:

1. Go to the Credential Management page (System > Manage > Credentials).

2. Click the Actions button and select Create Basic/Snippet Credential. The Credential Editor page appears.

3. Supply values in the following fields:

• Credential Name. Type a new name for the credential.

• Hostname/IP. Type the IP address of the API interface.
• Port. Type "443". 
• Timeout(ms). Type "15000". This value can be adjusted depending on your environment.
• Username. Type the username for the Cisco Meeting Server account with admin access or the account with api access.
• Password. Type the password associated with the above account.

4. Click the Save As button.

To configure the SNMP credential for Cisco: Meeting Server:

1. Go to the Credential Management page (System > Manage > Credentials).

2. Click the Actions button and select Create SNMP Credential. The Credential Editor page appears.

3. Supply values in the following fields:

• Profile Name. Name of the credential. Can be any combination of alphanumeric characters. This field is required.

• SNMP Version. SNMP version. Choices are SNMP V1, SNMP V2, and SNMP V3. The default value is SNMP V2. This field is required.
• Port. The port SL1 will use to communicate with the external device or application. The default value is 161. This field is required.
• Timeout (ms). Time, in milliseconds, after which SL1 will stop trying to communicate with the SNMP device. The default value is 1500. This field is required.
• Retries. Number of times SL1 will try to authenticate and communicate with the external device. The default value is 1. This field is required.

4. Click the Save button to save the new SNMP credential.

Discovering Cisco Meeting Server Component Devices

The following sections describe how to discover Cisco Meeting Server devices. Discovery methods are described for devices that use a single IP address as well as those that use multiple IP addresses.

Discovering Cisco Meeting Server Devices That Use a Single IP Address

To model and monitor your Cisco Meeting Server devices, you must run a discovery session to discover the Cisco Meeting Server component devices that SL1 will use as the root devices for monitoring the applications.

After the discovery session completes, the Dynamic Applications in the Cisco: Meeting Server PowerPack automatically align to the component device, and then the PowerPack discovers, models, and monitors the remaining Cisco Meeting Server devices.

To discover the devices that you want to monitor:

1. On the Devices page () or the Discovery Sessions page (Devices > Discovery Sessions), click the Add Devices button. The Select page appears:

2. Click the Unguided Network Discovery button. Additional information about the requirements for discovery appears in the General Information pane to the right.

3. Click Select. The Add Devices page appears.
4. Complete the following fields:

• Name. Type a unique name for this discovery session. This name is displayed in the list of discovery sessions on the Discovery Sessions tab.
• Description. Optional. Type a short description of the discovery session. You can use the text in this description to search for the discovery session on the Discovery Sessions tab.
• Select the organization to add discovered devices to. Select the name of the organization to which you want to add the discovered devices

5. Click Next. The Credentials page of the Add Devices wizard appears:

6. On the Credentials page, select the SNMP credential and the Basic/Snippet credential you created.

7. Click Next. The Discovery Session Details page of the Add Devices wizard appears:

8. Complete the following fields:

• List of IPs/Hostnames. Type the IP address or hostname for the set of Cisco Meeting Server devices that you want to monitor.
• Which collector will monitor these devices?. Required. Select an existing collector to monitor the discovered devices.
• Run after save. Select this option to run this discovery session as soon as you save the session.

In the Advanced options section, click the down arrow icon () to complete the following fields:

• Discover Non-SNMP. Enable this setting.
• Model Devices. Enable this setting.

9. Click Save and Run if you enabled the Run after save setting, or Save and Close to save the discovery session. The Discovery Sessions page (Devices > Discovery Sessions) displays the new discovery session.
10. If you selected the Run after save option on this page, the discovery session runs, and the Discovery Logs page displays any relevant log messages. If the discovery session locates and adds any devices, the Discovery Logs page includes a link to the Device Investigator page for the discovered device.

Discovering Cisco Meeting Server Devices That Use a Single IP Address in the SL1 Classic User Interface

To model and monitor your Cisco Meeting Server devices, you must run a discovery session to discover the Cisco Meeting Server component devices that SL1 will use as the root devices for monitoring the applications.

After the discovery session completes, the Dynamic Applications in the Cisco: Meeting Server PowerPack automatically align to the component device, and then the PowerPack discovers, models, and monitors the remaining Cisco Meeting Server devices.

To discover the devices that you want to monitor:

1. Go to the Discovery Control Panel page (System > Manage > Classic Discovery).

2. On the Discovery Control Panel, click the Create button.

3. The Discovery Session Editor page appears. On the Discovery Session Editor page, define values in the following fields:

• IP Address/Hostname Discovery List. Type the IP address or hostname for the set of Cisco Meeting Server devices that you want to monitor.
• SNMP Credentials. Select the SNMP credential you created.

• Other Credentials. Select the Basic/Snippet credential you created.
• Discover Non-SNMP. Select this checkbox.
• Model Devices. Select this checkbox.

4. Optionally, you can enter values in the other fields on this page. For more information about the other fields on this page, see the Discovery & Credentials section.
5. Click the Save button, and then close the Discovery Session Editor window.
6. The discovery session you created appears at the top of the Discovery Control Panel page. Click its lightning-bolt icon () to run the discovery session.
7. After the Cisco Meeting Server devices are discovered, click the device icon () to view the Device Properties page for each device.

Discovering Cisco Meeting Server Devices That Use Multiple IP Addresses

To model and monitor your Cisco Meeting Server devices, you must run a discovery session to discover the Cisco Meeting Server component devices that SL1 will use as the root devices for monitoring the applications.

In in an environment where you access the Cisco Meeting Server MMP and the Cisco Meeting Server API through multiple IP addresses, after the discovery session completes, you must manually align the Dynamic Applications associated with each Basic/Snippet credential you created.

To discover the devices that you want to monitor:

1. On the Devices page () or the Discovery Sessions page (Devices > Discovery Sessions), click the Add Devices button. The Select page appears:

2. Click the Unguided Network Discovery button. Additional information about the requirements for discovery appears in the General Information pane to the right.

3. Click Select. The Add Devices page appears.
4. Complete the following fields:

• Name. Type a unique name for this discovery session. This name is displayed in the list of discovery sessions on the Discovery Sessions tab.
• Description. Optional. Type a short description of the discovery session. You can use the text in this description to search for the discovery session on the Discovery Sessions tab.
• Select the organization to add discovered devices to. Select the name of the organization to which you want to add the discovered devices

5. Click Next. The Credentials page of the Add Devices wizard appears:

6. On the Credentials page, select the SNMP credential and the Basic/Snippet credential you created.

7. Click Next. The Discovery Session Details page of the Add Devices wizard appears:

8. Complete the following fields:

• List of IPs/Hostnames. Type the IP address or hostname for the set of Cisco Meeting Server devices that you want to monitor.
• Which collector will monitor these devices?. Required. Select an existing collector to monitor the discovered devices.
• Run after save. Select this option to run this discovery session as soon as you save the session.

In the Advanced options section, click the down arrow icon () to complete the following fields:

• Discover Non-SNMP. Enable this setting.
• Model Devices. Enable this setting.

9. Click Save and Run if you enabled the Run after save setting, or Save and Close to save the discovery session. The Discovery Sessions page (Devices > Discovery Sessions) displays the new discovery session.
10. If you selected the Run after save option on this page, the discovery session runs, and the Discovery Logs page displays any relevant log messages. If the discovery session locates and adds any devices, the Discovery Logs

11. After the Cisco Meeting Server devices are discovered, go to the classic Device Manager page (Devices > Device Manager) and locate the discovered devices.
12. Click on the wrench icon () to view the Device Properties page for each device.

13. In the Device Properties page, click the Collections tab. The Dynamic Application Collections page appears.

14. Click Actions and then select Add Dynamic Application from the menu. The Dynamic Application Alignment page appears.

15. In the Dynamic Applications field, select the following Dynamic Applications:

• Cisco: Meeting Server Network Interface Cache
• Cisco: Meeting Server NTP Cache
• Cisco: Meeting Server System ID Cache

16. In the Credentials field, select the Basic/Snippet credential you configured for the MMP/SSH.
17. Click Save.
18. Click Action and then select Add Dynamic Application from the menu. The Dynamic Application Alignment page appears.
19. In the Dynamic Applications field, select the following Dynamic Applications:

• Cisco: Meeting Server Alarms Configuration
• Cisco: Meeting Server CoSpaces Cache
• Cisco: Meeting Server System Status Cache
• Cisco: Meeting Server Tenants Cache

20. In the Credentials field, select the Basic/Snippet credential you configured for the API interface.
21. Click Save.
22. Click Action and then select Add Dynamic Application from the menu. The Dynamic Application Alignment page appears.
23. In the Dynamic Applications field, select the following Dynamic Applications:

• Cisco: Meeting Server System Configuration
• Cisco: Meeting Server System Performance

24. These applications do not require an associated credential.
25. Click Save. A few minutes after aligning the Dynamic Applications, SL1 will discover and model your Cisco Meeting Server and automatically align other Dynamic Applications to the devices in the system.

Discovering Cisco Meeting Server Devices That Use Multiple IP Addresses in the SL1 Classic User Interface

To model and monitor your Cisco Meeting Server devices, you must run a discovery session to discover the Cisco Meeting Server component devices that SL1 will use as the root devices for monitoring the applications.

In in an environment where you access the Cisco Meeting Server MMP and the Cisco Meeting Server API through multiple IP addresses, after the discovery session completes, you must manually align the Dynamic Applications associated with each Basic/Snippet credential you created.

To discover the devices that you want to monitor:

1. Go to the Discovery Control Panel page (System > Manage > Classic Discovery).

2. On the Discovery Control Panel, click the Create button.

3. The Discovery Session Editor page appears. On the Discovery Session Editor page, define values in the following fields:

• IP Address/Hostname Discovery List. Type the IP address or hostname for the set of Cisco Meeting Server devices that you want to monitor.
• SNMP Credentials. Select the SNMP credential you created.

• Other Credentials. Select the Basic/Snippet credential you created.
• Discover Non-SNMP. Select this checkbox.
• Model Devices. Select this checkbox.

4. Optionally, you can enter values in the other fields on this page. For more information about the other fields on this page, see the Discovery & Credentials section.
5. Click the Save button, and then close the Discovery Session Editor window.
6. The discovery session you created appears at the top of the Discovery Control Panel page. Click its lightning-bolt icon () to run the discovery session.
7. After the Cisco Meeting Server devices are discovered, click the device icon () to view the Device Properties page for each device.

8. In the Device Properties page, click the Collections tab. The Dynamic Application Collections page appears.

9. Click Action and then select Add Dynamic Application from the menu. The Dynamic Application Alignment page appears.

10. In the Dynamic Applications field, select the following Dynamic Applications:

• Cisco: Meeting Server Network Interface Cache
• Cisco: Meeting Server NTP Cache
• Cisco: Meeting Server System ID Cache

11. In the Credentials field, select the Basic/Snippet credential you configured for the MMP/SSH.
12. Click Save.
13. Click Action and then select Add Dynamic Application from the menu. The Dynamic Application Alignment page appears.
14. In the Dynamic Applications field, select the following Dynamic Applications:

• Cisco: Meeting Server Alarms Configuration
• Cisco: Meeting Server CoSpaces Cache
• Cisco: Meeting Server System Status Cache
• Cisco: Meeting Server Tenants Cache

15. In the Credentials field, select the Basic/Snippet credential you configured for the API interface.
16. Click Save.
17. Click Action and then select Add Dynamic Application from the menu. The Dynamic Application Alignment page appears.
18. In the Dynamic Applications field, select the following Dynamic Applications:

• Cisco: Meeting Server System Configuration
• Cisco: Meeting Server System Performance

19. These applications do not require an associated credential.
20. Click Save. A few minutes after aligning the Dynamic Applications, SL1 will discover and model your Cisco Meeting Server and automatically align other Dynamic Applications to the devices in the system.

Verifying Discovery and Dynamic Application Alignment

To verify that SL1 has automatically aligned the correct Dynamic Applications during discovery using a single IP address:

1. After discovery has completed, from the Device Investigator page for the Cisco Meeting Server, click the Collections tab. The Dynamic Application Collections page appears.
   

2. All applicable Dynamic Applications for the switch are automatically aligned during discovery.

It can take several minutes after the discovery session has completed for Dynamic Applications to appear in the Dynamic Application Collections page.

You should see the following Dynamic Applications aligned to the Cisco Meeting Server:

• Cisco: Meeting Server Network Interface Cache
• Cisco: Meeting Server NTP Cache
• Cisco: Meeting Server System ID Cache
• Cisco: Meeting Server Alarms Configuration
• Cisco: Meeting Server CoSpaces Cache
• Cisco: Meeting Server System Status Cache
• Cisco: Meeting Server Tenants Cache
• Cisco: Meeting Server System Configuration
• Cisco: Meeting Server System Performance

If the listed Dynamic Applications have not been automatically aligned during discovery, you can align them manually.

To manually align Dynamic Applications:

• Go to the classic Device Manager page (Devices > Device Manager), locate the Cisco Meeting Server device and select its wrench icon ().
• Click the Collections tab.
• Click the Action button and then select Add Dynamic Application. The Dynamic Application Alignment page appears.
• In the Dynamic Applications field, select the Dynamic Application you want to align.
• In the Credentials field, select the appropriate credential.
• Click the Save button.
• Repeat steps 1-4 for the other unaligned Dynamic Applications.

Verifying Discovery and Dynamic Application Alignment in the SL1 Classic User Interface

To verify that SL1 has automatically aligned the correct Dynamic Applications during discovery using a single IP address:

• After discovery has completed, click the device icon for the Cisco Meeting Server (). From the Device Properties page for the Cisco Meeting Server, click the Collections tab. The Dynamic Application Collections page appears.
• All applicable Dynamic Applications for the switch are automatically aligned during discovery.

It can take several minutes after the discovery session has completed for Dynamic Applications to appear in the Dynamic Application Collections page.

You should see the following Dynamic Applications aligned to the Cisco Meeting Server:

• Cisco: Meeting Server Network Interface Cache
• Cisco: Meeting Server NTP Cache
• Cisco: Meeting Server System ID Cache
• Cisco: Meeting Server Alarms Configuration
• Cisco: Meeting Server CoSpaces Cache
• Cisco: Meeting Server System Status Cache
• Cisco: Meeting Server Tenants Cache
• Cisco: Meeting Server System Configuration
• Cisco: Meeting Server System Performance

If the listed Dynamic Applications have not been automatically aligned during discovery, you can align them manually.

To manually align Dynamic Applications:

• Click the Action button and then select Add Dynamic Application. The Dynamic Application Alignment page appears.
• In the Dynamic Applications field, select the Dynamic Application you want to align.
• In the Credentials field, select the appropriate credential.
• Click the Save button.
• Repeat steps 1-4 for the other unaligned Dynamic Applications.