You are on page 1of 103

BitSpyder - The Culture of Knowledge

BitSpyder - The Culture of Knowledge

Accelerated Interoperability and Troubleshooting HP Networks


Part 2: Troubleshooting HP Networks
Rev. 11.31 - Course #: 00314282
Part Number: 00314282L21104 - Book 2 of 2

Lab guide
HP Partner Learning
BitSpyder - The Culture of Knowledge

 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 Interoperability and Troubleshooting HP Networks – v11.31
Lab guide – Book 2 of 2
April 2011
HP Restricted
BitSpyder - The Culture of Knowledge

Contents
Module 3: Layer 2 Troubleshooting and Problem Resolution ..................Module 3 - 1
Objectives ................................................................................Module 3 - 1
Outline ....................................................................................Module 3 - 2
Lab 4 equipment .......................................................................Module 3 - 3
Your trouble ticket assignment .....................................................Module 3 - 5
Step 1 – Identification .............................................................. Module 3 - 11
Step 2 – Analysis .................................................................... Module 3 - 12
Step 3 – Hypothesis ................................................................ Module 3 - 13
Step 4 – Validation ................................................................. Module 3 - 15
Useful CLI commands .............................................................. Module 3 - 16
Module 4: Layer 3 Troubleshooting and Problem Resolution ..................Module 4 - 1
Objectives ................................................................................Module 4 - 1
Outline ....................................................................................Module 4 - 2
Lab 5: Scenarios and Practice with Layer 3 Tools ..........................Module 4 - 3
Lab 5.1 ....................................................................................Module 4 - 4
Lab 5.2 ....................................................................................Module 4 - 7
Lab 5.3 .................................................................................. Module 4 - 11
Lab 6: Troubleshooting Routing Protocol Issues ............................ Module 4 - 15
Lab 7: Addressing Issues .......................................................... Module 4 - 22
Lab 4: VLAN Routing Issues ...................................................... Module 4 - 28
Module 5: Layer 4 Troubleshooting and Problem Resolution ..................Module 5 - 1
Objectives ................................................................................Module 5 - 1
Outline ....................................................................................Module 5 - 2
Lab 9 equipment .......................................................................Module 5 - 3
Your trouble ticket assignment .....................................................Module 5 - 5
Step 1 – Identification ................................................................Module 5 - 6
Step 2 – Analysis ......................................................................Module 5 - 7
Step 3 – Hypothesis ................................................................ Module 5 - 10
Step 4 – Validation ................................................................. Module 5 - 11
Step 5 – Implementation .......................................................... Module 5 - 13
Step 6 – Verification ................................................................ Module 5 - 15
Module 6: Layer 5 Troubleshooting and Problem Resolution ..................Module 6 - 1
Objectives ................................................................................Module 6 - 1
Outline ....................................................................................Module 6 - 2
Lab equipment ..........................................................................Module 6 - 3
Your trouble ticket assignment .....................................................Module 6 - 5
Step 1 – Identification ................................................................Module 6 - 6
Step 2 – Analysis ......................................................................Module 6 - 7
Step 3 – Hypothesis ................................................................ Module 6 - 10
Step 4 – Validation ................................................................. Module 6 - 12
Step 5 – Implementation .......................................................... Module 6 - 14
Step 6 – Verification ................................................................ Module 6 - 16
Module 7: Troubleshooting a Complex Integrated MultiProtocol Network Module 7 - 1
Objectives ................................................................................Module 7 - 1
Lab Objective ...........................................................................Module 7 - 2
Rev 10.41 i
BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Lab configuration ......................................................................Module 7 - 3


Your trouble ticket assignment .....................................................Module 7 - 4

ii Rev 10.41
BitSpyder - The Culture of Knowledge

Layer 2 Troubleshooting and Problem Resolution


Module 3 – Lab Guide

Objectives
This lab introduces you to the HP equipment that you will be working on throughout
this course and assigns you real-life troubleshooting tickets for you to solve. You will
use the knowledge you acquired in your ASE Network Infrastructure certification
training track and apply the troubleshooting methodology you learned in this course.
After completing this module and associated hands-on activities, you will be able to
demonstrate proficiency:
 Using the troubleshooting methodology described in this course.
 Analyzing and isolating VLAN switching problems.
 Correcting issues with VLAN switching.

Rev 10.41 Module 3 – 1


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Outline
The Troubleshooting HP Networks course is built around the Five Layer Internet
Model, often referred to as the TCP/IP protocol suite. Each lab module introduces the
techniques and tools to troubleshoot a specific layer of the Internet model. The final
lab module concludes with a large, comprehensive exercise that requires you to use
your skills and knowledge to troubleshoot a problem across these layers. Each lab
has been designed to develop specific learner expertise, which then provides the
building blocks for doing the final lab.
Layer Application
5
Layer Transport
4
Layer Network
3
Layer Data link
2 (network interface)
Layer Physical
1 (hardware)
Table 3-1: Five layer Internet model
In this specific lab module you will be troubleshooting layer 2, the data link layer. The
labs in this module cover the troubleshooting scenarios most frequently encountered
involving VLAN switching.
You will do these labs and exercises in lab teams. Your facilitator will divide you into
lab pairs and assign you a lab number.

Module 3 – 2 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 2 Troubleshooting and Problem Resolution

Lab 4 equipment
The figure below shows the lab equipment used in this course and its configuration.
Branch
Campus A-MSR30
A-MSR30

G0/0 G0/0 G0/1


G0/1 Core
A-MSR50
G3/0/1 G3/0/2
G1/0/3 G1/0/3

10Gig
CoSw1 CoSw2
A5800 A5800
10Gig Branch
G1/0/2 G1/0/2 A7503
G1/0/1 G1/0/1

Int1 Int1

Int2 Int2
ASw1 ASw2
E3500yl E3500yl

Int5 Int5

10.P.10.100 10.P.20.100

Windows Client
VLAN10 Windows Server
VLAN20

Figure 3-1: Basic lab set up


This lab consists of a campus network and a remote branch network. The campus
network equipment is:
 Two HP A5800 chassis switches interconnected with 10-Gigabit Ethernet.
These switches include HP’s Intelligent Resilient Framework (IRF) technology that
allows A5800 switches to be interconnected for higher resiliency and
performance. CoSw1 is operating as the primary root switch for VLAN 1 and
VLAN 10 and the backup root switch for VLAN 6 and VLAN 20, CoSw2 is
operating as the primary root switch for VLAN 6 and VLAN 20, and the backup
root switch for VLAN 1 and VLAN 10.
 Two HP E3500yl edge switches.
 One Windows Server.

Rev 10.41 Module 3 – 3


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

 One Windows client machine.


The remote branch office network equipment is:
 One A7503 switch chassis.
Interconnection between the campus network and the remote branch network s is via
MSR routers.
 Two A-MSR30s multi-service routers.
Where one A-MSR30 is located in the campus network and one in the branch
office, and the A-MSR50 larger multi-service router located in the core of the
network, providing WAN connectivity.
Pre-lab exercise
To help prepare you to do the labs in this course, add to the lab configuration
diagram above, information that will be helpful in troubleshooting this network. For
example IP addresses and VLANs port assignment.
Be prepared to discuss what type of information you added to the diagram and why.
Capture your notes here:

Module 3 – 4 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 2 Troubleshooting and Problem Resolution

Your trouble ticket assignment


Virtual LAN switching has become a foundation technology for LANs and is rapidly
becoming equally important across metro, national and international networks. In this
lab you will troubleshoot a problem with the VLAN switching implementation.
In this lab your facilitator will assign you one of following three trouble tickets, namely
lab 4.1, 4.2 or 4.3. Each trouble ticket describes a problem related to a VLAN
configuration, deployment or performance. You need to isolate the problem and
solve.
You are required to complete only one trouble ticket. All three problems will however
be discussed in the class and space has been allocated below for you to capture
notes on all three labs. If you have time later in the course, you can come back and
complete the other labs.

1. Lab 4.1 trouble ticket


Below are the trouble ticket and the associated lab configuration for lab 4.1. If
you have been assigned this trouble ticket review the problem ticket and
configuration diagram and proceed to Step 1 - identification.

Figure 3-2: Lab 4.1 trouble ticket

Rev 10.41 Module 3 – 5


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

10Gig
CoSw1 CoSw2
A5800 10Gig A5800
G1/0/2 G1/0/2
G1/0/1 G1/0/1

Int1 Int1

ASw1 Int2 Int2


ASw2
E3500yl E3500yl

VLAN 30 Added
Int5 Int5 to Instance 1

10.P.10.100
10.P.20.100

Windows Client
VLAN10 Windows Server
VLAN20

Figure 3-3: Lab 4.1 equipment configuration


Write your notes here:

Module 3 – 6 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 2 Troubleshooting and Problem Resolution

2. Lab 4.2 Trouble Ticket


Below are the trouble ticket and the associated lab configuration for lab 4.2. If
you have been assigned this trouble ticket review the problem ticket and
configuration diagram and proceed to Step 1 - identification.

Figure 3-4: Lab 4.2 trouble ticket


The equipment configuration diagram for this lab is shown below. The lab
includes the same equipment as described earlier. In addition there are
aggregate link trunks set up from the edge switches to the core network switches.

Rev 10.41 Module 3 – 7


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

10Gig
IRF IRF
Member 1 10Gig Member 2
G1/0/2
G2/0/2
G1/0/1 G2/0/1

Aggregate Link
Aggregate Link Trunk
Int1 Trunk
Int1

ASw1 Int2 Int2


ASw2
E3500yl E3500yl

Int5 Int5

10.P.10.100
10.P.20.100

Windows Client
VLAN10 Windows Server
VLAN20

Figure 3-5: Lab 4.2 equipment configuration

Write your notes here:

Module 3 – 8 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 2 Troubleshooting and Problem Resolution

3. Lab 4.3 Trouble Ticket #3:


Below are the trouble ticket and the associated lab configuration for lab 4.2. If
you have been assigned this trouble ticket review the problem ticket and
configuration diagram and proceed to Step 1 - identification.

Figure 3-6: Lab 4.3 trouble ticket


The equipment configuration for this lab is shown in the figure below. It includes
the same equipment as described earlier. In addition this diagram is showing
that there are aggregate link trunks set up from the edge switches to the chassis
switches is using the Link Aggregation Control Protocol (LACP).

Rev 10.41 Module 3 – 9


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Branch
Campus A-MSR30
A-MSR30

G0/0 G0/0 G0/1


G0/1 Core
A-MSR50
G3/0/1 G3/0/2

G1/0/3 G2/0/3

10Gig
IRF IRF
Member 1 10Gig Member 2 Branch
G1/0/2 A7503
G2/0/2
G1/0/1 G2/0/1

LACP MAD LACP MAD


Int1
Int1

ASw1 Int2 Int2


ASw2
E3500yl E3500yl

Int5 Int5

10.P.10.100
10.P.20.100

Windows Client
VLAN10 Windows Server
VLAN20

Figure 3-7: Lab 4.3 equipment configuration

Write your notes here:

Module 3 – 10 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 2 Troubleshooting and Problem Resolution

Step 1 – Identification
In module 1 you learnt about the six step troubleshooting methodology. You are now
going to apply that methodology, starting with step 1 identification. Refer to module
1 of your learner’s guide for details.

Figure 3-8: Troubleshooting methodology identification


The facilitator may ask you to present your solution to the class. So it is a good idea
to write down a concise problem definition. Discuss with your lab partner(s) what
level of priority you would assign to this trouble ticket and why?
Problem definition:

Your recommended priority:

Rev 10.41 Module 3 – 11


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Step 2 – Analysis

Figure 3-9: Troubleshooting methodology analysis


Do you know what network component is failing? Write down what you think the
problem could be. There may be multiple possible causes.

Module 3 – 12 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 2 Troubleshooting and Problem Resolution

Step 3 – Hypothesis
Even for apparently straightforward problems, it is important to think through the
technical aspects and form a hypothesis and validation process. Small network
changes have been known to have catastrophic effects.

Figure 3-10: Troubleshooting methodology hypothesis


There are many tools and techniques for troubleshooting network problems. List what
tools you would use to both evaluate this problem and to validate the solution. Be
prepared to share your experience with the class.

Rev 10.41 Module 3 – 13


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

List what CLI commands you would use and why.

The course facilitator will give you instructions on where to find customer
configuration files for your troubleshooting ticket. Load these configuration files and
see if you can simulate the problem.
Where you able to recreate the problem, Y/N? ____________
What is your hypothesis and validation process?

Module 3 – 14 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 2 Troubleshooting and Problem Resolution

Step 4 – Validation
Test your hypothesis.
Did your hypothesis work (Y/N): ____________

Figure 3-11: Troubleshooting methodology validation


If your hypothesis did not work, undo the change and return to step 3 and reassess
other possible causes of this problem.

In this lab you are not required to do step 5 (implementation) or step 6 (verification).

You have now completed this lab

Rev 10.41 Module 3 – 15


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Useful CLI commands

Windows Devices:
ping default gateway from PC or Server (10.P.10.1 or 10.P.20.1)
arp -a
arp -d
ping Campus Router from PC and/or Server
A-Series:
display stp brief
display stp region-configuration
display port trunk
display brief interface
display
display vlan
display vlan <id#>
display mac-address dynamic
display link-aggregation summary
display link-aggregation bridge-aggregation<#> verbose
display irf topology
display mad verbose
display stp brief
display mac-address dynamic
E- Series:
show spanning-tree
show spanning-tree instance ist
show spanning-tree instance <id#>
show spanning-tree instance <port#> detail
show spanning-tree mst-config
show vlans
show vlan <vlan#>
show vlans ports <port-list> detail

Module 3 – 16 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 2 Troubleshooting and Problem Resolution

show interfaces brief


show mac-address
show trunks

Rev 10.41 Module 3 – 17


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Module 3 – 18 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 3 Troubleshooting and Problem Resolution


Module 4 – Lab Guide

Objectives
This lab introduces you to the HP equipment that you will be working on throughout
this course and assigns you real-life troubleshooting tickets for you to solve. You will
use the knowledge you acquired in your ASE Network Infrastructure certification
training and apply the troubleshooting methodology you learned in this course.
After completing this module and associated hands-on activities, you will be able to
demonstrate proficiency in:
 Using the layer 3 troubleshooting tools.
 Analyzing, isolating and correcting OSPF routing problems.
 Analyzing, isolating and correcting addressing problems.
 Analyzing, isolating and correcting inter-VLAN and VRRP problems.

Rev 10.41 Module 4 – 1


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Outline
The Troubleshooting HP Networks course is built around the Five Layer Internet
Model, often referred to as the TCP/IP protocol suite. Each lab module introduces the
techniques and tools to troubleshoot a specific layer of the Internet model. The final
lab module concludes with a large, comprehensive exercise that requires you to use
your skills and knowledge to troubleshoot a problem across these layers. Each lab
has been designed to develop specific learner expertise, which then provides the
building blocks for doing the final lab.
Layer 5 Application
Layer 4 Transport
Layer 3 Network
Layer 2 Data link
(network interface)
Layer 1 Physical
(hardware)
Table 4-1: Five layer Internet model
In this module you will be troubleshooting layer 3, the network layer.
The labs in this module cover the troubleshooting scenarios most frequently
encountered involving IP layer routing. There are 4 labs in this module:
 Lab 5: Scenarios and Practice with Layer 3 Tools
 Lab 6: Trouble Tickets Regarding OSPF Routing Issues
 Lab 7: Trouble Tickets Regarding Addressing Issues
 Lab 8: Trouble Tickets Regarding Inter-VLAN Issues
You will do these labs and exercises in your assigned lab team.

Module 4 – 2 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 3 Troubleshooting and Problem Resolution

Lab 5: Scenarios and Practice with Layer 3 Tools


Lab objectives
There are a number of industry standard and HP-specific troubleshooting tools
available for troubleshooting and problem resolution of Layer 3 IP networks. You are
expected to have learnt how to use these tools either in the ASE Network
Infrastructure certification training course and your personal on-the-job experience.
The objectives of this lab are:
 To ensure you know the industry standard and HP-specific troubleshooting tools
available for troubleshooting and problem resolution of Layer 3 IP networks.
 To provide an opportunity for you to hear from other learners the tools that they
have found useful to troubleshoot layer 3 networking problems.
Your assigned trouble tickets
You have been assigned three trouble tickets. The problem definition from these
trouble tickets is:
 Lab 5.1 trouble ticket: The customer cannot access an internal web/ftp server.
 Lab 5.2 trouble ticket: The customer cannot access devices outside of their local
subnet.
 Lab 5.3 trouble ticket: Users on a specific VLAN cannot access any remote
devices.
There are no dependencies between these labs. However it is recommended that you
do them in the order shown in this document.
As the main purpose of this lab is familiarity with the tools, for these trouble shooting
tickets you will be doing steps 2 to 4 of the trouble shooting methodology, that is,
analysis, hypothesis and validation.

Rev 10.41 Module 4 – 3


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Lab 5.1
Lab 5.1 set up
The figure below shows the equipment configuration for lab 5.1.

10Gig
CoSw1 CoSw2
A5800 10Gig A5800
G1/0/2
G1/0/2
G1/0/1 G1/0/1

Int1 Int1

ASw1 Int2 Int2


ASw2
E3500yl E3500yl

Int5 Int5

www.labtest1.com
10.P.10.100 10.P.20.100

Windows Client
VLAN10 Windows Server
VLAN20

Figure 4-1: Lab 5.1 equipment configuration


This lab consists of a campus network and a remote branch network. The campus
network equipment is:
 Two HP A5800 chassis switches interconnected with 10-Gigabit Ethernet.
 Two HP E3500yl edge switches.
 One Windows Server.
 One Windows client.

Module 4 – 4 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 3 Troubleshooting and Problem Resolution

Lab 5.1 Trouble ticket

Figure 4-2: Lab 5.1 trouble ticket


Step 2 – Analysis

 Replicate the problem


The course facilitator will give you the customer configuration files for your
troubleshooting ticket. Load these configuration files and see if you can simulate
the problem.
Where you able to recreate the problem, Y/N? ____________
 Isolate the failing component
List the possible causes of this problem below.

Rev 10.41 Module 4 – 5


BitSpyder - The Culture of Knowledge

Layer 3 Troubleshooting and Problem Resolution

If you solution did NOT work, returns to step 2 and reassess possible solutions.

Lab 5.2
Lab 5.2 set up
The figure below shows the equipment configuration for lab 5.1.
Branch
Campus A-MSR30
A-MSR30

G0/0 G0/0 G0/1


G0/1 Core
A-MSR50
G3/0/1 G3/0/2

G1/0/3 G1/0/3

10Gig
CoSw1 CoSw2
A5800 A5800 Branch
G1/0/2 A7503
G1/0/2
G1/0/1 G1/0/1

Int1 Int1

ASw1 Int2 Int2


ASw2
E3500yl E3500yl

Int5 10.P.10.2 Int5

10.P.10.100 10.P.10.100

Windows Client
VLAN10 Windows Server
VLAN20

Figure 4-3: Lab 5.2 equipment configuration


The equipment in this lab 5.2 is the same as the previous lab 5.1, however the
configuration files are different.

Rev 10.41 Module 4 – 7


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Figure 4-4: Lab 5.2 trouble ticket

Step 2 – Analysis
 Replicate the problem
The course facilitator will give you the customer configuration files for your
troubleshooting ticket. Load these configuration files and see if you can simulate
the problem.
Where you able to recreate the problem, Y/N? ____________
 Isolate the failing component
List the possible causes of this problem below.

Module 4 – 8 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 3 Troubleshooting and Problem Resolution

Indicate below the troubleshooting tools you think would be helpful to solve this
problem.
Troubleshooting tools Plan to use (Y/N)

Display CLI commands _________


CLI debug commands _________
Ping _________
Traceroute _________
Protocol analyzer _________
Other? _________

Step 3 – Hypothesis
 Perform technical evaluation
Use the tools you identified and analyze the problem. Based on your analysis
what is the root cause of the problem described in your trouble ticket? Write your
hypothesis below.

What is your recommended resolution and how will you validate the solution?
Write the proposed changes and validation below.

Step 4 – Validation
 Test your hypothesis
Implement your proposed changes and validate the solution in the manner you
described above.
Did you solution work (Y/N) __________
Whether the hypothesis was correct or flawed, it is always possible to learn
something new about the problem. What did you learn? Write it down and be
prepared to share with the class.

Rev 10.41 Module 4 – 9


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

If you solution did NOT work, returns to step 2 and reassess possible solutions.

Module 4 – 10 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 3 Troubleshooting and Problem Resolution

Lab 5.3
Lab 5.3 set up
The figure below shows the equipment configuration for lab 5.1.

OSPF
Area 0
Branch
Campus A-MSR30
A-MSR30

OSPF G0/0 G0/0 G0/1


Area P10 G0/1 Core
A-MSR50
G3/0/1 G3/0/2

G1/0/3 G1/0/3

10Gig
CoSw1 CoSw2
OSPF A5800 A5800 Branch
Area P10 G1/0/2 A7503
G1/0/2
G1/0/1 G1/0/1

Int1 Int1

ASw1 Int2 Int2


ASw2
E3500yl E3500yl

Int5 Int5

10.P.10.100 10.P.10.100

Windows Client
VLAN10 Windows Server
VLAN20

Figure 4-5: Lab 5.3 equipment configuration


The equipment in this lab 5.3 is the same as the previous lab 5.2 however the
configuration files are different.
In this lab two OSPF areas have been configured. Two OSFP areas are defined as
follows:
 OSPF area 0 which encompasses the core, campus, and the branch routers.
 OSPF area pod #10 which encompasses the two chassis switches.
 The campus router and CoSw2 are area border routers (ABR) connecting OSPF
Area 0 and Area P10.

Rev 10.41 Module 4 – 11


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Trouble ticket

Figure 4-6: Lab 5.3 trouble ticket

Step 2 – Analysis
 Replicate the problem
The course facilitator will give you the customer configuration files for your
troubleshooting ticket. Load these configuration files and see if you can simulate
the problem.
Where you able to recreate the problem, Y/N? ____________
 Isolate the failing component
List the possible causes of this problem below.

Module 4 – 12 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 3 Troubleshooting and Problem Resolution

Indicate below the troubleshooting tools you think would be helpful to solve this
problem.
Troubleshooting tools Plan to use (Y/N)
Display CLI commands _________
CLI debug commands _________
Ping _________
Traceroute _________
Protocol analyzer _________
Other? _________
 New CLI commands
There are many CLI commands that can be used to display the status of device
parameters. These commands can be useful in helping to trouble shoot customer
problems.
Below is a list of CLI commands that can be used to display various aspects of
the switch settings. Indicate which of these commands you think would be helpful
to you in analyzing your troubleshooting problem.
A-Series Applicable
display ospf interface ____________
display ip routing-table ____________

Step 3 – Hypothesis
 Perform technical evaluation
Use the tools you identified and analyze the problem. Based on your analysis
what is the root cause of the problem described in your trouble ticket? Write your
hypothesis below.

What is your recommended resolution and how will you validate the solution?
Write the proposed changes and validation below.

Rev 10.41 Module 4 – 13


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Step 4 – Validation
 Test your hypothesis
Implement your proposed changes and validate the solution in the manner you
described above.
Did you solution work (Y/N) __________
Whether the hypothesis was correct or flawed, it is always possible to learn
something new about the problem. What did you learn? Write it down and be
prepared to share with the class.

If you solution did NOT work, returns to step 2 and reassess possible solutions.

Module 4 – 14 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 3 Troubleshooting and Problem Resolution

Lab 6: Troubleshooting Routing Protocol Issues


Lab Objectives
Open Shortest Path First (OSPF) is the most common interior routing protocol
encountered in enterprise networks.
The objectives of this lab are:
 Reinforce your understanding of the basic routing protocol.
 Build expertise in troubleshooting some common routing problems.
Lab outline
You have been assigned a trouble ticket. This troubleshooting ticket is more complex
than the previous trouble tickets and will require more time to resolve. You are to
carry out the first 4 steps of the troubleshooting methodology namely identification,
analysis, hypothesis and validation.

OSPF
Area 0
Branch
Campus A-MSR30
A-MSR30

OSPF G0/0 G0/0 G0/1


Area P10 G0/1 Core
A-MSR50
G3/0/1 G3/0/2
Stubby
G1/0/3 G1/0/3
OSPF
Area P10
10Gig
CoSw1 CoSw2
A5800 A5800 Branch
G1/0/2 A7503
G1/0/2
G1/0/1 G1/0/1
RIP

Int1 Int1
RIP RIP
ASw1 Int2 Int2
ASw2
E3500yl E3500yl

RIP
Int5 Int5

10.P.10.100 10.P.10.100

Windows Client
VLAN10 Windows Server
VLAN20

Figure 4-7: Lab 6 equipment configuration


This lab consists of the same equipment as outlines in the earlier labs but the
configuration and set up is very different.
There are two OSFP areas are defined as follows:

Rev 10.41 Module 4 – 15


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

 OSPF area 0 which encompasses the core, campus routers, and branch routers.
 OSPF area pod #10 which encompasses the two core switches.
 The campus router and CoSw2 are set up as area border routers (ABR)
connecting OSPF Area 0 and Area P10.
Routers and switches outside of the OSPF areas use the distance vector protocol RIP.
Lab 6 Trouble ticket

Figure 4-8: Lab 6 trouble ticket

Module 4 – 16 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 3 Troubleshooting and Problem Resolution

Step 4 – Validation
Implement your proposed changes and validate the solution in the manner you
described above.
Did you solution work (Y/N) __________
Whether the hypothesis was correct or flawed, it is always possible to learn
something new about the problem. What did you learn? Write it down and be
prepared to share with the class.

If you solution did NOT work, write below other possible causes that you would like
to validate? Write these causes below. Returns to step 3 and restart building your
hypothesis.

If you solution did NOT work and you have no more possible causes you should
return to Step 1 Identification and look for additional information that you may have
overlooked.

You have completed this lab.

Rev 10.41 Module 4 – 27


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Lab 4: VLAN Routing Issues


Lab objectives
Layer 2 entities such as VLANs can only maintain their integrity if they are connected
via Layer 3 Routers. Interconnection via Layer 2 switches and bridges does not create
interconnect VLANS but, rather, it creates a single large VLAN comprised of the two
VLANs being interconnected.
The objectives of this lab are to:
 Build skills in identifying common issues with Inter-VLAN routing.
 Reinforce usage of a structure approach to trouble shooting.
Lab overview
The equipment configuration for this lab is shown in the figure below.
Branch
Campus A-MSR30
A-MSR30

G0/0 G0/0 G0/1


G0/1 Core
A-MSR50
G3/0/1 G3/0/2

G1/0/3 G1/0/3

10Gig
CoSw1 CoSw2
A5800 10Gig A5800 Branch
G1/0/2 G1/0/2 A7503
G1/0/1 VRRP G1/0/1

Int1 Int1

ASw1 Int2 Int2


ASw2
E3500yl E3500yl

Int5 10.P.10.2 Int5

10.P.10.100 10.P.10.100

Windows Client
VLAN10 Windows Server
VLAN20

Figure 4-11: Lab 8 equipment configuration

Module 4 – 28 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 3 Troubleshooting and Problem Resolution

Figure 4-12: Lab 8 trouble ticket


In this lab you are required to complete steps 1 to 4 of the troubleshooting
methodology.

Step 1 – Identification
Describe the symptoms of the problem? Write them below.

Rev 10.41 Module 4 – 29


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

The course facilitator will give you the customer configuration files for your
troubleshooting ticket. Load these configuration files
What is the physical environment? Write the key aspects below.

Describe what the customer wants to do?

Write the problem definition below.

What priority would you give this problem and why? Capture your recommendation
below.

Module 4 – 30 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 3 Troubleshooting and Problem Resolution

Step 2 – Analysis
Where you able to recreate the problem, Y/N? ____________
List the possible causes of this problem below.

Indicate below the troubleshooting tools you think would be helpful to solve this
problem.
Troubleshooting tools

New CLI commands


Are there any CLI commands that you think would be helpful to you in analyzing
your troubleshooting problem.
CLI command Purpose

Rev 10.41 Module 4 – 31


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Step 3 – Hypothesis
Use the tools you identified and analyze the problem. Based on your analysis what is
the root cause of the problem describes in your trouble ticket? Write your hypothesis
below.

Module 4 – 32 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 3 Troubleshooting and Problem Resolution

What is your recommended resolution and how will you validate the solution? Write
the proposed changes and validation below.

Are there any possible side effects to your proposed solution? Write them below.

Step 4 – Validation
Implement your proposed changes and validate the solution in the manner you
described above.
Did you solution work (Y/N) __________
Whether the hypothesis was correct or flawed, it is always possible to learn
something new about the problem. What did you learn? Write it down and be
prepared to share with the class.

Rev 10.41 Module 4 – 33


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

If you solution did NOT work, write below other possible causes that you would like
to validate? Write these causes below. Returns to step 3 and restart building your
hypothesis.

If you solution did NOT work and you have no more possible causes you should
return to Step 1 Identification and look for additional information that you may have
overlooked.
If you solution worked, how certain are you that your solution will work? Indicate
your assessment below.

ŀ Absolutely positive this solution will work


ŀ Over 95% confident that this solution will work
ŀ Fairly certain it will work
ŀ Not confident at all
Write below what steps you would like to take to raise your confidence in your
solution. Be prepared to discuss these steps with the class.

You have completed all the labs in this module.

Module 4 – 34 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 4 Troubleshooting and Problem Resolution


Module 5 – Lab Guide

Objectives
This lab is focused on problems that occur at the layer 4 transport layer. You will be
given real-life troubleshooting tickets to solve. You will use the knowledge you
acquired in your ASE Network Infrastructure certification training track and apply the
troubleshooting methodology you learned in this course.
After completing this module and associated hands-on activities, you will be able to
demonstrate proficiency:
 Troubleshooting TCP, UDP and PAT network problems.
 Distinguishing between layer 3 networking and layer 4 transport issues.
 Resolving common transport layer problems.

Rev 10.41 Module 5 – 1


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Outline
The course is built around the Five Layer Internet
Model, often referred to as the TCP/IP protocol suite. The labs include a number of
small, very narrow troubleshooting exercises and conclude with a large,
comprehensive exercise. Each lab has been designed to develop specific learner
expertise, which then provides the building blocks for doing the final lab.
Layer 5 Application
Layer 4 Transport
Layer 3 Network
Layer 2 Data link
(network interface)
Layer 1 Physical
(hardware)
Table 5-1: Five layer Internet model
In this module you will be troubleshooting layer 4 of the IETF model, the transport
layer.
The transport layer is becoming increasingly important for troubleshooters and
problem solvers to understand because it is:
 The point of addressing and differentiation for applications via Layer 4 Port
numbers.
 A common attack path for hackers and their malicious software.
Port scans, for instance, are very common in many enterprises as well as
households and hotel rooms.
This lab will unveil some common problems with TCP, UDP and Port Address
Translation (PAT).
You will do these labs and exercises in your assigned lab teams.

Module 5 – 2 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 4 Troubleshooting and Problem Resolution

Lab 9 equipment
The figure below shows the lab equipment used in this course and its configuration.
Branch
Campus A-A-MSR30
A-A-MSR30

G0/0 G0/1
G0/0 G0/1 Core
ACL
A-A-MSR50
Applied G3/0/1 G3/0/2

G1/0/3 G1/0/3

10Gig
CoSw1 CoSw2
A5800 A5800 Branch
A7503
G1/0/2 G1/0/2
G1/0/1 G1/0/1

Int1 Int1

ASw1 Int2 Int2


ASw2
E3500yl E3500yl

Int5 10.P.10.2 Int5

10.P.10.100 10.P.10.100

Windows Client
VLAN10 Windows Server
VLAN20

Figure 5-1: Lab 9 equipment configuration


This lab consists of a campus network and a remote branch network. The campus
network equipment is:
 Two HP A5800 chassis switches interconnected with 10-Gigabit Ethernet.
 Two HP E3500yl edge switches.
 One Windows Server.
 One Windows client machine.
The remote branch office network equipment is:
 One A7503 switch chassis.
Interconnection between the campus network and the remote branch network s is via
MSR routers.
 Two A-MSR30s multi-service routers.

Rev 10.41 Module 5 – 3


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

 Where one A-MSR30 is located in the campus network and one in the branch
office.
 One A-MSR50 larger multi-service router located in the core of the network,
providing WAN connectivity.
The campus router has been configured with an Access Control List (ACL).

Module 5 – 4 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 4 Troubleshooting and Problem Resolution

Your trouble ticket assignment


Your trouble ticket is for a user who can’t get a new application to work in the current
IP network environment.

Figure 5-2: Lab 9 trouble ticket

Rev 10.41 Module 5 – 5


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Step 1 – Identification
Describe the symptoms of the problem? Write them below.

What is the physical environment? Write the key aspects below.

Describe what the customer wants to do? Write the customer need below.

Module 5 – 6 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 4 Troubleshooting and Problem Resolution

Write the problem definition below.

What priority would you give this problem and why? Capture your recommendation
below.

Step 2 – Analysis
Replicate the problem
The course facilitator will give you the customer configuration files for your
troubleshooting ticket. Load these configuration files and see if you can simulate the
problem.
Where you able to recreate the problem, Y/N? ____________
Isolate the failing component
What were the previous changes to the system? Could these changes cause this
problem? Write below your findings.

Rev 10.41 Module 5 – 7


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

List the possible causes of this problem below.

Indicate below the troubleshooting tools you think would be helpful to solve this
problem.
Troubleshooting tools Plan to use (Y/N)
Display CLI commands _________
CLI debug commands _________
Ping _________
Traceroute _________
Protocol analyzer _________
Other? _________

Module 5 – 8 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 4 Troubleshooting and Problem Resolution

New CLI commands


There are many CLI commands that can be used to display the status of device
parameters. These commands can be useful is helping to trouble shoot customer
problems.
Below is a list of additional CLI commands that can be used to display various
aspects of the switch settings.
A-Series:
display acl all
display firewall-statistics
telnet <IP> <port#>

Rev 10.41 Module 5 – 9


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Step 3 – Hypothesis
Perform technical evaluation
Use the tools you identified and analyze the problem. Based on your analysis what is
the root cause of the problem described in your trouble ticket? Write your hypothesis
below.

What is your recommended resolution and how will you validate the solution? Write
the proposed changes and validation below.

Module 5 – 10 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 4 Troubleshooting and Problem Resolution

Are there any possible side effects to your proposed solution? Write them below.

Step 4 – Validation
Test your hypothesis
Implement your proposed changes and validate the solution in the manner you
described above.
Did your solution work (Y/N) __________
Whether the hypothesis was correct or flawed, it is always possible to learn
something new about the problem. What did you learn? Write it down and be
prepared to share with the class.

If your solution did NOT work, write below other possible causes that you would like
to validate? Write these causes below. Returns to step 3 and restart building your
hypothesis.

Rev 10.41 Module 5 – 11


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

If your solution did NOT work and you have no more possible causes you should
return to Step 1 Identification and look for additional information that you may have
overlooked.
If your successfully validated your hypothesis, how certain are you that your solution
will work when implemented in the live network? Indicate your assessment below.

□ Absolutely positive this solution will work


□ Over 95% confident that this solution will work
□ Fairly certain it will work
□ Not confident at all
If you think your confidence level is enough to proceed go on to the next step. Write
below what steps you would like to take to raise your confidence in your solution.

Discuss these with your course facilitator and decide whether to implement these
steps or continue to the next step.

Module 5 – 12 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 4 Troubleshooting and Problem Resolution

Step 5 – Implementation
Develop your implementation plan
Network nodes impacted Proposed changes

Verification process
Step 1: ____________________________________________________________
Step 2: ____________________________________________________________
Step 3: ____________________________________________________________
Step 4: ____________________________________________________________
Step 5: ____________________________________________________________
Step 6: ____________________________________________________________
Step 7: ____________________________________________________________
Step 8: ____________________________________________________________
Back-out plan
Step 1: ____________________________________________________________
Step 2: ____________________________________________________________
Step 3: ____________________________________________________________
Step 4: ____________________________________________________________
Step 5: ____________________________________________________________
Step 6: ____________________________________________________________
Step 7: ____________________________________________________________
Step 8: ____________________________________________________________

Rev 10.41 Module 5 – 13


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Other relevant information

Be prepared to present your implementation plan to the class.

Module 5 – 14 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 4 Troubleshooting and Problem Resolution

Step 6 – Verification
In normal work environments you would run your implementation plan and
verification procedure to determine if successful. In this lab the facilitator and other
students’ feedback on your plan will determine if your plan was successful.
Was your plan deemed successful (Y/N) _____________
Write notes here on how other student plans differ from yours. Make a list of good
ideas you want to take away from this lab.

Your facilitator may ask you to share these ideas.

You have completed this lab.

Rev 10.41 Module 5 – 15


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Module 5 – 16 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 5 Troubleshooting and Problem Resolution


Module 6 – Lab Guide

Objectives
This lab focuses on problems that occur at layer 5, the application layer. You will be
given real-life troubleshooting tickets to solve. You will use the knowledge you
acquired in your ASE Network Infrastructure certification training track and apply the
troubleshooting methodology that you have learned in this course.
After completing this module and associated hands-on activities, you will be able to
demonstrate proficiency:
 Troubleshooting common layer 5 application problems.
 Recognize common problems around application unavailability, poor
application performance and poor quality (VoIP).
 Utilize the HP troubleshooting methodology for problem solving.

Rev 10.41 Module 6 – 1


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Outline
The course is built around the Five Layer Internet
Model, often referred to as the TCP/IP protocol suite. The labs include a number of
small, very narrow troubleshooting exercises and conclude with a large,
comprehensive exercise. Each lab has been designed to develop specific learner
expertise, which then provides the building blocks for doing the final lab.

Layer 5 Application
Layer 4 Transport
Layer 3 Network
Layer 2 Data link
(network interface)
Layer 1 Physical
(hardware)
Table 1-1: Five layer Internet model
In this lab you will troubleshoot the layer 5 applications.
You will be given a trouble ticket to resolve.
You will do these labs and exercises in your assigned lab team.

Module 6 – 2 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 5 Troubleshooting and Problem Resolution

Lab equipment
The figure below shows the lab equipment used in this course and its configuration.

OSPF
Area 0
Branch
Campus MSR30
MSR30 QoS & NAT
Applied

OSPF G0/0 G0/0 G0/1


Area P10 G0/1 Core
MSR50
G3/0/1 G3/0/2

G1/0/3 G1/0/3

10Gig
CoSw1 CoSw2
OSPF 5800 5800 Branch
Area P10 G1/0/2 7502
G1/0/2
G1/0/1 G1/0/1

Int1 Int1

ASw1 Int2 Int2


ASw2
3500XL 3500XL

Int5 Int5

10.P.10.100 10.P.10.100

Win7 Client
VLAN10 WinServer
VLAN20

Figure 6-1: Lab 10 equipment configuration


This lab consists of a campus network and a remote branch network. The campus
network equipment is:
 Two HP A5800 chassis switches interconnected with 10-Gigabit Ethernet.
 Two HP E3500yl edge switches.
 One Windows Server.
 One Windows client.
The remote branch office network equipment is:
 One A7502 switch chassis.
Interconnection between the campus network and the remote branch network s is via
MSR routers.
 Two A-MSR30s multi-service routers.
 Where one A-MSR30 is located in the campus network and one in the branch
office.

Rev 10.41 Module 6 – 3


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

 One A-MSR50 larger multi-service router located in the core of the network,
providing WAN connectivity.

Module 6 – 4 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 5 Troubleshooting and Problem Resolution

Your trouble ticket assignment


In this trouble ticket you will solve Quality of Service problems that remote users are
experiencing when using the network for VoIP calls.

Figure 6-2: Lab 10 trouble ticket

Rev 10.41 Module 6 – 5


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Step 1 – Identification
Describe the symptoms of the problem? Write them below.

What is the physical environment? Write the key aspects below.

Describe what the customer wants to do? Write the customer need below.

Module 6 – 6 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 5 Troubleshooting and Problem Resolution

Write the problem definition below.

What priority would you give this problem and why? Capture your recommendation
below.

Step 2 – Analysis
Replicate the problem
The course facilitator will give you the customer configuration files for your
troubleshooting ticket. Load these configuration files and see if you can simulate the
problem.
Where you able to recreate the problem, Y/N? ____________
Isolate the failing component
What were the previous changes to the system? Could these changes cause this
problem? Write below your findings.

Rev 10.41 Module 6 – 7


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

List the possible causes of this problem below.

Indicate below the troubleshooting tools you think would be helpful to solve this
problem.
Troubleshooting tools Plan to use (Y/N)
Display CLI commands _________
CLI debug commands _________
Ping _________
Traceroute _________
Protocol analyzer _________
Other? _________

Module 6 – 8 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 5 Troubleshooting and Problem Resolution

CLI commands
There are many CLI commands that can be used to display the status of device
parameters. These commands can be useful is helping to trouble shoot customer
problems.
Below is a list of CLI commands that you may wish to use to display various aspects
of the switch settings.
A-Series:
display acl all
display traffic classifier user-defined
display traffic behavior user-defined
display qos policy user-defined
display interface <if-name>
display qos policy interface <if-name> [inbound | outbound]
ping -tos <value> -c <count> -s <size bytes> -m <interval ms> IP

Rev 10.41 Module 6 – 9


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Step 3 – Hypothesis
Perform technical evaluation
Use the tools you identified and analyze the problem. Based on your analysis what is
the root cause of the problem described in your trouble ticket? Write your hypothesis
below.

What is your recommended resolution and how will you validate the solution? Write
the proposed changes and validation below.

Module 6 – 10 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 5 Troubleshooting and Problem Resolution

Are there any possible side effects to your proposed solution? Write them below.

Rev 10.41 Module 6 – 11


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Step 4 – Validation
Test your hypothesis
Implement your proposed changes and validate the solution in the manner you
described above.
Did your solution work (Y/N) __________
Whether the hypothesis was correct or flawed, it is always possible to learn
something new about the problem. What did you learn? Write it down and be
prepared to share with the class.

If your solution did NOT work, write below other possible causes that you would like
to validate? Write these causes below. Returns to step 3 and restart building your
hypothesis.

If your solution did NOT work and you have no more possible causes you should
return to Step 1 Identification and look for additional information that you may have
overlooked.
If your hypothesis worked, how certain are you that your solution will work in the live
environment? Indicate your assessment below.

Module 6 – 12 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 5 Troubleshooting and Problem Resolution

□ Absolutely positive this solution will work


□ Over 95% confident that this solution will work
□ Fairly certain it will work
□ Not confident at all
If you think your confidence level is enough to proceed go on to the next step. Write
below what steps you would like to take to raise your confidence in your solution.

Discuss these with your course facilitator and decide whether to implement these
steps or continue to the next step.

Rev 10.41 Module 6 – 13


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Step 5 – Implementation
Develop your implementation plan
Network nodes impacted Proposed changes

Verification process
Step 1: ____________________________________________________________
Step 2: ____________________________________________________________
Step 3: ____________________________________________________________
Step 4: ____________________________________________________________
Step 5: ____________________________________________________________
Step 6: ____________________________________________________________
Step 7: ____________________________________________________________
Step 8: ____________________________________________________________
Back-out plan
Step 1: ____________________________________________________________
Step 2: ____________________________________________________________
Step 3: ____________________________________________________________
Step 4: ____________________________________________________________
Step 5: ____________________________________________________________
Step 6: ____________________________________________________________
Step 7: ____________________________________________________________
Step 8: ____________________________________________________________

Module 6 – 14 Rev 10.41


BitSpyder - The Culture of Knowledge

Layer 5 Troubleshooting and Problem Resolution

Other relevant information

Be prepared to present your implementation plan to the class.

Rev 10.41 Module 6 – 15


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Step 6 – Verification
In normal work environments you would run your implementation plan and
verification procedure to determine if successful. In this lab the facilitator and other
student’s feedback on your plan will determine if your plan was successful.
Was your plan deemed successful (Y/N) _____________
Write notes here on how other student plans differ from yours. Make a list of good
ideas you want to take away from this lab.

Your facilitator may ask you to share these ideas.

You have completed this lab.

Module 6 – 16 Rev 10.41


BitSpyder - The Culture of Knowledge

Troubleshooting a Complex Integrated


MultiProtocol Network
Module 7 – Lab Guide

Objectives
This lab brings together all of the key aspects in the previous labs. You will be given
real-life troubleshooting tickets to solve. You will use the knowledge you acquired in
your ASE Network Infrastructure certification training track and apply the
troubleshooting methodology and skills you learned in this course.
After completing this module and associated hands-on activities, you will be able to
demonstrate proficiency:
 Troubleshooting HP network problems at all layers.
 Utilize the HP troubleshooting methodology for problem solving.

Rev 10.41 Module 7 – 1


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Lab Objective
The course is built around the Five Layer Internet
Model, often referred to as the TCP/IP protocol suite. The labs include a number of
troubleshooting exercises focused at specific layers and conclude with a large,
comprehensive exercise.

Layer 5 Application
Layer 4 Transport
Layer 3 Network
Layer 2 Data link
(network interface)
Layer 1 Physical
(hardware)
Table 7-1: Five layer Internet model
This lab is the final lab.
To simulate a real-life experience, you will be given a trouble ticket, a diagram of the
network and the configuration files. You are required to solve the problem.
To complete this lab successfully you will need to apply the knowledge gained in the
previous labs. You are expected to solve the trouble ticket by completing the steps
outlined in the troubleshooting methodology.
Capture your work on the note pages provided. Be prepared to present on one or
two of the six troubleshooting methodology steps.
You will do these labs and exercises in your assigned lab team.

Module 7 – 2 Rev 10.41


BitSpyder - The Culture of Knowledge

Troubleshooting a Complex Integrated MultiProtocol Network

Lab configuration
The figure below shows the lab equipment used in this course and its configuration.

BGP 6520P BGP 65100


Branch
Campus A-MSR30
A-MSR30

G0/1
G0/0 G0/0 G0/1
ACL Core OSPF
Applied A-MSR50 Area P30
G3/0/2
OSPF G3/0/1
G1/0/3 Area 0 G1/0/3 BGP 6530P
10Gig
CoSw1 CoSw2
A5800 10Gig A5800 Branch
A7503
10.P.30.100
G1/0/1 G1/0/1

OSPF OSPF
Area P10 Area P20

Int1 Int1

ASw1 ASw2
E3500yl E3500yl

Int5 10.P.10.2 Int5

10.P.10.100 10.P.10.100

Windows Client
VLAN10 Windows Server
VLAN20

Figure 7-1: Lab 11 equipment configuration

Rev 10.41 Module 7 – 3


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Your trouble ticket assignment

Figure 7-2: Lab 11 trouble ticket

Module 7 – 4 Rev 10.41


BitSpyder - The Culture of Knowledge

Troubleshooting a Complex Integrated MultiProtocol Network

The following pages are for you to write down your notes from this lab:

Rev 10.41 Module 7 – 5


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Module 7 – 6 Rev 10.41


BitSpyder - The Culture of Knowledge

Troubleshooting a Complex Integrated MultiProtocol Network

Rev 10.41 Module 7 – 7


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Module 7 – 8 Rev 10.41


BitSpyder - The Culture of Knowledge

Troubleshooting a Complex Integrated MultiProtocol Network

Rev 10.41 Module 7 – 9


BitSpyder - The Culture of Knowledge

Troubleshooting HP Networks

Module 7 – 10 Rev 10.41

You might also like