3troubleshootingjunos
.pdf
Not
Troubleshooting JUNOS Platforms
|
Reproduction |
|
|
|
|
|
|||
Interface Case Study C: Background |
||||
The slide s |
ts the stage for a third interface troubleshooting case study. We begin with |
|||
a general |
scription of the problem, which, in this case, indicates that the Ethernet |
|||
link between the San Jose and Montreal devices appears to be in Down state. |
||||
for |
|
|
|
|
Note that in this example, you are not permitted to view the interface-related configu ation at either end.
Interface Troubleshooting • Chapter 5–91
Troubleshooting JUNOS Platforms
Not
Interface Case Study C: Course of Action
Several reasons might xist for an Ethernet links to be in the Down state. The reasons include:
• |
|
Misconfigured Ethernet parameters or incomplete auth-negotiations; |
• |
|
Faulty PIC; or |
• |
|
Faulty interface wiring. |
|
|
Reproduction |
In JUNOS S |
ftware, Ethernet link autonegotiation is enabled by default. |
|
for |
|
|
Chapter 5–92 • Interface Troubleshooting
Not
Troubleshooting JUNOS Platforms
InterfaceReproductionCase Study C: Check the Ethernet Interface Details
Suspecting a Lay 2 configuration mismatch, you begin by displaying media interface information for the ge-0/1/0 interfaces at the San Jose and Montreal stations. The show command indicates that the interface’s autonegotiation is enabled, which is the
default behavior. Also, you see that the negotiation status is Incomplete. for
Interface Troubleshooting • Chapter 5–93
Troubleshooting JUNOS Platforms
|
Reproduction |
|
|
|
|
|
|||
Interface Case Study C: Solution |
||||
To fix the problem, you |
nsure that both local and remote devices can successfully |
|||
autonegotiate the conn |
param ters. If that does not solve the problem, you |
|||
explicitly configure San Jose and Montreal stations to operate in the desired mode |
||||
for |
|
|
|
|
with autonegotiation disabled. In our case the autonegotiation succeeded. Now the |
||||
inte face status is Up, as illustrated: |
||||
user@San_Jose> sh w inte faces ge-0/1/0 media
Physical inter ace: ge-0/1/0, Enabled, Physical link is Up Interface index: 133, SNMP ifIndex: 169
Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, MAC-REWRITE Error: None,
Loopback: |
Disabled, Source filtering: Disabled, Flow control: Enabled, |
|
Auto-neg |
ia ion: Enabled, Remote fault: Online |
|
Device flags |
: Present Running |
|
Interface flags: SNMP-Traps Internal: 0x4000 |
||
Link flags |
|
: None |
. . . |
|
|
Autonegotiation information: |
||
egotiation status: Complete |
||
Link partner: |
|
|
NotLink mode: Full-duplex, Flow control: Symmetric/Asymmetric, Remote |
||
fault: OK
Local resolution:
Flow control: Symmetric, Remote fault: Link OK
Chapter 5–94 • Interface Troubleshooting
Troubleshooting JUNOS Platforms
|
|
|
Reproduction |
|
|
|
|
|
|
|
|||
|
|
This Chapt |
Discuss d: |
|||
|
|
|
• |
Physical and logical interface properties; |
||
|
|
|
• |
Deactivating and disabling interfaces; |
||
|
|
for |
• |
Configuring loopbacks and BERT tests; and |
||
|
|
• |
Using operational mode commands to monitor and troubleshoot a variety |
|||
|
|
|
||||
|
|
|
|
of interfaces and media types. |
||
Not |
|
|
|
|
|
|
Interface Troubleshooting • Chapter 5–95
Troubleshooting JUNOS Platforms
Not
3. |
Reproduction |
|
|
|
|||
Review Questions |
|||
1. |
|
|
|
2. |
|
|
|
for |
|
|
|
4. |
|
|
|
Chapter 5–96 • Interface Troubleshooting
Troubleshooting JUNOS Platforms
|
|
|
Reproduction |
|
|
|
|
|
|
||
|
|
Lab 3: Int rface Troubl shooting |
|||
|
|
The slide shows the obj ctive for this lab. |
|||
Not |
for |
|
|
|
|
|
|
|
|
||
Interface Troubleshooting • Chapter 5–97
Troubleshooting JUNOS Platforms
|
for |
Reproduction |
Not |
|
|
|
|
Chapter 5–98 • Interface Troubleshooting
|
|
Reproduction |
|
Troubleshooting JUNOS Platforms |
|
|
Chapter 6: JTAC Processes, Guidel nes, and |
|
|
Support Resources |
|
Not |
for |
|
|
|
|
Troubleshooting JUNOS Platforms
Not
• |
TheReproductionJuniper Networks Technical Assistance Center (JTAC) Knowledge |
|
This Chapter Discuss |
s: |
|
• |
Support ntitl |
m nt and opening a support case; |
• |
Support resources; |
|
• |
The Customer Support Center (CSC); |
|
for |
Case management; |
|
• |
||
|
Base (KB) and Problem Report (PR) search tools; |
|
• |
The IOS-to-JUNOS Conversion (I2J) tool; |
|
• |
Downloading software and technical documentation; and |
|
• |
Transferring files to JTAC using FTP. |
|
Chapter 6–2 • JTAC Processes, Guidelines, and Support Resources