In the process of converting our configs to be correctly interpreted
when they are uploaded via TFTP we have noticed the following syntax
differences:
 
1. If you boot a blank switch and configure it via a console (or
bootstrap then telnet) the switch detects it's software version and
modules. You can enter your config in no problems. If you try to upload
a config via TFTP you must explicitly specify the version and installed
modules for example:
    version V3.3.0T163
    module 1 ni-mlx-20-port-1g-100fx
 
2. Some commands don't work as specified in the documentation. If using
console/telnet you can enter a motd as follows:
    banner motd $
    message
    $
However if you try and TFTP upload this config it fails. You must do
this:
    banner motd ^C
    message^C
    ^C
 
3. The command "!" is interpreted as "no-operation" on the
console/telnet and as "exit" when TFTP uploaded.
 
Hope that saves someone some time... Or has someone else already come
across this one..?
 
Any more differences that I should be aware of when TFTPing up configs?
 
James Piper 

 


This e-mail and any attachments may contain confidential information that is 
intended solely for the use of the intended recipient and may be subject to 
copyright. If you receive this e-mail in error, please notify the sender 
immediately and delete the e-mail and its attachments from your system. You 
must not disclose, copy or use any part of this e-mail if you are not the 
intended recipient. Any opinion expressed in this e-mail and any attachments is 
not an opinion of RailCorp unless stated or apparent from its content. RailCorp 
is not responsible for any unauthorised alterations to this e-mail or any 
attachments. RailCorp will not incur any liability resulting directly or 
indirectly as a result of the recipient accessing any of the attached files 
that may contain a virus.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
https://puck.nether.net/pipermail/foundry-nsp/attachments/20070612/54b8e36f/attachment.html
 

Reply via email to