Search the Community
Showing results for tags 'TFTP'.
Found 3 results
Dears, I have a problem in GNS3 when copying file from my PC (TFTP server) to disk0: od ASA. I issue the follwoing commands in ASA in GNS3: asa# format disk0: asa# copy tftp://192.168.1.1/asdm-713.bin disk0: The process is started normally but it is too slow and then it is stopped and error message appear that (unspecific error). I turned off the windows firewall of my PC, and the same problem occured. The connection in GNS3: ASA ----- Cloud ------- myPC(tftp server) I used all types of exiting interfaces to connect myPC to cloud (MS loopback, wireless interface and local area network) and also facing the same problem. I make troubleshoot when using MS loopback interface and I found that the loopback interface is 10Mbps half-duplex but unable to make it 100Mbps full-duplex. Please advice how to resolve the problem.
Hey everyone, I have a tricky one for you. I am obviously over looking somthing thats quite simple. I have a Fortigate 60B. I made the mistake of trying to upgrade the firmware with a mis labeled file...I was quite angry. So i formatted the Fortigate to start again. I got the proper firmware from the support site. I am trying to update from th CLI. Here is my current setup: - Connected to console port with console cable - LAN 1 connected to gigabite switch - computer with solarwinds TFTP server (10.1.1.3) - Ive renamed the image to image.out Ive copied the console session below üFGT60B (15:29-09.06.2007) Ver:04000006 Serial number:FGT60B3908638531 RAM activation Total RAM: 256MB Enabling cache...Done. Scanning PCI bus...Done. Allocating PCI resources...Done. Enabling PCI resources...Done. Zeroing IRQ settings...Done. Verifying PIRQ tables...Done. Boot up, boot device capacity: 64MB. Press any key to display configuration menu... ... [G]: Get firmware image from TFTP server. [F]: Format boot device. : Configuration and information. [Q]: Quit menu and continue to boot with default firmware. [H]: Display this list of options. Enter Selection [G]: Enter G,F,I,Q,or H: Please connect TFTP server to Ethernet port "1". Enter TFTP server address [192.168.1.168]: 10.1.1.3 Enter firmware image file name [image.out]: image.out Local address from DHCP server:10.1.1.4 MAC:00090F79E605 FGT60B (15:29-09.06.2007) Ver:04000006 Serial number:FGT60B3908638531 RAM activation Total RAM: 256MB Enabling cache...Done. Scanning PCI bus...Done. Allocating PCI resources...Done. Enabling PCI resources...Done. Zeroing IRQ settings...Done. Verifying PIRQ tables...Done. Boot up, boot device capacity: 64MB. Press any key to display configuration menu... ...... info: Failed to scan JFFSv2 file structure Open boot device failed. This is all it does. I dont get any notification on the TFTP server that anything is being transfered. Does anyone have a guide or knows what i am doing wrong? Please im desperate!! Thanks in advance for your help i really appreciate it. Regards, eXstat1c
This thread belongs to my "Cisco 88xVA – A home router on steroids" project. The initial thread serving as an anchor can be found HERE. Please use that thread for all general comments or requests. Cisco 88xVA – Part 3: Management tasks As mentioned in the previous section I ran into some issues once the router was connected to the internet. Smaller downloads - for me that means less than 1GB size - had no problems but larger downloads suddenly stopped almost always at some point. The output of the "show controller vdsl 0" command showed a pretty high number of CRC and header errors so that I opened a ticket at my ISP. After a day or two they called back and told me that they adjusted some parameters on the line that were not set correctly. The number of CRC and header errors dropped significantly after that but still large downloads tended to freeze. A quick look at Cisco's website showed that there was not only a newer IOS version but - more important - a newer firmware for the VDSL controller. I'm glad to say that all problems were gone after this upgrade! I assume that everyone is familiar with TFTP and how to copy files onto a router or switch. The flash of the 88xVA routers has enough space to take 3 images at this point of time so I could simply add the new one. The first step of upgrading the VDSL firmware is also a simple upload onto the router's flash via tftp. If you count downloading the firmware from Cisco's website, then it's the second step, of course. BTW, it's not necessary to rename the firmware file on these newer routers as described in some older Cisco documents. ! ! *** We want to boot the new IOS preferably but the old one if it fails for some reason ! *** it's always a good idea to have a backup plan... ! no boot system flash:c880data-universalk9-mz.151-4.M1.bin boot system flash:c880data-universalk9-mz.152-1.T1.bin boot system flash:c880data-universalk9-mz.151-4.M1.bin ! ! *** The following command loads the new VDSL firmware file ! *** You can go back to the build-in version by simply deleting this line at any time ! controller VDSL 0 firmware filename flash:vdsl.bin-A2pv6C035d_d23j ! ! *** It is strongly recommended to disable CDP on all outside interfaces ! *** I included this in part 2 already but without any comment ! interface Dialer0 no cdp enable ! ! *** You could also disable CDP on all client ports if you like ! *** but I don't do it as I also connect ip phones and ap's to those ports ! ! *** It is best practice to disable logging to the console and to use a buffer instead ! *** so you can do a "show logging" at any time without affecting the router's performance ! no logging console logging buffered 100000 informational ! ! *** I also run dedicated syslog and snmp servers in my network ! *** in this sample configuration I simply use 192.168.10.10 for all server related stuff ! logging host 192.168.10.10 session-id hostname ! snmp-server community sadikhov RW snmp-server community sadikhovro RO snmp-server trap-source Vlan1 snmp-server host 192.168.10.10 version 2c sadikhov ! ! *** We already covered NTP in the first part of this series as I consider it critical ! *** to have the correct time set on all devices... ! *** ...but now we also turn on ntp logging and make this router a ntp server for other devices ! ntp logging ntp master 5 ntp update-calendar ntp server 192.168.178.10 source Vlan1 iburst ! ! *** if you want to use some public ntp servers the config might look like this ! ! ntp server <ip address of first ntp server> prefer source Dialer0 ! ntp server <ip address of alternate npt server> source Dialer0 ! ! *** remember that we could also use hostnames instead as dns is running on this router ! ! *** finally we should not forget to turn on SSH even though I do not use it from the outside ! *** we already defined the hostname, domain name and a username that we can use ! *** so we can directly move on to create the necessary keys ! *** we generate dedicated SSH keys as we create additional ones for other purposes later ! crypto key generate rsa usage-keys modulus 1024 label SSHKEY ! ! *** we assign those keys to ssh and enforce version 2 as version 1 is unsecure ! ip ssh rsa keypair-name SSHKEY ip ssh version 2 ! ! *** don't forget to change the login for the terminal lines ! *** finally we enforce ssh for all remote connections AFTER you confirmed it's working ! line vty 0 4 login local transport input ssh ! ! end Comments and remarks There is no need to always run the latest and greatest IOS versions. Well-known rules like "never change a running system" do have their value. However, if you face some problems, testing new versions can't hurt. I focused on the standard SNMP version 2c in this part but might add the newer SNMP v3 at some later point of time. Be sure to test that SSH is working before you turn telnet access off, especially if you depend on the remote connection. What we achieved so far... In this part we upgraded the IOS and VDSL firmware to get rid of some stability problems. We also set up basic logging and monitoring so that we can take a look at the logs just in case something happened or if the router does not behave as expected. We also turned CDP off on all outside interfaces and moved from telnet to ssh for all remote connections. Now it's time to deal with the fact that we have a dynamically assigned public ip address and get disconnected every 24 hours... Feel free to ask if something is not clear to you! Comments and questions regarding this base configuration should be posted right here while general comments or requests should go into the anchor post mentioned at the beginning.