quote:Originally posted by snowjaySo far I love this tool, so much easier than the clunky old CW2k. I do however have one recommendation/request/feature enhancement that I think would really be beneficial to some of us.How about autodiscovery based on CDP? Sometimes switches will be put into service with out our (HQ) knowledge so it slips through the cracks and configs aren't backed up etc... During an inventory Cirrus is already capturing CDP details from each switch, but it would be nice to have anything new showing up on those CDP list be automatically added. Or maybe at the very least an Inventory Change report that can show if CDP info has changed.Just an idea.
quote:Originally posted by Don YonceBryan,The device inventory can be extended easily. Cirrus is using the Sonar Inventory Engine that previously was only available to OEM partners. It can be extended to included other device details and other Vendor specific information.I'll build you an example inventory add-on to collect the Route TableWhich one do you want ? IP-FORWARD-MIB:ipCidrRouteTable IP-FORWARD-MIB:ipForwardTable RFC1158-MIB:ipRoutingTableYou probably want IP-FORWARD-MIB:ipCidrRouteTable
quote:Originally posted by trm33When will the Windows Inventory package be available?
quote:Originally posted by RyanJettJon,After installing the Windows Server Inventory Add-on, you should see three new .ConfigMgmtInventory files in the \SolarWinds\Configuration Management\Inventory folder:50-Windows-Services.ConfigMgmtInventory51-Windows-Software.ConfigMgmtInventory52-Windows-Accounts.ConfigMgmtInventoryIf you do not see these files, reinstall the add-on package.If these files do exist, restart Cirrus and then select Inventory Settings from the Inventory menu. You should see a list of Inventory options including the default groups "Standard" and "Cisco". In addition to those groups, there should be a new group called "Windows" with three Inventory options to choose from.If you still do not see these Inventory options, did you install Cirrus in the default location? And if not, did you install the add-on to the same \SolarWinds folder that Cirrus was installed to? The fastest way to check would be to do a search for folders named "SolarWinds". If you see more than one instance, this is likely the cause of the problem.If none of this resolves your issue, feel free to email me at ryan.jett@solarwinds.netRyan JettSolarWinds.Net918-307-8100