Accelerated Migrating and Troubleshooting HP Enterprise Networks

Part 2: Troubleshooting HP Enterprise Networks

Rev. 11.31 - Course #: 00314301
Part Number: 00314301S21105 - Book 2 of 2

Student guide
HP Partner Learning
 Copyright 2011 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties
for HP products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial errors or
omissions contained herein.
This is an HP copyrighted work that may not be reproduced without the written permission
of HP. You may not use these materials to deliver training to any person outside of your
organization without the written permission of HP.
Printed in United States of America
Accelerated Migrating and Troubleshooting HP Enterprise Networks
Part 2: Troublershooting HP Enterprise Networks

Student guide – Book 2 of 2

May 2011
HP Restricted
 Contents

Module 1: Troubleshooting Methodologies and Practices

Objectives .................................................................................................... 1-1
Troubleshooting Methodology ......................................................................... 1-2
Methodology .......................................................................................... 1-2
Skill Sets ................................................................................................ 1-3
Problem solving methodology .......................................................................... 1-4
Identification and analysis .............................................................................. 1-6
Hypothesis and validation .............................................................................. 1-8
Implementation and verification ......................................................................1-10
Summary ..................................................................................................... 1-11

Module 2: Intelligent Resilient Framework

Objectives .................................................................................................... 2-1
Lab 2: IRF Troubleshooting and Problem Resolution ............................................ 2-2
Lab Activity 2.1: Trouble Ticket 1 ......................................................................2-3
Lab Activity 2.2: Trouble Ticket 2 .................................................................... 2-4

Module 3: Rapid Ring Protection Protocol—Basic Concepts

Overview ..................................................................................................... 3-1
RRPP topologies............................................................................................. 3-2
RRPP single ring ........................................................................................... 3-3
RRPP single ring control and data VLANs ........................................................ 3-4
RRPP single ring primary and secondary ports ................................................. 3-5
RRPP mechanisms: Ring health ....................................................................... 3-6
RRPP PDUs ............................................................................................ 3-6
HELLO ............................................................................................ 3-6
LINK-DOWN................................................................................... 3-6
COMMON-FLUSH-FDB .................................................................... 3-7
COMPLETE-FLUSH-FDB ..................................................................... 3-7
EDGE-HELLO ................................................................................... 3-7
MAJOR-FAULT ................................................................................. 3-7
RRPP mechanisms: Ring recovery .................................................................... 3-8
RRPP single ring configuration example........................................................... 3-9
MSTP configuration ..................................................................................... 3-10
RRPP port configuration .................................................................................3-11
RRPP master node configuration .................................................................... 3-12
RRPP transit nodes configuration .................................................................... 3-13
RRPP intersecting rings.................................................................................. 3-14
RRPP intersecting rings subring ...................................................................... 3-15
RRPP intersecting rings subring control VLAN .................................................. 3-16

Rev. 11.11 i
Troubleshooting HP Enterprise Networks

RRPP intersecting rings L2 frame flow ............................................................. 3-17

RRPP intersecting ring configuration example................................................... 3-18
RRPP port configuration ................................................................................3-20
RRPP master node configuration .................................................................... 3-21
RRPP transit node configuration ..................................................................... 3-22
RRPP configuration edge node ...................................................................... 3-23
RRPP configuration assistant edge node .......................................................... 3-24
RRPP configuration subring master node ......................................................... 3-25
RRPP display commands ............................................................................... 3-26
Lab 3: RRPP Troubleshooting and Problem Resolution ....................................... 3-27
Lab Activity 3: Trouble Ticket 3: ..................................................................... 3-28

Module 4: BGP Troubleshooting and Problem Resolution

Objectives .................................................................................................... 4-1
Lab 4: BGP Troubleshooting and Problem Resolution ......................................... 4-2
Lab Activity 4.1: Trouble Ticket 4 ..................................................................... 4-3
Lab Activity 4.2: Trouble Ticket 5 .................................................................... 4-4

Module 5: MPLS L3VPN

Objectives .................................................................................................... 5-1
Lab 5: MPLS L3VPN Troubleshooting and Problem Resolution ..............................5-2
Lab Activity 5.2: Trouble Ticket 7 .................................................................... 5-4

Module 6: MPLS L2VPN

Objectives .................................................................................................... 6-1
Lab 6: MPLS L2VPN Troubleshooting and Problem Resolution ............................. 6-2
Lab Activity 6.1: Trouble Ticket 8 ..................................................................... 6-3
Lab Activity 6.2: Trouble Ticket 9 .................................................................... 6-5
Lab Activity 6.3: Trouble Ticket 10 .................................................................. 6-6

ii Rev. 11.11
 Troubleshooting Methodologies and Practices
Module 1

Objectives
No network or networking technology operates smoothly all of the time. Every
network technician will be required at some time to troubleshoot issues in network
configuration and performance. This module introduces basic techniques for network
troubleshooting.
After completing this module, you will be able to:
 Describe a framework for basic network troubleshooting

Rev 11.11 1 –1
Troubleshooting HP Enterprise Networks

Troubleshooting Methodology
Network troubleshooting benefits from having:
 Methodology
 A discipline for evaluating, analyzing and investigating problem conditions
 Includes determining the scope of the problem, developing a hypothesis,
testing it out, and if successful, implementing a resolution
 Skill sets
 Familiarity with network devices, how they operate and how they are
managed
 Technical tools that may be useful for investigating and verifying problems;
from CLI commands and protocol analyzers
 Good Q&A skills
 Experience
 Over time, applying a methodology and the technical tools helps develop
your own “library” of problem recognition capabilities and yields a more
efficient problem resolution process
The basics of troubleshooting any kind of networking trouble might be succinctly
stated as “keep eliminating obvious causes until the real cause presents itself.” But
understanding what this means requires a systematic approach and real discipline
when attempting to identify causes from symptoms and apply the right fixes or
workarounds.
Troubleshooting is a skill that all networking professionals learn by trial and error. But
skipping some of the more painful or obvious errors can make your learning
somewhat less trying than it might be otherwise. The most important characteristic to
cultivate when solving problems is calmness. If you can keep a clear head when
things fail or start degrading seriously, you’ll be better able to assess your situation
and better equipped to solve whatever problems you discover.

Methodology
Development of problem solving techniques is often an on-the-job acquisition
process. Few of us can expect much along the lines of formal network
troubleshooting training in our job positions for a number of reasons. These reasons
may include:
 The relatively fast pace of the day-to-day job tasks and challenges yields little
time to pursue formal training on troubleshooting aspects such as technical tools
like a protocol analyzer.

1 –2 Rev 11.11
 Troubleshooting Methodologies and Practices

 Few business environments provide the luxury of a “test lab” and the time to
hone your skills where a progression of test problems can be examined, worked
through, and resolutions tried out.
In the absence of a more ideal situation, a problem solving methodology can
increase the effectiveness of support staff by standardizing the approach used to
some extent. With a fairly modest amount of discipline, network technicians can
improve their problem resolution efficiency in terms of the effort needed and the
number of other people that must be directly involved.

Skill Sets
There are a variety of skill sets that can enhance a network technician’s success in
problem solving. Some of these skills are purely technical in nature. For instance, it is
important to understand the fundamentals of how network devices operate and how
they are managed. Having proficiency in reading logs or interpreting a protocol
analyzer display are examples of having familiarity with the potential tools you may
need to call upon from your “toolbox”.
Other skills are much less technical, but still very important. As part of the problem
investigation process, a network technician may need to talk with various levels of
staff. The staff may include non-technical end-users and business unit managers to
software and hardware vendor support people. Having sufficient interpersonal skills
coupled with good investigative reporter-like skills can expedite the isolation of a
problem and eliminate the “noise” that often conceals the real problem.
Proactive IT support groups tend to spend time on developing procedures and tools
to facilitate problem resolutions. Some examples of technical tools used by the
network technicians are:
 Device logs—Archived instances of the logs as well as the current one may
provide hints of where the problem may be. At the very least, familiarity with a
log file’s typical contents helps you differentiate normal from abnormal
situations.
 Device statistics and status information—Being able to determine the health of a
system or the network is important for gathering the “vital” signs. This type of
information can include anything from port statistics and CPU utilization to
network reachability results.
 Protocol analyzer—Although this may not be a frequently used tool, it can be
invaluable for examining what conversations are or are not occurring between
communicating devices.
A problem solving methodology that is refined over time can be very beneficial to
network technicians. Being methodical and learning from the macro and micro levels
of mistakes can help network technicians improve problem recognition capabilities
and yield a more efficient application of a problem resolution process.

Rev 11.11 1 –3
Troubleshooting HP Enterprise Networks

Problem solving methodology

1. Identification
1. Identification

2.Analysis
2. Analysis

3.3.Hypothesis
Hypothesis

4.4.Validation
Validation

5. Implementation

6.6.Verification
Verification

Figure 1-1

A problem solving methodology is a process for managing problem resolution.

Although there is no one specific model that may be useful for all problem situations,
a general framework can provide guidelines and help ensure efficiency in the efforts
made to solve a problem. Applying a methodology can improve the probability of a
successful resolution. This graphic illustrates the framework for a general problem
solving methodology that has many applications, including in today’s contemporary
network environments.
There are six steps to the problem solving methodology outlined here. The steps must
be executed in order starting with identification. The rules of the methodology state
that if a step fails, you must return to the preceding step above or possibly return to
the top level step.
The six steps are:
 Identification—Understand and document the problem from both a user and
technical perspective. Sometimes it is possible to lose sight of what the potential
problem is before searching for a cause when we don’t consider multiple
perspectives.
 Analysis—Evaluate the situation by investigating using problem resolution tools,
product documentation and user input.
 Hypothesis—Develop possible resolutions based on the analysis and document
a possible resolution. This documentation may be fairly informal, but it is
important to be able to explain it in writing. Doing so can reveal a hypothesis
that is unclear and for which a possible resolution may not be plausible.

1 –4 Rev 11.11
 Troubleshooting Methodologies and Practices

 Validation—Run a validation process to prove or disprove the hypothesis. This

may not be particularly feasible, for example, if you have no test lab equipment
to try out your hypothesis. At the very least, performing a walk-through of the
hypothesis in an articulate manner with other team members may help.
 Implementation—Develop an implementation plan along with a back-out plan,
just in case, and then implement the resolution. For example, have a backup
configuration and software image readily available.
 Verification—Verify the success or failure of the implementation. If it fails,
implement the back-out plan.

Rev 11.11 1 –5
Troubleshooting HP Enterprise Networks

Identification and analysis

Start Analysis

Identification Isolate failing

component

Understand the
environment No
Successful?

Understand the Yes

customer/user need
Review previous
problem resolutions and
Develop problem appropriate
definition documentation

Document probable
Prioritize the problem
causes

Go to Go to
Analysis step Hypothesis step

Figure 1-2

The first step of the six-step methodology is identification, which is an observation

process. Try to observe everything, not just the apparent problem, and avoid
assuming something. Because network troubleshooting primarily involves evaluating
and resolving connectivity issues, the general procedure begins with an analysis of
symptoms to determine the scope of the issue.
For example, it is important to determine whether the problem is affecting a single
host, a group of hosts, or the entire network. If many hosts are affected, determine
what they have in common. For instance, if a host can communicate with local hosts,
but not remote hosts, verify connectivity with its default gateway. If all hosts in the
same VLAN can communicate with local hosts, but not remote hosts, the issue may
be a logical problem with the default gateway or a physical problem concerning
connectivity with the default gateway. Although the default gateway performs Layer 3
forwarding on behalf of local hosts, their communication with the default gateway is
done using Layer 2 addressing.

1 –6 Rev 11.11
 Troubleshooting Methodologies and Practices

The identification process consists of doing tasks that can include:

 Documenting the physical settings. The specifics will of course vary depending
on the problem scenario, but some examples are the following:
 What client, server and network device hardware and software are in use?
 What is the network topology between the client and server?
 Where are the applications and services located? Determine the effects the
problem has on the user/customer and the business.
 Developing a problem definition—Document probable failures.
 Prioritizing the problem—Prioritize based on defined user/customer policies. Is
this a problem that must be investigated immediately or can it wait until you can
assemble a strategy using the problem solving methodology?
Step 2 is analysis. Analysis is the process of isolating the problem with the objective
to narrow down the different possibilities.
 The analysis process considers such factors as the following:
 Does the system work without the problem
 Previous changes to the system
 Something new, such as networking equipment, that may have been introduced
 Any changes to peripheral equipment that may have been made
 Whether the hardware or software is being used correctly
With the scope of the problem having been narrowed down, that can help suggest
the type of network troubleshooting tools you may want to use to test probable
causes. For example, the problem investigation may involve using simple network
reachability tools, such as traceroute or ping, or examination of the logs of multiple
switches, or even use of a protocol analyzer.

Rev 11.11 1 –7
Troubleshooting HP Enterprise Networks

Hypothesis and validation

Hypothesis Validation

Perform technical Test hypothesis

evaluation

Yes
Formulate hypothesis Validate?

Develop validation No
process Discard hypothesis

Evaluate possible side

effects
Yes
More probable
causes to
Yes validate?
More probable
causes? No
Return to Identification
No
step or go to
Go to Implementation step
Validation step

Figure 1-3

Step 3 is hypothesis. The hypothesis step involves the evaluation of the information
acquired from the analysis step to determine a number of probable causes.
Some things to keep in mind are:
 What is the technical reason for the business problem?
 You need a validation procedure for the hypothesis to be usable. Although your
intuition may prove to be correct at times, in the business world, relying on that
primarily makes it difficult for management to feel confident about the process.
 Eventual resolution of the problem could create side effects, some that are not
immediately obvious.
Validation, step 4, typically involves experimentally determining whether the
hypothesis is reasonable. It increases the confidence level that the problem will in fact
be resolved after implementation of a potential solution.

1 –8 Rev 11.11
 Troubleshooting Methodologies and Practices

The validation step involves:

 Testing each hypothesis until you validate a probable cause with a high degree
of certainty. The objective is not necessarily to be 100% sure, but to balance the
time criticality of resolving a problem with the information you have available.
 If validation fails for all probable causes you developed, then you may need to
return to the problem definition phase and start over. Despite what may appear
to be time wasted, you will likely have improved your awareness of the problem
situation and will have some additional facts to use when you attempt to
redefine the problem.

Rev 11.11 1 –9
Troubleshooting HP Enterprise Networks

Implementation and verification

Implementation Verification

Develop implementation Run implementation plan

plan

Develop verification Run verification procedure

process

Develop back-out plan No

Successful?

Yes
Schedule implementation
Any side Yes
Run back-out plan and
effects? return to identification

Go to No
Verification step
Document and distribute to
effected personnel

Figure 1-4

Implementation, step 5, requires planning for installation of some form of system or

network fix or modification along with preparation for failure. If an implementation
fails, you must be able to restore the system to a previous stable state.
The planning involves:
 Development of a specific implementation plan.
 Development of a verification process to prove the implementation was
successful.
 Development of a back-out plan to ensure the implementation can be removed, if
it fails. It should also address how to handle side effects.
Verification, step 6, is the process of proving the implementation was successful and
determining that any side effects are acceptable. If verification fails or side effects
are unacceptable, the back-out plan developed in the implementation phase is
executed.
Upon successful completion, the user or customer must be informed and the problem
resolution should be documented in a trouble log. Lack of documentation can lead to
lengthy resolution for recurring problems.

1 –10 Rev 11.11

 Troubleshooting Methodologies and Practices

Summary
 Network troubleshooting benefits from having a methodology, skill sets and
experience
 General problem solving methodology consists of six steps:
 Identification: Develop a problem statement
 Analysis: Narrow the scope
 Hypothesis: Define procedures to validate
 Validation: Test probable causes
 Implementation: Make changes with back-out plan ready
 Verification: Ensure that changes resolve problem without side effects

Rev 11.11 1 –11

Troubleshooting HP Enterprise Networks

1 –12 Rev 11.11

 Intelligent Resilient Framework
Module 2

Objectives
In this module, you will:
 Observe IRF operational failures
 Use the troubleshooting methodology to resolve these failures
The technologies used in the lab for this module include:
 IRF
 MAD
 BFD
 LACP

Rev. 11.11 2 –1
Troubleshooting HP Enterprise Networks

Lab 2: IRF Troubleshooting and Problem Resolution

Lab 2 is designed to ensure you can use a structured troubleshooting methodology to
resolve IRF routing issues. The lab consists of two trouble tickets that you will work to
resolve. Refer to your lab guide for instructions on how to do the lab.

PX-58sw1
A5800

sw

A5800
PX-58sw2

Figure 2-1: Lab 2: IRF Troubleshooting and Problem Resolution

2 –2 Rev. 11.11
 Rapid Ring Protection Protocol—Basic Concepts

RRPP single ring configuration example

Domain 1

d.
A B

ite
GE3/0/1 GE3/0/1

ib
oh
Master node GE3/0/2 GE3/0/2 Transit node

pr
Ring 1

is
n
io
GE3/0/2 GE3/0/1
Transit node Transit node

s
is
GE3/0/1 Port 2

m
D GE3/0/2 C

er
tp
ou
ith
Figure 3-7: RRPP single ring configuration example

w
rt
The tasks to configure RRPP single ring:

pa
1. Define VLANs (not shown)
i n
or
2. Defining MSTP regions
l e
ho

3. Configuring RRPP Ports

w

4. Creating an RRPP Domain on the Master

in
n

a. Configuring Control VLANs

c tio

b. Configuring Protected VLANs

du
ro

1) Configuring RRPP Rings

ep

2) RRPP Nodes
.R
ly

5. Activating an RRPP Domain

on

6. Configuring the RRPP Domain on the Transit Nodes

u se

a. Configuring Control VLANs

er
ld

b. Configuring Protected VLANs

ho

1) Configuring RRPP Rings

ake

2) RRPP Nodes
St
&L

7. Activating an RRPP Domain

C
P
H

Rev. 11.11 3 –9
 Troubleshooting HP Enterprise Networks

MSTP configuration
– All VLANs default to being in MSTI Instance 0
– Create two MSTI instances:

d.
ite
revision-level 1

ib
oh
instance 1 vlan 1 to 500

pr
instance 2 vlan 501 to 999

is
active region-configuration

n
– Assign odd VLANs to Instance 1 and even VLANS to

sio
Instance 2:

is
m
revision-level 1

er
tp
vlan-mapping modulo 2

ou
active region-configuration

ith
w
Figure 3-8: MSTP configuration

rt
pa
Defining MSTP regions:
 in
MSTP instances are assigned to a Protected VLAN.
or
The Protected VLANs are used by RRPP to define how ports are forwarded.
e


l
ho

Different RRPP domains on the same RRPP ring are configured with different
w

protected VLANs, and each RRPP domain controls the forwarding status of ports
in

in it independently. By defining different MSTP instances in separate RRPP

n
tio

domains protected VLANs, load balancing of the ring can occur.

c
du
ro
ep
.R
ly
on
u se
er
ld
ho
ake
St
&L
C
P
H

3 –10 Rev. 11.11

 Rapid Ring Protection Protocol—Basic Concepts

RRPP port configuration

– Configure the suppression time of physical-link-state changes
on Gigabit ports as zero, disable STP, configure the ports as

d.
trunk ports, and assign them to all VLANs.

ite
ib
oh
[DeviceA] interface gigabitethernet 3/0/1

pr
[DeviceA-GigabitEthernet3/0/1] link-delay 0

is
[DeviceA-GigabitEthernet3/0/1] undo stp enable

n
io
[DeviceA-GigabitEthernet3/0/1] port link-type trunk

s
is
[DeviceA-GigabitEthernet3/0/1] port trunk permit vlan all

m
er
[DeviceA-GigabitEthernet3/0/1] quit

tp
ou
Figure 3-9: RRPP port configuration

ith
Configuring RRPP Ports requires that spanning tree on the port be disabled and the

w
rt
port support VLANs required, data and control.

pa
The ports can be configured as:
i n
or
 Trunk
le

Bridge-Aggregation
ho


w

 Must be Ethernet
in

The ports cannot be configured as:

n
tio

802.1X authentication
c


du

MAC address authentication

ro


ep

 Voice VLAN
.R

Remote Loopback
ly


on

 Spanning Tree
se

Access
u


er
ld
ho
ake
St
&L
C
P
H

Rev. 11.11 3 –11

 Troubleshooting HP Enterprise Networks

RRPP master node configuration

– Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of
RRPP domain 1, and configure the VLANs mapped to MSTIs 0 through 47 as the
protected VLANs of RRPP domain 1.

d.
ite
[DeviceA] rrpp domain 1

ib
[DeviceA-rrpp-domain1] control-vlan 4092

oh
[DeviceA-rrpp-domain1] protected-vlan reference-instance 0 to 47
– Configure Device A as the master node of primary ring 1, with Gigabit 3/0/1

pr
as the primary port & Gigabit 3/0/2 as the secondary port, and enable ring 1.

is
[DeviceA-rrpp-domain1] ring 1 node-mode master primary-port

n
io
gigabit 3/0/1 secondary-port gigabit 3/0/2 level 0

s
[DeviceA-rrpp-domain1] ring 1 enable

is
m
[DeviceA-rrpp-domain1] quit

er
– Enable RRPP.

tp
[DeviceA] rrpp enable

ou
ith
w
rt
Figure 3-10: RRPP master node configuration

pa
Creating an RRPP Domain on the Master Node: in
or
Configuring Control VLANs
e


l
ho

 Configuring Protected VLANs

w
in

 Configuring RRPP Rings

n
tio

 RRPP Nodes
c
du

Activating an RRPP Domain:

ro

All the work conducted in prior tasks is brought together to configure the RRPP
ep

domain and define its operation. Activation of the ring and RRPP generate the RRPP
.R

PDUs.
ly
on
u se
er
ld
ho
ake
St
&L
C
P
H

3 –12 Rev. 11.11

 Rapid Ring Protection Protocol—Basic Concepts

RRPP transit nodes configuration

– Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of
RRPP domain 1, and configure the VLANs mapped to MSTIs 0 through 47 as the
protected VLANs of RRPP domain 1.

d.
ite
[DeviceB] rrpp domain 1

ib
[DeviceB-rrpp-domain1] control-vlan 4092

oh
[DeviceB-rrpp-domain1] protected-vlan reference-instance 0 to 47

pr
– Configure Device B as the transit node of primary ring 1, with GigabitEthernet
3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port,

is
and enable ring 1.

n
io
[DeviceB-rrpp-domain1] ring 1 node-mode transit primary-port

s
gigabitethernet 3/0/1 secondary-port gigabitethernet 3/0/2 level

is
0

m
[DeviceB-rrpp-domain1] ring 1 enable

er
tp
[DeviceB-rrpp-domain1] quit
– Enable RRPP.

ou
ith
[DeviceB] rrpp enable

w
rt
Figure 3-11: RRPP transit nodes configuration

pa
Configuring an RRPP Domain on the Transit Node:
in
or
 Configuring Control VLANs
le
ho

 Configuring Protected VLANs

w

 Configuring RRPP Rings

in
n

 RRPP Nodes
ctio

Activating the RRPP Domain:

du
ro

The key difference between configuring a Master node and a Transit node is the
ep

definition of the node-mode:

.R

Master
ly


on

 Transit
use
er
ld
ho
ake
St
&L
C
P
H

Rev. 11.11 3 –13

 Troubleshooting HP Enterprise Networks

RRPP intersecting rings

RRPP domain Domain 1

Edge node

d.
A B

ite
Port 1 Port 1

ib
Master node

oh
Master node Port 2 Port 2

pr
Ring 1 Ring 2

is
n
Port 2 Port 1

io
Transit node

s
is
Port 1 Port 2

m
D C

er
Assistant edge node
RRPP ring 1=

tp
RRPP ring 2=
Master ring= Sub ring=

ou
Ring level 0 Ring level 1

ith
Figure 3-12: RRPP intersecting rings

w
rt
pa
In the RRPP intersecting rings many of the same requirements as the single ring. As in
the Single ring, the domain is identified by an Index number that identifies its
i n
or
configuration and RRPP PDUs. The master node generates the HELLO RRPP PDUs to
e

maintain ring state and forwards them out its Primary Port. The transit nodes receive
l
ho

and forward the HELLO to the next switch until it is received by the Master’s
w

Secondary Port, which will block Data Frames, but not Control Frames - RRPP PDUs.
in
n
c tio
du
ro
ep
.R
ly
on
u se
er
ld
ho
ake
St
&L
C
P
H

3 –14 Rev. 11.11

 Rapid Ring Protection Protocol—Basic Concepts

RRPP intersecting rings subring

Edge node:
Belongs to primary
Domain 1 and subrings

d.
ite
A B Edge node

ib
Port 1 Port 1

oh
Master node

pr
Master node Port 2 Port 2

is
E
Ring 1 Ring 2

n
io
s
Port 2 Port 1

is
Transit node

m
Port 2

er
Port 1
D C

tp
Assistant edge node

ou
Assistant edge node:

ith
Belongs to primary
and subrings

w
rt
Figure 3-13: RRPP intersecting rings subring

pa
n
In addition, the subring (secondary ring) has specific requirements for its RRPP PDUs
i
or
to flow around the subring and is attached to the primary ring via edge node and
e

assistant edge node off the primary ring’s transit nodes.

l
ho
w
in
n
c tio
du
ro
ep
.R
ly
on
use
er
ld
ho
ake
St
&L
C
P
H

Rev. 11.11 3 –15

 Troubleshooting HP Enterprise Networks

RRPP intersecting rings subring control VLAN

Control VLAN: Domain 1
Dedicated to

d.
transferring RRPPDUs A B Edge node

ite
Port 1 Port 1

ib
Master node

oh
Master node Port 2 Port 2

pr
E
Ring 1 Ring 2

is
n
io
Port 2 Port 1 Secondary control
Transit node

s
VLAN: Acts as control

is
VLAN on all subrings

m
Port 1 Port 2
D C

er
Data VLAN: Dedicated Assistant edge node

tp
to transferring data
packets

ou
ith
Figure 3-14: RRPP intersecting rings subring control VLAN

w
rt
pa
Subring Level 1 RRPP PDUs flow in their own control VLAN which is defined as the
primary rings VLAN + 1.
i n
or
l e
ho
w
in
n
c tio
du
ro
ep
.R
ly
on
u se
er
ld
ho
ake
St
&L
C
P
H

3 –16 Rev. 11.11

 Rapid Ring Protection Protocol—Basic Concepts

RRPP intersecting rings L2 frame flow

Domain 1

d.
A B

ite
Port 1 Port 1
Edge node
Port 3

ib
Master node

oh
Master node Port 2 Port 2

pr
E
Ring 1 Ring 2

is
n
io
Port 2 Port 1
Transit node

s
Edge ports:

is
Port 3
Connect edge nodes

m
Port 1 Port 2
C
D to the subring

er
tp
Common ports: Assistant edge node
Connect edge nodes

ou
to the primary ring Data packets

ith
Loop detect packets

w
Figure 3-15: RRPP intersecting rings L2 frame flow

rt
pa
The Primary’s Master Node control Frames flow around both rings, where as the
n
subring’s master node control frames only reside in its control VLAN which is kept to
i
or
the devices in the subring.
l e
ho
w
in
n
ctio
du
ro
ep
.R
ly
on
use
er
ld
ho
ake
St
&L
C
P
H

Rev. 11.11 3 –17

 Troubleshooting HP Enterprise Networks

RRPP intersecting ring configuration example

Domain 1

d.
ite
A B Edge node
GE3/0/1 GE3/0/1

ib
oh
GE3/0/3
Master node
GE3/0/2 GE3/0/2 GE3/0/1

pr
Master node
E

is
Ring 1 Ring 2

n
GE3/0/2

io
GE3/0/1

s
GE3/0/2
Transit node

is
GE3/0/3

m
GE3/0/2

er
D GE3/0/1 C

tp
Assistant edge node

ou
ith
w
Figure 3-16: RRPP intersecting ring configuration example

rt
pa
To configure RRPP, the domain defines how RRPP PDU’s will operate. This example

n
actually includes two rings—a main ring, or a primary ring, which is labeled as ring
i
or
1, and a secondary ring, which is labeled as ring 2.
l e

The primary ring dictates the control VLAN that will be used to send the RRPP PDUs
ho

from the Master to maintain the ring. The secondary ring has its own master with its
w
in

own RRPP PDUs that will flow in a control VLAN that is 1 higher than the control
n

VLAN defined in the primary ring.

c tio

The primary ring has four interconnected switches. The devices are interconnected
du

from port to port on the ring. A Master node is defined on the ring and all other
ro

nodes become Transit. For the secondary ring to attach to the primary ring it is
ep

connected at two Transit switches on the primary ring, defined as edge node and an
.R

assistant edge node.

ly
on

Notice that ring 2 is connected to two of the switches that are on the primary ring.
se

Those switches are referred to as edge node and assistant edge node. The primary
u

ring is called a level 0 ring, and the secondary ring is a level 1 ring. All level 1
er

rings, secondary rings, must connect to the Primary ring on edge and assistant edge
ld
ho

nodes.
ke

1. Define VLANs (not shown)

a
St

2. Defining MSTP regions

&L

3. Configuring RRPP Ports

C
P
H

3 –18 Rev. 11.11

 Rapid Ring Protection Protocol—Basic Concepts

4. Creating an RRPP Domain on the Master

a. Configuring Control VLANs
b. Configuring Protected VLANs

d.
1) Configuring RRPP Rings

ite
2) RRPP Nodes

ib
oh
c. Activating an RRPP Domain

pr
5. Configuring the RRPP Domain on the Transit Nodes

is
n
io
a. Configuring Control VLANs

s
is
b. Configuring Protected VLANs

m
er
1) Configuring RRPP Rings

tp
ou
2) RRPP Nodes

ith
c. Activating an RRPP Domain

w
rt
6. Configure Edge Node

pa
a. Configuring RRPP Rings
i n
or
b. RRPP Nodes
l e

7. Configure Assistant Edge Node

ho
w

a. Configuring RRPP Rings

in

b. RRPP Nodes
n
tio

8. Configure Subring Master Node

c
du

a. Configuring RRPP Rings

ro
ep

b. RRPP Nodes
.R
ly
on
u se
er
ld
ho
ake
St
&L
C
P
H

Rev. 11.11 3 –19

 Troubleshooting HP Enterprise Networks

RRPP port configuration

– Configure the suppression time of physical-link-state changes
on Gigabit ports as zero, disable STP, configure the ports as

d.
trunk ports, and assign them to all VLANs.

ite
ib
[DeviceA] interface gigabitethernet 3/0/1

oh
pr
[DeviceA-GigabitEthernet3/0/1] link-delay 0

is
[DeviceA-GigabitEthernet3/0/1] undo stp enable

n
io
[DeviceA-GigabitEthernet3/0/1] port link-type trunk

s
is
[DeviceA-GigabitEthernet3/0/1] port trunk permit

m
er
vlan all

tp
[DeviceA-GigabitEthernet3/0/1] quit

ou
ith
Figure 3-17: RRPP port configuration

w
rt
Same configuration as done for Single Ring.

pa
in
or
le
ho
w
in
n
ctio
du
ro
ep
.R
ly
on
u se
er
ld
ho
ake
St
&L
C
P
H

3 –20 Rev. 11.11

 Rapid Ring Protection Protocol—Basic Concepts

RRPP master node configuration

– Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of
RRPP domain 1, and configure the VLANs mapped to MSTIs 0 through 47 as the
protected VLANs of RRPP domain 1.

d.
ite
[DeviceA] rrpp domain 1

ib
[DeviceA-rrpp-domain1] control-vlan 4092

oh
[DeviceA-rrpp-domain1] protected-vlan reference-instance 0 to 47

pr
– Configure Device A as the master node of primary ring 1, with Gigabit 3/0/1 as
the primary port & Gigabit 3/0/2 as the secondary port, and enable ring 1.

is
n
[DeviceA-rrpp-domain1] ring 1 node-mode master primary-port

io
gigabit 3/0/1 secondary-port gigabit 3/0/2 level 0

s
[DeviceA-rrpp-domain1] ring 1 enable

is
m
[DeviceA-rrpp-domain1] quit

er
– Enable RRPP.

tp
[DeviceA] rrpp enable

ou
ith
w
Figure 3-18: RRPP master node configuration

rt
pa
Same configuration as done for Single Ring.
i n
or
le
ho
w
in
n
ctio
du
ro
ep
.R
ly
on
use
er
ld
ho
ake
St
&L
C
P
H

Rev. 11.11 3 –21

 Troubleshooting HP Enterprise Networks

RRPP transit node configuration

– Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of
RRPP domain 1, and configure the VLANs mapped to MSTIs 0 through 47 as

d.
the protected VLANs of RRPP domain 1.

ite
[DeviceB] rrpp domain 1

ib
[DeviceB-rrpp-domain1] control-vlan 4092

oh
[DeviceB-rrpp-domain1] protected-vlan reference-instance 0 to 47

pr
– Configure Device B as the transit node of primary ring 1, with GigabitEthernet

is
3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port, and

n
enable ring 1.

io
[DeviceB-rrpp-domain1] ring 1 node-mode transit primary-port

s
is
gigabitethernet 3/0/1 secondary-port gigabitethernet 3/0/2 level 0

m
[DeviceB-rrpp-domain1] ring 1 enable

er
[DeviceB-rrpp-domain1] quit

tp
– Enable RRPP.

ou
[DeviceB] rrpp enable

ith
w
rt
Figure 3-19: RRPP transit node configuration

pa
n
Same configuration as done for Single Ring.
i
or
l e
ho
w
in
n
c tio
du
ro
ep
.R
ly
on
u se
er
ld
ho
ake
St
&L
C
P
H

3 –22 Rev. 11.11

 Rapid Ring Protection Protocol—Basic Concepts

RRPP configuration edge node

– Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and
configure the VLANs mapped to MSTIs 0 through 47 as the protected VLANs of RRPP domain 1.

d.
[DeviceB] rrpp domain 1

ite
[DeviceB-rrpp-domain1] control-vlan 4092

ib
[DeviceB-rrpp-domain1] protected-vlan reference-instance 0 to 47

oh
– Configure Device B as a transit node of primary ring 1, with Gigabit 3/0/1 as the primary port and
Gigabit 3/0/2 as the secondary port, and enable ring 1.

pr
[DeviceB-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet

is
3/0/1

n
secondary-port gigabitethernet 3/0/2 level 0

io
[DeviceB-rrpp-domain1] ring 1 enable

s
– Configure Device B as the edge node of subring 2, with GigabitEthernet 3/0/3 as the edge port,

is
and enable ring 2.

m
er
[DeviceB-rrpp-domain1] ring 2 node-mode edge edge-port gigabitethernet 3/0/3

tp
[DeviceB-rrpp-domain1] ring 2 enable

ou
[DeviceB-rrpp-domain1] quit
– Enable RRPP.

ith
[DeviceB] rrpp enable

w
rt
pa
Figure 3-20: RRPP configuration edge node

i n
For the Edge Node configuration, the switch is configured as a Transit node as in a
or
Single ring but a subring configuration is entered and the port that is handling the
l e
ho

secondary ring leading to subring Master node is configured as EDGE.

w
in
n
c tio
du
ro
ep
.R
ly
on
use
er
ld
ho
ake
St
&L
C
P
H

Rev. 11.11 3 –23

 Troubleshooting HP Enterprise Networks

RRPP configuration assistant edge node

– Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and
configure the VLANs mapped to MSTIs 0 through 47 as the protected VLANs of RRPP domain 1.
[DeviceB] rrpp domain 1

d.
[DeviceB-rrpp-domain1] control-vlan 4092

ite
[DeviceB-rrpp-domain1] protected-vlan reference-instance 0 to 47

ib
– Configure Device B as a transit node of primary ring 1, with Gigabit 3/0/1 as the primary port and

oh
Gigabit 3/0/2 as the secondary port, and enable ring 1.

pr
[DeviceB-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet
3/0/1

is
secondary-port gigabitethernet 3/0/2 level 0

n
[DeviceB-rrpp-domain1] ring 1 enable

io
– Configure Device B as the edge node of subring 2, with GigabitEthernet 3/0/3 as the edge port,
and enable ring 2.

s
is
[DeviceB-rrpp-domain1] ring 2 node-mode assistant-edge edge-port

m
gigabitethernet 3/0/3

er
[DeviceB-rrpp-domain1] ring 2 enable

tp
[DeviceB-rrpp-domain1] quit
– Enable RRPP.

ou
[DeviceB] rrpp enable

ith
w
rt
pa
Figure 3-21: RRPP configuration assistant edge node

n
For the Assistant Edge Node configuration, the switch is configured as a Transit node
i
or
as in a Single ring but a subring configuration is entered and the port that is
l e

handling the secondary ring leading to subring Master node is configured as

ho

ASSISTANT EDGE.
w
in
n
c tio
du
ro
ep
.R
ly
on
u se
er
ld
ho
ake
St
&L
C
P
H

3 –24 Rev. 11.11

 Rapid Ring Protection Protocol—Basic Concepts

RRPP configuration subring master node

– Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of
RRPP domain 1, and configure VLANs mapped to MSTIs 0 through 47 as the
protected VLANs of RRPP domain 1.

d.
ite
[DeviceE] rrpp domain 1

ib
[DeviceE-rrpp-domain1] control-vlan 4092

oh
[DeviceE-rrpp-domain1] protected-vlan reference-instance 0 to 47
– Configure Device E as the master node of subring 2, with GigabitEthernet 3/0/1

pr
as the primary port and GigabitEthernet 3/0/2 as the secondary port, and

is
enable ring 2.

n
io
[DeviceE-rrpp-domain1] ring 2 node-mode master primary-port
gigabitethernet 3/0/1 secondary-port gigabitethernet 3/0/2 level 1

s
is
[DeviceE-rrpp-domain1] ring 2 enable

m
[DeviceE-rrpp-domain1] quit

er
– Enable RRPP.

tp
ou
[DeviceE] rrpp enable

ith
w
Figure 3-22: RRPP configuration subring master node

rt
pa
The subring Master node handles the HELLO RRPP PDUs for its subring and has
primary and secondary ports defined. in
or
le
ho
w
in
n
c tio
du
ro
ep
.R
ly
on
use
er
ld
ho
ake
St
&L
C
P
H

Rev. 11.11 3 –25

 Troubleshooting HP Enterprise Networks

RRPP display commands

– Display brief information about RRPP configuration
display rrpp brief

d.
ite
– Display detailed information about RRPP configuration

ib
oh
display rrpp verbose domain domain-id [ ring ring-id ]

pr
– Display RRPP statistics

is
display rrpp statistics domain domain-id [ ring ring-id ]

n
io
– Clear RRPP statistics

s
is
reset rrpp statistics domain domain-id [ ring ring-id ]

m
er
tp
Figure 3-23: RRPP display commands

ou
ith
The display commands are mainly useful on the Master Node(s) to determine state of

w
the ring. The Transit nodes will show their configuration but be blank on ring status

rt
pa
for there is no state mechanism in RRPP.

in
or
le
ho
w
in
n
ctio
du
ro
ep
.R
ly
on
u se
er
ld
ho
ake
St
&L
C
P
H

3 –26 Rev. 11.11

 Rapid Ring Protection Protocol—Basic Concepts

Lab 3: RRPP Troubleshooting and Problem Resolution

Lab 3 is designed to ensure you can use a structured troubleshooting methodology to
resolve RRPP issues. There is one trouble ticket in this lab. Refer to your lab guide for

d.
more instructions.

ite
ib
PX-58sw1 PY-58sw2

oh
A5800 A5800

pr
is
n
s io
PX-75sw PY-75sw

is
Ring 1

m
A7503 Ring 2 Ring 3 A7503

er
tp
ou
ith
w
rt
pa
A5800 A5800
PX-58sw2 n
PY-58sw1
i
or
le

Figure 3-24: Lab 3: RRPP Troubleshooting and Problem Resolution

ho
w
in
n
c tio
du
ro
ep
.R
ly
on
use
er
ld
ho
ake
St
&L
C
P
H

Rev. 11.11 3 –27

 Troubleshooting HP Enterprise Networks

Lab Activity 3: Trouble Ticket 3:

In Lab Activity 3, you will work to resolve the issue outlined in Trouble Ticket 3:

d.
ite
ib
oh
pr
is
n
sio
is
m
er
tp
ou
ith
w
rt
pa
i n
or
l e
ho
w
in
n
c tio
du

Figure 3-25: Lab Activity 3: Trouble Ticket 3:

ro
ep
.R
ly
on
u se
er
ld
ho
ake
St
&L
C
P
H

3 –28 Rev. 11.11

 BGP Troubleshooting
and Problem Resolution
Module 4

d.
ite
ib
oh
Objectives

pr
is
In this module, you will:

n
io
 Observe BGP operational failures

s
is
Use the troubleshooting methodology to resolve these failures

m


er
The technologies used in the lab for this module include:

tp
ou
 BGP

ith
Internal BGP

w


rt
External BGP

pa


BGP filtering
n

i
or
le
ho
w
in
n
c tio
du
ro
ep
.R
ly
on
use
er
ld
ho
ake
St
&L
C
P
H

Rev. 11.11 4 –1
 Troubleshooting HP Enterprise Networks

Lab 4: BGP Troubleshooting and Problem Resolution

Lab 4.1 is designed to ensure you can use a structured troubleshooting methodology
to resolve BGP issues. The lab consists of one trouble ticket that you will work to

d.
resolve. Refer to your Lab Guide for instructions on how to do the lab.

ite
ib
oh
pr
is
n
s io
is
m
er
tp
ou
ith
w
rt
pa
in
or
le
ho

Figure 4-1: Lab 4.1 topology: Network to troubleshoot with pod peer
w
in
n
c tio
du
ro
ep
.R
ly
on
u se
er
ld
ho
ake
St
&L
C
P
H

4 –2 Rev. 11.11
 BGP Troubleshooting and Problem Resolution

Lab Activity 4.1: Trouble Ticket 4

In Lab Activity 4.1, you will use the troubleshooting methodology introduced in
Module 1 to resolve the problem outlined in Trouble Ticket 6.

d.
ite
ib
oh
pr
is
n
sio
is
m
er
tp
ou
ith
w
rt
pa
i n
or
l e
ho
w
in
n
c tio
du
ro
ep
.R
ly

Figure 4-2: Lab Activity 4.1: Trouble Ticket 4

on
use
er
ld
ho
ake
St
&L
C
P
H

Rev. 11.11 4 –3
Troubleshooting HP Enterprise Networks

Lab Activity 4.2: Trouble Ticket 5

In Lab Activity 4.2, you will try to resolve the issue outlined in Trouble Ticket 5:

Figure 4-3: Lab Activity 4.2: Trouble Ticket 5

4 –4 Rev. 11.11
 MPLS L3VPN
Module 5

Objectives
In this module, you will:
 Observe MPLS L3VPN operational failures
 Use the troubleshooting methodology to resolve these failures
The technologies used in the lab for this module include:
 MultiProtocol Label Switching (MPLS)
 Label Distribution Protocol (LDP)
 Import routes
 MultiProtocol Border Gateway Protocol (MP-BGP)

Rev 11.11 5 –1
Troubleshooting HP Enterprise Networks

Lab 5: MPLS L3VPN Troubleshooting and Problem

Resolution
Lab 5 is designed to ensure you can use a structured troubleshooting methodology to
resolve MPLS L3VPN issues. There are two trouble tickets in this lab. Refer to your lab
guide for instructions on how to complete this lab.

RIP RIP
CE-1K CE-2K
A5800 A5800

BGP AS65100
PEX PEY
A7503 P1 P2 A7503

OSPF A7506 A7506 OSPF

CE-1T CE-2T
A5800 A5800

Figure 5-1: Lab 5: MPLS L3VPN Troubleshooting and Problem Resolution

g
The figure below shows the complete topology for Lab 5.

BGP CE-2A
CE-1A AS65100

CE-1B PE1 PE2 CE-2B

PE3 CE-2C
CE-1C PE4
P1 P2 CE-2D
CE-1D
PE5 PE6 CE-2E
CE-1E
CE-2F
CE-1F

CE-2G
CE-1G
PE7 PE8 CE-2H
CE-1H

Figure 5-2: Lab 5 topology

5 –2 Rev 11.11
 MPLS L3VPN

Lab Activity 5.1: Trouble Ticket 6

In Lab Activity 5.1, you will use the troubleshooting methodology introduced in
Module 1 to resolve the problem outlined in Trouble Ticket 6.

MASE Troubleshooting Trouble Ticket

Time Received: 1054 GMT
Ticket Number: 2011‐769234 Date Received: 10‐Mar‐11
Assigned to: Alison/1018 Time Closed:
Priority: HIGH Date Closed:

Customer Name: Slate Quarry Communications

Contact Name: Fred Jetson
Contact Phone: +61 03 7010 5000
Contact eMail: [email protected]

Trouble Site or
Melbourne, Victoria, Australia
Location:

Brief Problem Slate Quarry Communications (SQC) attempting to transition to be an MPLS provider, and
Description: unable to set up basic MPLS

Problem History: 10‐Mar‐11: MPLS configured and enabled on all devices in SQC network, but no packets
being label‐switched

Figure 5-2: Lab Activity 5.1: Trouble Ticket 6

Rev 11.11 5 –3
Troubleshooting HP Enterprise Networks

Lab Activity 5.2: Trouble Ticket 7

In Lab Activity 5.2, you will try to resolve the problem outlined in Trouble Ticket 7.

MASE Troubleshooting Trouble Ticket

Time Received: 1348 GMT
Ticket Number: 2011‐769599 Date Received: 13‐Mar‐11
Assigned to: Joshua/0918 Time Closed:
Priority: HIGH Date Closed:

Customer Name: Slate Quarry Communications

Contact Name: Fred Jetson
Contact Phone: +61 03 7010 5000
Contact eMail: [email protected]

Trouble Site or
Melbourne, Victoria, Australia
Location:

Brief Problem See resolved Ticket 2011‐769234. Even though MPLS seems to be working, customer
Description: connectivity not occurring.

Problem History: 13‐Mar‐11: Discovered that customer routes are visible in the local PE router in the
correct customer‐specific vpn‐instance routing tables, and being advertised via Multi‐
Protocol BGP (MP‐BGP) to remote PE routers, yet not present in remote PE router
customer‐specific vpn‐instance routing tables.

14‐Mar‐11: Further discovered that even for routes that are present in customer‐specific
vpn‐instance routing tables, they do not appear in the customer device routing tables.
command hop by hop, discovered that there is no end‐to‐end Label‐Switched Path (LSP)
between PE routers, even though IP reachability (verified via ping and tracert) is in place
end‐to‐end.

Figure 5-3: Lab Activity 5.2: Trouble Ticket 7

5 –4 Rev 11.11
 MPLS L2VPN
Module 6

Objectives
In this module, you will:
 Observe MPLS L2VPN operational failures
 Use the troubleshooting methodology to resolve these failures
The technologies used in the lab for this module include:
 MultiProtocol Label Switching (MPLS)
 Label Distribution Protocol (LDP)
 Remote LDP
 Layer 2 Virtual Private Network (L2VPN)
 Virtual Private LAN Service (VPLS)

Rev 11.11 6 –1
Troubleshooting HP Enterprise Networks

Lab 6: MPLS L2VPN Troubleshooting and Problem

Resolution
Lab 6 is designed to ensure you can use a structured troubleshooting methodology to
resolve MPLS L2VPN issues. There are three trouble tickets in this lab. Refer to your
lab guide for instructions on how to complete this lab.
Figure 6-1 shows the complete topology for Lab 6.

CE-2A
CE-1A

CE-1B PE1 PE2 CE-2B

OSPF
Area 0
PE3 CE-2C
CE-1C PE4
P1 P2 CE-2D
CE-1D
PE5 PE6 CE-2E
CE-1E
CE-2F
CE-1F

CE-1G CE-2G

PE7 PE8 CE-2H

CE-1H
4 Rev. 11.11

Figure 6-1: Lab 6: MPLS L2VPN Troubleshooting and Problem Resolution

For Lab Activity 6.1, you will use the configuration shown below.

RIP
CE-1K CE-2K
A5800 A5800
L2VC # 1

PEX OSPF PEY

A7503 P1 P2 A7503

A7506 A7506

L2VC # 2
CE-1T CE-2T
A5800 OSPF A5800

Figure 6-2: Configuration for Lab Activity 6.1

6 –2 Rev 11.11
 MPLS L2VPN

Lab Activity 6.1: Trouble Ticket 8

Lab 6.1 is based on Trouble Ticket 8.

MASE Troubleshooting Trouble Ticket

Time Received: 1537 GMT
Ticket Number: 2011‐789166 Date Received: 31‐May‐11
Assigned to: Nelson/6987 Time Closed:
Priority: HIGH Date Closed:

Customer Name: BirdTime Inc.

Contact Name: Morris Rogers
Contact Phone: +1 612 777 9311
Contact eMail: [email protected]

Trouble Site or
Minneapolis, MN, USA
Location:

Brief Problem
Linked datacenters in Minneapolis and St. Paul not communicating
Description:

Problem History: 31‐May‐11: Customer is attempting to link data centers via two Martini L2VPNs over their
network core.

31‐May‐11: Remote LDP peer sessions are configured, but don't seem to be established.

31‐May‐11: The Layer 2 Virtual Circuits (l2vc) have been configured but are in a "down"
state.

Figure 6-3: Lab Activity 6.1: Trouble Ticket 8

Rev 11.11 6 –3
Troubleshooting HP Enterprise Networks

Configuration for Lab Activities 6.2 and 6.3

CE-1K RIP CE-2K
A5800 A5800
VPN1

PEX BGP AS65100 PEY

A7503 P1 P2 A7503

A7506 A7506

VPN2 RIP
VPN3 OSPF
CE-1T CE-2T
A5800 A5800

Figure 6-4: Configuration for Lab Activities 6.2 and 6.3

As this figure shows, you will use a different configuration to complete Lab Activities
6.2 and 6.3. Before you begin reading the trouble tickets for these activities, you
may want to note the main differences between this configuration and the one you
used for Lab Activity 6.1 in the space provided below.
_________________________________________________________________________

_________________________________________________________________________

_________________________________________________________________________

_________________________________________________________________________

_________________________________________________________________________

_________________________________________________________________________

_________________________________________________________________________

_________________________________________________________________________

_________________________________________________________________________

6 –4 Rev 11.11
 MPLS L2VPN

Lab Activity 6.2: Trouble Ticket 9

Lab 6.2 is based on Trouble Ticket 9—MPLS L2VPN:

MASE Troubleshooting Trouble Ticket

Time Received: 1108 GMT
Ticket Number: 2011‐612098 Date Received: 25‐Feb‐11
Assigned to: Oscar/9050 Time Closed:
Priority: High Date Closed:

Customer Name: Fester Manufacturing

Contact Name: Herman Addams
Contact Phone: +40 264 565 000
Contact eMail: [email protected]

Trouble Site or
Cluj‐Napoca, Romania
Location:

Brief Problem
Linked Datacenters in Cluj‐Napoca and Sibiu not communicating
Description:

Problem History: 25‐Feb‐11: Customer is attempting to link Data Centers via Kompella L2VPN connections
over their network core.

25‐Feb‐11: The MPLS L2VPN configuration on the PE routers seems to be correct, but the
connection vpn1 (from CE‐1K to CE‐2K) shows as down.

Figure 6-5: Lab Activity 6.2: Trouble Ticket 9 9

Rev 11.11 6 –5
Troubleshooting HP Enterprise Networks

Lab Activity 6.3: Trouble Ticket 10

Lab 6.3 is based on Trouble Ticket 10—MPLS L2VPN.

MASE Troubleshooting Trouble Ticket

Time Received: 1108 GMT
Ticket Number: 2011‐612098‐2 Date Received: 27‐Feb‐11
Assigned to: Oscar/9050 Time Closed:
Priority: High Date Closed:

Customer Name: Fester Manufacturing

Contact Name: Herman Addams
Contact Phone: +40 264 565 000
Contact eMail: [email protected]

Trouble Site or
Cluj‐Napoca, Romania
Location:

Brief Problem A follow‐up to Ticket# 2011‐612098 ‐ Customer trying to connect a 2nd pair of Data Centers
Description: over L2VPN

Problem History: 27‐Feb‐11: Though PE routers show L2VPN connection "vpn2" as up, devices attached to CE‐
1T and CE‐2T (as well as the CE devices themselves) are unable to communicate with one
another via subnet 10.YX.100.0/24 (X and Y correspond to the pods of the students working
together, X=odd, Y=even: A=1, B=2, C=3, D=4, etc.).

28‐Feb‐11: Further discovered that L2VPN connection "vpn3" which should connect subnet
10.YX.200.0/24 from CE‐1T and CE‐2T is also not working (connection status is down).

Figure 6-6: Lab Activity 6.3: Trouble Ticket 10 10

6 –6 Rev 11.11
 To learn more about HP networking, visit
www.hp.com/networking
© 2010 Hewlett-Packard Development Company, L.P. The information contained herein is
subject to change without notice. The only warranties for HP products and services are set forth
in the express warranty statements accompanying such products and services. Nothing herein
should be construed as constituting an additional warranty. HP shall not be liable for technical
or editorial errors or omissions contained herein.