Hi Al,

Thanks for the guidance. I was already familiar with the entire process. The 
problem with this device (I don't know about the entire AT family) is that the 
response to SSH/Telnet request is not the standard one. I managed to get it 
working by using the Cisco NX OS scripts and a modified Net::SSH::Expect perl 
module to address the non-standard response from the device.

It is indeed a trial/error based process of testing every possible situation 
and response/request.

Tomorrow I'll have it finished.

Thanks again!
Catalin

Sent from my mobile

> On 20 Mar 2014, at 15:01, "Sorrell, Al" <[email protected]> wrote:
> 
> While I don't have that device, I can offer some general guidance.
> 
> NCM will allow you to setup new device families just like any collection.
> 
> Getting configs is generally done by running a Perl script which basically 
> does a 'show running config' or something of that sort. It then sucks up the 
> returned lines. Testing the script within NCM is a pain, so the easiest way 
> is to export the script from, say the Cisco NX OS or some other family. Copy 
> that to your Spectrum server and run it with the appropriate parameters - add 
> debug as needed and use that to customize your script. If you - or someone 
> else in your organization is familiar with Perl - this should not be too 
> hard. I've created several variants of the script for various Cisco 
> environments.
> 
> Hope this helps,
> Al
> 
>> -----Original Message-----
>> From: Catalin Farcasanu [mailto:[email protected]]
>> Sent: Thursday, March 20, 2014 7:32 AM
>> To: spectrum
>> Subject: [spectrum] AT8000GS NCM script
>> 
>> Hi,
>> 
>> Anyone has tried configuring NCM for Allied Telesis 8400 series and would 
>> like to share
>> some insights?
>> 
>> Regards,
>> 
>> Catalin Farcasanu
>> Mobile: +40730123014
>> 
>> 
>> 
>> ---
>> To unsubscribe from spectrum, send email to [email protected] with the body: 
>> unsubscribe
>> spectrum [email protected]
> 
> T. Rowe Price (including T. Rowe Price Group, Inc. and its affiliates) and 
> its associates do not provide legal or tax advice.  Any tax-related 
> discussion contained in this e-mail, including any attachments, is not 
> intended or written to be used, and cannot be used, for the purpose of (i) 
> avoiding any tax penalties or (ii) promoting, marketing, or recommending to 
> any other party any transaction or matter addressed herein.  Please consult 
> your independent legal counsel and/or professional tax advisor regarding any 
> legal or tax issues raised in this e-mail.
> 
> The contents of this e-mail and any attachments are intended solely for the 
> use of the named addressee(s) and may contain confidential and/or privileged 
> information. Any unauthorized use, copying, disclosure, or distribution of 
> the contents of this e-mail is strictly prohibited by the sender and may be 
> unlawful. If you are not the intended recipient, please notify the sender 
> immediately and delete this e-mail.
> 
> ---
> To unsubscribe from spectrum, send email to [email protected] with the body: 
> unsubscribe spectrum [email protected]

---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

Reply via email to