Task 6: Perform General Maintenance and Software Upgrade

Task 6: Perform General Maintenance and Software Upgrade

At this stage, your basic system configuration should be completed and its operational status confirmed. If you have not already looked for hardware anomalies or alarms, now might be a good time to issue some chassis/hardware related show commands to confirm that all is good to go with your gear. You should also take note of the JUNOS software version on each router, because an upgrade or a downgrade may be necessary to meet the requirements of your scenario. The following commands illustrate the most common ways of accessing the state of your hardware. The syntax and output can vary depending on M-series router type, but the general concept and results are similar for all Juniper Networks routers.

First, verify that there are no chassis alarms:

lab@r1> show chassis alarms No alarms currently active

The lack of alarms indicates the router is free from serious hardware and environmental defects. Next, check out the general hardware environment of each router:

lab@r1> show chassis environment Class Item                 Status    Measurement Power Power Supply A       OK       Power Supply B       Absent Temp  FPC Slot 0           OK        33 degrees C / 91 degrees F       FEB                  OK        34 degrees C / 93 degrees F       PS Intake            OK        29 degrees C / 84 degrees F       PS Exhaust           OK        31 degrees C / 87 degrees F Fans  Left Fan 1           OK        Spinning at normal speed       Left Fan 2           OK        Spinning at normal speed       Left Fan 3           OK        Spinning at normal speed       Left Fan 4           OK        Spinning at normal speed Misc  Craft Interface      OK

The missing power supply B is generally not an issue in a test bed, so all looks normal here. For even more information on the router's hardware, issue the following command:

lab@r1> show chassis hardware Hardware inventory: Item             Version Part number Serial number     Description Chassis                              50779             M5 Midplane         REV 03  710-002650  HF2739 Power Supply A   Rev 04  740-002497  LK23083           AC Display          REV 04  710-001995  AV8231 Host                                 bb00000792cd4801  teknor FEB              REV 09  710-002503  HF2037            Internet Processor II FPC 0   PIC 0          REV 04  750-002992  HD4121            4x F/E, 100 BASE-TX   PIC 1          REV 03  750-002971  HE5549            4x OC-3 SONET, MM

Based on this display, you can confirm you are working on an M5 router, with a single FPC (only one FPC is supported on an M5), equipped with a four-port Fast Ethernet PIC and a four- port OC-3 SONET PIC. It is worth noting that this router, as with all M5s, M10s, M160s, and M40e platforms, is IP II equipped. Because the IP II is needed for various enhanced functions, such as firewalls and VPNs, the absence of an IP II in any router making up your test bed is certainly worth noting. Similarly, you should take note of any service PICs available in your test bed. For instance, noting what routers have a tunnel PIC installed can be real handy if you later find yourself trying to decide on which pair of routers to use when a tunnel application is thrown your way.

Next, let's check the software versions on all the machines:

lab@r2> show version Hostname: r2 Model: m5 JUNOS base [4.4R1.5] JUNOS Kernel Software Suite [4.4R1.5] JUNOS Routing Software Suite [4.4R1.5] JUNOS Packet Forwarding Engine Support [4.4R1.5] JUNOS Online Documentation Files [4.4R1.5] . . . 

While r2 is probably free from rust, it is running a rather old version of JUNOS software. Candidates taking the JNCIP exam are expected to know how to perform command line-based FTP transfers, and should be prepared to perform JUNOS software upgrades (or downgrades) using jinstall, jbundle, and individual jbundle components such as a jroute package, when called for. In this sample scenario, all routers must be running some form of 5.x release, so it looks like r2 is in line for some new bits pretty quickly.

Upgrading or downgrading an M-series router between 4.x and 5.x releases requires the use of a jinstall package due to the resulting change from a.out to ELF binaries; use of a jinstall package will affect both the system binaries and the JUNOS software components. Within a 4.x or 5.x release, the operator should use either a jbundle or individual j-package for upgrade or downgrade. Attempting to upgrade or downgrade between 4.x and 5.x releases using a jbundle package will result in wasted time, as the install script will abort without making any modifications to the system being upgraded or downgraded.

Since r2 is running a 4.x release, we know that we need to locate a 5.x related jinstall on the FTP server. The following capture illustrates typical FTP session commands and the actual file transfer. The capture begins by showing the initial FTP login:

lab@r2> ftp 10.0.200.2 Connected to 10.0.200.2. 220-cert-lab NcFTPd Server (free personal license) ready. 220-Warning!!! 220-This is a restricted computer system. 220- 220-ALL ACTIONS ARE LOGGED! 220 Name (10.0.200.2:lab): lab 331 User lab okay, need password. Password: 230-You are user #1 of 3 simultaneous users allowed. 230- 230-Welcome to the FTP site. 230 Restricted user logged in. Remote system type is UNIX. Using binary mode to transfer files. 

Now that we are logged into the FTP server, let's see what packages are available by obtaining a file listing:

ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for /bin/ls. -rw-r--r-- 1 ftpuser ftpusers 19538662 Apr 2 04:23 4.1R1.5-domestic.ls120.tgz -rw-r--r-- 1 ftpuser ftpusers 19512433 Apr 2 04:23 4.1R1.5-domestic.pcm110.tgz -rw-r--r-- 1 ftpuser ftpusers   433758 Apr 2 04:23 jbase-4.0B3-domestic.tgz -rw-r--r-- 1 ftpuser ftpusers  7927224 Apr 2 04:23 jbundle-3.4R3.2.tgz -rw-r--r-- 1 ftpuser ftpusers  6530202 Apr 2 04:23 jbundle-4.0R4.tgz -rw-r--r-- 1 ftpuser ftpusers  7774361 Apr 2 04:23 jbundle-4.1R1.5.tgz -rw-r--r-- 1 ftpuser ftpusers  8687924 Apr 2 04:23 jbundle-4.2R2.4-domestic.tgz -rw-r--r-- 1 ftpuser ftpusers  9187867 Apr 2 04:23 jbundle-4.3R1.4-domestic.tgz -rw-r--r-- 1 ftpuser ftpusers  9202130 Apr 2 04:23 jbundle-4.3R2-domestic.tgz -rw-r--r-- 1 ftpuser ftpusers  9208526 Apr 2 04:23 jbundle-4.3R3-domestic.tgz -rw-r--r-- 1 ftpuser ftpusers  9871826 Apr 2 04:23 jbundle-4.4B1.2-domestic.tgz -rw-r--r-- 1 ftpuser ftpusers 10094406 Apr 2 04:23 jbundle-4.4R1.5-domestic.tgz -rw-r--r-- 1 ftpuser ftpusers  6530202 Apr 2 04:23 jbundle-4_0R4.tgz -rw-r--r-- 1 ftpuser ftpusers 24217723 Apr 2 04:23 jbundle-5.2R2.3- domestic-signed.tgz -rw-r--r-- 1 ftpuser ftpusers 19685721 Apr 2 04:23 jinstall-4.4R1.5- domestic.tgz -rw-r--r-- 1 ftpuser ftpusers 21543210 Apr 2 04:23 jinstall-5.2R2.3- domestic.tgz -rw-r--r-- 1 ftpuser ftpusers 21530984 Apr 2 04:23 jinstall-5.0B1.2- domestic.tgz 226 Listing completed.

In this example, there are many packages from which to choose, but it has already been determined that a 5.x version of jinstall package is needed to satisfy the requirements of this example. In this case, the operator takes the "easy" way out by using the globbing character (*) in conjunction with the mget FTP transfer option, which results in a prompt for the transfer of each matching file:

ftp> mget jinstall* mget jinstall-4.4R1.5-domestic.tgz? n mget jinstall-5.2R2.3-domestic.tgz? y 200 PORT command successful. 150 Opening BINARY mode data connection for jinstall-5.2R2.3-domestic.tgz   (21543210 bytes) 226 Transfer completed. 21543210 bytes received in 22.07 seconds (953.15 Kbytes/s) ftp>quit 

Now that the correct 5.x jinstall package has been transferred to r2, the operator instructs the router to load the new software and to automatically reboot so that the new code is put into effect:

lab@r2> request system software add jinstall-5.2R2. 3-domestic.tgz reboot Installing package ‘/var/home/lab/jinstall-5.2R2.3-domestic.tgz' ... WARNING: This package will load JUNOS 5.2R2.3 software. WARNING: It will save JUNOS configuration files, log files, and SSH keys WARNING: (if configured), but erase all other files and information WARNING: stored on this machine. This is the pre-installation stage WARNING: and all the software is loaded when you reboot the system. Saving the config files ... NOTICE: uncommitted changes have been saved in /var/db/config/juniper.conf.pre-  install . . .

After the two reboots associated with jinstall package installation, r2 comes back up and the new code installation is confirmed:

lab@r2 show version Hostname: r2 Model: m5 JUNOS Base OS boot [5.2R2.3] JUNOS Base OS Software Suite [5.2R2.3] JUNOS Kernel Software Suite [5.2R2.3] JUNOS Routing Software Suite [5.2R2.3] JUNOS Packet Forwarding Engine Support [5.2R2.3] JUNOS Crypto Software Suite [5.2R2.3] JUNOS Online Documentation [5.2R2.3]




JNCIP. Juniper Networks Certified Internet Professional Study Guide Exam CERT-JNCIP-M
JNCIP: Juniper Networks Certified Internet Professional Study Guide
ISBN: 0782140734
EAN: 2147483647
Year: 2003
Pages: 132

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net