mpayne1

Just upgraded to SP3; SSID's work for me now as well

After testing and confirmation from the developers, you can only have one type of service per site being monitored. (Example: Site A SLA test for TOS 5 or TOS 0 to site B, not both) This would be a nice feature request, as well as making the SLA configuration numbers in the router persistent.

Forgot to mention that I have applied SP2 to Orion; now I am running NPM 9.5 SP2 This was in the hopes to resolve "unintended" wireless features. Unfortunately, this did not resolve the issue.

The access points are thick client (IOS based), no controller is used. From the development team, I learned they are polling the following OIDs: OID 1.3.6.1.4.1.11.2.14.11.6.4.1.1.9.2.1.2 OID 1.3.6.1.4.1.9.9.272.1.1.1.6.1.2 The second one is valid for my access points. Both a MIB walk and a packet capture (access point to…

Can I have multiple manual SLA tests created on the router and will they be monitored by VoIP Monitor? (example: Site A: SLA test for TOS 5 and TOS 0 to site B ; Site B: SLA test for TOS 5 and TOS 0 to site A)

You need to specify an entry number for a SLA test. Then the sub cmds will become available: router(config)#ip sla 10 router(config-ip-sla)#? IP SLAs entry configuration commands: dhcp DHCP Operation dns DNS Query Operation exit Exit Operation Configuration frame-relay Frame-relay Operation ftp FTP Operation http HTTP…

Had the same problem with VoipMonitor SP3 when I upgraded to Orion9.1 to SP1. Fix was to upgrade Orion9.1 to SP2.

I had the same experience. Don't stop the services manually or kill NPM from task manager. Rerunning SP3 and letting it shutdown the processes caused no issue

1. Generate and monitor more than 1 type of service. It would be nice to see and compare Default class with Protected Class (voice). This way you can keep your WAN provider honest. 2. Persistent SLA configuration numbers in the router. Auto configurations increment the SLA configuration numbers if the router is reloaded.

I have a packet capture from the access point to the server, and would like to make sure that the correct SNMP information is sent to the server. I am looking for the correct MIB value that ORION uses to search for the SSID and associate it with a client MAC or IP address.

It would also be nice if you could sort by snmp location or contact, without having to create a duplicate custom property

Case opened #101693

If you haven't already done so, make sure the SQL database is not on the same server with Orion. I have seen dramatic improvements having the database separated, and problems with services not starting disappear.