Haley

For VoIP Monitor v2, you have two options for working with multiple pollers. Option 1: Poll all VoIP Sites from one Orion server and monitor VoIP sites from the main Orion poller and additional pollers. Option 2: Deploy VoIP Monitor on the primary Orion server and VoIP Monitor pollers on each Orion poller where you have…

Thanks for posting your input and adjustments to the View Cirrus Configs and View Cirrus Reports resources that are available in Additional Components. We plan to evaluate and update the ability to view Cirrus Reports and Configs from the Orion website in the next major Cirrus release.

We appreciate your comments and feedback regarding the Cirrus Configuration Manager. We are currently evaluating the Find MAC/Find IP functionality. I do not have a specific date for improving the mapping capability; however, this is a top priority and is slated for an upcoming release.

I recommend contacting SolarWinds support for assistance on troubleshooting the issue. Support will need the following information to help determine how Cirrus is trying to communicate with the device and how the device is responding. * A session trace. The session tracing settings are available under…

 FYI, the default NetFlow Traffic Analyzer (NTA) summary view timeframe will be Last 2 Hours for the next release. 

The Network Traffic Analyzer (NTA) Node Details and Interface Details views include the ability to easily adjust the time frame you are viewing by clicking the drop-down in the upper left-hand corner of the view. You have several options including Last X Time and Absolute time frames.

We are about to start round 2 of the VoIP beta program and are accepting additional participants Let me know if you are interested in joining the beta program.

The security error appears to be related to the account you are using to launch the jobs within Cirrus not having sufficient rights. The user needs to have local launch and activation rights. The following steps should help resolve the issue. Open Component Services from Administrative Components, drill down to My…

VoIP Monitor version 1 will monitor voice quality using Cisco's IP SLA technology. The requirement is to have a Cisco device at each of your locations. VoIP Monitor will auto-configure IP SLA on the Cisco router/switches and monitor the voice quality between each of the sites. You can gather SNMP data from the Avaya…

Can you please elaborate on the type of information you would like to view from Unity and IPCC?

VoIP Monitor is not VoIP infrastructure specific. The Orion module meausures call quality between WAN links or geographic locations using Cisco IP SLA. So, you simply need a Cisco IP SLA capable router at each location. 

VoIP Monitor version 1 leverages Cisco IP SLA to gather QoS metrics and gathers SNMP data that is specific to CallManager. Do the Avaya call managers store active VoIP call data within SNMP MIBs? If the call data is stored within MIBs, then we should be able to add this support either in the next minor revision or next…

VoIP Monitor will work with Orion 8.5, which will release at the same time as VoIP Monitor.

VoIP Monitor will enable you to monitor voice performance over your WAN. You can simply need to ensure the Cisco Cat 6500 and Cisco Cat3750 have IOS versions that support IP SLA UDP Jitter operations. You will be able to monitor MOS, Packet Loss, Latency, and Jitter for the WAN links. I recommend downloading the evaluation…

The download issue should be resolved with Cirrus v3.5.1 which is available in the Downloads section within your Customer Portal.

Thank you very much for the feedback!! What specific DN information would you like to see reported for the call routes and how would you like to see it reported within VoIP Monitor? We plan to implement the ability to specify IP SLA settings, such as codec, port, etc. at the node level later this year. Would you prefer to…

Thank you for taking the time to provide great feature requests!!! These requests have been documented and will be evaluated for future releases. We love to hear what our customers would like to see in future releases so keep them coming.

The error message you are seeing was created in Cirrus 3.5. Cirrus products this error message when it has issues communicating with a device via ssh. To help us better understand your setup, can you please provide answers to the following questions: 1. Are you managing all devices within the job via ssh? Or are some…

The issue mentioned above has been resolved with Cirrus 3.5.

Just an FYI, you can use the Policy Reporter to search for missing commands within configurations.

Hi Haley - since no-one else has jumped in, I will. I'm sure that the call data has some very useful information (including MOS scores for each call). I really haven't looked closely at this data however, as I'm flat out just trying to sort out a management strategy for the VoIP network layer. Rather than introducing Call…

Your feedback from the PCI Compliance review is very helpful. I wanted to address a couple of the concerns posed by the PCI Compliance review. 1. If you have aaa enabled and syslog logging enabled, then you should be able to track which users made configuration changes and when. Within Cirrus, we plan to add permissions…

An Alteon device template was created and placed in the Content Sharing Zone within Thwack. If you need to backup Alteon devices, you can simply download the template and save it to your ..\Program Files\SolarWinds\Configuration Management\DeviceTypes folder. 

You should now be able to access the RC from your Customer Portal!!

I have notified the team that handles the downloads and they should have the files updated soon. I will post an update here once I hear the update is complete. Thanks for posting the issue.

Cirrus v4 provides the ability to leverage AD to automatically login to Cirrus. For accessing devices, Cirrus v4.0 provides two options: * Option 1: Use one set of device login credentials - same as Cirrus v3.5.1 * Option 2: For devices connected to an authentication server, you can use device login credentials assigned to…

I recommend opening a support case at www.solarwinds.com/support and ensure to include the Orion diagnostics. 

The inability to include or filter by Orion's custom properties in the NetFlow reports has been documented as an issue and will be updated in the next Orion release. 

The ${SysName} variable reports the value stored in the RFC1213-MIB:sysName MIB (OID: 1.3.6.1.2.1.1.5). This MIB is an administratively asisgned name for the managed node. By convention, this is the node's fully-qualified domain name. This value can be modified by updating the value via SNMP or for most devices, by…

Thanks for starting the beta thread :) The next version of Cirrus is not currently in beta. However, we are planning to start up the beta program within next month or so. Please post to this thread if you are interesting in particpating in the next Cirrus beta. We will send out a notification to interested parties once the…