The document provides instructions for copying configuration files between devices using the copy command, and describes boot processes and restoring configurations from backups. It also includes commands for viewing router interfaces and configurations, and resetting the router to factory defaults.
The document provides instructions for copying configuration files between devices using the copy command, and describes boot processes and restoring configurations from backups. It also includes commands for viewing router interfaces and configurations, and resetting the router to factory defaults.
The document provides instructions for copying configuration files between devices using the copy command, and describes boot processes and restoring configurations from backups. It also includes commands for viewing router interfaces and configurations, and resetting the router to factory defaults.
The document provides instructions for copying configuration files between devices using the copy command, and describes boot processes and restoring configurations from backups. It also includes commands for viewing router interfaces and configurations, and resetting the router to factory defaults.
Download as TXT, PDF, TXT or read online from Scribd
Download as txt, pdf, or txt
You are on page 1/ 8
copy a:/primary/boot.cfg 10.101.1.236:boot.
cfg
UBICARSE PRIMERO EN EL PRIMARY CON un comando CD
copy 10.0.0.1:z01rf022r2_10.101.22.251.cfg a:/primary/boot.cfg (COPIAR ARCHIVO DE
PC A GGM) copy 10.0.0.1:z01rf022r2_10.101.22.251_acl.cfg a:/primary/acl.cfg (COPIAR ARCHIVO DE PC A GGM) copy 10.0.0.1:staticRP.cfg a:/primary/staticRP.cfg (COPIAR ARCHIVO DE PC A GGM)
copy a:/primary/boot.cfg 10.1.233.189:boot.cfg (COPIAR ARCHIVO DE GGM A PC)
copy a:/primary/acl.cfg 10.1.233.189:acl.cfg (COPIAR ARCHIVO DE GGM A PC) copy a:/primary/staticRP.cfg 10.1.233.189:staticRP.cfg (COPIAR ARCHIVO DE GGM A PC)
To subsequently restore the router configuration from the backup in the secondary directory in the event that the contents of the primary directory have become corrupted, follow these steps: a) From the EnterpriseOS# prompt, enter SF 7 to open the SysconF command Boot Sources menu. b) Enter 3 to direct the router to boot from the secondary directory. c) Reboot the router.
Pushing EOS Locally
=================== Push new EOS locally from a latop by using TFTP. Procedure: 1 Log on to the router by using the console connection. Enter the username (root) and appropriate password (usually no password on a new gateway). 2 Point the TFTP server to the boot.ppc file.
3 Assign an IP address to the laptop with the appropriate subnet mask.
For example, assign 10.0.0.1 with 255.255.255.0. Note: This IP address has to be in the same subnet as the router�s interface that will be connected to the laptop�s Ethernet card.
4 Connect the laptop�s Ethernet card to port 1 of the device (!1) by using a crossover cable.
5 On the router (with the 10.0.0.2 IP address in this example), perform the following actions: a) Enter: setd !1 -ip netaddr= 10.0.0.2 255.255.255.0 b) Enter: setd !1 -po cont=e c) Enter: setd !1 -pa cont=e
6 To check if Port 1 status is up, enter: show �ip neta
7 Ping the laptop IP address to check connectivity.
8 Enter: copy 10.0.0.1:/boot.ppc a:/primary/boot.ppc Note: The boot.ppc file is copied from the TFTP directory into the router's primary directory. The file transfer takes about 1 to 3 minutes.
9 Reboot the router.
10 After the reboot, verify EOS by entering:
show -sys soi a:/primary/boot.ppc This command displays the EOS software package and version number for the specified boot file in the gateway�s primary directory. Verify that the correct package and version are listed.
En la configuracion del router son 3 archivos que se deben pasar al equipo, el boot el acl y el stactiRP(este es un unico archivo para cualquier router)
show interfaces brief
sh -ip netaddr sh bfds (tunel) sh bgp all sh -bgp peer sh -bgp rts
sh -nat
sh -ip alr (routes)
sh -ip ro (routes) sh -nat am sh -nat sess (show my nat)
ACL === Muestra si la ACL esta cargada sh -fw control
lc antiACL.cfg ia (carga el antiacl e gnora errores)
lc acl.cfg (recarga el acl.cfg e ignora errores)
El archivo antiacl.cfg es uno solo para todos los routers del sistema y es el mismo para sistemas en la misma versi�n. El antiacl.cfg se introdujo en version 7.15. El ACL no debe cararse en los border routers o debe sedr configurado a mano antes de cargarlo debido a las redes del cliente.
SYNTAX BS DESCRIPTION Use the BS command to display a menu that allows you to display or change boot source information and to boot the GGM 8000. SOURCE Boot Source Selection SRC1 Source 1 Configuration SRC2 Source 2 Configuration SRC3 Source 3 Configuration SOURCE (BOOT SOURCE SELECTION) SYNTAX SOURCE sel=<0|1|2|3>
sh -po virtualport Port !V1 VirtualPort = IPIP 192.168.24.105 192.168.24.100 Port !V2 VirtualPort = IPIP 192.168.24.105 192.168.24.101 Port !V20 VirtualPort = 3 VLan 765
z01nmd002r1# sh -po name
Port !1 NAme = PO_1 Port !2 NAme = PO_2 Port !3 NAme = PO_3 Port !4 NAme = PO_4 Port !V1 NAme = PO_C002A Port !V2 NAme = PO_C002B Port !V20 NAme = Backhaul
sh -po paths Port !1 PAths = 1 Port !2 PAths = 2 Port !3 PAths = 3 Port !4 PAths = 4 Port !V1 PAths = IPIP 192.168.24.105 192.168.24.100 Port !V2 PAths = IPIP 192.168.24.105 192.168.24.101 Port !V20 PAths = 3 VLan 765
sh -po control Port !1 CONTrol = Enabled Port !2 CONTrol = Disabled Port !3 CONTrol = Enabled Port !4 CONTrol = Disabled Port !V1 CONTrol = Enabled Port !V2 CONTrol = Enabled Port !V20 CONTrol = Enabled
En boot mode FO : format flash (borra todo!!! factory default)
(C)ount : Number of ping requests to send (1-1000000)
(W)ait : Time in millisec to wait for each reply (100-1000000 ms) (T)TL : Time to live (1-255) (L)ength : Size of the data in bytes (1-16000) (I)ncrement: Data increment for multiple requests (1-1024) (D)ata : Data string in quotes (1-80 characters) (R)ecord : If present, turns on record route option in ping pkts
-----------------------------MIP Service Commands------------------------------
--<CR> to continue, Q to quit-- IGMPSend !<source-port> [V1 | V2] <Type> [SubType] <GroupAddr> [Count]
source-port: port no. through which you want IGMP packets out source-IP : IP address to use when sending IGMP packets out V1_V2 : IGMP Version to use Type : IGMP packet type to sent; hex value SubType : SubType field value in IGMP packet in hex GroupAddr : GroupAddr in IGMP packet depending on Packet type Count : No. of IGMP packets to be sent
-----------------------------NAT Service Commands------------------------------
NATReStart
-----------------------------PATH Service Commands-----------------------------
