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

3troubleshootingjunos

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

Not

Troubleshooting JUNOS Platforms

Media Typ s and Int rface Naming

JUNOS platforms support s veral flavors of Ethernet. The following are the relevant media types:

 

Fast Ethernet: fe-F/P/P;

 

Gigabit Ethernet: ge-F/P/P;

 

10-Gigabit Ethernet: xe-F/P/P; and

for

Reproduction

Management Ethernet: fxp0 (10, 100, or 1000 Mbps).

 

 

Link Mode

When troubleshooting LAN topologies, consider the link mode:

Full duplex;

Half duplex; or

Link bonding (802.3ad)

Fast Ethernet interfaces can support half duplex or full duplex, but Gigabit Ethernet interfaces only function in full-duplex mode.

Continued on next page.

Interface Troubleshooting • Chapter 5–31

Troubleshooting JUNOS Platforms

JUNOS Software Tools

JUNOS Software provides the tools shown on the slide. The following pages examine these tools.

 

for

Reproduction

Not

 

 

 

Chapter 5–32 • Interface Troubleshooting

Troubleshooting JUNOS Platforms

 

 

 

 

Reproduction

 

 

 

 

 

 

 

 

 

 

Configuring Loo back Mode

 

 

 

 

 

 

 

To place an Eth

rn

int rface in loopback mode, issue a set gigether-options

 

 

 

loopback at the [ dit interfaces ge-interface-name] hierarchy. You

 

 

 

use a similar command for Fast Ethernet interfaces. When the interface loops, you

 

 

 

can monitor traffic and expect to see all traffic that travels out—that is, an Address

 

 

 

Resolution Protocol (ARP) request—coming right back in:

user@host> m nit

 

t affic interface fe-0/0/0

 

 

 

 

verbose output supp essed, use <detail> or <extensive> for full protocol decode

Listening

n e-0/0/0, capture size 96 bytes

 

 

 

 

21:14:04.424904 Out arp who-has 200.0.0.30 tell 200.0.0.1

21:14:04.425328

In arp who-has 200.0.0.30 tell 200.0.0.1

 

 

 

When operating in the default full-duplex mode, you can also attach an external

 

 

forloopback plug to effect an external local loopback. To see TTL expired messages (as

 

 

 

expected for point-to-point interfaces), you must add a static ARP entry that matches

 

 

 

the media access control (MAC) address for the looped interface for the target IP

 

 

 

address. This addition is necessary so that the interface accepts returning traffic

 

 

 

because a nonpromiscuous Ethernet interface only accepts broadcast and unicast

 

 

 

traffic sent to its MAC address. When all is working you should see TTL errors:

user@host> ping 200.0.0.20 count 1

 

 

 

 

 

NotPING 200.0.0.20 (200.0.0.20): 56 data bytes

 

 

 

 

36 bytes from 200.0.0.1: Time to live

exceeded

Src

Dst

Vr HL TOS

Len

ID Flg off TTL Pro

cks

4 5 00 0054 4e67

0 0000

01

01 db2c 200.0.0.1

200.0.0.20

 

 

Interface Troubleshooting • Chapter 5–33

Troubleshooting JUNOS Platforms

Not

Reproduction

 

 

 

Pinging a Locally Conn

D vice

A reply received from the

vice typically provides verification that the link and

interface are operating corr

ctly.

forDisplaying A P Table

The sh w a p no-resolve command displays the entries in the ARP table. Using the noes lve option prevents the device from attempting to determine the host name that c rresponds to the IP address.

Veri ying Cable Length

Ensure the cables used on the network do not exceed recommended lengths and meet all relevant specifications. If the cabling specifications are not met, the input errors on the interface will increase.

Continued on next page.

Chapter 5–34 • Interface Troubleshooting

Troubleshooting JUNOS Platforms

Generic Tips

The following are a few generic tips:

Ensure that encapsulation types are equivalent to other devices on link.

Not

for

 

Use the show interfaces extensive command to check the status the of interface.

Reproduction

Use the monitor interfaces command to receive real-time

 

statistics.

 

Use the monitor interface interface-name c mma d to

 

display real-time statistics about a physical interface. The utput updates

 

every second. The output of this command also sh ws

he am unt that

 

each field has changed since you started he command

r since you

 

cleared the counters by using the key. This ommand also checks for

and displays common interface failures, su h as SONET/SDH and T3 alarms, loopbacks detected, and in reases in framing errors. If the framing errors are increasing, this in rease indi ates that frames are being corrupted. If the input errors are increasing, check the cabling to the device and have the carrier verify the integrity of the line.

Interface Troubleshooting • Chapter 5–35

Continued on next page.

Troubleshooting JUNOS Platforms

 

 

 

Reproduction

 

 

 

 

 

 

 

 

Checking the Port

 

 

To troubleshoot T3 and E3, s up a physical loopback between the transmit and

 

 

receive ports. If the T3 int rface is functioning properly, you should see a

 

 

Loop-Detected flag in the device flags section of the show interface output.

 

for

 

 

Also, the monitor interface command should show that the input packet count

 

 

matches the output packet count. For Cisc HDLC encapsulation, the input keepalive

 

 

packet count should also match the output keepalive packet count.

 

 

If y u do n

t see the Loop-Detected flag, the PIC port might be bad. To isolate the

 

 

pr blem, m

ve the T3 link to another T3 interface on the router and verify whether the

 

 

new p rt w

rks. To move the configuration of the existing T3 interface to the new

Not

inter ace, use the rename command under the [edit interfaces] hierarchy in

configuration mode:

 

 

[edit in erfaces]

user@h st# rename t3-1/0/0 to t3-1/0/1

Chapter 5–36 • Interface Troubleshooting

Not

Troubleshooting JUNOS Platforms

Checking the Compatibility Mode

The subrate of an E3 or T3 interface must match that of the remote CSU exactly. The purpose of a subrate is to fit more bandwidth into an E3 or T3 circuit. To specify the subrate, include the subrate option in the compatibility-mode statement. Follow these instructions for different types of CSUs:

 

For Adtran CSUs, specify the subrate as a number from 1 through 588

 

Reproduction

 

 

that exactly matches the value configured on the CSU. A subrate value of

 

 

588 corresponds to 44.2 Mbps, or 100 percent of the

 

 

HDLC-encapsulated payload. A subrate value of 1 correspo ds to

 

 

44.2 / 588, which is 75.17 Kbps, or 0.17 percent

f the

 

 

HDLC-encapsulated payload.

 

 

 

For Digital Link CSUs, specify the subrate value as

he data rate y u

 

 

configured on the CSU in the format xKb or x.xMb. For a l st of specific

 

 

rate values, use the command completion fea ure in he command-line

 

 

interface (CLI). The range is 358 Kbps through 33.7 Mbps for E3

 

 

interfaces and 301 Kbps thro gh 44.2 Mbps for T3 interfaces.

 

For Kentrox CSUs, specify the s brate as a n

mber from 1 through 69

 

 

that exactly matches the value config red on the CSU. A subrate value of

 

 

69 corresponds to 34.995097 Mbps, or 79.17 percent of the

 

 

HDLC-encapsulated payl ad (44.2 Mbps). A subrate value of 1

 

 

corresponds to 999.958 Kbps, which is 2.26 percent of the

 

 

HDLC-encapsulated payl ad.

 

 

 

For T3 inte faces configu ed with Larscom CSUs, specify the subrate

 

 

value as a number f om 1 through 14 that matches the value configured

 

 

on the CSU xactly. E3 interfaces do not support the subrate option with

 

 

Larscom CSUs.

 

 

 

For V rilink CSUs, specify the subrate as a number from 1 through 28

 

 

that xactly matches the value configured

the CSU. To calculate the

 

 

maximum allowable peak rate, multiply the configured subrate by 1.578

 

 

Mbps. For example, a subrate value of 28 corresponds to 28 x 1.578

for

 

Mbps, which is 44.2 Mbps—100 percent of the HDLC-encapsulated

 

payload.

 

 

 

 

 

 

Ensuring Compatible Settings

The f llowing settings ensure compatibility:

E3 and T3 frame checksums: By default, E3 and T3 interfaces use a 16-bit frame checksum. You can configure a 32-bit checksum that provides more reliable packet verification. However, some older equipment might not support 32-bit checksums.

HDLC payload scrambling: E3 or T3 HDLC payload scrambling, which is disabled by default, provides better link stability. Both sides of a connection must either use or not use scrambling.

Line buildout: To have the interface drive a line that is longer than 255 feet, include the long-buildout statement at the [edit interfaces interface-name t3-options] hierarchy level.

Continued on next page.

Interface Troubleshooting • Chapter 5–37

Troubleshooting JUNOS Platforms

Ensuring Compatible Settings (contd.)

Not

for

 

T3 C-bit parity mode: For T3 interfaces, the C-bit parity mode controls the type of framing present on the transmitted T3 signal. When C-bit parity mode is enabled, the C-bit positions are used for the far-end block error (FEBE), FEAC, the terminal data link, path parity, and mode indicator bits, as defined in American National Standards Institute (ANSI)

T1.107a-1989. When you disable C-bit parity mode, the basic T3 framing modeReproductionis used. By default, C-bit parity mode is enabled. To disable it, include the no-cbit-parity statement at the [edit interfaces

interface-name t3-options] hierarchy level.

Chapter 5–38 • Interface Troubleshooting

Not

Troubleshooting JUNOS Platforms

DisplayingReproductionActive Alarms

If the first line shows Physical link is Up, it means that the physical link is healthy and can pass pack ts. If the first line shows Physical link is Down, it means that the physical link is unhealthy and cannot pass packets. To display more

forextensive information about the T3 interfac if the physical link is down, use the show inte face t3-x/y/z extensive command. Look at the active alarms and active defects for the T3 interface, and troubleshoot the T3 media accordingly.

Interface Troubleshooting • Chapter 5–39

IDLE: An idle alarm indicates that the line is not provisioned for service. Have the carrier ensure line-provisioning for service.
Yellow: An incoming yellow alarm indicates that the router’s DS-3 interface has a problem with the signal it is receiving from the remote equipment’s DS-3 interface. Check the cable between the DS-3 interface and the directly connected network equipment.

Troubleshooting JUNOS Platforms

 

 

 

 

 

 

 

LoFReproduction: A loss of frame (LoF) alarm indicates loss of DS-3 framing bits. Verify

 

 

 

 

Important DS-3 Alarms

 

 

The following list provid s scriptions of the important DS-3 alarms:

 

 

AIS: An incoming alarm indication signal (AIS) indicates a problem with

 

 

 

the line upstream of the network equipment connected to the DS-3

 

for

 

 

 

inte face. Have the carrier check the equipment connected to the DS-3

 

 

 

inte face and trace the problem.

 

 

 

the framing format configuration (C-bit parity mode) and check the DS-3

 

 

 

line. Bursts of Line Code Violations (LCVs) could indicate a timing

Not

 

problem.

LoS: A loss of signal (LoS) alarm means that a signal could not be

 

 

detected at the DS-3 interface. Check the cables connected to the DS-3 interface, and have the carrier verify the integrity of the line.

Continued on next page.

Chapter 5–40 • Interface Troubleshooting