This is what I guessed, backup of Cisco IOS and/or Cisco config files. That is precisely where my expertise in TFTP originates
To backup the IOS, you will have to touch a file (and give open permissions) to the same name of the file you are saving. When you do a 'write net' on the Cisco boxes, it will ask for the name/ip of the TFTP server AND the name of the file (the Cisco IOS gives a default). That file MUST exist in the TFTP directory of the server.
So before you do a 'write net' you much touch a file with the same name as the file you are writing. For example, on the server:
On the router you would then 'write net' file name, cisco-ios-dec-05-v11.03a. (use your own file names). The confusion most people have is that the file must exist in the TFTP directory in order to write it from a device, like the Cisco IOS. To read the file (get), you must know the exact name of the file you are 'getting'. Same is true for Cisco configurations:
I forget the exact Cisco syntax, so if you need help in that area, please login to the router from an X or other GUI telnet session and use the mouse to capture the screen (Cisco console) and upload to this thread. I can help you through the 'write net' and other commands between the Cisco IOS and your UNIX TFTP platform.
Hi,
Setting up print queue, using SMIT on AIX
And I have an option saying do I wish to make this a BOOTP/TFTP server. What exactly does this do?
Thanks (3 Replies)
I have been hearing that this protocol offers faster throughput rate than FTP, is it true? If so, are there any compromise in reliability on data being sent? How do I set up a TFTP transfer instead of a FTP to download?
Thanks (3 Replies)
Hi everyone,
I am currently receiving an error on my console that reads something like:
<host> tftpd: socket (delay): Protocol not supported
I have done so much research into tftpd, i've looked everywhere to find out what this might be caused by...unfortunately i have Solaris 8, so there... (5 Replies)
RH 7.2
I am attempting to get tftp working but I'm having a problem. On the server, xinetd has libwrap options compiled in. I have a deny all policy in my hosts.deny file and the following entries in my hosts.allow file:
in.tftpd:.10.151.2.6
But...when I attempt to tftp from... (1 Reply)
ive been trying to enable a tftp service on a unix box
using the command atftpd --daemon
but when i scan the open ports using nmap it doesnt show that port 21 as up
does anyone know the reason...
ive tried /etc/init.d/atftpd start , it didnt work
if i type atftpd by it self it gives me a set... (2 Replies)
Hi
I am trying to do a network install of Solaris 10 08_07 onto a Sunfire T2000. I have configured all my network-boot-arguments on the client server (named sundb1). I have installed my image of Solaris on my install server (sun1).
But when I try to install using
# boot net -s
I get the... (0 Replies)
Hi,
I'm trying to run the tftp client on tsch shell and I get command not found, but on bash tftp ran fine, can anyone help me on how to run it on tsch?
Thanks (1 Reply)
I know that IBM's official stance is that NIM does not work on etherchannel environment, but has anyone able to get around it?
I'm working on a p5-590 LPAR system, and the NIM master and clients are all on the same frame.
Any help is appreciated. (1 Reply)
I have setup nimol on a Fedora 9 machine. Nimol is installed and correctly configured and I have a client rs6000 (43p) declared in the dhcpd.conf file. all is running correctly and tftp is installed. I am monitoring /var/log/messages when I start the 43p and see the dhcp request come in and a reply... (0 Replies)
Discussion started by: johnf
0 Replies
LEARN ABOUT DEBIAN
net::cli::interact::manual::phrasebook
Net::CLI::Interact::Manual::Phrasebook(3pm) User Contributed Perl Documentation Net::CLI::Interact::Manual::Phrasebook(3pm)NAME
Net::CLI::Interact::Manual::Phrasebook - List of Supported CLIs
INTRODUCTION
The bundled phrasebook includes support for a variety of network device CLIs. Many were contributed by users of the module. If you set up
a new CLI dictionary, please consider contributing it back! The phrasebook specification is given in Net::CLI::Interact::Phrasebook.
For each supported CLI, there is a name which must be passed in the "personality" option to Net::CLI::Interact's "new()" method. After
that, you can call the included Macros, and the module will use the included Prompt to match the current state of the CLI. More information
is available in the Tutorial and Cookbook.
Below is a list of all current bundled CLI dictionaries. Each lists its name, the available Prompts, Macros and Continuations, and from
which other CLI dictionaries it inherits.
IOS # Cisco IOS
CatOS # for older, pre-IOS Cisco devices
PIXOS # for PIX OS-based devices
PIXOS7 # Slightly different commands from other PIXOS versions
FWSM # currently the same as 'PIXOS'
FWSM3 # for FWSM Release 3.x devices (slightly different to FWSM 2.x)
JunOS # Juniper JUNOS support
HP # HP support
Nortel # Nortel support
ExtremeOS # Extreme Networks support
Foundry # Foundry/Brocade device support
PERSONALITIES
Cisco
This personality goes by the name of "cisco" and provides a basis for many other CLI dictionaries.
Prompts are "basic", "privileged", "configure", "user", and "pass".
Macros are "begin_privileged", "end_privileged", "begin_configure", "end_configure", and "disconnect".
CatOS
This personality goes by the name of "catos" and inherits from the "cisco" dictionary.
Additionally it provides the "privileged" Prompt.
Additionally it also provides the "paging" Macro to set the terminal page size.
ExtremeOS
This personality goes by the name of "extremeos" and inherits from the "cisco" dictionary.
Additional Prompts are "basic", "privileged", "configure", "user", and "pass".
Additional Macros are "begin_privileged", "end_privileged", and "disconnect".
Foundry / Brocade
This personality goes by the name of "foundry" and inherits from the "cisco" dictionary. Before connecting to the device you probably want
to set the output separator to be:
$nci->transport->ors("
");
For users of Net::Appliance::Session this should be:
$session_obj->nci->transport->ors("
");
IOS
This personality goes by the name of "ios" and inherits from the "cisco" dictionary.
Additionally it provides the "paging" Macro to set the terminal page size.
HP
This personality goes by the name of "hp" and inherits from the "cisco" dictionary.
Additionally it provides the "basic" and "user" Prompts.
JunOS
This personality goes by the name of "junos" and inherits from the "cisco" dictionary.
Additionally it provides the "privileged", "configure", and "user" Prompts.
Additionally it also provides the "begin_configure" and "paging" Macros.
Nortel
This personality goes by the name of "nortel" and inherits from the "cisco" dictionary.
Additionally it provides the "user" Prompt.
PIXOS
This personality goes by the name of "pixos" and inherits from the "cisco" dictionary.
Additionally it provides the "paging" Macro to set the terminal page size.
It can be used in its own right for Cisco PIX firewalls, but is also used as a base for other dictionaries.
PIXOS 7
This personality goes by the name of "pixos7" and inherits from the "pixos" dictionary.
Additionally it provides the "paging" Macro to set the terminal page size.
FWSM
This personality goes by the name of "fwsm" and inherits from the "pixos" dictionary.
It provides no further functionality, as Cisco FWSM software version 1 and 2 was the same as the PIX OS.
FWSM 3
This personality goes by the name of "fwsm3" and inherits from the "pixos" dictionary.
Additionally it provides the "paging" Macro to set the terminal page size.
perl v5.14.2 2012-06-12 Net::CLI::Interact::Manual::Phrasebook(3pm)