12-20-2018 01:53 PM
I have some SM-X-ES3-16-P modules inside our routers, with SNTC collecting the information about them.
Inside my collector, the SM-X-ES3-16-P modules show up in the "managed devices" showing the hostname configured on the SM-X-ES3-16-P. Then when the data is exported/imported to the SNTC portal, the hostnames of the SM-X-ES3-16-P modules will be the parent router, NOT the configured hostname.
Has anyone else seen this? Bug? or configuration issue?
Thanks
12-20-2018 02:14 PM
01-03-2019 04:03 PM
Greetings Chris,
I'm searching in the portal for the hostname that's configured on the SM-X-ES3-16, and that hostname is found in the collector, but is missing from the portal. Inside the collector, I have separate entries for the SM-X module and the router. In the portal, the SM-X is only seen as a module of the router, not as its own entity.
I want the portal to show the hostname configured in the SM-X module, as it's own "chassis" with the proper hostname.
01-04-2019 07:42 AM
The "managed" version of the SM should show up under "All Hosts" whereas the hardware will show up under "All Equipment".
01-04-2019 08:39 AM
Unfortunately the "All Hosts" view is unacceptable for use as its table only has a sliver of the information available compared to the "custom inventory".
If the SM-X-ES3-16 is indeed a host (as indicated by its inclusion in managed devices within the collector) I would expect to see this managed device, with its proper hostname within the "Custom inventory" view, or any other view besides just the "all hosts" view specifically.
Is there any way to achieve this? This really will make SNTC unusable for our needs.
01-04-2019 08:52 AM
01-04-2019 08:56 AM
01-04-2019 09:01 AM
01-04-2019 09:03 AM
01-04-2019 09:28 AM
01-04-2019 10:19 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide