Haley

Thanks for the update. I provided the error and details to development so they can try to duplicate the issue and provide a more meaningful error message.

Additionally, for one of the devices that already exist, I recommend double-clicking on the device and selecting Actions > Validate Login. This should show you exactly which credentials are being used to connect to the device and where the login is failing. 

Currently, Cirrus does not allow a ">" character to exist before the login prompt. Cirrus currently reserves this character as the character that will be used in the enable level prompt. MIBs can be edited by entering the read/write community string within Cirrus, browsing to the desired MIB, and updating the appropriate…

It would be very helpful to find out more information about your network setup in order to help us determine why you are not seeing the information you are expecting using the Find IP/MAC tool. Can you please provide a diagram of your network which includes the firewall and switch connectivity? It will also be helpful to…

Currently, this setting will automatically remove desired configs based off the configured setting either in real-time or for a scheduled later date. At this time, this is a run once setting. We plan to add auto-purge in a future release.

The development team is currently looking into this issue. I also recommend creating a support ticket at https://forms.netsuite.com/app/site/crm/externalcasepage.nl?compid=638609&formid=12&h=3d0552f20b2e9bd6580b and reference that you spoke with Haley within Thwack.

The description is misleading. A more appropriate description would be "The period between collections of test traffic.". I have noted this issue and it will be updated in a later release.

For most baystack Nortel devices, the method to enable the command line interface is as follows: * Login to the device * choose command line from the menu system * type cmd-interface cli * logout * log back in Please let me know if this changes the way the screen after login appears.

If you have Cirrus Configuration Manager, you can run the Switch Ports report to get a listing of vlan #s and port status. The port status field is not included in the report by default, but you can easily modify, and select port status as a new field to include in the report.

I'm agreeing on that part. It would be nice to be able to monitor inbound/ outbound calls on FXO's and PRI's. to also chart out the possible channels including peaks to assist in capacity upgrades. It would also be nice to be able to show Top Calls, on-net calls, off-net calls, etc. Some sort of drilldown would be nice.…

The Cirrus installation includes a TFTP Server. You can always start it up by going to Start > Programs > SolarWinds Configuration Management > TFTP Server. When Cirrus needs to perform a config transfer, the TFTP Server in the Cirrus directory should automatically start up. If another application is currently running on…

If you are experiencing issues with Cirrus supporting specific HP Procurve devices, then I recommend opening a case with support at https://forms.netsuite.com/app/site/crm/externalcasepage.nl?compid=638609&formid=12&h=3d0552f20b2e9bd6580b. They should be able to help you customize a device template for those devices.

I see that a recommendation for installing the hotfix was provided by support. Please let us know if this does not resolve the issue.

The Session Trace is showing that Cirrus is expecting a response back from the device but no response is being returned by the device. Therefore, the device is waiting the entire time before sending the next command. You can modify this time setting under File > Settings > Network > Telnet Settings > Telnet Prompt Timeout.

The Cirrus Beta program is now in progress!! This beta round is only available to licensed customers. 

Cisco stores Card details within three different MIBs (New IOS MIBs, OLD IOS MIBs, and CatOS MIBs). Within Cirrus 3.5, you can pull card information from the Physical Entities, Cisco Cards, and Cisco Catalsyt Cards Reports. If the Cisco Catalyst Cards report does not include the serial numbers for the switches mentioned…

The eval should now be available

For Netflow we use Netflow Analyzer. This is because the Solarwinds product is not robust enough to do what we need. We need to be able to make reports about specific interfaces and to be able to name the interface whatever we want. The reports need to be in PDF, and be able to show nice pretty pie charts. We also use it…

Due to web architecture changes within the Orion, the resources that show Cirrus configs were modified. To resolve the issue, please peform the steps below: * Download the latest Config List files from ftp://ftp.solarwinds.net/cmb03/cirrus/ConfigListing.zip. * Extract ConfigListing.asp to…

We are aware of this issue and are currently working on a service pack. I recommend creating a ticket at www.solarwinds.net/support so we can track your issue and provide you the latest available update. 

FYI, providing the ability to track command output other than running and startup configs is a feature we are considering for a future release.

If you have Cirrus v3.5 and are upgrading to Cirrus v3.5.1, then it has been determined that there will be a couple of additional steps compared to upgrading from v3.0 to v3.5.1. From v3.5 to v3.5.1 Step 1: Uninstall Cirrus v3.5 Step 2: Install Cirrus v3.5.1 Step 3: Register the ..\Program…

Bryan, you are correct. At this point, I recommend uninstalling Cirrus v3.5 before installing Cirrus v3.5.1. Your data should remain intact after the uninstall. Only executables, ocx files, dll files, should be removed on the uninstall.

Since the versions are not changing when you select Modify, I recommend that you uninstall Cirrus v3.5 and install Cirrus v3.5.1. Your database, device templates, and reports should not be impacted by the uninstall. We are currently investigating the potential installation issue.

For the "Connectivity issues discarding config file" issue on the NetScaler Load Balancers, I recommend creating a ticket with support at https://forms.netsuite.com/app/site/crm/externalcasepage.nl?compid=638609&formid=12&h=3d0552f20b2e9bd6580b and include session traces from the NetScaler devices. 

I understand that support just resolved the issue with you. Please let us know if you are still experiencing issues.

Cirrus v3.5.1 includes a Fortigate device template!!

We have not had any reported issues or tickets created around the default Physical Entities report available in Cirrus v4.0. I recommend running a repair on the Cirrus v4.0. If after the repair, you still still experience an issue with the Physical Entities report, I recommend creating a support case at…

You should be able to manage the Nortel 5510 with the banner enabled using Cirrus, as long as cli mode is enabled. I recommend opening a case with support at forms.netsuite.com/.../externalcasepage.nl. You will want to also include a session trace (enabling this feature is available under File->Settings->Advanced->Session…

I was unable to locate your open ticket. Can you please provide your open ticket number related to telnet issues? This will help us to identify the issue you are seeing.