Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:

3troubleshootingjunos

.pdf
Скачиваний:
19
Добавлен:
09.06.2015
Размер:
32.13 Mб
Скачать

Appendix D: Answer Key

Chapter 1:

Chapter 2:

Chapter 3:

Not

Course Introduction

This chapter does not contain any review questions.

TroubleshootingReproductionTool Kit for JUNOS Platforms

Overview of JUNOS Platforms

1.

To safely power off an M Series router, you must perform a graceful shu d wn f JUNOS Software before removing power. Use the request system reboot ommand, which causes the device to reboot.

2.

The RE is the brains of the platform; it is responsible for performing routing updates and system management. The RE runs various protocol and management software processes inside a protected memory environment. The PFE is responsible for forwarding transit packets through the router using an ASIC-based switching path.

3.

The Craft Interface is the collection of mechanisms n some JUNOS platforms that allow you to

view system status messages an

t oubleshoot the router. The Craft Interface is located on the

front of the chassis and ty

ically consists of va ious system status LEDs and FPC (or PIC) online

and offline buttons. On su

ort d

latforms the Craft Interface includes an LCD screen that

provides status reporting for the

ntire system.

4.

Interface name at-0/1/1.100 references a logical unit 100 of the ATM interface in FPC 0, PIC 1, and port 1.

forBecause m dern communications networks are complex, troubleshooting them can be challenging. To alleviate this challenge, we recommend a layered troubleshooting approach. Such an approach utilizes the OSI model to identify prospective problems, isolate the likely causes of those problems, and then systematically eliminate each potential cause. By conducting tests that accurately isolate a symptom to the root-cause layer, you avoid wasting time testing layers that are not at fault.

1.

2.

The three ways in which the CLI can help to perform fault analysis are: (1) deployment of key commands; (2) process restart and bringing hardware online and offline; and (3) deployment of network and diagnostic utilities.

Answer Key • D–1

Chapter 3: Troubleshooting Tool Kit for JUNOS Platforms (contd.)

3.

The two good reasons to escape to an interactive shell are: (1) to access standard utilities and programs, enabling experienced UNIX users to perform advanced troubleshooting tasks; and

(2) the ability to establish a connection to embedded hosts within the PFE to perform complex diagnostics.

 

4.

 

Reproduction

 

 

 

 

You can reset the OSPF process without affecting other routing protocols by deactivati g OSPF

 

in the configuration mode and then committing the configuration file. This appr ach requires

 

you to have configuration privileges.

Chapter 4:

JUNOS Platforms Hardware Troubleshooting

 

1.

 

 

 

The correct procedure for powering off a JUNOS platform is as follows: First shutdown the

 

JUNOS Software using the CLI request system halt command. Next, t rn off the power

 

supplies.

 

 

2.

 

 

 

You can use the JUNOS Software CLI to display inf rmati n ab ut the chassis and the PFE using

 

the show chassis ... and show pfe ... commands to display information about the system

 

and software processes using the show system ... mmands and to display system log files.

 

3.

 

 

 

The two ways of determining if chassis alarms are resent are using the show chassis

 

alarms command; and the show chassis craft-interface command.

 

4.

 

 

 

The following command searches the messages file for all lines matching fail and error:

 

show log messages | match fail | match error.

Chapter 5:

 

for

 

Interface T oubleshooting

 

1.

 

 

 

When y u deactivate an interface, JUNOS Software completely ignores that specific interface

Not

 

and does not apply it when you issue a commit command. When you disable an interface, it ac iva es when you issue a commit command but is treated as being down or administratively disabled.

2.

Y u can check the results of your BERT test using the show interfaces extensive command.

3.

When troubleshooting T3 or E3 interface problems you must ensure that the two ends of the circuit have the following compatible parameters: clocking, frame checksum, HDLC payload scrambling (if using Cisco HDLC encapsulation), T3 line buildout, and T3 C-bit parity mode.

D–2 • Answer Key

Chapter 5: Interface Troubleshooting (contd.)

Chapter 6:

Not

4.

You use the monitor interface interface-name command to display real-time statistics about a physical interface. The output updates every second. The output of this command also shows the amount that each field changes from the time you start the command or from the time you clear the counters by using the c key.

JTAC Processes, Guidelines, and Support Resources

1.

You need a chassis serial number when opening a case. The serial number w ll help JTAC staff to determine the support status.

2.

When you access the CSC, you have a wealth of technical s pport information in the form of the JTAC Knowledge Base, the PR database, technical b lletins, and white papers that provide configuration examples and technology primers.

3.

 

The I2J tool converts Cisco IOS configurati

into a JUNOS Software configuration. It is a good

idea to inspect the output, ensuring that y u

btained the desired results.

4.

 

 

You should use FTP to transfer files to JTAC when the size of those files is larger than 10

MB.

for

Reproduction

 

 

 

Answer Key • D–3

 

for

Reproduction

Not

 

 

 

D–4 • Answer Key