Haley

At this point, I cannot say whether VoIP Monitor will have specific support for Nortel VoIP equipment or Meridian in 2008. We are still finalizing some of the plans for 2008. You should still be able to gather SNMP data from within the Orion Network Performance Monitor Custom Property Editor.

Bryan, Thanks for posting the update.

Are you aware of how long after the sign up for the beta NTA 3.0 (NetFlow v9) that I will be contact for the download / installation? Thank you for your interest in the SolarWinds Orion NetFlow v3 beta program. This beta program is now closed since it the new release is scheduled to release very soon!! We will post an…

Thanks for the update. One of our field engineers should be contacting you soon to work with you more closely on the issue with the Nortel Alteon Application switch.

Cirrus will enter the enable command and enable password (specified for the device) by default when downloading/uploading configurations. We will need more information in order to troubleshoot where the communication is failing. I recommend enabling a session trace under File > Settings > Advanced > Session Tracing and…

I recommend modifying the language region to English to see if this resolves the issues.

Dear, I have tried all the mentioned steps where: * The device is added in the Orion System Manager * Only a select number of interfaces are monitored within Orion * * The device and its monitored interfaces are added as NetFlow sources * NetFlow provides a message indicating that NetFlow traffic is received on an…

Don, Using regular expressions, you can group several lines into 1 rule. Each line does not need to be a new rule. The following example includes 4 lines in 1 rule clock timezone CST -6 \nip subnet-zero\nno ip source-route\nip telnet source-interface Loopback1

SNMP v3 is fully supported by VoIP Monitor.

That feature is not currently available. I will post the ability to specify the returned prompt with a wild card character as a feature request.

I recommend performing all the steps mentioned in the zip file. Possibly, some of the additional files were out of sync. In our test labs, updating the two files resolved the issue; however, the other files included in the zip were the same as those loaded on the Orion server.

I recommend installing v3.5.1. The current Cirrus v4 beta is not recommended for production install.

The countdown begins!!! The Cirrus Beta v4.0 is scheduled to start within the week. Please ensure to add your name to the thread in order to have access to test out the new features of Cirrus Configuration Manager.

I recommend performing a repair on the Cirrus installation. This should set the Cirrus install back to its original state. Please let me know if this resolves the issue for you.

VoIP Monitor leverages the ability to specify a codec within Settings. The selected codec defines the number of packets, size of the packets, the time period between each packet transmission, and the frequency of the IP SLA operations. For your deployment, are you wanting to define these parameters instead of simulating…

If Cirrus still hasn't updated the machine type value. Please open a case at https://forms.netsuite.com/app/site/crm/externalcasepage.nl?compid=638609&formid=12&h=3d0552f20b2e9bd6580b so we can ensure this issue is tracked appropriately. Another workaround option is to close Cirrus, open the database, remove the machine…

David, I just downloaded a demo version of Orion and the netflow module. We are seeing the Stacked Chart Error as well. Orion Version 8.5.1 - October 2007 I recommend contacting your sales representative for assistance with troubleshooting this issue. If you have not yet talked with our sales department, then you can call…

Thanks for the great post. I think many customers will find this useful. Another FYI, you can import text files into Cirrus by highlighting the desired device within Cirrus, selecting the desired text file from Windows Explorer, dragging the text file to the Cirrus Node list, and selecting OK. I will also add the ability…

Exactly. In 2008, our goal is to collect Avaya specific phone/VoIP data that is available via SNMP. All IP SLA data will still be collected by the Cisco routers.

Thank you for sending the Syslog Message. The ability to pass information in addition to the IP address of the device whose configuration was modified to Cirrus is a feature we are planning for a later Cirrus release. Currently, we recommend you pull this information from the Orion Syslog Server.

The ability to view Cirrus Configs and Reports from the Orion website currently works as long as the Orion server has a mapped drive to the Cirrus server and vice versa. The integration pulls the configs that are saved using the Config Archive feature and reports that are exported as html.

I recommend checking out the thread at . This includes steps for verifying that the appropriate interfaces are being managed as NetFlow sources.

Do you happen to have RADIUS enabled for the Nortel 470 device? Additionally, is RW the username or the password value for the device?

The new addition to Cirrus v4.0 is the abiltity to download/upload configs from devices that have a menu-driven interface and transfer the configations as text files via tftp. For these devices, Cirrus would need to be able to transfer the configs via snmp/tftp or telnet/tftp. If the Cisco VPN 3030 meets this criteria,…

VoIP Monitor v2.0 Service Pack 1 is now available. You can find our more details at . 

Currently, the Toolset TFTP Server and Free TFTP Server have been updated to accept hot fixes. The next major release of Cirrus will be updated to accept to accept hot fixes, as well. At this point, I recommend running either the updated Toolset TFTP Server or the Free TFTP Server.

Thanks for the update. You should be able to pull the that MIB with the Physical Entities Report. Cisco pulls card serial numbers from either the ENTITY-MIB, CISCO-STACK-MIB, or OLD-CISCO-CHASSIS-MIB based off of whether the device has Cat OS or IOS and based off the IOS version. Currently, Cirrus has 1 report for each…

Thanks for sending the device information for tfping the device. From the session trace, it does not appear that Cirrus is able to login to the device. If you double-click on the Nortel device, select Actions > Validate Login Information from within the Node Details, is the login successful? We will first need to ensure…

Same here... facing the same problem. any solutions yet? We have identified an issue where the following steps require the user to restart the NetFlow service in order for NetFlow to detect the newly added interface. * The device is added in the Orion System Manager * Only a select number of interfaces are monitored within…

Jay, Thanks for the info. When I look at the tables it says that 52.4GB is used and that NetFlowSummary2 table is using 46.3 GB of it. My TrapVarbinds table is only 142MB. Do yo suggest truncating both tables? The total space used is 120GB, Data Space used is 52.4GB, Index space used is 10.4GB. After the truncation,…