Kazi_Zial_Hoque.2013-11-22.SAM_StudentGuide_Ver1.4

Network and Service Troubleshooting with the 5620 SAM

Course Introduction

Module 0 - 1 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 0 - 2Network and Service Troubleshooting with the 5620 SAM

Module 0 | 2 All rights reserved © 2012-2013 Alcatel-LucentNetwork and Service Troubleshooting with the 5620 SAM v1.4

Module Overview

Alcatel-Lucent Career Certification

Course Introduction

Course Modules

Additional Optional Modules

Administration

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module 0 | 3 All rights reserved © 2012-2013 Alcatel-Lucent

The Alcatel-Lucent SRC Program – Five Certifications

ALCATEL-LUCENT NETWORK ROUTING SPECIALIST I4 DAYS / 1 COURSE / 1 WRITTEN EXAM

ALCATEL-LUCENT TRIPLE PLAY ROUTING PROFESSIONAL36 DAYS / 8 COURSES / 8 WRITTEN EXAMS / 1 PRACTICAL LAB EXAM

ALCATEL-LUCENT SERVICE ROUTING ARCHITECT49 DAYS / 11 COURSES / 11 WRITTEN EXAMS / 2 PRACTICAL LAB EXAMS

ALCATEL-LUCENT NETWORK ROUTING SPECIALIST II18 DAYS / 4 COURSES / 4 WRITTEN EXAMS / 1 PRACTICAL LAB EXAM

ALCATEL-LUCENT MOBILE ROUTING PROFESSIONAL32 DAYS/ 7 COURSES / 7 WRITTEN EXAMS / 2 PRACTICAL LAB EXAMS

Network and Service Troubleshooting with the 5620 SAM v1.4

This course is NOT part of the Alcatel-Lucent Service Routing Certification (SRC) Program. See www.alcatel-lucent.com/src for more information on the SRC program.

The Alcatel-Lucent Service Routing Certification (SRC) program gives you the training required to design, operate, and troubleshoot today’s IP/MPLS based multi-service networks, allowing your corporation to get the most from its investment in IP service routing.

The Alcatel-Lucent SRC program is specifically designed to arm network engineers, as well as operations and strategic planning staff, with the skills necessary to meet new operational challenges and to align network changes with their companies’ business goals.

Adding video to the service mix creates an entirely new set of networking architectural challenges. Our program is unique in its ability to prepare you for these challenges, both now and in the future.

The NRSI is our introductory certification and the SRA is our highest level certification. As you move from the introductory certification toward the SRA, you will gain more knowledge associated with the ALU approach to services such as VPLS and VPRNS, and solutions such as Triple Play.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



SRC Courses and Exams


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



SRC Program Exam Profile

Exam Name Exam Number Exam Pre-requisites(4A0-XXX)

Alcatel-Lucent Scalable IP Networks 4A0-100 NA

Alcatel-Lucent Interior Routing Protocols 4A0-101 NA

Alcatel-Lucent Border Gateway Protocol 4A0-102 NA

Alcatel-Lucent Multiprotocol Label Switching 4A0-103 NA

Alcatel-Lucent Services Architecture 4A0-104 NA

Alcatel-Lucent Virtual Private LAN Services 4A0-105 NA

Alcatel-Lucent Virtual Private Routed Networks 4A0-106 NA

Alcatel-Lucent Quality of Service 4A0-107 NA

Alcatel-Lucent Multicast Protocols 4A0-108 NA

Alcatel-Lucent Triple Play Services 4A0-109 NA

Alcatel-Lucent Advanced Troubleshooting 4A0-110 NA

Alcatel-Lucent IP/MPLS Mobile Backhaul Transport 4A0-M01 NA

Alcatel-Lucent Mobile Gateways for the LTE Evolved Packet Core

4A0-M02 NA

Alcatel-Lucent Network Routing Specialist II Lab Exam NRSII4A0 100, 101, 103, 104

Alcatel-Lucent Mobile Routing Professional Lab Exam MRP4A0 100, 101, 103, 104, 107, M01, M02, NRSII4A0

Alcatel-Lucent Service Routing Architect Lab Exam ASRA4A0100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110,

NRSII4A0


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


MySRLabLike owning your own Service Router Lab

Need access to an SR lab to help you: Practice and build your service routing knowledge and configuration skills?

Test new network and service features?

Prepare for your NRS II, MRP and SRA exams?

The Alcatel-Lucent MySRLab service provides: Remote, private access(7X24) to an Alcatel-Lucent service router lab

Multiple lab topologies for both wireline and wireless service environments

Access to a suite of over 50 lab “practice” scenarios with optimal solutions

Access to traffic simulation and analysis tools

Sign up today at www.alcatel-lucent.com/src/mysrlab


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

•7


SRC Self-study Options

Alcatel-Lucent Scalable IP Networks Self-Study Guide

ISBN: 978-0-470-42906-8

Prepares the reader for the NRS I certification exam

Alcatel-Lucent Network Routing Specialist II Self-Study Guide

ISBN 978-0-470-94772-2

Prepares reader for the NRS II certification exams

Both guides include CD with lab exercises and solutions

MySRLab for hands-on lab exercises and exam preparation

•http://www.alcatel-lucent.com/srpublications


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Exam Delivery

Written Exams

Delivered by Prometric

Global provider of testing services

5000+ test sites worldwide

Register at: www.prometric.com/alcatel-lucent

Lab Exams

Administered at Alcatel-Lucent locations

NRS II Certification

• Half-day lab exam

• MRP Certification

• Half-day lab exam

SRA Certification

• Full-day lab exam

Register at: www.alcatel-lucent.com/src/examreg


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Global Reach, Flexible Learning Options

APAC― Shanghai, China― Sydney, Australia― Melbourne, Australia ― Wellington, New Zealand ― Bangalore, India― Chennai, India― Gurgaon, India― Mumbai, India

Europe ― Antwerp, Belgium― Newport, UK ― Paris, France

Americas― Plano, USA― Ottawa, Canada― Mexico City, Mexico― Sao Paulo, Brazil

On-site delivery at your business location anywhere in the world

Virtual classroom

Delivery from any Alcatel-Lucent locations globally

Class schedules available at www.alcatel-lucent.com/src

Online registration at www.alcatel-lucent.com/src/coursereg


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Virtual Classroom Delivery

Get the benefits of live SRC training without expensive travel &living and time-away costs

Live, Instructor-led, 100% on-line

Remote access to a Service Router lab for hands-on lab exercises

Interactive and engaging learning environment

Available for public class offerings or private, dedicated customer deliveries

View the class schedule and register at

http://www.alcatel‐lucent.com/src/courses


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


SRC Student Portal

Login to the SRC Student Portal to:•Check your exam history•Verify your certification status and reminder

dates (renewal, expiry, etc.)• Download and display logos for your active

certifications•Publish your certification status to third

parties •Check on the status of your fulfillment

items (plaques, diplomas, etc.) •Get program updates•Review FAQs and get support

http://www.alcatel.lucent.com/src/studentportal


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

•12


Credit for other IP Certifications

Cisco or Juniper certified?

You can receive exemptions from some of the SRC exams, if you hold any one of the Cisco or Juniper certifications identified

Certifications must be valid to receive exemptions

Submit your request for exemptions at: http://www.alcatel-

lucent.com/src/exemptions


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Course Introduction

This course is designed to teach students techniques for troubleshooting Network and Services issues using the 5620 SAM.

Students are expected to have already acquired at least some intermediate skills in using the 5620 SAM for provisioning, network and fault management.

This is not a 5620 SAM introductory course. To find courses designed for learning the 5620 SAM in general, or for specific feature training, please contact/consult the Alcatel-Lucent University list of 5620 SAM courses.


http://www.alcatel-lucent.com/university

http://www.alcatel-lucent.com/src

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Course Introduction (cont.)

Demonstrations, practical exercises and “hands-on” labs are used to teach students the skills required to apply the various features available in the 5620 SAM to troubleshoot and to become familiar with best practices.

Duration: 4-5 days


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



1 – Introduction to Troubleshooting with the 5620 SAM

2 – 5620 SAM Alarms

3 – Navigation Trees

4 – Topology Views

5 – Service Test Manager

6 – Statistics for Troubleshooting

7 – Troubleshooting IGP

8 – Troubleshooting MPLS

9 – Troubleshooting Services

Course Modules


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Additional Optional Modules

Additional Optional Modules are also available:

L2 IEEE OAM & Y.1731

Bidirectional Forwarding Detection (BFD)

Troubleshooting BGP

Troubleshooting Redundancy (i.e. MC-LAG, PseudowireRedundancy, etc.)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Administration

Registration

Facility information

Restrooms

Communications

Materials

Schedule

Introductions

Name and Company Experience

Questions


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



This page has been intentionally left blank.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

www.alcatel-lucent.com

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module 1 — Introduction

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Network and Service Troubleshooting with the 5620 SAM v1.4 Module 1 | 2 All rights reserved © 2013 Alcatel-Lucent

Module Objectives

After successfully completing this module, you should be able todescribe:

The benefits of using 5620 SAM for troubleshooting

The 5620 SAM features that assist troubleshooting

A standardized troubleshooting methodology

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Introduction

Benefits of 5620 SAM as a Troubleshooting Tool

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Benefits of 5620 SAM as a Troubleshooting Tool

View of the entire network

Centralized alarm management

Topology maps to show connectivity and status of links

Ability to view a service end-to-end, rather than a single service site

Ability to use bulk operations on multiple network elements at the same time

Statistics management

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Introduction

Overview of 5620 SAM features that assist in

troubleshooting

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



SAM features commonly used for network troubleshooting

Alarms, status values and GUI object coloring

OAM tools managed with the Service Test Manager (STM)

Topology maps

Physical SDP Service

Navigation Trees

Equipment Routing Service components

Statistics

Policy audits

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Introduction

Troubleshooting Methodology

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



What is required for effective troubleshooting?

Knowledge of the system:

Network architecture Routing protocols Services

Knowledge of available tools

A reasonable/proven, systematic, traceable methodology to follow

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Why use a methodology?

There are too many possible scenarios to have a specific solution ready for each one

The biggest challenge may be discovering what the actual problem is, rather than devising the fix

A standardized approach to troubleshooting is better than a haphazard one

Most troubleshooting situations can be managed by a generic methodology

Some cases require stepping outside a fixed approach

Having a methodology already in place is a good starting point.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Methodology: Troubleshooting Steps

1. Identify the problem/symptoms

Understand the issue Verify the reported issue Establish a baseline Gather information

2. Investigation

Determine the cause

3. Take corrective action (fix)

4. Verification

Troubleshooting is not just diving in and fixing the problem. Complex problems can require a more systematic approach.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




If you lose sight of the real issue or dive into investigation too soon, you may fail to fix the right problem

Requires an understanding of the system and network

Gathering Symptoms vs. Determining the cause

Establish a baseline

Verify reported issue does exist (trust but verify reported information)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



2. Investigation

Requires an understanding of what information is available (or can be generated)

Searching for the problem's cause using 5620 SAM tools

Keep an audit trail

where have you looked?what have you changed during the investigation?

Avoid common pitfalls: unchecked assumptions, red herrings and being stuck on the common path

Be aware of usual suspects, current network’s activities

Searching for the cause

Functional fixation – viewing a specific tool as having only the primary use it was designed for (ever used a screwdriver as a hammer?).

E.g. Ping can be used for more than just testing that an NE is there -> packet size, timings.

The “Acknowledgement info” and “Notes” sub-tabs in the Alarm Info window can be used to record part of the Audit Trail: Where have I looked? Who is looking at the problem? Who was informed? etc.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



3. Take corrective action (fix)

The cause has been established by this point

Plan the solution that will be applied

Apply the fix and keep an audit trail of actions taken (check off steps from the plan)

Audit trail – many changes applied at once may have to be tracked in order to be rolled back.

Ideally, only one thing at a time should be changed.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



4. Verification

Confirm that the problem has been resolved and all symptoms have been accounted for

Revisit the notes from “Identify the Problem”

Perform other cleanup (e.g. service is restored but some alarms may still need to be manually cleared)

Monitor the issue if necessary, depending on the type, complexity and severity of the issue

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Methodology Summary

Phases:

1. Identify the problem/symptoms2. Investigation3. Take corrective action4. Verification

Key points

Knowledge of system, network and tools Audit trail

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Module Summary

Benefits of using the 5620 SAM for troubleshooting

5620 SAM features that assist troubleshooting

Standardized troubleshooting methodology

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module 2 — 5620 SAM Alarms

Module 2- 1Network and Service Troubleshooting with the 5620 SAM v1.4 All Rights Reserved © 2013 Alcatel-Lucent

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module Objectives

After successful completion of this module, you should be able to describe:

The sources of alarms presented by the 5620 SAM

Alarm information

Alarm coloring

How to optimize alarm viewing using the Dynamic Alarm window

How to acknowledge and add notes to alarms

Alarm correlation and suppression

Alarm hierarchy/relationships


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module Objectives (cont.)

Alarm history

Additional text policies

How to monitor service alarms

Best practices for troubleshooting using the 5620 SAM fault management system

Unexpected alarm behaviors


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

5620 SAM Alarms

5620 SAM Alarm Creation


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Alarm Sources

All alarms that appear in the 5620 SAM Alarm window are assembled by the SAM.

There are two sources where information contained in an alarm originates

1. Internal to the 5620 SAM2. External to the 5620 SAM

Internal Alarms are originated by the 5620 SAM itself.

Deal with conditions or activities within the NMS (Network Management System)

External alarms originate from NE events (traps)

From network events to 5620 SAM alarms:

An event happens on the network. For example, a link is cut. A number of traps are generated in

the router. Typically on an SR, there will be at least one link down and an equipment failure trap

on the port.

Traps are generated for other objects on the router associated with the port, such as SAPs or SDPs.

These traps are sent to the active and standby 5620 SAM. The 5620 SAM notes the changes,

generates alarms and, in some cases, resyncs the object. The 5620 SAM alarms are displayed in the

Dynamic Alarm windows and various objects’ fault tabs. The alarms are also used in the 5620 SAM

to show the alarm status of objects in the Equipment tree or the map, for example.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Conditions where alarms may not get created

Trap from NE not received by the 5620 SAM

Trap lost Trap floodNMS network overloaded or down

SNMP trap sequence verification

By default, the 5620 SAM retrieves the last SNMP trap sequence number sent by all network elements every 4 minutes This number is compared to the last sequence number received If they do not match, the 5620 SAM will request only the missing

traps from the required NEs If the 5620 SAM is missing more than 200 traps, or the missing

traps are no longer available, a full resync is requested

See “SNMP trap sequence verification” in the Planning Guide for more info.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Trap Relationship to 5620 SAM Alarms

<date> UTC WARNING: SNMP #2004 Base 1/1/7

"Interface 1/1/7 is not operational"

Log 98 on NE

5620 SAM alarm

Example of what appears in the log 98 of the NE and the resulting alarm created by the 5620 SAM.

Note that there is not always a “one-to-one” correspondence.

When the 5620 SAM receives a trap, it then re-syncs with objects related to the trap and raises additional alarms according to the status of those objects.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

5620 SAM Alarms

Alarms Example #1


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Recall the general troubleshooting steps (from Module 1)

1. Indentify the problem/symptoms

Understand the issue Gather information Establish baseline Verify reported issue

2. Investigation

Determine cause

3. Apply Fix - Take corrective action

4. Verification

Remember to keep an audit trail.

SAM alarms provide acknowledgment and notes can be added to individual alarms to help you track the actions taken for alarms.

Alarms can come into play during steps 1, 2 and 4; however, they are most important during step 2 (Investigation).

For the purpose of this example we will only focus on the investigation step.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Investigation Phase Using Alarms

1. Find/discover an alarm (in Dynamic Alarm window, maps, trees, Properties Forms)

2. Acknowledge alarms to signal that an investigation is underway

3. Determine which alarm to investigate first

4. Examine the details of the alarm

5. If the cause of the issue has not been determined, look at related objects, alarm statistics and Historical alarms


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

5620 SAM Alarms

1. Finding Alarms


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


An Alarm Appears…

An alarm can come to the attention of operators in several ways:

Alarm appears in the Dynamic Alarm window Something changes color in the maps and/or trees Alarm appears in the Faults tab of an object’s Properties form

— Look for Fault Notification Indicators!

- Or -

An operator looks for an alarm because of a problem reported by a customer or OSS system

The color of the alarm indicates the alarm’s severity. Tip: the color associated with a severity can be seen in the Dynamic Alarm window’s Alarm Statistics tab.

Fault Notification Indicators are present in release 10.0 R1 and above. The sub-tabs under the Faults tab have notification capabilities as well.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Finding an Alarm

There are three methods for viewing an alarm

1. Dynamic Alarm window (Filtering, Sorting)2. Faults tab on Object Properties Form (Best Practice)3. Alarm History

If it is not obvious what type of alarm to look for, the Customer and Service information can be used to track down an alarm

Alarms can be tracked down by using the Topology Maps or Navigation trees

Best Practice:

Disable operator ability to purge alarms (5620 SAM User Security)

If it is known which Customer is having the issue: Manage -> Customers (Search for customer and view the “Services” tab).

If it is known which type of service is down: Manage -> Services.

Disable the Update/Execute permissions on “fm.AlarmHistoryDatabase.method.purge” in order to disable an operator’s ability to purge alarms.

(Administration -> Security -> 5620SAM User Security -> Scope of Command).

Hitting the Pause button on the Dynamic Alarm window may be necessary if there is a constant arrival of new alarms. The Pause button does not prevent new alarms from being created, it simply delays adding them to the Dynamic Alarm Window until the Pause button is turned off.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Alarm History

There are three ways to search for historical alarms:

1. Look at the entire history (Tools -> Historical Alarms) and apply a filter.

2. Go directly to the Properties of a suspected object, click on its Faults tab and then click the View Alarm History button.

• This causes a filter to be auto-generated for that object.

3. From the Alarm Info form, click the View Alarm History button.

• This causes a filter to be auto-generated for that object and specific alarm.

Best Practice:

When possible, the 2nd and 3rd methods should be used because they automatically build a filter


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Example – A port/link issue

Scenario: Physical Port Admin Down

The GUI “lights up” in multiple places:

Node icons in Physical and Service Tunnel Topology maps

Equipment and Routing trees

Alarm appears in Dynamic Alarm Window

Fault Notification Indicators


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Dynamic Alarm Window Columns

The Dynamic Alarm window has columns for Name, Probable Cause, and Severity, as well as other fields.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


The Alarm Info Window

The Description under the Details tab may reveal the issue immediately…

Double clicking on an alarm in the Dynamic Alarm Window will open the Alarm Info Window for that alarm.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


The Alarm Info Window (continued)

The Remedial Action under the Details tab may give instructions on how to fix the issue…

Best Practice:

When viewing the alarm info, be sure to note the following attributes: Probable Cause, Additional Text, Description and Remedial Action.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Alarm Information Legend

•Circle indicates aggregated alarm

status

•Square indicates object alarm status

The alarm coloring can been seen by looking at the Alarm Statistics tab of the Dynamic Alarm Window


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Dynamic Alarm Window: Layout alarm table to taste

Sort field order to individual taste

Drag columns in title field

Save layout using right-click menu

Hide unwanted fields

To make the new Dynamic Alarm window configuration default, in the SAM main menu select;

Application -> Save Workspace


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Some Alarm Table Capabilities

Up to 6 alarm windows supported

Quick filter

Type and hit Enter

Advanced filter allows complex search criteria.

Filters can be saved.

Filter by Equipment Group

Multiple Alarm Windows:

This allows operators to monitor alarms in different network areas at the same time, or make each window represent a different level in the object containment hierarchy, e.g. port, LSP, Tunnel, SAP, SDP, Service. This will accelerate troubleshooting.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Alarm Flags

The Monitoring Flag panel under the Alarm Table tab indicates the number of alarms, color-coded by severity, that have been detected since the window has been open OR flag was reset.

The time the last alarm for that severity was detected is also displayed

Show or hide the Monitoring Flag panel using ApplicationUser Preferences menu option

— select/unselect the Show Alarm Flags checkbox

Reset the flag and values by clicking the flag


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Detachable Windows

Provides the ability to move SAM windows, such as the Dynamic Alarm window, outside of the main SAM GUI

Excellent for multi-monitor setups (Dynamic Alarm window and main SAM window on separate monitors)

To move a panel outside the main SAM GUI

Select the desired window to move, and from the main menu click Window Move to External Window

To close all windows outside the main GUI: Window -> Close All External SAM Windows

To close all windows inside the main GUI: Window -> Close All Internal Windows

When opening a child window from an external window, the child window will become an external window as well

Limitation:

Once a panel is moved outside the main GUI, it cannot be brought back in. It must first be closed and then re-opened from within the main GUI.

This feature is only available in 5620 SAM 8.0 R5 and above


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

5620 SAM Alarms

2. Acknowledging Alarms


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Acknowledging an Alarm

Signals to other operators that the alarm is being investigated

Indicates which operator is investigating the alarm in the Acknowledged By alarm field

To take advantage of this, it is a best practice to create separate operator user accounts

Notes can be added to an alarm

Adding notes keeps a revision history, which is a great tool forkeeping an audit trail

Best Practice:

When troubleshooting, be sure to acknowledge all associated alarms.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

5620 SAM Alarms

3. Determine which alarms to investigate first


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Alarm Hierarchy

Alarms are assigned a managed object

These are organized into a hierarchy to help prioritize the significance of alarms

Alarms can be filtered by Object Type

Note: After being assigned a managed object, alarms are further organized by domain. For more information, please view the 5620 SAM 10.0 Troubleshooting Guide

Best Practice:

If multiple alarms are present, the alarm(s) at the lowest MO should be investigated first.

Usually it is obvious where an alarm fits into the hierarchy.

For example, an alarm on a port would be at a lower level than an alarm on a service that uses that port, so investigation should focus on the port issue as it is likely causing the service alarm as well.

•When alarms are raised, they are assigned a managed object and domain

•They fit into a hierarchy of SAM Managed Objects.

•The managed object (Object Type) and domain of an alarm can be seen in the Alarm Info window.

•An alarm’s position in the hierarchy can be determined by looking up the managed object and domain in the SAM Troubleshooting Guide’s “Hierarchy of 5620 SAM-managed objects” if required.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Alarm Hierarchy of Managed Objects

- General network-management or 5620 SAM-related objects- Network- Service- SDP binding- Tunnel- LSP binding- LSP- Session- LDP Interface or Targeted peer- Network Interface- Physical Equipment- SONET/SDH bundle, port or channel- DS1/E1 channel

From the SAM Troubleshooting Guide’s “Hierarchy of 5620 SAM-managed objects”.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Alarms, Object Alarm Status and Operational Status

Aggregation Objects have object and aggregated

alarm status icons The square is the object’s alarm status The circle is the aggregated alarm status

The object’s color on the map is based on its operational status and the alarm with the highest severity

The whole Node icon will go red if it is not reachable by SNMP.

Note that this doesn’t necessarily mean that the node is down; SAM is just indicating that it can’t communicate with it via SNMP.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Equipment Hierarchy: Aggregated Alarm Status

Object alarm on any port causes its parent object’s Aggregation Alarm status.

Node

Shelf

Slot

Card

PortX

Aggregatedalarm status

Object alarm

Aggregated Alarm status allows the operator to view the equipment hierarchy when it is closed, and to drill down to findthe object that is causing the alarm.

Alarms visible at higher levels than the object directly involved.

Alarm aggregation allows the GUI to flag alarms on parent objects.

The Faults tab on the Properties window of any of the parent objects will list the aggregated alarms

‘Aggregated’ does not mean that there’s an alarm at each level; it means that the higher levels have an indicator when there’s an alarm at a lower level.

This helps operators to “drill down” to the cause more quickly.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Service Hierarchy: Aggregated Alarm Status

Service

Site

SAP

Aggregated alarm status

The Aggregated Alarm status indicates when alarms exist within a service component’s hierarchy. Operators can then drill down to find the object that is causing the alarm.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Alarm Association – Affecting/Related Objects

Allows the operator to quickly trace to the lowest level of alarm and see what objects are affected by a given alarm

Best Practice:When both sets of alarms are present, troubleshoot the Affecting alarm first


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Alarm Association – affecting/related objects

Port down causes SAP down (port is shown in equipment hierarchy, and SAP is shown in service hierarchy)

Port SAP

Alarms on related objects

Affecting alarms


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Affecting/Affected/Related objects/Aggregated

Affected Objects tab — objects also affected by this alarm

Affecting Objects tab — objects affecting this alarm

Aggregated – alarms on objects below this object

Alarms on Related Objects

From SAM User’s Guide:

Alarm tab — contains alarm information that includes the object, severity, statistics and acknowledgement status.

Affected Objects tab — contains a list of objects that are affected by the alarm. All alarms list the affected objects, even when correlation alarm suppression is enabled.

Affecting Objects tab — contains a list of objects that directly affect the object in the alarm.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Fault Management

Node

Shelf

Slot

Card

Port

Service

Site

SAPXObject alarm

Object alarmAlarms on Related Objects (i.e. SAPs)

Affecting Alarms (i.e Port)

Aggregatedalarms i.e. port alarm Aggregated

alarmsi.e. SAP alarm


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Alarm Correlation and Suppression

When an object with a lot of dependent objects fails (such as a port), a large number of alarms are created on the dependent objects (such as SAPs on that port)

Without alarm suppression enabled, all of these alarms appear in the alarm window, making it difficult to notice that the parent alarm is the port

Alarm suppression hides the child alarms and shows only the parent alarm


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Network Model Alarm Correlation and Suppression

Network

Node

Shelf

Slot

Card

Port

Service

Site

SAP

LSP

MPLS

Equipment

Service


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


How Alarm Correlation works

Correlation in the 5620 SAM is based on correlation rules that are built into it for each alarm

By default, correlated alarms are not displayed on the Dynamic Alarm window; they can be viewed by drilling into the correlating alarm

The correlating (parent) alarm’s severity reflects the highest severity of either it or its correlated alarms

Images show the object alarm of a Physical port going down and its correlated alarms.

To view all correlated alarms in the Dynamic Alarm window, select the checkbox labeled “Show Correlated Alarms” in the Dynamic Alarm Window.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Correlating Alarm (Parent)

This is a correlating alarm

because the View Correlating

Alarm button is not active


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Correlated Alarm (Child)

This is a correlated alarm

because the View Correlating

Alarm button is active and the

Correlating Alarm ID field

contains the parent alarm

name


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


The Alarm Window shows the number of correlated alarms

The number of correlated alarms is visible in: the Dynamic Alarm window, the Alarm Info window and when alarms appear in lists


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Turning Alarm Correlation/Suppression on/off

You can turn Alarm Correlation/Suppression on by default in the Preferences on a per-operator-position basis.

To view correlated alarms in the Dynamic Alarm window, select the Show Correlated Alarms checkbox

Correlation On

Correlation Off

To Enable/Disable the display of correlated alarms by default in the Dynamic Alarm window:

(Application -> User Preferences -> select Show Correlated Alarms by Default)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Alarm Correlation/Suppression and SAM-O

A 5620 SAM OSS Interface (SAM-O) client can subscribe to JMS messages based on the correlation attribute

Only receives alarms that are not already correlated under another alarmHelps reduce the number of JMS messages going to the OSS

An OSS client can subscribe to all alarms, whether or not they are correlated

JMS - Java Messaging Service

OSS - Operations Support System


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Correlation Hierarchy

A card alarm correlates the port alarms, which correlate the SAP alarms The correlating alarms appear in the Alarm window (the card alarm) The correlated alarms (port and SAP) appear in the Correlated Alarm tab.

Double click the Card alarm to see the window

Node

Shelf

Slot

Card

Port

Service

Site

SAP

X

XObject alarmX

Correlating Alarm

Correlated Alarm


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

5620 SAM Alarms

4. Examine the details of alarms


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


The port appears to be the cause of the problem

Both the Probable Cause and Description attributes show that the port is administratively shutdown


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

5620 SAM Alarms

Example: Link cut on network port


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Example: Network-side Alarms

A VPLS service runs between r5, r1 and r2 over RSVP tunnels

First we make a cut at 1 and observe the alarms. Although the equipment and network interfaces show alarms, the service is not affected because the service tunnel reroutes through r2. Then we make a cut at 2. Equipment and network alarms are generated, and the service goes into an alarm state.

Cut 1

Cut 2


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Before any cable cuts: everything is green, no alarms

Physical Topology


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Before cut 1, LSP goes directly from r5 to r2

(Select Service with ID # 71 -> Tunnel used by mesh-SDP on r5 from r5-r2 properties -> LSPs tab -> Properties of the Dynamic LSP from r5-r2 -> General tab)

(Select Service with ID # 71 -> Tunnel used by mesh-SDP on r5 from r5-r2 properties -> LSPs tab -> Properties of the Dynamic LSP from r5-r2 -> LSP Path Bindings Tab -> Properties of LSP Path Binding -> Actual Path tab)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Cut 1: Equipment and network alarms, but no service alarms

Physical Topology Service Tunnel Topology

VPLS Service Topology


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


The service re-routes the ingress interface from r2 to r1



Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Cut 2: Equipment, network and service alarms


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Service topology and hierarchy after cut 2


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Routing tree after cut 2


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


The service has no ingress interface because both links are down



Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


The physical port shows the impact on other objects in the Alarms on Related Objects tab


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


The network interface shows Object Alarms, Affecting Alarms Alarms on Related Objects alarms

(Routing -> properties of routing network interface “r5-r2” on r5 -> Faults tab)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

5620 SAM Alarms

Investigating Service Alarms


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Investigating Service Alarms Using the Service Manager

Alcatel-Lucent 5620 SAM’s Service Manager provides a useful way to monitor all services to track their health.

The procedure (described in the next slide) does not replace analyzing alarms in the alarm window. It provides another way to track the health of services.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Service Manager: Investigating alarms

Configure the Service Manager to show the Aggregated Alarm Status in an easy viewing position

If required, narrow the search by using a filter

Wording such as Critical in the Aggregated Alarm column indicates the highest severity alarm among the service components

Row color applies to the service’s alarm status

In above image the rows are white because the services are operationally up.

(Manage -> Service -> Services)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Service Manager: Investigating Alarms – State Cause

Open the Service Configuration form and note the State Cause information

To drill further, expand the service navigation tree.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Service Manager: Investigating Alarms – States Tab

From the service navigation tree, click the objects with object alarms (red square)

Go to the States tab, which provides good error information


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Service Manager: Investigating alarms – Faults Tab

The Faults tab of the service shows the mesh binding in a critical state under the aggregated alarms, as everything is under the service.

Open the alarm…


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Service Manager: Investigating Alarms – View Correlating

There is a correlating alarm, so we know this alarm is not the source of the problem

Click on View Correlating Alarm to open it

“If you see it click it”


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Service Manager: Investigating Alarms – Probable Cause

There are no more correlating alarms, so this is as far as the 5620 SAM will take you on this path

View the alarm information, specifically the Probable Cause, Additional Text and Description and Remedial Action attributes


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

5620 SAM Alarms

Tools


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Alarm Tools

Specific alarm policies and configurations

Alarm Squelching Additional Text

Changes to these alarm policies have a global effect


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Global Alarm Policies

Administration -> Alarm Settings

All alarms in 5620 SAM list can be seen under: (Administration -> Alarm Settings -> “Specific” tab)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Specific Alarm Policy Window

If facing a flood of a particular alarm type, select Squelch.

Alarm policies can also be viewed by (Administration -> Alarm Settings -> Specific tab)

An Alarm Info window has a button on the bottom that will open the Specific Policy for the Alarm.

A squelched alarm no longer correlates alarms, nor does it go to the OSS. Other alarms that would have been correlated by the squelched alarm are still generated.

Troubleshooting value - temporary squelching of an alarm (note that this will squelch that type of alarm from all NEs).


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Populating Additional Text

Alarms can be configured to have the Additional Text field populated with specific values.

Displaying associated information within the alarm’s Info tab makes identifying the cause of the problem easier

You must create an Additional Text Policy


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



To create an Additional Text Policy;

1. From the SAM main menu, select Administration -> Alarm Settings

2. Select the Additional Text tab and click the Create button

(Administration -> Alarm Settings -> Additional text)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



3. Select the Domain, Object Type and whether or not to Overwrite existing

4. Select the Additional Text Attributes tab and add the desired attributes and their order by clicking the Create button. Add as many attributes as needed.

5. Click the OK buttons to save the policy

Overwrite existing – some objects have pre-populated Additional Text values. Selecting this option will remove this value and replace it with the one defined by this policy.

Once the above policy is created, any new physical port alarms will include the port’s MTU value in the alarm’s additional text field.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Best Practice:

Select attributes where problems or misconfigurations commonly occur. E.g. MTU Value

If there are particular values set the same across a network and operators are aware of these values, adding them to an additional text policy can allow an operator to easily pinpoint the problem


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

5620 SAM Alarms

Unexpected Behaviors


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Some Counter-Intuitive Cases

1. An object may have an alarm coloring for aggregated objects and yet have no child objects with alarms

2. Implicitly self-clearing vs. non-self-clearing alarms


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


1. Alarms Appearing to Have No Child

In the Navigation tree, an aggregated alarm may be present when no child object in the tree has an alarm.

This is because the Navigation tree is a filter for different viewsWhen you change the view using the drop-down menu - from

Equipment to Routing, for example — the aggregated alarm on the child object may appear Also, the alarmed object may not exist in the Navigation tree

(The Power Supply is an example)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


1. Alarms Appearing to Have No Child

?

Where’s the critical alarm?

View from Equipment Navigation Tree might not show an alarm.

Consider examining the Routing Navigation Tree instead…

Equipment Navigation Tree shows a critical alarm circle, but its source is not visible in the tree.

There are a few options to pursue:

1. Open the Properties of the object, look at its Faults tab and look for Aggregated Alarms (recall that circular icon == aggregated)

Or

2. Since the issue does not appear to be equipment-related, switch to the Routing Navigation Tree.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


2. Implicitly Self-clearing vs. Non-self-clearing Alarms

Implicitly self-clearing alarms will clear when an appropriate trap is received

Non-self-clearing alarms need to be manually cleared

Each alarm has a field that indicates if the alarm is ImplicitlyCleared or not

Example: NodeRebooted alarm


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Auto-Deletion of Non-Self-Clearing Alarms

Can set to auto-delete an alarm after 4, 7, or 30 days

Specified per alarm type

Can be viewed from the Alarm Settings window

This feature is only available in 5620 SAM Release 10.0 R5 and above.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Setting the Auto-Deletion Rule

Select the desired specific alarm and open its policy form

Open the selection box and choose the desired time


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module Summary

The sources of alarms presented by SAM

Alarm information & coloring

Optimizing alarm viewing using the Dynamic Alarm window

Acknowledging and adding notes to alarms

Alarm correlation and suppression

Alarm hierarchy/relationships

Alarm history

Additional Text

Monitoring service alarms

Unexpected alarm behaviors


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module 3 — Navigation Trees

Module 3 - 1Network and Service Troubleshooting with the 5620 SAM v1.4 All Rights Reserved © 2013 Alcatel-Lucent

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Network and Service Troubleshooting with the 5620 SAM v1.4 Module 3 | 2 All Rights Reserved © 2013 Alcatel-Lucent

Module Objectives

After successful completion of this module, you should be able to:

Determine the status of an object from the Equipment Navigation tree

Determine if an IOM or MDA is properly configured

Determine the status of a service from the Service Navigation Tree

Change the view and the root of a view in the Equipment Navigation trees

View the status of L3 protocols in the Routing Navigation tree

Open new Equipment trees at different hierarchy levels


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module Objectives (cont.)

Determine the following information on L3 interfaces:

IP address, Port and Status

Determine if all the interfaces and adjacencies are functional

Derive the status, IP address and neighbor of each interface

Determine if there are alarms on the objects

Identify which instances and areas have been configured

View the type (broadcast or point-to-point) and designated router status of an interface

Use the contextual menus of the trees


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Navigation Trees

Overview


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Navigation Trees

Provide a quick way to view all, or portions of, the network’s equipment, routing instances or services

Allow multiple windows to be opened, with each one capable of showing a different view of the network. These views assist in troubleshooting by allowing the operator to compare objects

Clearly show hierarchy of items

Allow operators to work within the tree, not just view items, through contextual menus

Are dynamically updated so that the alarm status of an object is kept current


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Navigation Tree - Find

Enter text in the Find textbox

Press Enter to perform the search

If multiple instances are found, the arrow buttons are enabled to allow the user to step through each instance


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Navigation Tree – Advanced Find

Click the Binoculars button to open up the Advanced Find window

Enter text into one or more text boxes

Next/Previous buttons appear when multiple matches are found


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Navigation Trees - Contextual Menus

Depending on the tree and the target object, a right-click will cause a contextually-based menu to appear.

Several menu items appear in more than one context: e.g. Resync, Properties


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Equipment Navigation Tree Contextual Group Menu

Right-click on a Group


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Equipment Navigation Tree Contextual Router Menu

Right-click on a router


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Equipment Navigation Tree Contextual Router Menu

On a router -> NE Sessions

Network Element Sessions

Launches a Telnet, SSH or File Browsing session to the router.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Navigation Trees

Equipment Navigation Tree


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Equipment Navigation Tree

Allows you to locate a problem faster

Alarm aggregation helps operators to quickly drill down the Navigation tree to find objects with alarms


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Equipment Navigation Tree – Object Status

Status of slots, cards and ports are easily seen

Helps to determine if an IOM or MDA is properly configured.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Equipment Navigation Tree - Make Root in New Tree

Allows operators to focus on specific branches of the network tree

Opens a new window

In the contextual menu via right-click, select Make Root in New Tree

New window gets created, with the root of that window’s tree being the originating selected object.

Helps manage large lists by letting the operator examine an individual branch.

Can be used to compare two sub-trees by opening multiple new trees.

Trees can then be used to create more new trees.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Equipment Navigation Tree - Make Root

Becomes

Does not open a new window

Within a Navigation Tree window, the root can be changed. No new window is spawned.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Equipment Navigation Tree - Reverting Back to Full Tree

A Navigation Tree window can be reverted back to using the entire network as the root of its displayed tree by clicking on the Make Root At Top Level button.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Navigation Trees

Routing Navigation Tree


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Similar to the Equipment tree

The Routing tree allows operators to quickly navigate through the network’s L3 interfaces and protocols

Alarm indicators are also present


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Routing Navigation Tree – Protocol Instances

For IGP/IRP protocols, alarms are shown below the instance

The IGP/IRP Instances don’t have alarm indicators. Their alarms do appear below them in the tree.

Where is an alarm? Open each high level protocol branch to spot the issue.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Shows:

Enabled protocols on routing instances

Admin Status

Status

Site ID

Partially configured items (in this case the interface “Bogus” and RIP)

In this case, the RIP protocol is enabled, but its status is down. There’s no child of that line in the tree, which suggests that there’s no group/interface assigned to it.

Note: You may see a drop-down key when no child exists. Once the key is clicked, the system will look for a child, not find one, and then remove the key icon. The row above, with No Association, is an example of this, indicating that there’s no associated port.

Good naming conventions help add extra meaning, for example “to75” above indicates that the interface is connected to another router identified by “75.”


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Navigation Trees

Service Component Navigation Tree


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Service Navigation Tree

The overview of an entire service presented in one window can help to quickly determine where a fault exists.

Determine the status of a service from the service’s Navigation Tree. It is located on the Service Properties Form.

(Manage -> Service -> Services -> VPLS #)

Displayed on one screen are: statuses, alarm coloring, the service components that are broken or missing, and key values that commonly need to be compared.

Contextual menus exist for many of the objects presented in this tree to help with configuration and troubleshooting a service.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module Summary

Navigation trees provide a fast way to simultaneously view the attributes of many network objects within a hierarchy.

Attributes such as:

Status and alarm coloring

Configuration

Network Objects:

Physical equipment

Routing

Service components

Many options are available in contextual menus to help investigate and modify network objects:

Make Root, Create, Properties, etc.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module Summary (cont.)

Multiple windows with different views of the same tree can be opened

Trees are dynamically updated


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module 4 — Topology Views

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Network and Service Troubleshooting with the 5600 SAM v1.4 All Rights Reserved © 2013 Alcatel-Lucent Module 4 - 2


Module Objectives


Use the legend

Interpret the icons in the topology map

Find a specific router on the map

Apply filters and configure flat maps

Use the Highlight MTU mismatch tool

Highlight active sessions

Explain various contextual menus of icons

Use the LLDP functionality of the 5620 SAM

Understand extended functionality offered by CPAM

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Map Legends

Topology maps have a button that opens a quick reference window explaining the icons that may appear on the maps

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Show Alarmed Links Only (Physical or Service Tunnel)

Use Show Alarmed Links Only to switch from a normal view of all links to displaying only links that have alarms

Very useful when map is densely populated

Enabled (Yellow)

This is a very useful troubleshooting tool!

In a large network with many links, the display of links may be very dense.

By using Show Alarmed Links Only, links that have potential issues can be found easily.

The button turns yellow when activated.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Show Alarmed Links

Note: only the Alarmed Service tunnel is shown

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Enable Alarm Link Pullout

Use this option to separate alarm links from the link group within the topology window

Enable Alarm Link Pullout - The icon is yellow, and links with associated alarms are displayed separately on the topology map. The link groups containing all links are grey.

This feature is very helpful for monitoring when alarms are cleared on a specific link. Picture a scenario where there is more than one alarmed link in a group and this feature is not enabled. Fixing only one of these would not turn the link group grey, as there are still links with alarms within the group. This may lead the operator into thinking that both or all links are still in an alarmed state.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Show Selected Only

This functionality appears as an option in the right click context menu if one or more routers are selected on the map

Use Ctrl-click to select multiple routers

Very helpful for focusing on a subset of the network

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Finding a Router (Vertex) or a Link

Topology maps have a Find button (binoculars)

Select Find Vertex or Find Link to display a list

The list has the common quick find, filtering and span abilities

From the list, select an item to view and the topology map will switch to that object regardless of which group the object is in

Useful in troubleshooting to find specific objects

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



The Search Field on Topology Maps

The searchable area is limited to the map’s current group

Found items are indicated by a black box.

To search the entire network use Find (binoculars) instead

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Navigate to Object (Topology View)

To find a router in a topology map: from the Properties form, click More Actions Navigate Physical View OR Service Tunnel View

Navigate, located at the bottom of the Properties window, allows the operator to find the router in the Physical or Service Topology map quickly.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Flat Maps

Allow operators to create and save filtered views of the network

Can display up to 1000 objects

Display the Physical or Service Tunnel topology

Can create simpler views of a large number of network objects or link groups

Display icons at a reduced size, with thinner link lines, and no object information displayed

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Flat Maps – Viewing Objects Across Groups

Provides a complete network view without topology groups

Physical Topology

Flat Map

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Overview Button

Opens an overview window that has the current map’s view marked on it

• Click and hold anywhere in the box to move

• Click, hold and drag one of the yellow squares in the corners to resize

Click and hold anywhere in the box, then drag to move.

Click, hold and drag one of the yellow squares in the corners to resize.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Highlight MTU Mismatch

Right-click on Physical Topology map and select Highlight MTU Mismatch

Shows differences in physical port MTU only

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Highlight Sessions

Applies to the current Physical Topology window

The sessions are preserved only until the topology window is closed

Highlight MTU Mismatch, for example

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Highlight Sessions (cont.)

Right-click on a session to:

Delete the session

Show Only Highlighted helps to view links on dense maps

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



User Preferences - Topology

Some Topology icons have two text labels that can be configured to display various fields.

A common practice is to set/change the 2nd text label of NEs when performing different activities.

• Application User Preferences

For example, the 2nd text field can be used to display the Location or Management IP address.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Global Info Tables

You can create an information table configuration for all map objects, selected map objects, or map highlights

Ability to quickly see some chosen values

“Header” option allows the user to enable or disable the viewing of the table header information.

“Mouse” option enables the viewing of the Info Table on object mouse-over only

• This is the preferred method, as turning Info Tables on permanently can sometimes clutter topology windows.

Excellent tool to quickly view multiple router values at once without having to search through the router’s Properties form.

Also great for viewing the same value over multiple routers without having to launch multiple Properties forms.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Global Info Tables Creation

Click the Global Info Tables button, then select Configure…

1

3

2

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Global Info Tables (cont.)

From the Global Info Tables button, select which table to enable.

This will apply the selected table globally

Mouse-over the NE to view the Info Table

Right-click on the NE to enable/disable or change the Info Table for that specific NE only

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Physical Topology: Contextual Menu

Right-click on a router

Also present in the Service Tunnel Topology

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Layout

Clicking the layout button can help with cluttered topology views

Before

After

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Spawn Navigation Tree from Topology Map

Right-click on a group or node and select Make Root in New Tree to open a new equipment tree

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Physical Topology Filter

The Physical Topology can have filters applied to it

Filters can be saved

Span can also be enabled on a filter

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Physical Topology Filter

Example: a filter to show routers that are in the Maintenance OLC state

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Physical Links and LLDP

Link Layer Discovery Protocol (LLDP) is a neighbor-discovery protocol that allows a network access device to advertise its identity and capabilities to other stations attached to the same physical LAN

LLDP is enabled at the system and physical port levels

A red link may mean that the LLDP session is down, not that the actual link is down (remote peer not working)

Link Layer Discovery Protocol is a not a routing protocol, but rather a neighbor-discovery protocol. As such, it is configured in a different manner than the standard routing protocols. LLDP allows a network access device to advertise its identity and capabilities to other stations attached to the same physical IEEE 801 LAN. It also permits information that the devices discover about peer devices to be stored. LLDP is only applicable for devices using Ethernet connectivity.

5620 SAM uses the information stored in the applicable LLDP tables on the router to automatically discover the physical topology in the network. You can use this information to examine the L1/L2 topology and perform appropriate diagnostics and troubleshooting.

There are two ways for links to appear in the topology map: discovered via LLDP, and manually created in the GUI.

Manual Physical Link creation (Right-click on Physical Topology map -> Equipment -> Create Physical Link)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



LLDP and Discovered Physical Links

Physical Links discovered via LLDP have “LLDP” in their “Link Discovered from:” field in their Properties window

5620 SAM refers to LLDP links as Discovered Physical Links whilemanually added links are referred to as Physical Links

The Find button “Find Link” on the Topology Map offers two pre-defined filters in its search: “Discovered Physical Links” and “Physical Links”

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



LLDP Remote Peers

Displays a list of LLDP remote peers associated with a particular network element.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



LLDP Reference Menu

Right-clicking in the topology window will bring up the Reference menu options

Once LLDP timers expire

Becomes

On the physical topology map background, the Reference option takes a snapshot of the physical topology at a specific time. Any deviation from this checkpoint can then be subsequently shown. You can choose from the following options:

Reference all Discovered Links in NE Group - checkpoints all currently discovered links that exist. Any object that was previously checkpointed and found to be operationally down is left untouched. Any object that goes operationally down in the future is not removed, but is simply marked as operationally down.

Clear Reference for All Discovered Links in NE Group - clears all object checkpoints. Any object that is operationally down (shown as a red link) is removed from the database. Any non-checkpointed object that becomes operationally down in the future is removed from the system.

Cleanup all Discovered Links in NE Group - keeps the current checkpoint set for objects that are operationally up, but removes checkpoints from objects that are operationally down. This is the same as the Clear Reference for All Discovered Links in NE Group option, but only affects operationally down objects.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



LLDP Reference Single Links

SAM can reference individual links as opposed to all links in a group

Executed from the Discovered Physical Link properties form

This feature is only available in SAM R9.0 R7 or greater.

The Discovered Physical Link properties form also indicates:

If the link was referenced

When it was discovered and referenced

Which user referenced the link

If LLDP is disabled, when it was disabled

Clearing the reference also clears the User and Reference Time fields

The Discovery Time is unaffected by clearing the reference

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



LLDP Multi Selection of Reference Links

Allows the reference of multiple selected discovered physical links as opposed to all the links in a group

Use shift-click to select multiple links groups within a topology group

This feature is only available in SAM R10.0 R3 or greater.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



LLDP Labels

5620 SAM is able to display LLDP labels (name/description) instead of just the MAC address for an unmanaged router that is running LLDP

Gives meaningful names to unmanaged routers

Configured by selecting the required LLDP TLVs

For both nodes:

Notifications can be true or false.

Transmit Management Address can be Enabled or Disabled.

Any additional TLVs can be selected.

This feature is only available in 5620 SAM 8.0 R5 and above.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



LLDP Labels

Without Labels With Labels- System Name TLV

Th

is A

LU

-IP

D-S

RC

Alc

ate

l-L

uce

nt_

Ne

two

rk_

an

d_

Se

rvic

e_

Tro

ub

lesh

oo

tin

g_

wit

h_

the

_5

62

0_

SA

M G

uid

e is

fo

r e

xclu

sive

use

of

Ka

zi_

Zia

l_H

oq

ue

- W

IND

_M

ob

ile

Ka

zi_

Zia

l_H

oq

ue

- W

IND

_M

ob

ile



Module Summary: Troubleshooting Benefits of Topology Maps

Maps can be filtered to give operators a more targeted view

Help to quickly find an object within the network using search functionalities

Topology maps provide specific features to reveal issues in the network such as MTU Mismatch and Highlight Alarmed links/tunnels

Maps display object status with colors and changing icons

Make Root feature offers easy navigation in the tree

Groups allow organization of the network view as well as the ability to zoom in and out

LLDP Configuration allows enhanced physical link monitoring/troubleshooting

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module 5 — Service Test Manager (STM)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 2


Module Objectives


View and configure STM parameters

View, analyze and compare test results

List steps taken to auto generate and schedule tests

Use event logs and alarms in OAM tests

Network and Service Troubleshooting with the 5620 SAM v1.4 All rights reserved © 2013 Alcatel-Lucent

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Service Test Manager

This module describes how STM in 5620 SAM can

be used to troubleshoot common issues.

Network and Service Troubleshooting with the 5620 SAM v1.4 All rights reserved © 2013 Alcatel-Lucent Module 5 - 3

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Overview


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 5


Overview

Provides the ability to execute various OAM (Operation, Administration and Maintenance) tests for network troubleshooting

In order to verify that a service is operational, a set of packet-based OAM tools is required

Can be performed on a per-service basis

For in-band testing, the OAM packets closely resemble customer packets

There are diagnostics for LSPs, SDPs, and Services

For in-band testing, the OAM packets closely resemble customer packets, but are distinguishable from customer packets so they are kept within the service provider’s network and not forwarded to the customer.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 6


Creation and Management

Can configure and manage OAM tests:

From the Properties forms on network objects, for example, LSP pings from the LSP Properties form From the Tools -> Service Test Manager (STM) form From the Service Topology

Best practice:

Create and/or execute tests by viewing the Properties form of the specific object that is being tested and selecting the Tests tab. When creating tests for Services, use the Service Topology Window.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 7


OAM from the Service Topology

OAM Tests can be fully configured from the Service Topology window

Test results can also be displayed in an Info Table

To enable the OAM menu options, select the OAM checkbox

Right-click on a service site to open the menu

1

2

3

4

Create a new test

Once the test is completed, the results are displayed in an Info Table

ORSelect a previously created test

This feature is only available in 5620 SAM Release 8.0 R5 and above.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 8


Service Assurance OAM Test Types and Objects

The following is a list of supported OAM test types and the objects each test can be performed against:

This chart is from the 5620 SAM User Guide.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 9


Service Assurance OAM Test Types and Objects (cont.)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 10


Service Assurance OAM Test Types and Objects (cont.)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


OAM Tests for Troubleshooting


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 12


Service Site Ping (svc-ping)

Tests a service ID for correct and consistent provisioning between two service endpoints

This test verifies:

Local and remote service sites exist The current state of the local and remote service sites Local and remote service types are correlated The same customer is associated with both local and remote

service Local and remote ingress and egress service labels match There is a service-to-SDP binding association at both local and

remote service sites

Test Initiated from one Service Edge router.

Used to verify full roundtrip and delay.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 13


MTU Ping (sdp-mtu)

Performs in-band MTU path tests on an SDP to determine the largest path-MTU supported on a service tunnel (SDP), within one byte

It is important to understand the MTU of the entire path end-to-end when provisioning services that must support the ability to transmit the largest customer packet

MTU – Maximum Transmission Unit


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 14


Tunnel Ping (sdp-ping)

Performs in-band unidirectional or roundtrip connectivity tests on SDPs

Follows the same path as traffic within the service

For roundtrip tunnel ping, the Return Tunnel ID must be specified or a unidirectional SDP test is performed

For a unidirectional test:

• The egress SDP’s encapsulation

• Ability to reach the far-end IP address of the SDP within the SDP encapsulation

• Path MTU to the far-end IP address over the SDP

• Verifies Forwarding class mapping between the near-end SDP encapsulation and the far-end tunnel termination

• Determine whether SLA delay metrics are met

SDP roundtrip testing extends SDP unidirectional tests with the additional ability to test:

• The remote SDP’s encapsulation

• Potential service roundtrip time

• Roundtrip path MTU

• Roundtrip forwarding class mapping


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 15


Performs in-band VLL connectivity tests

Works with third-party NEs

The packets are sent using the same encapsulation and along the same path as user packets in the VLL

Provides a check of both the control and data plane

VCCV Ping (vccv-ping) and Trace (vccv-trace)

PE2 (third-party switch)

VLL Service

SAP to CE1

SAP to CE2

VCCV echo request

VCCV echo reply

PE1

VCCV Trace - Displays the hop-by-hop path used by the VLL

In this example:

• The ping test packet or packets are sent with the destination IP address of PE2

• The request is encapsulated in a VLL packet and is forwarded to PE2

• PE2 replies to the source device IP address

Difference between sdp-ping and vccv-ping?

- sdp-ping only works with 7x50 equipment, but vccv-ping works with third party NEs

- vccv-ping asks to assign a spoke-SDP ONLY

VCCV- ping message format is similar to LSP-ping, but the functionality is closer to an sdp-ping on 7x50.

Dedicated control channel between pseudowire endpoints for VCCV messaging.

Three ways of sending VCCV messages:

1. In-band connectivity testing using Control Word

2. In-band connectivity testing using pseudowire TTL label

Set the TTL in the VC label (inner label) to 1

3. Out-of-band using Router Alert Label

VCCV - Virtual Circuit Connection Verification


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 16


ICMP Ping (icmp-ping) and Trace (icmp-trace)

Identify the reachability of a remote host across the IP network

Can be used together to detect and localize faults in IP networks

Ping

Can be used from a VRF (Virtual Routing and Forwarding) site of the subscriber’s VPRN service to determine the existence of the far-end egress point

Trace

Displays hop-by-hop path for a destination IP address Allows target types of Core Routing Site or VPRN Site

Can be sent in-band or out-of-band

VRF -> virtual routing and forwarding - A logical or virtual routing function with associated routing table that can be instantiated in a device capable of supporting IP VPN services.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 17


LSP Ping (lsp-ping)

Performs in-band LSP connectivity tests

Tests whether the LSP tunnels are working in both directions

Provides two functions: MPLS ping and MPLS traceroute

MPLS ping verifies whether the packet reaches the egress LER

Ingress LER (Originating

SR)

LSP LSP LSP

Egress LER (terminating

device of the LSP)

LSP Ping

request

LSP Ping reply

In this example:

• The originating router creates an MPLS echo request packet for the LSP and MPLS path to be tested

• The MPLS echo request packet is sent and awaits an MPLS echo reply packet from the router that terminates the LSP

• The LSP status is displayed when the MPLS echo reply packet is received

• Modeled after the ICMP echo request/reply to detect and localize faults in IP networks


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 18


LSP Trace (lsp-trace)

Displays the hop-by-hop path used by the LSP

Ingress LER (Originating

SR)

LSP LSP LSP

Egress LER (terminating

device of the LSP)

LSP Trace request

LSP Trace replies

LSP T LSP T

In this example:

• The originating router creates an MPLS echo request for the LSP to be tested

• Packet contains increasing TTL values

• The MPLS echo request packet is sent and waits for a TTL exceeded response or the MPLS echo reply packet from the router that terminates the LSP

• Each device along the hop-by-hop route replies to the MPLS echo request packets with TTL and MPLS echo reply information


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 19


Example - LSP Trace

Run an OAM LSP trace test on Dynamic LSP “r2-r4-r3-r1-#2”


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 20


MAC Populate (mac-populate)

Checks the accuracy of the FIB table by testing forwarding plane correctness

Populates a service FIB with an OAM-tagged MAC entry This MAC entry indicates that the router is the egress address of

the service

Sends a message by flooding the domain to learn a MAC address

This test can:

Force an existing MAC address to become OAM-tagged Distinguish MAC addresses that are OAM-tagged Age an OAM-tagged MAC address


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 21


MAC Populate (cont.)

Specify if you want to flood this OAM-tagged MAC address to other devices, so that the same OAM-tagged entry is added to the FIB tables of other devices

FIB entries must be resynced through SAM before they can be viewed. Be sure to click the Resync button on the right side of the panel before viewing any FIB entries.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 22


MAC Ping (mac-ping) and Trace (mac-trace)

Ping

Tests connectivity in a VLL or VPLS by verifying a remote MAC address at the far-end of a service

Trace

Displays the hop-by-hop route of MAC addresses used to reach the target MAC address at the far-end of a service

For both tests, one must specify either the far target (far-end) MAC address or the broadcast address

MAC-PING

— For in-band:

–The ping packet goes across each hop, and when it reaches the egress router, it is identified by the OAM label and the response is sent back along the management plane

— For out-of-band:

–The ping is forwarded along the flooding domain when no MAC address bindings exist, or is sent along the bindings if MAC address bindings do exist

–A response ping is sent from the far-end device when there is an egress binding for the service

MAC-TRACE

— For in-band:

–The trace request contains tunnel encapsulation, VC label, OAM, and other information

–For known-destination MAC address, the appropriate tunnel encapsulation and VC label is used

–Otherwise, the packet is sent to all service tunnels, including all necessary tunnel encapsulation and egress VC labels for each bound service tunnel

— For out-of-band:

–The destination IP address is specified by mapping the destination MAC address

–If the destination MAC address is known to be a specific site, the far-end IP address of the service tunnel is used

–Otherwise, the packet is sent to all service tunnels in the service.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 23


MAC Purge (mac-purge)

Deletes an OAM-tagged entry from a FIB, which was generated using the MAC populate test

Allows one to do a controlled OAM test without the learning induced by customer packets

The purge can also tell the control plane to not allow further learning from customer packets


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 24


CPE Ping (cpe-ping)

Traces end-to-end switching of specified MAC address of customer premises equipment

Can detect an end-station IP address inside a VPLS

Each peer PE within the VPLS context will trigger an ARP requestfor the specific IP address The PE receiving a response to this ARP request will report back

to the requesting device

CPE Ping request (Destination 5.5.5.187)

CPE Ping reply

SAP

CPE Ping reply

The MAC ping OAM tool makes it possible to detect whether a particular MAC address has been learned in a VPLS.

The CPE Ping extends this capability to detecting end-station IP addresses inside a VPLS.

Important to use non-existent source address so customer ARP cache is not polluted with an invalid ARP entry.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


OAM Test Parameter Configuration


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 26


Common OAM Test Parameters

General – configures general settings of the test and 5620 SAM managed objects when tests are to be run

IDName Description Administrative StateNE Persistent – if enabled, the OAM test is deployed to a router

after the first run and it remains on the router in memory onlyNE Schedulable - specifies whether the associated OAM test, or

the test suite generated from the policy, can be scheduled and run on managed NEs (default = disabled)

General tab –

ID – specifies a unique numeric identifier for the created object (by default set to auto-assign ID)

Name – specifies the name of an object

Description – specifies a description for the created object

Administrative State – specifies whether the object can be put in service

NE Schedulable

— If enabled, “Ignore Probe Results” and “Lightweight Execution” parameters are configured and the test is deployed to the NE

– Ignore Probe Results - specifies that the 5620 SAM ignores all test probe result records (default = disabled)

– Lightweight Execution - specifies that the 5620 SAM only displays results for tests that fail, generate threshold crossing alarms, or time out (default = disabled). When enabled, the “Ignore Probe Results” and “Trap Generation” parameters options are enabled


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 27



Test Parameters – configures details on how the test should be run and determines test packet settings (different options are available for different type of tests)

Execute Details— Number of Test Probes— Probe Interval (s)

— Probe Timeout (s)

Test Probe— Size (octets)— Time To Live

— Forwarding Class

— Forwarding Profile

Test Parameters tab -

• Execute Details

— Number of Test Probes - specifies the number of OAM probes to send

— Probe Interval (s) – specifies how often, in seconds, to send a probe

— Probe Timeout (s) – specifies how soon, in seconds, a message request times out and is aborted

• Test Probe

— Size (octets) – specifies the OAM packet size, in octets, of the probe for a trace diagnostic

— Time To Live – specifies the TTL value, in hops, that is added to the test packet to ensure that the packet does not circulate in a routing loop past the configured time

— Forwarding Class – specifies the forwarding class for OAM packets (default = be)

— Forwarding Profile - specifies whether the test packets are in or out of profile, ascompared to the forwarding class of the test packet


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 28



Result Configuration – configures details regarding how results should be reported

Test Failure Threshold Probe Failure Threshold Trap Generation

— The options are– Test Completion (default)

– Test Failure – Probe Failure

– Path Change

Result Configuration tab -

• Test Failure Threshold - specifies the number of test failures that occur before a router sends a trap about the test failure (default = 1)

• Probe Failure Threshold – specifies the number of times a probe can fail before the test fails. The parameter has no effect if the value is higher than the Number of Test Probes parameter value

• Trap Generation - specifies the conditions under which a device sends a trap or raises an alarm during an OAM test. Multiple options can be selected, but not all options are available for every type of test. The options are

– Test Completion (default)

– Test Failure

– Probe Failure

– Path Change


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 29



NM Threshold – configures NM threshold-crossing alarms for OAM tests that are non-NE-schedulable. An alarm is raised when an NM threshold is crossed, either because the value rose above or fell below the configured level

Type— Inbound Jitter (default) - Inbound Loss - Inbound Latency— Outbound Jitter - Outbound Loss - Outbound Latency

— Roundtrip Jitter - Roundtrip Loss - Roundtrip Latency

Generate Alarm on Rising Threshold Clear Alarm on Failing ThresholdUpdate Test Result Status Include Falling Threshold

“NE Threshold” tab -

Type – specifies which type of threshold crossing event generates an alarm. The options are:

– Inbound Jitter (default) - Inbound Loss - Inbound Latency

– Outbound Jitter - Outbound Loss - Outbound Latency

– Roundtrip Jitter - Roundtrip Loss - Roundtrip Latency

Generate Alarm on Rising Threshold – specifies whether to raise a threshold-crossing alarm when a rising threshold is crossed (default = enabled). The values can be set under the “NM Rising Threshold” tab

Clear Alarm on Failing Threshold - specifies whether to clear a threshold-crossing alarm when a falling threshold is crossed and the threshold condition no longer exists (default = disabled). The values can be set under the “NM Falling Threshold” tab

Update Test Result Status – specifies whether the Threshold Crossing Event should change the test result status (default = disabled)

Include Falling Threshold – specifies whether to generate a threshold-crossing alarm for an OAM test if the value falls below a specified level


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Comparing Test Results


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 31


STM Results Comparison

Two results of the same test type can be compared

Search and Find the results in the STM list window

Select the desired test results and click the Compare button

The comparison form opens with each difference highlighted


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Test Suites and Troubleshooting


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 33


Test Suites

The 5620 SAM STM provides the ability to group various OAM tests into test suites for network troubleshooting

These tests are combined based on the Entity Type parameter Allows automatic generation of tests based on

a test policy Can set a suite to be used for service

validation Can be scheduled to provide continual

performance feedback

Best practice:

Create at least one test suite for each Entity Type for validation and troubleshooting purposes

(Entity Type: Tools -> Service Test Manager -> Create -> Test Suite -> General tab)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 34


Test Suites

First-run tests

Execute before the tests in the other groupsMight typically include high-level diagnostics, such as a service

site ping or VPRN ping

Generated tests

Created by the 5620 SAM for use against a specific network entityWhen there is a change in the configuration of a network entity,

such as a service, one must regenerate the generated tests that apply to that entity

Last-run tests

Executes after the tests in the other groupsMight typically include transport-layer diagnostics, such as an

LSP trace or a tunnel ping


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 35


Test Policy

Contains a set of test definitions and pre- and post-processing rules

Applies to only one test suite, and a test suite can have only one associated test policy

Parameters can be configured to display test results only if a test fails or generates a threshold crossing alarm (Lightweight Tests)

Allows enabling of OAM test results to be stored in XML files

File can be stored on the server, written to the DB, or bothMust create an Accounting Policy with Type = NE Schedulable

Tests

The Lightweight Execution parameter specifies that the 5620 SAM only displays results for tests that fail, generate threshold crossing alarms, or time out. The options are:

• Disabled (default)

• Enabled

This can substantially reduce the amount of test data that the 5620 SAM needs to collect. When enabling, make sure to select the “Lightweight Execution” AND “Ignore Probe Results” checkboxes.

When the parameter is enabled, the Ignore Probe Results (ignoreResults) parameter is enabled and the Trap Generation (trapGenerationPolicy) parameter options are enabled.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 36


Saving Results to an XML File

Tools -> Statistics -> Accounting Policies

Tools -> Service Test Manager -> Create -> Test Policy


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 37


STM Scalability

Please see the 5620 SAM 10.0 R5 Planning Guide for more scalability information, such as “Guidelines for maximizing STM text execution.”


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 38


STM Scalability

By default, 5620 SAM will only allow test suites with a combined weight of 80,000 or less to run concurrently

Test suite weights are identified in the 5620 SAM GUI’s Test Suites List window

If too many tests are run concurrently and this limit is exceeded, tests will be skipped


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 39


Test Policy and 5650 CPAM

In 5650 CPAM:

Auto-OAM feature allows the operator to assign an appropriate STM test policy to an IP / LSP Path Monitor The tests defined in the policy are then executed whenever the

path reroutes

This is a great tool for automatic monitoring and test execution!

(Tools -> Service Test Manager -> Create -> Test Suite -> General tab).


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 40


Validating Tunnels (SDPs) Using Test Suite

Validate newly created tunnels to

Ensure it is operationally up Ensure roundtrip connectivity Raise an alarm if rising roundtrip latency on the SDPs is greater

then 10 milliseconds Ensure correct hops are taken by the LSPs

r6r5

Uni-directional Tunnels

ID 59

ID 60


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 41


Validate Tunnel (1. Identify)

Symptoms:

Tunnels (SDP) are operationally up LSPs have been assigned

(Manage -> Service Tunnels -> Tunnel).


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 42


Validate Tunnel (2. Investigation)

Are there any open alarms?

None

Is the State Cause clear?

Yes

No fault indicator

(Manage -> Service Tunnels -> Tunnel -> General Tab -> State cause)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 43



Check roundtrip connectivity between routers r5 and r6

Use Tunnel Ping to check the roundtrip connectivity

(Manage -> Service Tunnels -> Tunnel -> Tests -> Tunnel Ping)

To check for round-trip connectivity, the Return Tunnel ID must be set.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 44



Check roundtrip latency is not greater then 2 milliseconds

Can be checked by testing roundtrip latency from NM Threshold

(Manage -> Service Tunnels -> Tunnel -> Tests -> Tunnel Ping)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 45


Validate Tunnel (2. Investigation) (Optional)

Escalate the severity of SasThresholdExceeded Alarm from Major to Critical if it is seen more than 3 times in 24 hours

This policy will apply to all the SasThresholdExceeded alarms for every test where the SAS threshold is being tested.

(Administration -> Alarm Settings -> Specific)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 46


Validate Tunnel (2. Investigation) (Optional)

De-escalate the severity of SasThresholdExceeded Alarm from Critical back to Major if it is not seen more than 3 times in 24 hours

(Administration -> Alarm Settings -> Specific)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 47



Result of Tunnel Ping with roundtrip latency

Roundtrip latency threshold is crossed


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 48



Alarms are raised as a result of roundtrip latency crossing the threshold:

SasThresholdExceeded alarm might have Critical severity because of the escalation policy configured earlier.

(Dynamic Alarm window)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 49



Verify LSP hops

Can be checked by running LSP trace on the LSP associated with this tunnel

(Manage -> Service Tunnels -> Tunnel -> LSPs tab -> Dynamic LSP -> Tests -> LSP Trace)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 50



Result of LSP trace


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 51


Validate Tunnel (3. Fix)

There is no problem with the newly-created tunnel’s round-trip connectivity or LSP hops

Alarm was raised when roundtrip latency threshold in the Tunnel Ping test was higher then 2 milliseconds


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 52


Validate Tunnel (4. Verify)

You can create a tunnel (SDP) test suite to test/validate all the existing or newly created tunnels:

First create a test suite and select the Validation Test Suite option


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 53



Assign a Test Policy; in this example the Test Policy defines a Tunnel Ping

Assign all the tunnels to be tested in Tested Entities

(Tools -> Service Test Manager -> Test Suite -> Test Policy)


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 54



Generate tests for all assigned tested entities


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 55



Assign the test suite to Tunnel (SDP) for validation


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 56


Troubleshooting Services Using OAM (LAB 5.1)

A newly created VPLS service with mesh-SDP from r1 to r3 does not become active (operationally up)

1. Find the cause of the problem, but do not fix it

r3r1

VPLS Service


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 57


Troubleshooting Services Using OAM (LAB 5.1)

The cause of the problem is that the size of the tunnel from r1 to r3 has the MTU size too low at 1512

2. Using MTU ping, find the maximum MTU size available for the tunnel

The lab equipment (sims) has these characteristics:

GRE SDP

Default MTU = 1536

MTU ping = 1536

Port MTU - overhead = 1578 – 42 = 1536

Where overhead = 14 (Ethernet) + 20 (IP header) + 4 (GRE header) + 4 (service label)

MPLS SDP

Default MTU without FRR = 1556

MTU ping = 1556

Port MTU – overhead = 1578 – 22 = 1556

Where overhead = 14 (Ethernet) + 8 (two MPLS labels).


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 58


Monitoring Services Using OAM (LAB 5.2)

Configure the 5620 SAM to monitor a VPLS service and raise an alarm when the roundtrip latency between a VPLS site and the connected CPE device rises above a specified threshold.

1. Create a scheduled CPE ping test suite for VPLS 31 that periodically measures the Roundtrip Latency between each VPLS site and an enddevice (in this case the CPE is the Traffic Generator). Set a Roundtrip Latency Rising Threshold equal to 2 milliseconds.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Summary


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 5 - 60


Benefits of Using STM in 5620 SAM

Provides the ability to group OAM diagnostic tests into test suites for more comprehensive fault monitoring and troubleshooting

A test suite can perform end-to-end testing of a customer service and the underlying network transport elements

Test suites are especially useful when multiple objects of the same type require testing

Test suites can be scheduled to run on a regular basis to provide continual network performance feedback


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module 6 — Statistics for Troubleshooting

Module 6 - 1 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Module Objectives


View Performance and Accounting Statistics

Enable the Collection of Statistics

Configure different statistics policies

Explain the difference between Performance, Accounting and 5620 SAM Server Performance Statistics

Explain the difference between on-demand and scheduled statistics

Use the Plotter for Real-Time and/or Historical Statistics

Use Statistics to troubleshoot common network issues

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Statistics for Troubleshooting

This module describes how 5620 SAM Statistics

can be used to troubleshoot common network

issues.

Module 6 - 3 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Collection

Polling MIB counters for Performance Statistics

SNMP

Transferring accounting files from NEs for Accounting Statistics

FTP or SCP

Internal collection for 5620 SAM Server Performance Statistics

Internal on each server

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Policy Types

Accounting policy: defines record statistics type and collection interval

Storage criteria

File policy - for accounting stats on NEs

Statistics policy - for stats on 5620 SAM

MIB statistics policy used for managing Performance Statistics

NE MIB statistics policy—All objects on the NE that use the MIB entry

– e.g. All L2 and L3 SAPs

Specific MIB statistics policy—Specified objects on the NE that use the MIB entry

– e.g. only selected L2 or L3 SAPs

Server performance stats policy for 5620 SAM server stats

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Characteristics of Statistics Types

Characteristic

Statistics Type

Performance Accounting Server Performance

Typical use NE troubleshooting Trend analysis &

troubleshooting

5620 SAM server

troubleshooting

Source NE MIBs NE XML files and

MIBs

Internal 5620 SAM

server data

On-demand Yes Yes if MIB-based Yes

Scheduled Specific or general

collection policy

File and accounting

policy

Collection policy

Real-Time Graph Yes Yes if MIB-based Yes

Collection default Off Off On, 15-min intervals

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Performance vs Accounting Statistics

When viewing statistical records from an object’s Properties form, a user can quickly tell whether it is Performance or Accounting

Accounting (XML file, non MIB-based) stats do not have the option to collect on-demand, so there are no Collect or Collect All buttons

Performance (NE MIB) stats have the option to collect on-demand

Collect - do a one-time collection for the type of statistic selected in the drop down for this particular object

Collect All - do a one-time collection for ALL performance statistics on this particular object

Module 6 - 7 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting Using Statistics

Traffic flows

Dropped packets

Forwarding Classes

---

5620 SAM Server Node Resync issues

5620 SAM Server Memory usage

5620 SAM Server SNMP Traps missing

5620 SAM Server Statistics collection failure

---

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Policy Configuration

Tools -> Statistics gives access to the configuration forms for all policies. Statistics policies are also accessed via the Statistics Record window and the Statistics Browser.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



NE MIB Statistics Policy

Per Product type and release (use filter)

Different MIBs

Polling interval can be set to a minimum of 5 minutes

Applies to all objects on a router (Eg. All GigE ports)

(Tools -> Statistics -> MIB policies -> NE MIB Statistics Policy)

Module 6 - 10 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Specific MIB Statistics Policy

Per product type and release

Different MIBs per Class (see Statistics Guide for more info)

Polling interval minimum: 5 minutes

Specific objects on a router (e.g. Only 1 out of 10 GigE ports)

Statistics Guide has all MIBs linked to the different Classes.

One Class can link to different MIBs, each MIB can be activated separately.

(Tools -> Statistics -> MIB policies -> Specific MIB Statistics Policy)

Module 6 - 11 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Example of an NE MIB Statistics Policy (1/2)

Each port will have statistics collected

This will put extra load on the router, so it is better to use aSpecific MIB Statistics Policy

Assigned to an NE either by clicking Assign Sites, shown in the image above, or through the discovery rule in the 5620 SAM Discovery Manager.

(Tools -> Statistics -> MIB policies -> NE MIB Statistics Policy)

Module 6 - 12 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Example of an NE MIB Statistics Policy (2/2)

Statistics will show up under the Statistics tab of each physical port.

Module 6 - 13 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Statistics will only be collected from the selected port

Direct link from Statistics Policy to monitored object (in this case a port)

Example of a Specific MIB Statistics Policy

(Tools -> Statistics -> MIB policies -> Specific MIB Statistics Policy)

Module 6 - 14 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Statistics Manager

Tools -> Statistics Manager

Per Object Type :

View the current collected data

View the actual Statistics Records (Historical)

View and configure the Statistics Policy

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Accessing the Plotter

In the Statistics tab of an object, you’ll find a link to the Plotter

Can use the link in the Tools menu and paste the monitored object from the clipboard

12

3

(Object Properties form -> Statistics tab)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Accessing the Plotter (continued)

Launch the plotter directly from the navigation tree

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Using the Plotter

Update the Group and Counter to meet your requirements

The plotter interval can be selected

If you already have statistics collected for the object, you canget a Historical Plot

The user can save the plotted data to a file in either tabular (.CSV/HTML file) or graphical format (.JPG/PNG file).

To save the tabular data, right-click on the table header and select Save to File option.

To save the current view of the graph, click on the Save Current View button on the toolbar.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Statistics Plotter Profiles

Allows users to save a statistics plotter configuration

Easy access of the same plot at a later time

Once a plotter configuration is complete, click the Save Profile(s) button

Module 6 - 19 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Launching Statistics Plotter Profiles

After a profile has been saved, it can be loaded from the Properties form of objects matching the profile type

Module 6 - 20 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Statistics Plotter Profiles Management

Statistics plotter profiles are managed through the Tools Statistics Statistics Plotter Profiles menu option

Either “System” or “User Defined” type

“System” type profiles are built in and cannot be deleted. They can, however, be disabled. Disabling them will remove the ability to launch them from an object’s properties form. To disable, simply deselect the “Display in Menus” checkbox.

Module 6 - 21 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Best Practices for Viewing Statistics and Plotter

Viewing one specific type of statistics on one object:

View the statistics or access the plotter from the object’s Statistics tab, as this will automatically paste in the monitored object

Viewing one specific type of statistics on multiple objects:

View the statistics or access the plotter from Tools -> Statistics -> Statistics Manager.

(Tools -> Statistics -> Statistics Browser)

Module 6 - 22 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Link Utilization Statistics

Introduced in 5620 SAM 8.0 R5

1. Determines, in bytes, the total amount of data that can be sent over a Physical Port or channel in a specific amount of time

2. Determines the total amount of data that was sent during that same time period

3. Uses the values from steps 1 and 2 to calculate the utilization as a percentage of the total possible amount of data on the port or channel

Requires “Interface Stats” to be enabled on the port

Uses “Received/Transmitted Octets Periodic” counter

Uses the configured periodic collection interval (minimum of 5 minutes)

Calculates the Utilization Percentage at each collection interval

Link Utilization Statistics can be configured on the following objects:

•DS1/E1 Channel

•DS3/E3 Channel

•Physical Port

•Sts1 SONET Channel





The Link Utilization Statistics depend on TCA, which is covered in the next few slides.

The Link Utilization values appear in an alarm that is generated by the TCA mechanism.

Module 6 - 23 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



TCA Policy

Can configure a Rising and/or Falling threshold value

At each interval, if the threshold value is passed, 5620 SAM will generate a Threshold Crossing alarm

Alarm info contains the values (in this case percentage) that caused crossing of the threshold

To take advantage of the Link Utilization Statistics Thresholds, the operator must create a TCA (Threshold Crossing Alarm) Policy

1. From the 5620 SAM main menu, select Tools TCA Policies

Module 6 - 24 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



TCA Policy

2. On the TCA Policies form, click the Create button

3. Enter a Displayed Name, select the Monitored Object Type and set the Admin State

4. Click the Apply button

(Tools -> TCA Policies)

Module 6 - 25 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



TCA Policy

5. Create Threshold Crossing Rule(s)a. Expand the Utilization section

b. Under Rules, click the Create button

c. Set the Displayed Name, Alarm Severity, Threshold (%) and Threshold Direction

d. Click the OK button

Module 6 - 26 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



TCA Policy

6. Add the desired objects to be monitoreda. Click the Monitored Objects tab

b. Click the Add button

c. Enter a filter and search for the desired object(s)

d. Highlight the object(s) in the list and click the OK button

A port can only be assigned to one TCA policy at a time.

Module 6 - 27 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



TCA Policy

7. On the TCA Policy form, click OK or Apply to activate Link Utilization monitoring on the monitored objects

Note: As of SAM Release 9.0 R5, a TCA policy can be created for all Performance Statistics types.

Module 6 - 28 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



TCA Tab

An operator can view which TCA policies are assigned to a physical object by selecting the TCA tab in the object’s Properties form

Within this tab, click the Assign button on the right to assign this physical object to a previously configured TCA Policy

Module 6 - 29 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Link Utilization Threshold Crossing Alarm

On any Interface Stats collection interval, an alarm will be raised if the link utilization crosses the configured threshold value.

Module 6 - 30 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Plotting Link Utilization

As of SAM Release 10.0 R5, users are able to plot port utilization directly in the statistics plotter

Statistics group must be Interface Additional Stats

Module 6 - 31 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Statistics - Exercise 1

Traffic is generated from r6 to r5

Use Physical Port Interface Stats (Received and Transmitted Unicast Pkts Periodic) to find which way the traffic flows through the network

Statistics are already enabled

A port that is carrying traffic will show scheduled 5-minute periodic unicast pkts (approx. 41,000)

Each group has to find out which ports are involved in the traffic flow on their assigned router

Group 1 – router r1




Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Accounting Statistics

File Policy :

Storage Location of the Statistics (cf2: in our lab setup)

Accounting Policy :

Link File Policy to Accounting Policy

Select specific Accounting statistics type for troubleshooting purposes

The Plotter can be used, but only for an Historical Plot.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Viewing SAP Traffic

There are multiple statistics types that can be used to view traffic on a customer SAP Below are 2 recommendations:

1. Complete Service Ingress/Egress Packets Octets XML- based statistic which must be enabled through an Accounting policy

Cannot be monitored on-demand (can only view scheduled collection interval)

2. SAP Ingress/Egress Queue Accounting Stats MIB-based statistics

Can be monitored on-demand (real-time data using the statistics plotter)

(Manage -> Service -> Services -> VPLS # -> Layer 2 Access Interface -> Statistics)

Module 6 - 34 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Complete Service Ingress/Egress Packet Octets

Configured 5 minute interval

No traffic because Octets are constant

Traffic passing because Octets are rising

No dropped packets because value is constant

Historical plot only

(SAP properties -> Statistic tab)

(SAP properties -> Statistics tab -> Select Object type... -> Plotter).

Module 6 - 35 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



SAP Ingress/Egress Queue Accounting Stats

Periodic values enable easier traffic monitoring (E.g. No traffic will show a value of 0)

Real-time Plotting

On-Demand Collection

Note: This is one of the few accounting stats that is MIB-based and therefore can be collected on-demand.

Module 6 - 36 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Statistics - Exercise 2

Traffic is generated from r6 to r5 through VPLS Service ID 31

Use 5620 SAM Accounting Statistics (Complete Service Ingress and Egress packets) to find which two SAPs (1 per site) are carrying the traffic AND which queue is used.

Statistics are already enabled

For this exercise, use the Out of Profile Pkts Forwarded counter

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Server Performance Statistics

Each statistic is used to troubleshoot different issues:

Alarm Rate

Node Resync

Server Memory

SNMP Trap

(Tools -> Statistics -> Server Performance Statistics)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Module Summary

In this module, the following topics were covered:

Using 5620 SAM to view Statistics Records

Using 5620 SAM to configure Statistics Collection

Using multiple 5620 SAM Statistics to troubleshoot network issues

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



This page intentionally left blank

Module 6 - 40 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module 6 - 41 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module 7 — Troubleshooting IGPs

Module 7 - 1 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Network and Service Troubleshooting with the 5620 SAM v1.4 Module 7 |2 All rights reserved © 2013 Alcatel-Lucent

Module Objectives


View and configure IGP parameters

View the IGP configuration using the Routing Navigation tree

List the steps taken to troubleshoot IGP issues

Troubleshoot common IGP issues

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Troubleshooting IGPs

This module describes how 5620 SAM can be

used to troubleshoot common IGP issues.

Module 7 - 3 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



OSPF Configuration

OSPF Properties form

Shutdown/Turn up

View neighbors

View interfaces

OSPF Interface Properties form

Shutdown/Turn up

Authentication

View neighbors

OSPF interface/site search

Manage -> Networking -> Routing Instances…

Configuration planning is essential to organizing OSPF areas, interfaces and virtual links. OSPF provides defaults for basic protocol operability. OSPF configuration requires, at a minimum, that a single OSPF backbone area containing the area border routers is created. For larger networks, several areas can be created into which the routers are distributed for protocol management. In dealing with smaller networks, all routers can be placed in the OSPF backbone area.

The parameters that are required for OSPF deployment are:

A Layer 3 interface is a logical IP object that is defined on a physical port, such as an Ethernet port. A Layer 3 interface:

- has an IP address and subnet mask

- is configured with QoS policy settings

- associates its IP address with a physical port or channel

- has its physical port or channel cabled to another device

- has enabled routing protocols

The physical connection of one device to another device is through its port or channel. However, the Layer 3 interface determines its IP connectivity. The Layer 3 interface passes both routing information, using a routing protocol such as OSPF, and IP traffic.

Router ID — Devices that run OSPF must be configured with a unique router ID. The system interface is typically used as the router ID to preserve connectivity when an interface fails or is removed. A system interface must have an IP address with a 32-bit subnet mask. The system interface is used as the device identifier by higher-level protocols such as OSPF and BGP.The router ID is used by the OSPF and BGP routing protocols in the routing table manager. When a new router ID is configured, protocols are not automatically restarted with the new router ID. The protocol must be shut down and restarted to initialize the new router ID.

An Area — At least one OSPF area must be created. An interface must be assigned to each OSPF area. The types of OSPF areas include a backbone area, stub area and NSSA.

(M N t ki R ti I t R t T i ti I t f R t T i ti N IP

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



IS-IS Configuration

IS-IS Properties form

Shutdown/Turn up

View neighbors

View interfaces

IS-IS Interface Properties form

Shutdown/Turn up

Authentication

View neighbors

IS-IS interface/site search

Manage -> Networking -> Routing Instances…

IS-IS is a link-state interior gateway protocol that uses the Shortest Path First algorithm to determine a route. Routing decisions are made using the link-state information. IS-IS entities include:

- networks: autonomous system routing domains

- intermediate systems: routers such as the 7750 SR and 7710 SR

- end systems: network devices that send and receive Protocol Data Units (PDUs)

End system and intermediate system protocols allow devices and nodes to identify each other. The IS-IS protocol periodically sends link-state updates through the network, so each device can maintain current network topology information.

Large networks, or autonomous systems, are supported by the IS-IS using a two-level hierarchy. This divides a large area into smaller, more manageable areas. The first level (level 1) of routing is performed within an area. The second level (level 2) of routing is performed between areas.

Level 2 areas are also called backbones, similar to an OSPF backbone area. All traffic traversing different areas must traverse the backbone. A device can be configured as level 1, level 2, or both level 1 and 2. Level 1 devices are only aware of their own areas’ topology, and must forward traffic to a level 1/2 device to forward the data to another area.

Two devices are in the same level 1 area when they have level 1 adjacency. Level 1 adjacency occurs when the area IDs are common and there is a level 1 connection between the devices. Level 2 adjacency occurs when it has at least one level 1 or 2, or one level 2 interface configured. The 5620 The 5620 SAM supports the configuration of IPv6 addresses for IS-IS adjacencies.

(Manage -> Networking -> Routing Instances -> Router Terminating Interface -> Router Terminating Non-IP Interface -> ISIS Interface)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting Common IGP Issues

Link/Interface status

MTU mismatch

Mismatched interface type

Mismatched subnet mask or IP address

Interface not configured for OSPF/IS-IS

Neighbor is configured for authentication

OSPF timer parameters

Area ID does not match neighbor

IS-IS interface level capability

NOTE: This is also an excellent checklist to follow when troubleshooting IGP

issues

Filters (ACL, CPM, etc.)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Failure Scenario – OSPF

IGP traffic cannot pass from r2 to r4 directly, thus all traffic is taking a suboptimal route.

What route is the IGP traffic taking?

What is the cause of this problem?

r2 r4

r3r1

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Symptoms

IGP traffic is not using the directly connected link

OSPF adjacency between r2 and r4 is down

Reproduce

Using the STM, execute an ICMP trace test to confirm the issue

View the results and record the probe hops

Failure Scenario – OSPF (1. Identify)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Reproduce (continued)

Can also run a CLI script from the router’s Properties form

Under the Scripts tab, select the desired script and click the Execute button


Note: Only scripts that have router R2 configured as a Target will show up in the list above. Users can also access the script properties form and the STM list window from this tab.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




If the script is successful, a green checkbox will appear in theStatus column and the results will be displayed in the window below.


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Can use the script menu Shortcut or Action button to view and execute scripts much more quickly.


If a script is bound to an object, it will be bound to all other objects of the same type, but not to objects of a different type.

The Manage Scripts option allows adding/removal of scripts from an object type. Use this to add multiple scripts at once or to remove scripts from the object’s scripts menu option.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Failure Scenario – OSPF (2. Investigation)


If the Dynamic Alarm window is quiet, you may be able to quickly view any alarms from there.

Quick filter allows faster searching

To make searching the Dynamic Alarm window easier, filter for Domain containing OSPF.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




If the Dynamic Alarm window seems busy, navigate to the object(s) in question using the Navigation tree.

— There is an alarm on the interface and neighbor. The interface is a lower-level object, so start the investigation there

— Right-click on the object and select Properties

— Click the Faults tab to view any alarms

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Explore any open alarms/Acknowledge alarms

Warning - InterfaceDbDescriptConfig

2 x Major - NeighborDown

View the alarm information for possible clues to the cause (based on best practice, start with Probable Cause, Additional Text, Description and Remedial Action)

Click View Correlating Alarm if it is active to navigate to the parent alarm. Repeat this step until this button is no longer active.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




The Probable Cause on the InterfaceDbDescriptConfig alarm states there is an mtuMismatch

Navigate to the object in question (OSPF interface)

Click the View Alarmed Object button

Check for affecting, aggregated and related objects alarms

Located under the Faults tab

In the Aggregated Alarms tab there is a NeighborDown alarm

The presence of a NeighborDown alarm shows that the alarms may be related, and that fixing the mtuMismatch could possibly bring the neighbor back up

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Navigate to the network interface

On the General tab, click Properties, located next to the interface name

From the interface form, navigate to the port

On the Port tab, click the Properties button

Note: The port’s fault tab “Alarms on Related Objects” shows two alarms:

Routing Management: OSPF – Interface – “InterfaceDbDescriptConfig”

Network - Discovered Physical Link – “PhysicalLinkPortsMisconfigured”

(OSPF Interface -> Interface Properties -> Port)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Failure Scenario – OSPF (3. Fix)

On the General tab of the port, change MTU to the correct value (1578)

If you are unsure what it should be, you can check the other port of the physical link, the configuration of another similar port or a network design doc/diagram

Record the change in the Audit Trail

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Make sure any objects that were operationally down are now UP.

All self-clearing alarms should be implicitly cleared

Issue the same ICMP trace test as in step #1 to verify the fix

Best Practice:

Manually clear non-implicitly cleared alarms, but only once the fix is verified.

Failure Scenario – OSPF (4. Verify)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Highlight MTU Mismatch

5620 SAM Tool highlights any Physical Port MTU mismatch throughout the entire network

Right-click in the blue area of the Physical Topology and select Highlight MTU Mismatch

Use if there is an MTU mismatch alarm

Physical links must exist

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



MTU Defaults

Port Type Mode Encap Types Default

10/100, GigE, or 10GigE Access Null 1514

10/100, GigE, or 10GigE Access dot1q 1518

10/100, GigE, or 10GigE Access mpls 1518

10/100, GigE, or 10GigE Access q-in-q 1522

SONET/SDH or TDM Access range 1502-4470

ATM Access atm 1508

10/100 or 100FX Ethernet Network null 1514

10/100 or 100FX Ethernet Network dot1q 1518

1GE or 10GE Network null 9212

1GE or 10GE Network dot1q 9216

SONET/SDH or TDM Network range 9208

There are many different MTU defaults depending on the port type, encapsulation and mode applied to the port.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Failure Scenario – IS-IS

IGP traffic cannot pass from r2 to r4 directly, thus all traffic is taking a suboptimal route.

What route is the IGP traffic taking?

What is the cause of the problem?

r2 r4

r3r1

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Symptoms

IGP traffic is not using the directly connected link

IS-IS adjacency between r2 and r4 is down

Reproduce

Using the STM, execute an ICMP trace test to confirm the issue

View the results and record the probe hops

Failure Scenario – IS-IS (1. Identify)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Failure Scenario – IS-IS (2. Investigate)


If the Dynamic Alarm window is quiet, you may be able to quickly view any alarms from there

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Explore any open alarms

2 x Minor - IsisAdjacencyDown

View the alarm information for possible clues to the cause

Gather information from the alarm fields. More important ones include the following;

— Probable Cause

— Additional Text (showing 3 attribute values)

Click the Details tab to view the Description and Remedial Action

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




The Additional Text alarm feature that was mentioned in Module 2 can help here:

An Additional Text alarm policy for an IS-IS interface was previously created

It contains 3 major attributes:— encapType

— interfaceType

— levelCapability

Because of this tool, we are able to spot a misconfigurationon interface r2-r4

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




r2-r4 r4-r2

The Additional Text field shows that the level capability is misconfigured.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Failure Scenario – IS-IS (3. Fix)

On the General tab of the IS-IS interface r2-r4, change the Level Capability to Level 2.

(Alarm -> View Alarmed Object -> ISIS Interface -> General Tab -> Level Capability)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Failure Scenario – IS-IS (4. Verify)

Make sure any objects that were operationally down are now UP

All self-clearing alarms should be implicitly cleared

Issue the same ICMP Trace test as in step #1

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting Common IGP Issues 1 (LAB 7.1)

OSPF traffic cannot pass from r2 to r4 directly, thus all traffic is taking a suboptimal route

Find the cause, but do not fix it

r2 r4

r3r1

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting Common IGP Issues 2 (LAB 7.2)

OSPF traffic cannot pass from r2 to r4 directly, thus all traffic is taking a suboptimal route.

Find the cause, but do not fix it

r2 r4

r3r1

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Module Summary


Using 5620 SAM to view and configure IGP parameters

Listing the more common IGP problems

Using multiple 5620 SAM tools to troubleshoot IGP issues

Binding scripts to network objects

Using the MTU mismatch tool

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module 7 - 32 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module 8 — Troubleshooting MPLS

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 8 - 2Network and Service Troubleshooting with the 5620 SAM v1.4 All rights reserved © 2013 Alcatel-Lucent


Module Objectives


View and configure MPLS parameters and objects

View MPLS configuration using the Routing Navigation tree

List the steps to troubleshoot MPLS issues

Troubleshoot common MPLS issues

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Troubleshooting MPLS

This module describes how 5620 SAM can be

used to troubleshoot common MPLS issues.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Common MPLS configuration

In troubleshooting any MPLS issue, first verify the following:

MPLS, RSVP and LDP – Operationally Up on NE and interfaces LSP - Operationally Up MPLS path - Operationally Up LSP-Path Binding - Operationally Up LSP has a destination address assigned to it LSP has primary/secondary path assigned to it

MPLS (Multi-Protocol Label Switching) encompasses a growing set of protocols defined by the IETF. MPLS combines the performance capabilities of Layer 2 switching with the scalability of Layer 3 routing. It enables service providers to provide differentiated services utilizing existing infrastructure.

In conventional Layer 3 forwarding, as a packet traverses the network, each router extracts all the information from the packet header. The router then analyses this information and extracts what is relevant to forwarding the packet. This information is then compared to the routing table to determine the packet’s next hop.

In MPLS, the analysis of the packet header is done just once at the ingress to the network Label Edge Router (LER). The packet header is then assigned a label based on a manually configured value (static route) or a dynamically signaled value.

LDP (Label Distribution Protocol) is used to distribute labels in non-traffic-engineered MPLS applications. Routers can establish LSPs across a network by mapping network-layer routing information directly to the data link layer switched paths.

RSVP (Resource Reservation Protocol) is a network control protocol that defines procedures for signaling QoS requirements and reserving the necessary resources for a router. RSVP is not a routing protocol. It operates with unicast and multicast routing protocols, which determine where packets are forwarded.

RSVP-TE is a set of traffic engineering extensions to RSVP intended for use by label switching routers (as well as hosts) to establish and maintain LSP-tunnels and to reserve network resources for such LSP-tunnels. The RSVP-TE extensions are defined in RFC 3209.

The RSVP-TE specification essentially allows an RSVP session to consist of an arbitrary aggregation of traffic (based on local policies) between the originating node of an LSP-tunnel and the egress node of the tunnel. The session is defined as the set of packets that are assigned the same MPLS label value at the originating node of an LSP-tunnel. The assignment of labels to packets can be based on various criteria, and may even encompass all packets (or subsets thereof) between the endpoints of the LSP-tunnel.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Two Basic Types of Errors

There are basically two types of errors that could happen when creating an LSP using RSVP:

1. Routing issues: a route to a destination is not available2. Signaling issues: even with a valid route to a destination, the

LSP tunnel still is not operationally Up

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



MPLS Configuration Basics

MPLS Properties form

Shutdown/Turn up View all interfaces, In Segments, Cross Connects, Out Segments,

Static Label Maps on the router Specific MPLS parameters such as FRR, LSP resignal View default values

MPLS Interface Properties form

Shutdown/Turn up Specific MPLS interface parameters such as Admin Group, SRLG

Groups, Port-id In Segments, Cross Connects, Out Segments, Static Label Maps on

the interface

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



MPLS Information

Select Routing in the Navigation tree

Manage MPLS LSPs

Manage MPLS MPLS Objects

Manage MPLS MPLS Paths

Manage Networking Routing Instances

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



LDP Configuration Basics

LDP Properties form

Shutdown/Turn up View all interfaces, interface properties, targeted peers,

targeted peer properties, sessions Specific LDP parameters such as Import and Export Policies,

Distribution Mode, Retention Mode, Control Mode View default values

LDP Interface Properties form

Shutdown/Turn up Specific LDP interface parameters such as Keep-Alive Timeout,

Hello Timeout, Address Type Statistics, Faults

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting LSPs Checklist

Verify the following:

Check that IP reachability to the destination exists— ICMP ping and/or ICMP trace

Traffic engineering enabled on the IGP (optional)— All LSPs do not have to use CSPF / traffic engineering. It is possible to

have an LSP with a strict or loose hop using a regular IGP without TE extensions.

MPLS enabled on the router— Operationally Up?

MPLS enabled on the network interfaces— Operationally Up?

Are there associated LSP-Path bindings?— Operationally Up?

— Error Codes?

Items listed in this slide are in no particular order.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting Common MPLS Issues

Interface not configured for MPLS

LSP not signaled

Routing issues

This is a list of the more common MPLS problems.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues - Failure Scenario #1

A newly-created LSP between r2 and r3 does not become active (operationally up)

No CSPF or FRR

Loose

Strict

r2 r4

r3r1

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues – (1. Identify)

Symptoms

Verify Issue

(Manage -> MPLS -> Dynamic LPSs)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues - (2. Investigate)


Yes; in this case, there is one Object Alarm and one Aggregated Alarm related to the issue

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues – (2. Investigate)

Explore the Object Alarm (correlating) first

Critical - LspDown

View the Alarm Information for possible clues as to the cause

If no clues are present, check the status of the LSP Bindings

(Alarm properties)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




View the LSP-Path Bindings Status and Failure Code

• The two most informative windows for troubleshooting an LSP is the LSP Properties form and the LSP-Path Bindings window

Best Practice:

When an LSP is operationally down, view the LSP-Path Bindings Failure Code

(Properties of Dynamic LSP -> LSP-Path Bindings tab)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Note:

It may be necessary to resync the LSP-path binding to update the Failure code because the node does not always send a trap the moment the code changes (waits for retry period)

Best Practice:

Always resync the LSP-path bindings to view the most recent Failure Code

For a list of common error codes along with possible causes and suggested actions to resolve the problems, please check the Lab Guide Appendix A

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




This specific LSP event could be caused by different factors. First verify that MPLS is enabled on the NEs and interfaces used by the LSPs

Perform an OAM LSP trace test

• In this case, the error message “Invalid LSP label”appears

OAM LSP trace test result is being viewed

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




This can be done in the Routing Navigation tree or the Manage MPLS MPLS Objects MPLS Interface menus

Notice that Interface “r2-r4” is missing

• When used with filters, is very useful in larger networks.

(Manage -> MPLS -> MPLS Objects -> MPLS Interface)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues – (3. Fix)

On router r2, enable MPLS on the Interface “r2-r4” by creating the interface in the MPLS menu context

Use the Routing navigation tree to configure the MPLS interface.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues – (4. Verify)

The LSP tries to resignal within 30 seconds by default

The LSP is now operationally up, and the Failure Code is “No Error”

The LSP Object Alarm alarm has been implicitly cleared

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




A newly created LSP between r2 and r3 is not taking the shortest path. What is the current path? What caused it to reroute? Fix the issue so the LSP will take the shortest path.

CSPF is enabled, FRR is disabled

r2 r4

r3r1

Loose

Strict

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Symptoms

Verify Issue

(Properties of Dynamic LSP)

(Properties of Dynamic LSP -> Properties of LSP-Path Binding -> Provisioned Path tab)

(Properties of Dynamic LSP -> Properties of LSP-Path Binding -> Actual Path tab)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Are there any open alarms? Both the LSP and LSP-Path Binding are showing no

alarms

Are there any historical alarms? LspDown alarm raised 10:48:48 and cleared 10:50:18

(Rerouted)—By default, alarms are logged to historical once they

are cleared.

(Tools -> Historical Alarms)

Default settings of 5620 SAM:

-Delete an alarm when it is cleared

-Log to history when it is deleted

Based on the above information, we know that the “Time Logged” was the time the LspDown alarm cleared.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




What caused the LSP to reroute? Search both the Alarm History and Dynamic Alarm

window for ALL alarms with a time =< 10:48:48

In the Dynamic Alarm window, there are many critical alarms around the same time the LSP rerouted

One of these alarms is an interfaceDown alarm on RSVP Interface “r2-r4”, which should be the preferred first hop of the LSP

(Dynamic Alarm window)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




The description states there may be an underlyingResourceFailed

(InterfaceDown Alarm -> Details)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Using the Navigation tree, check the MPLS interface r2-r4 is Shutdown

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Turn Up MPLS on the interface

Re-signal the LSP-Path Binding if desired

Alternatively, wait until the re-signal timer expires

Use the Routing navigation tree to turn up the interface.

The Re-signal “Do Action” is on: (Properties of Dynamic LSP -> Properties of LSP-Path Binding -> General tab)

By default LSP re-signaling is disabled on the node. To enable this, go to the Routing Instance -> MPLS -> General Tab and check the LSP Resignal checkbox. Once enabled, the router will re-signal LSPs at the configured Resignal Timer interval.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Because the first hop is loose, the LSP re-signals and reverts to the original actual path


The LSP rerouted because the interface went down. The LSP was able to reroute because its first hop is loose. The rerouting was triggered by the retry time (30 seconds).

Once the interface was repaired, a re-signaling of the LSP allowed it to be optimized and thus revert back to the original path.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Another newly created LSP between r2 and r3 does not become active (operationally up)

CSPF enabled

r2 r4

r3r1

Loose

Strict

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Symptoms

Verify Issue

The LSP is administratively up, but operationally down.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile





Yes; in this case, there is one alarm related to the issue

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Best practice is to check the following:

1. IP reachability to the destination exists

2. Traffic engineering in OSPF is enabled

3. Verify all strict/loose hops are valid

4. Check if the requested bandwidth is too big

5. Check if the link color is assigned correctly

This code could be caused by different factors

Appendix A in the Lab Guide has these steps.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




MPLS is already enabled on NEs and Interfaces

Perform OAM ICMP trace test to determine IP reachability:

Based on the provisioned path (two strict hops), we will need to perform two ICMP trace tests to confirm IP reachabilityand that the direct hops are being used

The destination is reachable and both direct hops are being used

r2-r4 r4-r3

(Properties of Dynamic LSP -> Properties of LSP-Path Binding -> Provisioned Path tab)

(OAM ICMP test results)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Is Traffic Engineering enabled in the OSPF configuration?

For larger networks, use the Manage Networking Routing Instances window

From the top left hand drop down, select Router Site Protocol Site OSPF Site

Set filter to Traffic Engineering Support = false Check to see if any routers of the path are in the list

Notice that Traffic Engineering is disabled on r4

(Manage -> Networking -> Routing Instances, Router Site -> Protocol Site -> OSPF Site).

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Enable Traffic Engineering on the NE (router r4)

Can use the form search to find where this is Enabled/Disabled.

• Change to True

To open the site properties, just double-click on the row found in the previous slide.

Alternatively, disabling CSPF will also allow the LSP to come up since TE would not be needed if CSPF were disabled.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




The LSP is now operationally up, the Failure Code is “No Error”

All self-clearing alarms are implicitly cleared

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues 1 (LAB 8.1)

A newly created LSP between r2 and r1 does not become active (operationally up). CSPF and FRR are enabled

LSP Name is r2-r4-r3-r1 Find the cause, but DO NOT fix it

r2 r4

r3r1

Loose

Strict

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




A newly created LSP between r5 and r6 does not become active (operationally up).

Find the cause and fix the LSP

r2 r4

r6

r1

r5

r3

Loose

Strict

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues with FRR - Failure Scenario #4

A failure on r2 caused an LSP between r2 and r3 to reroute

Initially the path was from r2-r4-r3 Fast-Reroute(FRR) is enabled

Explain what happened and the investigation steps taken

r2 r4

r3r1

Loose

Strict

FRR is enabled on an LSP via Dynamic LSP -> Properties tab.

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues with FRR – (1. Identify)

Symptoms

The LSP is still UP.

(Properties of Dynamic LSP)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues with FRR – (2. Investigate)


• LspPathReroutedToByPassTunnel means FRR established path to destination

• Session Down

• LspDown

• InterfaceDown

Th

is A

LU

-IP

D-S

RC

Alc

ate

l-L

uce

nt_

Ne

two

rk_

an

d_

Se

rvic

e_

Tro

ub

lesh

oo

tin

g_

wit

h_

the

_5

62

0_

SA

M G

uid

e i

s fo

r e

xclu

sive

use

of

Ka

zi_

Zia

l_H

oq

ue

- W

IND

_M

ob

ile

Ka

zi_

Zia

l_H

oq

ue

- W

IND

_M

ob

ile




Status of the LSP binding associated to it

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




RSVP Session

RSVP sessions show that the node detour is in use (using tunnel ID 2061):

RSVP Session properties (tunnel 2052 has next hop of 10.2.3.3):


(Properties of Dynamic LSP -> RSVP Sessions tab)

(Properties of Dynamic LSP -> RSVP Session properties)

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Investigate the InterfaceDown alarm which was seen during this failure:

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Investigate MPLS and RSVP states on r2 on interface r2-r4

MPLS interface r2-r4 is in shutdown state

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues with FRR – (3. Fix)

Take corrective action

Turn up MPLS interface r2-r4 on r2

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues with FRR – (4. Verify)

LSP r2-r4-r3 and its associated binding has no failure code and is operational with the path from r2-r4-r3


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Troubleshooting MPLS Issues with FRR – (4. Verify)

LSP trace shows two-hop path

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



Module Summary


Using 5620 SAM to view and configure MPLS parameters

Which MPLS alarms are not self-clearing

Listing the more common MPLS problems

Using multiple 5620 SAM tools to troubleshoot MPLS issues

LSP Optimization Policy

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Appendix 8.1

Extra Labs

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




A newly created LSP between routers r4 and r3 does not become active (operationally up). CSPF is enabled.

LSP Name is r4-r3-lab8.3

r2 r4

r3r1

Strict

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




A newly created LDP-based SDP between routers r1 and r6 does not become active (operationally up).

Find the cause but do not fix the issue LSP description is “r1-r6 LDP (Course)”

r2 r4

r6

r1 r3

Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile




Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Module 9 — Service Level Troubleshooting

Network and Service Troubleshooting with the 5620 SAM v1.4 All rights reserved © 2013 Alcatel-Lucent Module 9 - 1 Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 2


Module Objectives


View and configure Service Level parameters

Understand the use of State Causes

Validate a service

Understand the usage of a Policy Audit

Troubleshoot VLL/VPLS issues

Troubleshoot VPRN issues

Use a Mirrored Service

Network and Service Troubleshooting with the 5620 SAM v1.4 All rights reserved © 2013 Alcatel-Lucent Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Service Level Troubleshooting

Services Overview


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 4


Service Components

Service Tunnel

Service TunnelSDPServiceID

SDP

Customer

Customer

ServiceIDSAP

SAP

Subscriber

Subscriber

PE-A PE-B

Service Site

Service Site

Service Site: The local instance of a service configured on a specific router.

Service Tunnel: An SDP uses a service tunnel to direct traffic from one 7750 SR router to another. The service tunnel is provisioned with an encapsulation (GRE, RSVP-TE, LDP) type and services are mapped to the service tunnel.

Service Access Point (SAP): A SAP is a logical entity that serves as a subscriber’s point of access to a service. Each service is configured with at least one SAP. A SAP can only be configured on a port that has been configured as an access port. The default configuration for a port is network, which means that a port will need to be configured as access before a SAP can be configured on it. SAPs for IES and VPRN services are configured on IP interfaces.

Service Distribution Path (SDP): An SDP acts as a logical way of directing traffic from one 7750 SR to another through a unidirectional service tunnel. An SDP originating on one node terminates at a destination node, which then directs incoming packets to the correct service egress SAPs on that node. A multi-node service needs at least one SAP and one SDP on each node. For a service to be bidirectional, an SDP must be provisioned on each node participating in the service.

Subscriber: This represents the user of the service (external to the router and the 5620 SAM).

Customer ID: This is a value associated with the service that can be used to group together several services to help manage them.

Service ID: A numeric value used to identify the service.

SDP Binding: This is the association between an SDP and a VC ID (the VC ID is usually the same as the Service ID).


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 5


Service Creation and Configuration

Service Creation steps

Use the Service Navigation Tree or Service Topology

Viewing Services

Grouped by CustomerUse a filter within the Manage Services window

— Sites, SAPs and SDP bindings

Topology view


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


State Cause Indicators


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 7


State Cause Indicators

When the operational state of an object is down, a check mark appears beside the appropriate State Cause indicator to identify the type of fault.

Some indicators are more descriptive than others and may lead the operator to the cause of the issue

Usually found on the General tab of a Properties form

For SDP bindings, it is on the States tab

Best Practice:

View the State Cause Indicator when troubleshooting an object


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 8


State Cause Example

When troubleshooting a SAP, view the State Cause indicator

In this example, it says to focus on the physical port

Viewing the State Cause indicator can save the operator from doing unnecessary work and speed up the overall investigation

(SAP properties -> General tab)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Service Validation

Module 9 - 9Network and Service Troubleshooting with the 5620 SAM v1.4 All rights reserved © 2013 Alcatel-Lucent Thi

s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 10


What is Service Validation?

Used to verify the operational status of a service or service-related entity

The operational status of a service depends on the operational states of its service sites or instances

It is possible for a service to be operationally up when communication between sites is not operational

For example, a VPLS can be operationally up although traffic cannot pass between two SAPs because of an ACL

If Service Validation failure occurs, the State Cause will be flagged with OAM Validation Failed


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 11


Service Validation Example

Create a validation test suite to perform MAC pings between the SAPs to validate the VPLS service.

r6r5


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 12


Service Validation Example (Creation)

Enabled through the creation of a Test Suite.

On the Test Suite Properties form, set the Entity Type and select the Validation Test Suite check box.

Finish creating the test suite by adding the MAC ping tests under the First Run Tests tab

(Tools -> STM -> Test Suite)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 13


Service Validation Example (Execution)

On the VPLS properties form, click the Tests tab, then click the Test Suite sub tab.

If there is already a validation test suite created for this service, an entry will appear in the list below and the Test Suite Validation check box will be selected.

(Manage -> Service -> Services -> Service ID # 37 properties -> Tests tab)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 14


Service Validation Example (Execution)

On the VPLS service Properties form, click the Validate button.

If no validation test suite is already created for this service, the following message will be displayed:

Click the OK button and select the test suite created in the previous slide.

Once selected, the test suite will run automatically.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 15


Service Validation Example (Results)

If one of the tests in the test suite fails, the service State Cause will be set to OAM Validation Failed.

(Service properties -> General tab)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 16



A new entry under the Tested Entity Result sub tab is available once the test suite execution is completed

Double click this entry to view the results of each individual test

(Service properties -> Tests tab)

MAC pings that don't have successful pings are due to an ACL.

The pings could also fail due to the MACs not being present as well.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 17



By viewing each Failed Result we can see that the problem is with traffic going to MAC address 22-66-66-66-66-02

(Service properties -> Tests tab -> Validation Results -> MAC Ping Result properties)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 18



Navigate back to the VPLS service properties form and click the Forwarding Control tab, then click the FIB Entries sub tab

Click the Search button and find the entries for the MAC address (There may be multiple entries containing the same MAC address)

You may have to click Resync before clicking Search

(Service properties -> Forwarding Control -> FIB Entries)

The Resync button on the right side of the list is for the FIB entries, while the Resync button at the bottom of the form is to Resync the VPLS Service.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 19



The “local” entry is where the MAC address lives

If the FIB is very large, filter for the MAC address and the keyword “local” in the Name field

Highlight the entry and click the Edit Access Interface button to navigate to the SAP in question

(Service properties -> Forwarding Control -> FIB Entries)

At this point, we have now narrowed down the issue to a particular SAP.

An operator would continue to troubleshoot the SAP for why the pings are failing, but in this case we know the reason is because of our filter.

The purpose of this example is to show Service Validation and how to view MACs.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 20


Service Validation (LAB 9.1)

Create and Run a Service Validation for a VPLS to determine if there are any issues with the customer SAPs. Are there any failures? If so, what object is causing the problem?

r5 r6


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Policy Audit


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 22


Policy Overview

Advantages of 5620 SAM Policies Management:

Provides a consistent way to manage various types of global and local policies

Helps users to manage hundreds of policies with ease and efficiency

Centralized control on policy distribution and updates Detect policy configuration discrepancies

Note: Avoid using Default policies as they cannot be edited. Create a new policy and assign it to the NEs instead.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 23


Global vs Local

Global Policies

Can be applied to multiple NEs Exist in 5620 SAM only

Local Policies

Instances of global policies that are distributed to individual NEs

Exist in 5620 SAM and on the NEs

In a typical workflow, a global policy is created in SAM first and then distributed to all required NEs within the network


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 24


Global Policy – Configuration Mode

Draft

not ready to be distributed

Released

ready to be distributed to new NEs OR

already assigned to the NEs

— View the Local Definitions tab to view Local Policies

Any changes made on a Released policy will automatically change the policy to Draft

When in Draft mode, click View Released to check the last Released policy configuration

Only keeps latest version (No History)

Switching from Draft to Released by clicking the Switch Mode button will trigger the changes of a policy to be distributed to the NEs (local policies will be updated)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 25


Policy Workflow – Create and Distribute

1. Create a new policy in 5620 SAM

Global policy is created

2. Switch configuration mode to Released

3. Click the Distribute button to select the NEs in 5620 SAM to define the policy distribution

4. Distribute the policy to the list of selected NEs

Local policies are created for each NE in the distribution list List of local policies are displayed under the Local Definitions

tab


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 26


Local Policies

Most of the time global and local policies are the same; however, an operator may want to change a local policy without changing the global policy

Distribution Mode

Sync with Global— Any changes being made in the corresponding global policy will

automatically be distributed to this local policy/NE

Local Edit Only— NOT affected by global policy changes— Only affected by local policy changes


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 27


Local Policy Creation

Can be created in two ways

1. Creating a global policy and distributing it to a router2. Discovering a router in 5620 SAM with existing policies

— With default Sync with Global as distribution mode— Can be changed by editing the following variable in the nms-

server.xml file<policyConfig isPolicyDiscoveredInLocalEditOnlyMode=“false” />— Change “false” to “true”— If created in Local Edit Only mode, the policy can be

changed to a global policy by clicking Synchronize

Best Practice:

When discovering new NEs, set the mode parameter to local configuration only to ensure that unique policies are not modified when a global policy is updated.

The default is “false,” but for best practice it should be changed to “true.”


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 28


Policy Audit Benefits

Able to identify local policies that are different from their global policies

Able to show the differences between global and local policies

Able to show the differences between local policies


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 29


Policy Audit Workflow

For a given list of global policies, find all the corresponding local policies that have different configurations

For a given local policy, click Local Audit On to show the differences against the global policy

Follow the first step to identify local policies with differences. If more details are required, follow the second step.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 30


Policy Audit Example

A customer on site r6 of a VLL is having traffic problems. Perform a policy audit to see if this issue is due to QoS policy configuration

VLL Service

r5 r6


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 31


Locate QoS Policy to Audit

Find the customer SAP on R6 and record the Access Ingress and Egress policies that are assigned

(Service properties -> SAP properties -> QoS tab)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 32


Policy Audit Alarm Filter

Load a filter for the Dynamic Alarm window to show only Policy Audit Alarms

Alarm Name = TemplateInconsistency

Place an advanced filter on the Dynamic Alarm window to show only the TemplateInconsistency alarm.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 33


Policy Audit Begin

Using the Access Ingress Policy list window, find the corresponding policy.

Highlight it and click the Policy Audit button

(Policies -> QoS -> SROS QoS -> Access Ingress -> Access Ingress)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 34


Policy Audit Attributes

General Tab includes the following selectable attributes

Include Non Applicable Attributes Set to Local Edit Only upon finding of differences Set to Sync with Global upon finding no differences

Include Non Applicable Attributes

Leave this unselected

Set to Local Edit Only upon finding of differences

If differences between the local and global are found, set the local policy to Local Edit Only

Set to Sync with Global upon finding no differences

If local policy is currently set to Local Edit Only, but is no different from the global policy, set it to Sync with Global


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 35


Start Audit

If desired, the user can select specific NEs to audit under the Network Element Selection tab.

If none are selected, all NEs will be audited

Click the Start Audit button to begin

If the audit finds a policy inconsistency, an alarm will be raised for each instance


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 36


Investigate Audit Results

Double click the TemplateInconsistency alarm and click the View Alarmed Object button

A Local Policy Properties form opens.

Click the Local Audit On button to view the inconsistencies.

From here, the user can choose to compare with the global policy or another local policy.

Clicking on “Local Audit On” from the local policy of a NE will pop up this dialog.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 37



Once the local audit is turned on, the compared policy Properties form, either global or local, will open

Locate the inconsistencies by following the purple arrows on either Policy form


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 38



Some entries in a list may be colored purple or pink

Purple – entry contains a value that is different between the two policies

Pink – entry is either new or deleted


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 39


View Assigned Objects

Double check all objects that will be affected before making a change to a policy

There is a separate tab for each type of object the policy can be assigned to.

Each tab lists the objects where this policy is currently assigned and will therefore be affected by any changes made.

(Policies -> QoS -> SROS QoS -> Access Ingress -> Access Ingress -> Policy # 5 properties -> Local Definitions tab -> properties of local policy on r5)

Try doing this easily in CLI!


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 40


Fixing Inconsistencies Options:

1. Edit the local definition

2. Resync to global

3. Sync with another local definition

Once one of the above actions has been performed, perform another Policy Audit for verification.

If everything is now in sync, the TemplateInconsistency alarm will clear.

Edit the local definition - set the distribution mode to Local Edit Only, make the changes and save the local policy.

Resync to global - set the local policy properties to match the global policy by clicking the Switch Mode button to change the distribution mode back to Sync with Global.

Sync with another local definition - to set the local policy properties to match that of another local policy, click the Synchronize button. Choose the desired router from the list and click Synchronize.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 41


QoS vs Filter (ACL, etc.)

Best Practice:

If the main symptom of an issue is Traffic Degradation, audit the QoS policies first.

If the main symptom of an issue is Total Traffic Loss, audit the Filter policies (ACL, etc.) first.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 42


Policy Audit (LAB 9.2)

A customer on site r6 of a VLL is having traffic problems. Perform a policy audit to see if this issue is due to ACL misconfiguration

VLL Service

r5 r6


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Troubleshooting Common VLL/VPLS Issues


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 44


VLL Overview

An L2 point-to-point service that connects access interfaces

Is completely transparent to customer or subscriber data and to control protocols; it looks like a leased link exists

No MAC learning

Uses T-LDP signaling, and MPLS or GRE as the service tunnel transport

The 5620 SAM supports the following VLL service types:

Apipe, or ATM VLL Service Epipe, or Ethernet VLL service Fpipe, or frame relay VLL serviceHpipe, or HDLC to HDLC Ipipe, or IP interworking VLL service Cpipe, or circuit emulation VLL service


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 45


VLL Overview

VLL Service

PE PE


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 46


Failure Scenario – VLL

Traffic cannot pass within a VLL service

VLL Service

r5 r6

X


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 47


Failure Scenario – VLL (1. Identify)

Symptoms

VLL Service is operationally down VLL Sites are down VLL SDP bindings are down

(Manage Service -> Services -> service id #47 -> General tab)

(Manage Service -> Services -> service id #47 -> General tab -> Topology)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 48


Failure Scenario – VLL (2. Investigation)


When viewing the critical alarm on the SDP binding, we can see two correlated alarms for the service site

The cause is most likely a misconfiguration of the SDP bindingand if fixed, the alarm on the site should clear as well


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 49



View the SDP binding alarm

None of the fields in the alarms help to pinpoint the cause

Click the View Alarmed Object button to view the SDP

Check the State Cause under the States tab

The State Cause is set to No Egress VC Label

(Service properties -> SDP properties -> States tab)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 50



Based on the State Cause, check the VCID and Label configuration

Located on the General tab VCID = 100 with No Operational Egress Label

(Service properties -> SDP properties -> General tab)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 51



Compare this to the returning SDP binding

VCID = 101 and No Operational Egress Label

The VCIDs of both SDP bindings should be equal; if they are not, one is configured incorrectly


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 52


Failure Scenario – VLL (3. Fix)

Because the VCID of an SDP binding cannot be changed once it is created, we must delete the existing one and create a new binding with the correct VCID.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 53


Failure Scenario – VLL (4. Verify)

Once this is done, the service and all components go operationally up


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 54


Failure Scenario – VLL (Alternate Investigation)

You may have been able to find the cause of this issue much faster simply by studying the service navigation tree, or by using the Info Tables feature for SDP bindings.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 55


VPLS Overview

VPLS is a class of L2 VPN service that allows multiple customer sites to be connected in a single bridged domain

Customer sites in the VPLS appear to be on the same LAN, even if the sites are geographically dispersed

Devices perform MAC learning

Uses T-LDP signaling, and MPLS or GRE as the service tunnel transport

Can use HVPLS to eliminate the need for a full mesh of virtual circuits between devices in a VPLS


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 56


VPLS Overview

PE PE

PE

PEBlue VPLS

Red VPLS


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 57


Failure Scenario – VPLS

End User A within a VPLS is stating that they are no longer receiving traffic from End User B

A B

r5 r6


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 58


Failure Scenario – VPLS (1. Identify)

All service objects are up and operational

Check statistics on the customer’s SAP (Complete Service Egress) to see if packets are being forwarded

Use the following counters: Out of Profile Pkts Forwarded and Out of Profile Pkts Dropped

View the current values and compare these with historical stats

Plotter provides a graphical view Apply filter on the desired queue (this example uses queue 1)

(VPLS 31 -> site r5 -> SAP 1/1/4 -> Statistics -> Select Object Type… -> Complete Service Egress Packet Octets, Filter)

(VPLS 31 -> site r6 -> SAP 1/1/4 -> Statistics -> Select Object Type… -> Complete Service Ingress Packet Octets, Filter)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 59



INGRESS

(R6 SAP 1/1/4)

EGRESS

(R5 SAP 1/1/4)

Ingress above is: (VPLS 31 -> site r6 -> SAP 1/1/4 -> Statistics -> Select Object Type… -> Complete Service Ingress Packet Octets, Filtered on q #1)

Egress above is: (VPLS 31 -> site r5 -> SAP 1/1/4 -> Statistics -> Select Object Type… -> Complete Service Egress Packet Octets, Filtered on q #1)

These are historical statistics (not available for real time plotting).

Note that the screen captures above are from when the Traffic Generator has stopped (ftp gave up).


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 60



Can also use the plotter to view SAP Egress QoS Queue Accounting statistics

This gives the operator a REAL TIME view of customer traffic passing on the SAP

(VPLS 31 -> site r5 -> SAP 1/1/4 -> Statistics -> Select Object Type… -> SAP Egress QoS Queue Accounting Statistics, Dropped Out of Prof PcktPeriodic, q 1)

(VPLS 31 -> site r5 -> SAP 1/1/4 -> Statistics -> Select Object Type… -> SAP Egress QoS Queue Accounting Statistics, Forwarded Out Prof Pckt Periodic, q 1)

Dropped and forwarded packets on SAP 1/1/4 of r5 are both 0.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 61


Failure Scenario – VPLS (2. Investigation)

Customer SAP Accounting stats

Statistics on a customer’s SAP can also be used for investigation purposes

The previous slides show that there is currently no traffic making it to this SAP (on r5)

There are no dropped packets reported by the SAP, therefore packets are being dropped before they reach this SAP


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 62




Viewing the VPLS service Components tab shows there are no objects in an alarmed state; therefore, the problem is most likely with the transport.

— Congestion?— QoS?


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 63



Trace the path that traffic is using

From the service Components tab, view the properties of the SDP binding from r6 to r5.

View the Properties form of the service tunnel used

Under the LSP tab, view the LSP properties

Click the LSP-Path Bindings tab

The Secondary path is currently in an Active state

— When and why did this switch from the Primary path?

— Is the route for the Primary path operational?

(Service properties -> SDP properties -> Tunnel properties -> LSPs tab -> LSP properties -> LSP-Path Bindings tab)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 64



To explain why the binding switched to the Secondary path, view the Dynamic Alarm window and/or Historical Alarms

The Primary LSP-Path Binding shows a major alarm— Time on alarm was 01/04 14:55— The cause of the switch is not indicated in this alarm

Filtering for a point in time just BEFORE 01/04 14:55, search for alarms using both the Dynamic Alarm and Historical Alarm windows

NOTE: If getting traffic back up and running is the main priority, this step can be performed later

The primary LSP-Path binding shows a major alarm (LSP Path Down), but the cause is not indicated. This alarm is still useful as it points to a time to look for other network events that could have caused the issue.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 65



Within the Historical Alarm window, at 14:55, there are many OSPF and MPLS alarms

Within these alarms is a EquipmentAdministrativelyDown alarm for Port 1/1/1 on site r4

(Tools -> Historical Alarms)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 66



This port is configured as the interface facing site r6 If we go back and look at the provisioned path of the primary

LSP-path binding, we see it goes through site r4

Port 1/1/1 on site r4 is currently operationally up, which should allow the primary path to become Active

(LSP-Path Bindings properties -> Provisioned Path tab)

The port 1/1/1 on r4 that bounced is connected to r6.

The primary LSP path did not switch back automatically because its Retry Limit was exceeded. This can be seen by looking at the failure code on the LSP-Path binding.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 67


Failure Scenario – VPLS (3. Fix)

Restart the Primary to make it active

The Primary LSP-path binding should become Active and the alarm will clear.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 68


Failure Scenario – VPLS (4. Verify)

View the SAP Egress QoS Queue Accounting statistics on the customer’s SAP to verify that traffic is passing

If the Plotter is still running, it should be plotting traffic flow

(VPLS 31 -> site r5 -> SAP 1/1/4 -> Statistics -> Select Object Type… -> SAP Egress QoS Queue Accounting Statistics, Dropped Out of Prof Periodic, q 1)

(VPLS 31 -> site r5 -> SAP 1/1/4 -> Statistics -> Select Object Type… -> SAP Egress QoS Queue Accounting Statistics, Forwarded Out Prof Pckt Periodic, q 1)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 69


Service Level Troubleshooting (LAB 9.3)

In a VPLS service, End User A cannot receive traffic from End User B

Service ID = 31 Find the cause but DO NOT fix it

A B

r5 r6


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 70



Best Practice:

When troubleshooting issues with end user SAPs, perform a policy audit to check for inconsistencies and examine statistics where appropriate.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 71



In a multi-site VPLS, site r6 cannot reach site r5. Site r6 can reach all other sites

r5 r6


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Troubleshooting Common VPRN Issues


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 73


Troubleshooting VPRNs

VPRNs, also called IP VPNs or BGP/MPLS VPNs, are defined in RFC 2547bis

This standard describes a method of forwarding data and distributing routing information across an IP/MPLS service provider core network.

Use MP-BGP to exchange the VPRN routes among the PE routers that participate in the VPRN

Done in a way that ensures that routes from different VPRNs remain distinct and separate. PE routers distribute routes to CE routers in the VPRN

The PE routers use BGP, RIP, or OSPFv2 as the IGP to distribute internal routes to the CE routers


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 74



Each VPN site must contain one or more Customer Edge (CE) devices

CE devices can be routers, a host or a Layer 2 device

A PE router is on the Service Provider Edge. Each CE device is attached, via some sort of attachment circuit, to one or more Provider Edge (PE) routers

The VRF is the VPN Routing and Forwarding Table

MPLS LSP or GRE tunnels are used to transfer the actual traffic


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 75



PE Blue VPRN

Red VPRN

MP-BGP route exchange for all services

PE

PE

PE

IP/MPLS infrastructure can be used to offer multiple services.

From a customer perspective, the VPRN looks like a Layer 3 router.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 76


Flowchart # 1 For Troubleshooting VPRN Issues

No routes in the VRF?

Is the VPRN Enabled? Enable VPRN

Is an RD configured?

Configure a Route-Distinguisher. An RD must be configured even if the VPRN

service is local.

NO

NO

YES

YES


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 77



CE routes missing in the VRF?

Is the interface within the VPRN UP?

Enable the interface. Check the status of the port that the

interface/SAP is bound to.

NO

YES


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 78



Routes from remote PE are not getting installed in the VRF?

Is MP-BGP Session UP? Enable BGP configuration

Are routes in BGP RIB-in?This is typically because the VRF import-target ≠ VRF export target

being used by the remote PE

NO

NO

YES

YES

Is the transport operational?

The VPRN must be bound to an operational SDP for the next-hop of the VPRN route or Auto-Bind LDP or

GRE must be configured.

NO

Is a policy configured? Confirm policy settingsNO

YES

YES

MP-BGP:

Multi Protocol BGP (required to support VPRNs).

To enable MP-BGP: Routing Instance -> BGP site -> VPN tab -> VPN IPv4 checked.

BGP RIB-in (Routing Information Base “in”):

(CLI: show router bgp routes)

Routes received from other BGP peers.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 79


Troubleshooting VPRNs – Failure Scenario 1

A newly created VPRN is operationally up but routes are not being properly advertised between sites.

r1

VPRN Service

r3


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 80




Verify Issue

Both VPRN sites have one interface All objects are operationally up

(Service 33 -> Topology)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 81



Show Routes on the routers

R3 sees no remote routes

R1 has no routes in the VRF

It is expected that we would see local and remote routes on both routers.

(Service -> Topology -> right click on site -> Show routes)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 82



A VPRN ping from r1 to r3 VPRN interface vprn_2_2 (10.1.3.2) fails with Status = Invalid Source IP


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 83



2. Investigation


View the alarm in the Dynamic Alarm window or in the VPRN service itself

There is one alarm related to the VPRN in question


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 84



The alarm indicates that a Route Distinguisher is not configured on r1

Click the View Alarmed Object button


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 85



The Route Distinguisher on Routing Instance r1 is not configured

(Service properties -> Routing tab -> General tab)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 86



3. Take corrective action

Correct the Route Distinguisher on r1

SAM can suggest values configured within the VPRN service

(Service properties -> Routing tab -> General tab)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 87



4. Verification

Verify that the routes are now correct on both sites

(Service -> Topology -> right click on site -> Show routes)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 88


Troubleshooting VPRNs – Failure Scenario 1 (Verification cont.)

Perform OAM test of VPRN ping, which was executed in step #1, to verify the issue no longer exists

Also, note that the alarm was implicitly cleared


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 89


Troubleshooting VPRN Issues (LAB 9.5)

Users on some (not all) subnets on r3 cannot connect to the corporate server located at headquarters on r1. For this exercise, subnets are represented by loopbacks.

Service ID = 34Which subnet(s) on r3 cannot connect to the corporate server? Find the cause but DO NOT fix it

r1Headquarters

Subnets

r3

10.3.3.0/24

10.4.4.0/24

10.5.5.0/24

10.2.2.0/24


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 90


Troubleshooting VPRN Issues (LAB 9.5)

Best Practice:

When troubleshooting VPRN issues, be sure to view and confirm the attributes under the Routing tab of a VPRN Routing Instance (Site)

(Service properties -> VPRN Site -> Routing tab)


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 91


Troubleshooting VPRN Issues (Lab 9.6)

Users between sites r1 and r3 cannot communicate to each other.

Service ID = 33 Find the cause but DO NOT fix it

r1

VPRN Service

r3

10.1.2.0/24 10.1.3.0/24


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile


Mirror Services


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 93


Mirror Services

Customer packets can be examined as they traverse the network

Alcatel-Lucent’s 7x50 routers support service-based mirroring

Can mirror on an n-to-1 unidirectional service basis and re-encapsulate the mirrored data for transport through the core network to another location, using either IP or MPLS tunneling as required

Original packets are forwarded, while a copy is sent from the mirrored port to the mirroring (destination) port


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 94


Mirror Services

Service mirroring allows an operator to see the actual traffic on a customer’s service with a ‘sniffer’ sitting in a central location

In many cases, this reduces the need for a separate, costly overlay sniffer network

Is not an End Customer consumable service

Allows operators to monitor live traffic

Traffic from a port, SAP or SDP can be mirrored (duplicated) and sent to a test device either locally or remotely


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 95


Mirror Services

Service Sites

Destination Site: a service site where the test equipment is attached

— A mirror service must have a destination site

Source Site: a service site where the traffic that is being monitored exists

— Only created if the port to be monitored is not on the same siteas the test equipment site.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 96


Mirror Services - Example #1

Create a remote mirror of the Traffic VPLS service

Traffic VPLS

Mirror

(Manage -> Service -> Mirror Services)

Note that for a Mirror Service, the source SAP is not shown in the topology view, and only one SDP is used.


s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Module 9 - 97




s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile



s A

LU-I

PD

-SR

C A

lcat

el-L

ucen

t_N

etw

ork_

and_

Ser

vice

_Tro

uble

shoo

ting_

with

_the

_562

0_S

AM

Gui

de is

for

excl

usiv

e us

e of

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Kaz

i_Z

ial_

Hoq

ue -

WIN

D_M

obile

Documents

Kazi_Zial_Hoque.2013-11-22.SAM_StudentGuide_Ver1.4