As i had to realize that on ~500 network devices, the most efficient way to do that is first setting the interface description right. That will allow you to use the option for setting description as alias, and use that in dashboards notifications etc. As long as you don't have to deal w/ shared workspaces and / or don't plan to use that in an fully automated way (in dynamic client environment), this should be all you have to do. Changes on switches would afford just a re-scan of the services.
when you plan do do something bigger, like integrating nedi (like me) , shared workspaces in 802.1x deployments w/ client monitoring, or other strange environment deployments w/ hosts/ports changing frequently. This would afford modarate python and bash skills for changing aliases in scan module or re-importing hosts form csv and rescanning hosts. W/ regards Fate Am 14.11.2014 20:51 schrieb "Stan Brown" <[email protected]>: > We have a number of network switches we are monitoring using OMD, > check_mk, and Wato. I need to be able to rename the automatically > generated service names for each physical port, so that the correspond to > the name of the physical device, such as a computer, that is attached to > that port. > > How can I do this? > > > _______________________________________________ > omd-users mailing list > [email protected] > http://lists.mathias-kettner.de/mailman/listinfo/omd-users > >
_______________________________________________ omd-users mailing list [email protected] http://lists.mathias-kettner.de/mailman/listinfo/omd-users
