Karlo.Zatylny

There does not appear to be scrolling ability built in to this application. Is the web interface lacking some feature that you are using this tool for? Thanks

Hi, Sorry that you are seeing this issue. We are looking at similar issues at the development team level. Would you please open a support ticket and reference this thwack thread so that we can get diagnostics from you and continue to investigate your problem. Thanks

Hi John, This sounds like you need to call support. Perhaps a repair would fix your issue. Thanks

I am not sure I completely understand your issue. Your first statement claims that you are seeing no information shown in Orion, so is the screenshot from somewhere else? Make sure that the VMware MIBs are enabled on the servers you want to see data on, and that your ESX servers are version 3.5. Which database do you want…

Hi, To clarify a little more. This does not "re-discover" your device or network for new interfaces, nodes, volumes, etc. -- However, that is a feature we are developing. See here. Thanks

Hi, The rediscovery interval has a few roles: 1. Remap interfaces. Some devices will change the interface index and in order to properly track this change we check to see if the interface we have mapped to a specific index is the one we expect it to be, if not update it. This doesn't occur that often, so we don't check…

This is a little high for what we would consider to be within the range of acceptable values. Sometimes, depending on the device, we see spikes over 100% but this is usually limited to a few percentages. Things to check: 1. Make sure the interface speed for these interfaces is correct. 2. Check if this is a known issue…

Wouldn't the correct formula be: (total - failed)/total * 100 Please let me know if you need additional help.

Thanks. We'll look into adding this into the product on installation. This type of index might also benefit customers who gets lots of Syslogs into the Syslog table. Great tip!

Hi, 1. It is configurable according to the Events Retention (in 9.5.1 and previous) setting on the Polling Settings page. Orphan data (something in the AlertLog with no ID in AlertDefinitions) is deleted immediately. Both of these are done during your scheduled DB maintenance. 2. There is no front end on the web for this…

Check out this thread Thanks

Sorry for the delayed response. Does your device support the running of an "debug snmp packet" from the command line? We have some customers who have also reported issues with the Cisco PIX devices and we are trying to determine why the devices are rejecting our snmp requests. Any network traces or debug sessions from the…

Denny in the jury.

This is a great question. In the Universal Device Poller you can click on the Show Advanced Options when you are editing your poller to show some additional options. Once there, select the Format to be "Enumeration" then click Map Values. Then type in your mapped values 0 Off 1 On And then you should see the text instead…

This is a message from your switch indicating that it cannot handle the volume of incoming SNMP messages. If the source of this is the Orion server, then you can do any of the following to help the situation: 1. Change the polling intervals on your interfaces to poll less frequently. 2. Poll less UnDPs if you have any. 3.…

Hi, There are generally two ways how to ensure that polling will continue. 1. First way is to check node property “Dynamic IP Address”. This property should be used if the IP address of the Node is obtained from DHCP or BOOTP. You can check this property on Web Node Management Page-> Edit Properties -> Check “Dynamic IP…

Hi, We place -2 in values in the database that we are unable to populate from the device. So if a device does not respond to any of the OIDs for any of the values we poll, we place a -2 in that column for that piece of data, indicating that we were unable to get a value. Please let me know if you have any additional…

I believe that a solid work around is to use the web interface to make this change. We had our QA test this scenario and it worked in our environment. Please let me know if you have troubles with this work around. Thanks

Hi, We have the 3.5.0 in our lab and everything is visible. Perhaps a MIB walk would help me debug your issues. Are you seeing the ESX Details page for the 3.5.0 server and the data isn't being populated properly, or are you just seeing the regular Node Details page? If this is the case, then you need to set your settings…

Hi, We found this bug as well and we already have it in our bug tracking system. However, as you suggested since 0 and 7 are equivalent in the CRON strings (both Sunday) then simply reformatting the string to use 0 instead of 7 will work every time. Our NCM product always uses 0 for Sunday. Thanks

Hi, Last boot is populated by the SysUpTime OID and a calculation. http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=sysUpTime The value in that field changes when we calculate that a reboot has happened. This OID is polled every cycle as reboots are important pieces of…

Hi, Here is a quick description of the AlertStatus States 1 = Trigger Pending 2 = Triggered 3 = Reset Pending 4 = Reset Please let me know if I can clarify any of these. Thanks

Hi, We have noted this bug in the Events, Traps, and Syslog pages and have an item in our bug tracking system to fix this issue. The dropdown list is causing a lot of the slowness and size. We will be addressing that part first. Thanks

test back

Hi, I was able to create an alert where I logged the telnet://${DNS}/ to the NPM Event log and it worked just fine. Perhaps you can give more detail as to what is not working about this syntax. Note that NPM will not have a DNS entry for all your nodes. Perhaps try using ${IP_Address} instead to see if that gets you closer…

Hi, The Validate button breaks your list into chunks of 5 at a time and validates if each item in your list is a valid IP address or resolvable DNS name. When this process is complete, it will show a message by the button like "Unable to resolve: my-bad-server-name". When all is well with the IP list, it shows nothing. We…

This is a known issue that we will be fixing in an upcoming service pack. Thanks

This should be working. We sum up all the CPU utilizations across all of the VMs and divide that by the number of CPUs. Can you verify that your utilization is the average across all your CPUs? Thanks

Hi, The overall status is simply reflecting the Operational Status since the Administrative Status is Up. The device is most likely telling NPM that the interface is Down in the IF-MIB. However, this status does not prevent NPM from gathering other statistics. So if the device is mistakenly reporting the interface as down…

There are a few reasons why this might be happening. Check out this thread, to see if it has any pointers to help you out. If you do a MIB walk of your ESX server, you should see details of each VM on your server. We have a known issue where the vmConfigFile value is too long for our database. Increasing the length of your…