Data Center LAN Migration Guide - Juniper Networks
Data Center LAN Migration Guide - Juniper Networks
Data Center LAN Migration Guide - Juniper Networks
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Data</strong> <strong>Center</strong> <strong>LAN</strong> <strong>Migration</strong> <strong>Guide</strong><br />
Troubleshooting<br />
Introduction<br />
The scope of this section is to provide an overview of common issues that might be encountered at different insertion<br />
points when inserting <strong>Juniper</strong> platforms as a result of a trigger event (adding a new application or service to the<br />
organization). This section won’t provide exhaustive troubleshooting details, however, we do describe the principal<br />
recommended approaches to troubleshooting the most common issues and provide guidelines for identification,<br />
isolation, and resolution.<br />
Troubleshooting Overview<br />
When investigating the root cause of a problem, it is important to determine the problem’s nature and analyze its<br />
symptoms. When troubleshooting a problem, it is generally advisable to start at the most general level and work<br />
progressively into the details, as needed. Using the OSI model as a reference, troubleshooting typically begins at the<br />
lower layers (physical and data link) and works progressively up toward the application layer until the problem is found.<br />
This approach tends to quickly identify what is working properly so that it can be eliminated from consideration, and<br />
narrows the problem domain for quick problem identification and resolution.<br />
The following list of questions provides a methodology on how to use clues and visible effects of a problem to reduce<br />
the diagnostic time.<br />
• Has the issue appeared just after a migration, a deployment of new network equipment, a new link connection, or<br />
a configuration change? This is the context being presented in this <strong>Data</strong> <strong>Center</strong> <strong>LAN</strong> <strong>Migration</strong> <strong>Guide</strong>. The Method of<br />
Procedure (MOP) detailing the steps of the operation in question should include the tasks to be performed to return<br />
to the original state before the network event, should any abnormal conditions be identified. If any issue arises during<br />
or after the operation that cannot be resolved in a timely manner, it may be necessary to roll back and disconnect<br />
newly deployed equipment while the problem is researched and resolved. The decision to back out should be<br />
made well in advance, prior to the expiration of the maintenance window. This type of problem is likely due to an<br />
equipment misconfiguration or planning error.<br />
• Does the problem have a local or a global impact on the network? The possible causes of a local problem may<br />
likely be found at L1 or L2, or it could be related to an Ethernet switching issue at the access layer. An IP routing<br />
problem may potentially have a global impact on networks, and the operator should focus its investigation on the<br />
aggregation and core layer of the network.<br />
• Is it an intermittent problem? When troubleshooting an intermittent problem, system logging and traceoptions<br />
provide the primary debugging tools on <strong>Juniper</strong> <strong>Networks</strong> platforms, and can be focused on various protocol<br />
mechanisms at various levels of detail. Events occurring in the network will cause the logging of state transitions<br />
related to physical, logical, or protocols to local or remote files for analysis.<br />
• Is it a total or partial loss of connectivity or is it a performance problem? All <strong>Juniper</strong> <strong>Networks</strong> platforms have<br />
a common architecture in that there are separate control and forwarding planes. For connectivity issues, <strong>Juniper</strong><br />
recommends that you first focus on the control plane to verify routing and signaling states and then concentrate<br />
on the forwarding or data plane, which is implemented in the forwarding hardware (Packet Forwarding Engine or<br />
PFE). If network performance is adversely affected by packet loss, delays, and jitter impacting one or multiple traffic<br />
types, the root cause is most likely related to network congestion, high link utilization, and packet queuing along the<br />
traversed path.<br />
56 Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.