Cisco CallManager Discovery fails due to missing host dependency
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
49m ago
Hi Community,
I am working on discovering Cisco CallManager virtual appliances hosted on VMware.
The out-of-box Cisco CallManager pattern connects successfully through SSH and retrieves the hostname, version, node role, and cluster information. However, final CI creation fails because the Cisco CallManager application CI does not have the required relationship to an underlying host CI.
Standard UNIX Discovery is not working for the appliance because the account opens a restricted Cisco administrative CLI rather than a normal Linux shell.
Has anyone handled a similar setup successfully? I would appreciate guidance on:
- The recommended CMDB class for the underlying CallManager virtual appliance
- The identification attributes used for that CI
- The appropriate relationship between the host CI and the Cisco CallManager application CI
- Whether a separate horizontal pattern is required before the out-of-box application pattern runs
A high-level explanation of the working design would be very helpful.
Thank you.
