Cirrus v3.5 support of the MDS iNET 900

Hello,

I'd like to use the Cirrus policy reporting tool to audit out iNET radios. I've been unsuccessful in getting Cirrus to log into the radio and pull the config file. I created a iNET device template and can add the radio to Cirrus, but when get a Login failed: bad password. I have run a trace of the login attemp and Cirrus does get to the main menu, but it seems as if it is waiting for character that the radio is never going to send. The device is very simple. You telnet into it; supply a password and then a text menu is displayed. You can use a single character to navigate through the menus (no CR required). Has anyone had luck with a similar style device?

I'd like point out that I do not really need to automate the download of the configs (yet). If I can add the radios into Cirrus and then maunally copy the file to the \Config-Archive folder so that Cirrus can view them, then I can run the Policy Reporting tool against those configs. Thanks for the help,

Esteban

Find more posts tagged with

template

device_configuration

import_configs

inet

Accepted answers

All comments

Haley

Esteban,

Welcome to Thwack!! You can drag a text config into Cirrus. It is a feature that we probably should make more apparent. In order to import a config, you will need to perform the steps below:

Highlight the desired device in Cirrus.
Open Windows Explorer and navigate to the text file.
Select the text file and drag it into the Node List portion of Cirrus.
Click OK

In regards to adding the ability for Cirrus to download configs from the iNET radio, I recommend contacting support at https://forms.netsuite.com/app/site/crm/externalcasepage.nl?compid=638609&formid=12&h=3d0552f20b2e9bd6580b for assistance with determing if customizing a template will provide the desired support.

ETirado

Hi Haley,

Thank you very much for the information. I actually opened a ticket at about the same time as I posted, and was very surprised when I saw your response. Support actually wrote back telling me there was no way to manually import the configs (Case# 20404)!

They also mentioned there was no way to support the iNet due to the text menus it uses. Honestly, I don't feel enough research went into that answer. Is there anything I could post here that could help determine whether the device is supportable or not?

Thanks,
Esteban

Haley

Esteban,

Thanks for the update. The ability to import configs is sort of a hidden feature we plan to document in the next major release. Being that the feature is not yet documented, I bet the support rep did not see our internal notes on the feature.

Most menu-driven devices are not supported by Cirrus. The exceptions are the devices that do not require you to navigate through the menu system. For example, the Nortel Alteon Application switch is menu-driven; however, from the menu, you can type the entire command to download the config via telnet/tftp. We were able to customize a template to work with this device.

I see the screenshots that were provided to support for the iNet device, and it does not apear that Cirrus will be able to automatically download configs from this device at this time. It looks as though you enter the login information and then there is a statement requiring that the letter "g" be pressed and the sentence is not included within a standard prompt. Cirrus expects the device to return a standard prompt. However, you can import the device config into the nodes list.

ringram

Did you ever get a device template created?