Module 0 - 1
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 0 |
Module 0 - 2
Module Overview
ALCATEL-LUCENT
NETWORK ROUTING SPECIALIST II
Kazi_Zial_Hoque - WIND_Mobile
ALCATEL-LUCENT
NETWORK ROUTING SPECIALIST I
ALCATEL-LUCENT
ALCATEL-LUCENT
TRIPLE PLAY ROUTING PROFESSIONAL MOBILE ROUTING PROFESSIONAL
36 DAYS / 8 COURSES / 8 WRITTEN EXAMS /
1 PRACTICAL LAB EXAM
ALCATEL-LUCENT
SERVICE ROUTING ARCHITECT
49 DAYS / 11 COURSES / 11 WRITTEN EXAMS / 2 PRACTICAL LAB EXAMS
Module 0 |
This course is NOT part of the Alcatel-Lucent Service Routing Certification (SRC) Program. See www.alcatellucent.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 todays 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.
Module 0 - 3
Module 0 |
Module 0 - 4
Kazi_Zial_Hoque - WIND_Mobile
Exam Pre-requisites
(4A0-XXX)
4A0-100
NA
4A0-101
NA
4A0-102
NA
4A0-103
NA
4A0-104
NA
4A0-105
NA
4A0-106
NA
4A0-107
NA
4A0-108
NA
4A0-109
NA
4A0-110
NA
4A0-M01
NA
4A0-M02
NA
NRSII4A0
MRP4A0
ASRA4A0
100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110,
NRSII4A0
Module 0 |
Module 0 - 5
Exam Number
Exam Name
Kazi_Zial_Hoque - WIND_Mobile
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?
Kazi_Zial_Hoque - WIND_Mobile
Sign up today at
www.alcatel-lucent.com/src/mysrlab
Module 0 |
MySRLab
Like owning your own Service Router Lab
Module 0 |
Kazi_Zial_Hoque - WIND_Mobile
Written Exams
Delivered by Prometric
Kazi_Zial_Hoque - WIND_Mobile
Module 0 |
Module 0 - 8
Exam Delivery
Virtual classroom
Delivery from any Alcatel-Lucent locations globally
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
Kazi_Zial_Hoque - WIND_Mobile
Module 0 |
Viewtheclassscheduleandregisterat
http://www.alcatellucent.com/src/courses
Module 0 |
10
Get the benefits of live SRC training without expensive travel &
living and time-away costs
Kazi_Zial_Hoque - WIND_Mobile
http://www.alcatel.lucent.com/src/studentportal
Module 0 |
11
Module 0 |
12
12
Module 0 |
13
http://www.alcatel-lucent.com/university
http://www.alcatel-lucent.com/src
Module 0 - 13
Kazi_Zial_Hoque - WIND_Mobile
Course Introduction
Kazi_Zial_Hoque - WIND_Mobile
Module 0 |
14
Module 0 - 14
Module 0 |
15
Module 0 - 15
Kazi_Zial_Hoque - WIND_Mobile
Course Modules
Module 0 |
16
Module 0 - 16
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Registration
Facility information
Restrooms
Communications
Materials
Schedule
Introductions
Name and Company
Experience
Questions
Module 0 |
17
Module 0 - 17
Administration
Module 0 |
18
Module 0 - 18
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
www.alcatel-lucent.com
Module 1 Introduction
Kazi_Zial_Hoque - WIND_Mobile
Module 1 |
Kazi_Zial_Hoque - WIND_Mobile
Module 1 - 2
Module Objectives
Kazi_Zial_Hoque - WIND_Mobile
Introduction
Module 1 |
Module 1 - 4
Kazi_Zial_Hoque - WIND_Mobile
troubleshooting
Kazi_Zial_Hoque - WIND_Mobile
Introduction
Navigation Trees
Equipment
Routing
Service components
Statistics
Policy audits
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 1 |
Module 1 - 6
Kazi_Zial_Hoque - WIND_Mobile
Troubleshooting Methodology
Kazi_Zial_Hoque - WIND_Mobile
Introduction
Network architecture
Routing protocols
Services
Module 1 |
Module 1 - 8
Kazi_Zial_Hoque - WIND_Mobile
Module 1 |
Module 1 - 9
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
2. Investigation
Module 1 |
10
Troubleshooting is not just diving in and fixing the problem. Complex problems can require a more systematic
approach.
Module 1 - 10
Module 1 |
11
Module 1 - 11
Kazi_Zial_Hoque - WIND_Mobile
Module 1 |
12
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.
Module 1 - 12
Kazi_Zial_Hoque - WIND_Mobile
2. Investigation
Module 1 |
13
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.
Module 1 - 13
Kazi_Zial_Hoque - WIND_Mobile
Module 1 |
14
Module 1 - 14
Kazi_Zial_Hoque - WIND_Mobile
4. Verification
Phases:
1.
2.
3.
4.
Kazi_Zial_Hoque - WIND_Mobile
Key points
Module 1 |
15
Module 1 - 15
Methodology Summary
Module 1 |
16
Module 1 - 16
Kazi_Zial_Hoque - WIND_Mobile
Module Summary
Module 1 |
17
Module 1 - 17
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
www.alcatel-lucent.com
Module 2- 1
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
Module 2- 2
Kazi_Zial_Hoque - WIND_Mobile
Module Objectives
Module 2 |
Module 2- 3
Alarm history
Kazi_Zial_Hoque - WIND_Mobile
Module 2- 4
Kazi_Zial_Hoque - WIND_Mobile
All alarms that appear in the 5620 SAM Alarm window are
assembled by the SAM.
Module 2 |
Module 2- 5
Kazi_Zial_Hoque - WIND_Mobile
Alarm Sources
Trap lost
Trap flood
NMS network overloaded or down
Module 2 |
See SNMP trap sequence verification in the Planning Guide for more info.
Module 2- 6
Kazi_Zial_Hoque - WIND_Mobile
Log 98 on NE
Module 2 |
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.
Module 2- 7
Kazi_Zial_Hoque - WIND_Mobile
Alarms Example #1
Module 2- 8
Kazi_Zial_Hoque - WIND_Mobile
2. Investigation
Determine cause
Module 2 |
Module 2- 9
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
10
Module 2- 10
Kazi_Zial_Hoque - WIND_Mobile
1. Finding Alarms
Module 2- 11
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
12
The color of the alarm indicates the alarms severity. Tip: the color associated with a severity can be seen
in the Dynamic Alarm windows 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.
Module 2- 12
Kazi_Zial_Hoque - WIND_Mobile
An Alarm Appears
Module 2 |
13
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.
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.
Module 2- 13
Kazi_Zial_Hoque - WIND_Mobile
Finding an Alarm
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.
3. From the Alarm Info form, click the View Alarm History button.
Best Practice:
When possible, the 2nd and 3rd methods should be used
because they automatically build a filter
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 2 |
14
Module 2- 14
Kazi_Zial_Hoque - WIND_Mobile
Alarm History
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
15
Module 2- 15
Module 2 |
16
Module 2- 16
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
17
Double clicking on an alarm in the Dynamic Alarm Window will open the Alarm Info Window for that
alarm.
Module 2- 17
The Description under the Details tab may reveal the issue immediately
Kazi_Zial_Hoque - WIND_Mobile
Best Practice:
When viewing the alarm info, be sure to note the following
attributes: Probable Cause, Additional Text, Description and
Remedial Action.
Module 2 |
18
Module 2- 18
The Remedial Action under the Details tab may give instructions on how to fix
the issue
Kazi_Zial_Hoque - WIND_Mobile
Square indicates
object alarm status
Module 2 |
19
The alarm coloring can been seen by looking at the Alarm Statistics tab of the Dynamic Alarm Window
Module 2- 19
Circle indicates
aggregated alarm
status
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
20
To make the new Dynamic Alarm window configuration default, in the SAM main menu select;
Application -> Save Workspace
Module 2- 20
Quick filter
Type and hit Enter
Module 2 |
21
Module 2- 21
Up to 6 alarm windows
supported
Kazi_Zial_Hoque - WIND_Mobile
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
Module 2 |
22
Module 2- 22
Kazi_Zial_Hoque - WIND_Mobile
Alarm Flags
Module 2 |
23
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
Module 2- 23
Kazi_Zial_Hoque - WIND_Mobile
Detachable Windows
2. Acknowledging Alarms
Module 2- 24
Kazi_Zial_Hoque - WIND_Mobile
Best Practice:
When troubleshooting, be sure to acknowledge all associated
alarms.
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 2 |
25
Module 2- 25
Kazi_Zial_Hoque - WIND_Mobile
Acknowledging an Alarm
Module 2- 26
Kazi_Zial_Hoque - WIND_Mobile
Best Practice:
If multiple alarms are present, the alarm(s) at the lowest MO
should be investigated first.
Module 2 |
27
Module 2- 27
Kazi_Zial_Hoque - WIND_Mobile
Alarm Hierarchy
Module 2 |
28
Module 2- 28
Kazi_Zial_Hoque - WIND_Mobile
Aggregation
Objects have object and aggregated
alarm status icons
The square is the objects alarm status
The circle is the aggregated alarm status
Module 2 |
29
Module 2- 29
Kazi_Zial_Hoque - WIND_Mobile
Node
Shelf
Aggregated
alarm status
Slot
Card
Object alarm
Port
Module 2 |
30
Aggregated does not mean that theres an alarm at each level; it means that the higher
levels have an indicator when theres an alarm at a lower level.
This helps operators to drill down to the cause more quickly.
Module 2- 30
Kazi_Zial_Hoque - WIND_Mobile
Service
Aggregated
alarm status
Site
SAP
Module 2 |
31
Module 2- 31
Kazi_Zial_Hoque - WIND_Mobile
Best Practice:
When both sets of alarms are present, troubleshoot the
Affecting alarm first
Module 2 |
32
Module 2- 32
Kazi_Zial_Hoque - WIND_Mobile
Port
Alarms on
related objects
Affecting
alarms
SAP
Module 2 |
33
Module 2- 33
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
34
Module 2- 34
Kazi_Zial_Hoque - WIND_Mobile
Affecting/Affected/Related objects/Aggregated
Shelf
Aggregated
alarms
i.e. port alarm
Slot
Service
Card
Object alarm X
Site
Affecting Alarms
(i.e Port)
Port
Alarms on
Related Objects
(i.e. SAPs)
Aggregated
alarms
i.e. SAP alarm
SAP
Object alarm
Module 2 |
35
Module 2- 35
Node
Kazi_Zial_Hoque - WIND_Mobile
Fault Management
Module 2 |
36
Module 2- 36
Kazi_Zial_Hoque - WIND_Mobile
Equipment
Node
Shelf
Service
Slot
Service
Card
Site
LSP
Port
SAP
MPLS
Network
Module 2 |
37
Module 2- 37
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
38
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.
Module 2- 38
Correlation in the 5620 SAM is based on correlation rules that are built
into it for each alarm
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
39
Module 2- 39
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
40
Module 2- 40
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
41
Module 2- 41
Kazi_Zial_Hoque - WIND_Mobile
Correlation Off
Module 2 |
42
Module 2- 42
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
43
Module 2- 43
Kazi_Zial_Hoque - WIND_Mobile
Node
Shelf
Slot
Service
Card
X Port
Correlating Alarm
Site
SAP
X Object alarm
Correlated Alarm
Module 2 |
44
Module 2- 44
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
Kazi_Zial_Hoque - WIND_Mobile
Correlation Hierarchy
Module 2- 45
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
46
Module 2- 46
Kazi_Zial_Hoque - WIND_Mobile
Module 2- 47
Kazi_Zial_Hoque - WIND_Mobile
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
Module 2 |
48
Module 2- 48
Kazi_Zial_Hoque - WIND_Mobile
Physical Topology
Module 2 |
49
Module 2- 49
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
50
(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)
Module 2- 50
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
51
Module 2- 51
Physical Topology
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
52
(Select Service with ID # 71 -> Tunnel used by mesh-SDP on r5 from r5-r1 properties ->
LSPs tab -> Properties of the Dynamic LSP from r5-r1 -> General tab)
Module 2- 52
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
53
Module 2- 53
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
54
Module 2- 54
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
55
Module 2- 55
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
56
(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)
Module 2- 56
Kazi_Zial_Hoque - WIND_Mobile
The service has no ingress interface because both links are down
Module 2 |
57
Module 2- 57
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
58
(Routing -> properties of routing network interface r5-r2 on r5 -> Faults tab)
Module 2- 58
Kazi_Zial_Hoque - WIND_Mobile
Module 2- 59
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
60
Module 2- 60
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
61
In above image the rows are white because the services are operationally up.
(Manage -> Service -> Services)
Module 2- 61
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
62
Module 2- 62
Open the Service Configuration form and note the State Cause information
To drill further, expand the service navigation tree.
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
63
Module 2- 63
From the service navigation tree, click the objects with object
alarms (red square)
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
64
Module 2- 64
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
65
Module 2- 65
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
66
Module 2- 66
Kazi_Zial_Hoque - WIND_Mobile
Tools
Module 2- 67
Kazi_Zial_Hoque - WIND_Mobile
Alarm Squelching
Additional Text
Module 2 |
68
Module 2- 68
Kazi_Zial_Hoque - WIND_Mobile
Alarm Tools
Module 2 |
69
All alarms in 5620 SAM list can be seen under: (Administration -> Alarm Settings -> Specific tab)
Module 2- 69
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
70
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).
Module 2- 70
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
71
Module 2- 71
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
72
Module 2- 72
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
73
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 ports MTU value in the
alarms additional text field.
Module 2- 73
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
74
Module 2- 74
Best Practice:
Kazi_Zial_Hoque - WIND_Mobile
Unexpected Behaviors
Module 2- 75
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
76
Module 2- 76
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
77
Module 2- 77
Kazi_Zial_Hoque - WIND_Mobile
View from
Equipment
Navigation Tree
might not show an
alarm.
Consider examining
the Routing
Navigation Tree
instead
Module 2 |
78
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.
Module 2- 78
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
79
Module 2- 79
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
80
This feature is only available in 5620 SAM Release 10.0 R5 and above.
Module 2- 80
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
81
Module 2- 81
Select the desired specific alarm and open its policy form
Kazi_Zial_Hoque - WIND_Mobile
Module 2 |
82
Module 2- 82
Kazi_Zial_Hoque - WIND_Mobile
Module Summary
Module 2 |
83
Module 2- 83
Kazi_Zial_Hoque - WIND_Mobile
Module 2- 84
Kazi_Zial_Hoque - WIND_Mobile
www.alcatel-lucent.com
Kazi_Zial_Hoque - WIND_Mobile
Module 3 - 1
Kazi_Zial_Hoque - WIND_Mobile
Module Objectives
Module 3 |
Module 3 - 2
Kazi_Zial_Hoque - WIND_Mobile
Module 3 |
Module 3 - 3
Overview
Kazi_Zial_Hoque - WIND_Mobile
Navigation Trees
Module 3 - 4
Navigation Trees
Kazi_Zial_Hoque - WIND_Mobile
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
Module 3 |
Module 3 - 5
Module 3 |
Kazi_Zial_Hoque - WIND_Mobile
Module 3 - 6
Module 3 |
Kazi_Zial_Hoque - WIND_Mobile
Module 3 - 7
Module 3 |
Kazi_Zial_Hoque - WIND_Mobile
Module 3 - 8
Kazi_Zial_Hoque - WIND_Mobile
Right-click on a Group
Module 3 |
Module 3 - 9
Kazi_Zial_Hoque - WIND_Mobile
Right-click on a router
Module 3 |
10
Module 3 - 10
Kazi_Zial_Hoque - WIND_Mobile
Module 3 |
11
Module 3 - 11
Kazi_Zial_Hoque - WIND_Mobile
Navigation Trees
Module 3 - 12
Module 3 |
13
Kazi_Zial_Hoque - WIND_Mobile
Module 3 - 13
Module 3 |
14
Kazi_Zial_Hoque - WIND_Mobile
Module 3 - 14
Module 3 |
15
In the contextual menu via right-click, select Make Root in New Tree
New window gets created, with the root of that windows 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.
Module 3 - 15
Allows operators to
focus on specific
branches of the
network tree
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Becomes
Module 3 |
16
Within a Navigation Tree window, the root can be changed. No new window is spawned.
Module 3 - 16
Module 3 |
17
Kazi_Zial_Hoque - WIND_Mobile
Module 3 - 17
Kazi_Zial_Hoque - WIND_Mobile
Navigation Trees
Module 3 - 18
Kazi_Zial_Hoque - WIND_Mobile
Module 3 |
19
Module 3 - 19
Kazi_Zial_Hoque - WIND_Mobile
Module 3 |
20
The IGP/IRP Instances dont 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.
Module 3 - 20
Module 3 |
21
In this case, the RIP protocol is enabled, but its status is down. Theres no child of that line in the tree, which
suggests that theres 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 theres 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.
Module 3 - 21
Shows:
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Navigation Trees
Module 3 - 22
Module 3 |
23
Determine the status of a service from the services 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.
Module 3 - 23
Kazi_Zial_Hoque - WIND_Mobile
Network Objects:
Physical equipment
Routing
Kazi_Zial_Hoque - WIND_Mobile
Module Summary
Service components
Module 3 |
24
Module 3 - 24
Module 3 |
25
Kazi_Zial_Hoque - WIND_Mobile
Module 3 - 25
Module 3 |
26
Kazi_Zial_Hoque - WIND_Mobile
Module 3 - 26
Kazi_Zial_Hoque - WIND_Mobile
www.alcatel-lucent.com
Module 3 - 27
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module Objectives
Module 4 |
Module 4 - 2
Module 4 |
Kazi_Zial_Hoque - WIND_Mobile
Map Legends
Module 4 - 3
Use Show Alarmed Links Only to switch from a normal view of all
links to displaying only links that have alarms
Kazi_Zial_Hoque - WIND_Mobile
Enabled (Yellow)
Module 4 |
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.
Module 4 - 4
Kazi_Zial_Hoque - WIND_Mobile
Module 4 |
Module 4 - 5
Module 4 |
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.
Module 4 - 6
Use this option to separate alarm links from the link group
within the topology window
Kazi_Zial_Hoque - WIND_Mobile
Module 4 |
Kazi_Zial_Hoque - WIND_Mobile
Module 4 - 7
Kazi_Zial_Hoque - WIND_Mobile
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
Module 4 |
Module 4 - 8
Kazi_Zial_Hoque - WIND_Mobile
Module 4 |
Module 4 - 9
Module 4 |
10
Navigate, located at the bottom of the Properties window, allows the operator to find the router in the Physical or
Service Topology map quickly.
Module 4 - 10
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Flat Maps
Module 4 |
11
Module 4 - 11
Kazi_Zial_Hoque - WIND_Mobile
Provides a complete
network view without
topology groups
Physical Topology
Flat Map
Module 4 |
12
Module 4 - 12
Kazi_Zial_Hoque - WIND_Mobile
Overview Button
Module 4 |
13
Module 4 - 13
Module 4 |
14
Kazi_Zial_Hoque - WIND_Mobile
Module 4 - 14
Module 4 |
15
Kazi_Zial_Hoque - WIND_Mobile
Highlight Sessions
Module 4 - 15
Module 4 |
16
Kazi_Zial_Hoque - WIND_Mobile
Module 4 - 16
Kazi_Zial_Hoque - WIND_Mobile
Some Topology icons have two text labels that can be configured to display
various fields.
Module 4 |
17
For example, the 2nd text field can be used to display the Location or Management IP address.
Module 4 - 17
Module 4 |
18
Excellent tool to quickly view multiple router values at once without having to search through the routers
Properties form.
Also great for viewing the same value over multiple routers without having to launch multiple Properties forms.
Module 4 - 18
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 4 |
19
Module 4 - 19
Kazi_Zial_Hoque - WIND_Mobile
Module 4 |
20
Module 4 - 20
Right-click on a router
Also present in the Service
Tunnel Topology
Module 4 |
21
Kazi_Zial_Hoque - WIND_Mobile
Module 4 - 21
Before
Kazi_Zial_Hoque - WIND_Mobile
Layout
After
Module 4 |
22
Module 4 - 22
Kazi_Zial_Hoque - WIND_Mobile
Module 4 |
23
Module 4 - 23
Module 4 |
24
Kazi_Zial_Hoque - WIND_Mobile
Module 4 - 24
Module 4 |
25
Kazi_Zial_Hoque - WIND_Mobile
Module 4 - 25
Module 4 |
26
Kazi_Zial_Hoque - WIND_Mobile
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)
Module 4 - 26
Module 4 |
27
The Find button Find Link on the Topology Map offers two pre-defined filters in its search: Discovered Physical
Links and Physical Links
Module 4 - 27
Kazi_Zial_Hoque - WIND_Mobile
Module 4 |
28
Kazi_Zial_Hoque - WIND_Mobile
Module 4 - 28
Module 4 |
29
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.
Module 4 - 29
Kazi_Zial_Hoque - WIND_Mobile
Module 4 |
30
Kazi_Zial_Hoque - WIND_Mobile
Clearing the reference also clears the User and Reference Time fields
The Discovery Time is unaffected by clearing the reference
Module 4 - 30
Kazi_Zial_Hoque - WIND_Mobile
Module 4 |
31
Module 4 - 31
LLDP Labels
Module 4 |
32
Kazi_Zial_Hoque - WIND_Mobile
Module 4 - 32
Without Labels
With Labels
- System Name TLV
Module 4 |
33
Kazi_Zial_Hoque - WIND_Mobile
LLDP Labels
Module 4 - 33
Kazi_Zial_Hoque - WIND_Mobile
Module 4 |
34
Module 4 - 34
Kazi_Zial_Hoque - WIND_Mobile
www.alcatel-lucent.com
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
Module 5 - 2
Kazi_Zial_Hoque - WIND_Mobile
Module Objectives
Module 5 - 3
Kazi_Zial_Hoque - WIND_Mobile
Overview
Module 5 - 4
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
For in-band testing, the OAM packets closely resemble customer packets, but are distinguishable from
customer packets so they are kept within the service providers network and not forwarded to the
customer.
Module 5 - 5
Kazi_Zial_Hoque - WIND_Mobile
Overview
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.
Module 5 |
Module 5 - 6
Kazi_Zial_Hoque - WIND_Mobile
Right-click on a
service site to open
the menu
3
Create a new test
OR
Select a previously
created test
1
To enable the OAM
menu options,
select the OAM
checkbox
Module 5 |
This feature is only available in 5620 SAM Release 8.0 R5 and above.
Module 5 - 7
OAM Tests can be fully configured from the Service Topology window
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
Module 5 - 8
Module 5 |
Module 5 - 9
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
10
Module 5 - 10
Kazi_Zial_Hoque - WIND_Mobile
Module 5 - 11
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
12
Module 5 - 12
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
13
Module 5 - 13
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
14
Module 5 - 14
Kazi_Zial_Hoque - WIND_Mobile
VCCV echo
reply
VLL Service
PE1
PE2 (third-party
switch)
SAP to
CE1
SAP to
CE2
Module 5 |
15
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
Module 5 - 15
Kazi_Zial_Hoque - WIND_Mobile
Trace
Displays hop-by-hop path for a destination IP address
Allows target types of Core Routing Site or VPRN Site
Module 5 |
16
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.
Module 5 - 16
Kazi_Zial_Hoque - WIND_Mobile
LSP
Ping
request
LSP
LSP
Egress LER
(terminating
device of the LSP)
Module 5 |
17
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
Module 5 - 17
Kazi_Zial_Hoque - WIND_Mobile
LSP Trace
request
LSP T
LSP
Ingress LER
(Originating
SR)
Kazi_Zial_Hoque - WIND_Mobile
LSP T
LSP
LSP
Egress LER
(terminating
device of the LSP)
LSP
Trace
replies
Module 5 |
18
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
Module 5 - 18
Module 5 |
19
Module 5 - 19
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
20
Module 5 - 20
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
21
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.
Module 5 - 21
Kazi_Zial_Hoque - WIND_Mobile
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 (farend) MAC address or the broadcast address
Module 5 |
22
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.
Module 5 - 22
Ping
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
23
Module 5 - 23
Kazi_Zial_Hoque - WIND_Mobile
SAP
Module 5 |
24
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.
Module 5 - 24
Kazi_Zial_Hoque - WIND_Mobile
Module 5 - 25
Kazi_Zial_Hoque - WIND_Mobile
ID
Name
Description
Administrative State
NE Persistent if enabled, the OAM test is deployed to a router
after the first run and it remains on the router in memory only
NE 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)
Module 5 |
26
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
Module 5 - 26
Kazi_Zial_Hoque - WIND_Mobile
Execute Details
Number of Test Probes
Probe Interval (s)
Probe Timeout (s)
Test Probe
Size (octets)
Time To Live
Forwarding Class
Forwarding Profile
Module 5 |
27
Module 5 - 27
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
28
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
Module 5 - 28
Kazi_Zial_Hoque - WIND_Mobile
Type
Inbound Jitter (default) - Inbound Loss
Outbound Jitter
- Outbound Loss
Roundtrip Jitter
- Roundtrip Loss
- Inbound Latency
- Outbound Latency
- Roundtrip Latency
NE Threshold tab -
Module 5 |
29
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
Module 5 - 29
Kazi_Zial_Hoque - WIND_Mobile
Module 5 - 30
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
31
Module 5 - 31
Kazi_Zial_Hoque - WIND_Mobile
Module 5 - 32
Kazi_Zial_Hoque - WIND_Mobile
Best practice:
Create at least one test suite for each Entity Type for validation
and troubleshooting purposes
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 5 |
33
(Entity Type: Tools -> Service Test Manager -> Create -> Test Suite -> General tab)
Module 5 - 33
The 5620 SAM STM provides the ability to group various OAM
tests into test suites for network troubleshooting
Kazi_Zial_Hoque - WIND_Mobile
Test Suites
Generated tests
Created by the 5620 SAM for use against a specific network
entity
When 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 groups
Might typically include transport-layer diagnostics, such as an
LSP trace or a tunnel ping
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 5 |
34
Module 5 - 34
First-run tests
Kazi_Zial_Hoque - WIND_Mobile
Test Suites
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 both
Must create an Accounting Policy with Type = NE Schedulable
Tests
Module 5 |
35
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.
Module 5 - 35
Kazi_Zial_Hoque - WIND_Mobile
Test Policy
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
36
Module 5 - 36
Module 5 |
37
Please see the 5620 SAM 10.0 R5 Planning Guide for more scalability information, such as Guidelines for
maximizing STM text execution.
Module 5 - 37
Kazi_Zial_Hoque - WIND_Mobile
STM Scalability
Test suite weights are identified in the 5620 SAM GUIs Test
Suites List window
If too many tests are run concurrently and this limit is exceeded,
tests will be skipped
Module 5 |
38
Module 5 - 38
Kazi_Zial_Hoque - WIND_Mobile
STM Scalability
Module 5 |
39
Module 5 - 39
In 5650 CPAM:
Kazi_Zial_Hoque - WIND_Mobile
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
ID 59
Uni-directional Tunnels
ID 60
r5
r6
Module 5 |
40
Module 5 - 40
Kazi_Zial_Hoque - WIND_Mobile
Symptoms:
Tunnels (SDP) are
operationally up
LSPs have been assigned
Module 5 |
41
Module 5 - 41
Kazi_Zial_Hoque - WIND_Mobile
No fault indicator
None
Module 5 |
42
(Manage -> Service Tunnels -> Tunnel -> General Tab -> State cause)
Module 5 - 42
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
43
(Manage -> Service Tunnels -> Tunnel -> Tests -> Tunnel Ping)
To check for round-trip connectivity, the Return Tunnel ID must be set.
Module 5 - 43
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
44
(Manage -> Service Tunnels -> Tunnel -> Tests -> Tunnel Ping)
Module 5 - 44
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
45
This policy will apply to all the SasThresholdExceeded alarms for every test where the SAS threshold is
being tested.
(Administration -> Alarm Settings -> Specific)
Module 5 - 45
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
46
Module 5 - 46
Kazi_Zial_Hoque - WIND_Mobile
Roundtrip latency
threshold is crossed
Module 5 |
47
Module 5 - 47
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
48
SasThresholdExceeded alarm might have Critical severity because of the escalation policy configured
earlier.
(Dynamic Alarm window)
Module 5 - 48
Module 5 |
49
(Manage -> Service Tunnels -> Tunnel -> LSPs tab -> Dynamic LSP -> Tests -> LSP Trace)
Module 5 - 49
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
50
Module 5 - 50
Module 5 |
51
Module 5 - 51
There is no problem with the newly-created tunnels roundtrip connectivity or LSP hops
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
52
Module 5 - 52
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
53
(Tools -> Service Test Manager -> Test Suite -> Test Policy)
Module 5 - 53
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
54
Module 5 - 54
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
55
Kazi_Zial_Hoque - WIND_Mobile
Module 5 - 55
VPLS Service
r1
r3
Module 5 |
56
Module 5 - 56
Kazi_Zial_Hoque - WIND_Mobile
2. Using MTU ping, find the maximum MTU size available for the
tunnel
Module 5 |
57
MPLS SDP
Default MTU without FRR = 1556
MTU ping = 1556
Port MTU overhead = 1578 22 = 1556
Where overhead = 14 (Ethernet) + 8 (two MPLS labels).
Module 5 - 57
The cause of the problem is that the size of the tunnel from
r1 to r3 has the MTU size too low at 1512
Kazi_Zial_Hoque - WIND_Mobile
1. Create a scheduled CPE ping test suite for VPLS 31 that periodically
measures the Roundtrip Latency between each VPLS site and an end
device (in this case the CPE is the Traffic Generator). Set a Roundtrip
Latency Rising Threshold equal to 2 milliseconds.
Module 5 |
58
Module 5 - 58
Kazi_Zial_Hoque - WIND_Mobile
Summary
Module 5 - 59
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
60
Module 5 - 60
Kazi_Zial_Hoque - WIND_Mobile
Module 5 |
61
Module 5 - 61
Kazi_Zial_Hoque - WIND_Mobile
www.alcatel-lucent.com
Module 6 - 1
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
Module 6 - 2
Module Objectives
issues.
Module 6 - 3
Kazi_Zial_Hoque - WIND_Mobile
SNMP
Module 6 |
Module 6 - 4
Kazi_Zial_Hoque - WIND_Mobile
Collection
Storage criteria
File policy - for accounting stats on NEs
Statistics policy - for stats on 5620 SAM
Module 6 |
Module 6 - 5
Kazi_Zial_Hoque - WIND_Mobile
Policy Types
Performance
Accounting
Server Performance
NE troubleshooting
troubleshooting
troubleshooting
Characteristic
Typical use
Source
NE MIBs
On-demand
Yes
Yes if MIB-based
Yes
Scheduled
Collection policy
collection policy
policy
Real-Time Graph
Yes
Yes if MIB-based
Yes
Collection default
Off
Off
Module 6 |
Module 6 - 6
Statistics Type
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
When viewing statistical records from an objects Properties form, a user can
quickly tell whether it is Performance or Accounting
Module 6 |
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
Kazi_Zial_Hoque - WIND_Mobile
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
---
Module 6 |
Module 6 - 8
Module 6 |
Module 6 - 9
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.
Kazi_Zial_Hoque - WIND_Mobile
Policy Configuration
Different MIBs
Polling interval can be set to a minimum of 5 minutes
Applies to all objects on a router (Eg. All GigE ports)
Module 6 |
10
(Tools -> Statistics -> MIB policies -> NE MIB Statistics Policy)
Module 6 - 10
Kazi_Zial_Hoque - WIND_Mobile
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)
Module 6 |
11
Module 6 - 11
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
12
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
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
13
Module 6 - 13
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
14
Kazi_Zial_Hoque - WIND_Mobile
(Tools -> Statistics -> MIB policies -> Specific MIB Statistics Policy)
Module 6 - 14
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
15
Module 6 - 15
Statistics Manager
Can use the link in the Tools menu and paste the monitored object
from the clipboard
2
1
3
Module 6 |
16
Module 6 - 16
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
17
Module 6 - 17
Kazi_Zial_Hoque - WIND_Mobile
If you already have statistics collected for the object, you can
get a Historical Plot
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 6 |
18
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.
Module 6 - 18
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
19
Module 6 - 19
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
20
Module 6 - 20
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
21
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 objects properties form. To disable, simply deselect the Display in
Menus checkbox.
Module 6 - 21
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
22
Kazi_Zial_Hoque - WIND_Mobile
Module 6 - 22
Module 6 |
23
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
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
24
Module 6 - 24
Kazi_Zial_Hoque - WIND_Mobile
TCA Policy
Module 6 |
25
Module 6 - 25
Kazi_Zial_Hoque - WIND_Mobile
TCA Policy
Module 6 |
26
Kazi_Zial_Hoque - WIND_Mobile
Module 6 - 26
TCA Policy
a.
b.
c.
d.
Module 6 |
27
Kazi_Zial_Hoque - WIND_Mobile
Module 6 - 27
TCA Policy
Module 6 |
28
Module 6 - 28
Kazi_Zial_Hoque - WIND_Mobile
TCA Policy
Within this tab, click the Assign button on the right to assign
this physical object to a previously configured TCA Policy
Module 6 |
29
Module 6 - 29
Kazi_Zial_Hoque - WIND_Mobile
TCA Tab
Module 6 |
30
Module 6 - 30
Kazi_Zial_Hoque - WIND_Mobile
As of SAM Release 10.0 R5, users are able to plot port utilization
directly in the statistics plotter
Module 6 |
31
Module 6 - 31
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
32
Module 6 - 32
Kazi_Zial_Hoque - WIND_Mobile
Statistics - Exercise 1
Accounting Policy :
Link File Policy to Accounting Policy
Select specific Accounting statistics type for troubleshooting
purposes
Module 6 |
33
Module 6 - 33
File Policy :
Kazi_Zial_Hoque - WIND_Mobile
Accounting Statistics
MIB-based statistics
Module 6 |
34
(Manage -> Service -> Services -> VPLS # -> Layer 2 Access Interface -> Statistics)
Module 6 - 34
Kazi_Zial_Hoque - WIND_Mobile
No traffic because
Octets are constant
No dropped packets
because value is constant
Historical
plot only
Module 6 |
35
Module 6 - 35
Configured 5
minute interval
Kazi_Zial_Hoque - WIND_Mobile
Periodic values
enable easier
traffic monitoring
(E.g. No traffic will
show a value of 0)
Real-time
Plotting
Module 6 |
36
Note: This is one of the few accounting stats that is MIB-based and therefore can be collected on-demand.
Module 6 - 36
On-Demand Collection
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
37
Kazi_Zial_Hoque - WIND_Mobile
Module 6 - 37
Statistics - Exercise 2
Alarm Rate
Node Resync
Server Memory
SNMP Trap
Module 6 |
38
Module 6 - 38
Kazi_Zial_Hoque - WIND_Mobile
Module 6 |
39
Module 6 - 39
Kazi_Zial_Hoque - WIND_Mobile
Module Summary
Module 6 |
40
Module 6 - 40
Kazi_Zial_Hoque - WIND_Mobile
Module 6 - 41
Kazi_Zial_Hoque - WIND_Mobile
www.alcatel-lucent.com
Module 7 - 1
Kazi_Zial_Hoque - WIND_Mobile
Module 7 |2
Kazi_Zial_Hoque - WIND_Mobile
Module 7 - 2
Module Objectives
Module 7 - 3
Kazi_Zial_Hoque - WIND_Mobile
Troubleshooting IGPs
Kazi_Zial_Hoque - WIND_Mobile
Module 7 |4
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
areas include
a the
backbone
area, stub All
area
and
NSSA.
Network
andOSPF
Service Troubleshooting
with
5620 SAM v1.4
rights
reserved
2013 Alcatel-Lucent
Module 7 - 4
(M
N t
ki
ti
ti
I t f
ti
IP
OSPF Configuration
Kazi_Zial_Hoque - WIND_Mobile
Module 7 |5
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)
Module 7 - 5
IS-IS Configuration
Kazi_Zial_Hoque - WIND_Mobile
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
Filters (ACL, CPM, etc.)
NOTE: This is also an excellent checklist to follow when troubleshooting IGP
issues
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 7 |6
Module 7 - 6
r2
r4
r1
r3
Module 7 |7
Module 7 - 7
Kazi_Zial_Hoque - WIND_Mobile
Symptoms
Reproduce
Module 7 |8
Module 7 - 8
Kazi_Zial_Hoque - WIND_Mobile
Reproduce (continued)
Can also run a CLI script from the routers Properties form
Under the Scripts tab, select the desired script and click the
Execute button
Module 7 |9
Kazi_Zial_Hoque - WIND_Mobile
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.
Module 7 - 9
Reproduce (continued)
Module 7 |10
Kazi_Zial_Hoque - WIND_Mobile
Module 7 - 10
Reproduce (continued)
Kazi_Zial_Hoque - WIND_Mobile
Can use the script menu Shortcut or Action button to view and
execute scripts much more quickly.
Module 7 |11
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 objects scripts menu option.
Module 7 - 11
Module 7 |12
To make searching the Dynamic Alarm window easier, filter for Domain containing OSPF.
Module 7 - 12
Kazi_Zial_Hoque - WIND_Mobile
Module 7 |13
Kazi_Zial_Hoque - WIND_Mobile
Module 7 - 13
Warning - InterfaceDbDescriptConfig
2 x Major - NeighborDown
Module 7 |14
Module 7 - 14
Kazi_Zial_Hoque - WIND_Mobile
Module 7 |15
Module 7 - 15
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 7 |16
Note: The ports fault tab Alarms on Related Objects shows two alarms:
Routing Management: OSPF Interface InterfaceDbDescriptConfig
Network - Discovered Physical Link PhysicalLinkPortsMisconfigured
(OSPF Interface -> Interface Properties -> Port)
Module 7 - 16
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
Module 7 |17
Module 7 - 17
Kazi_Zial_Hoque - WIND_Mobile
Make sure any objects that were operationally down are now UP.
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.
Module 7 |18
Module 7 - 18
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 7 |19
Module 7 - 19
Mode
Encap Types
Default
Access
Null
1514
Access
dot1q
1518
Access
mpls
1518
Access
q-in-q
1522
SONET/SDH or TDM
Access
range
1502-4470
ATM
Access
atm
1508
Network
null
1514
Network
dot1q
1518
1GE or 10GE
Network
null
9212
1GE or 10GE
Network
dot1q
9216
SONET/SDH or TDM
Network
range
9208
Module 7 |20
There are many different MTU defaults depending on the port type, encapsulation and mode applied to the port.
Module 7 - 20
Port Type
Kazi_Zial_Hoque - WIND_Mobile
MTU Defaults
r2
r4
r1
r3
Module 7 |21
Module 7 - 21
Kazi_Zial_Hoque - WIND_Mobile
Symptoms
Reproduce
Module 7 |22
Module 7 - 22
Kazi_Zial_Hoque - WIND_Mobile
Module 7 |23
Module 7 - 23
Kazi_Zial_Hoque - WIND_Mobile
2 x Minor - IsisAdjacencyDown
Module 7 |24
Module 7 - 24
Kazi_Zial_Hoque - WIND_Mobile
Module 7 |25
Module 7 - 25
Kazi_Zial_Hoque - WIND_Mobile
r4-r2
Module 7 |26
The Additional Text field shows that the level capability is misconfigured.
Module 7 - 26
r2-r4
Kazi_Zial_Hoque - WIND_Mobile
Module 7 |27
(Alarm -> View Alarmed Object -> ISIS Interface -> General Tab -> Level Capability)
Module 7 - 27
Kazi_Zial_Hoque - WIND_Mobile
Make sure any objects that were operationally down are now
UP
Module 7 |28
Kazi_Zial_Hoque - WIND_Mobile
Module 7 - 28
Kazi_Zial_Hoque - WIND_Mobile
r2
r4
r1
r3
Module 7 |29
Module 7 - 29
Kazi_Zial_Hoque - WIND_Mobile
r2
r4
r1
r3
Module 7 |30
Module 7 - 30
Module 7 |31
Module 7 - 31
Kazi_Zial_Hoque - WIND_Mobile
Module Summary
Module 7 - 32
Kazi_Zial_Hoque - WIND_Mobile
www.alcatel-lucent.com
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
Module 8 - 2
Kazi_Zial_Hoque - WIND_Mobile
Module Objectives
Kazi_Zial_Hoque - WIND_Mobile
Troubleshooting MPLS
Module 8 |
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 packets 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 LSPtunnels. 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.
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 8 - 4
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
Module 8 - 5
Kazi_Zial_Hoque - WIND_Mobile
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
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
Module 8 |
Module 8 - 6
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
Module 8 - 7
Kazi_Zial_Hoque - WIND_Mobile
MPLS Information
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
Module 8 |
Module 8 - 8
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
Module 8 - 9
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
10
Module 8 - 10
Kazi_Zial_Hoque - WIND_Mobile
No CSPF or FRR
r2
r4
Loose
Strict
r1
r3
Module 8 |
11
Module 8 - 11
Kazi_Zial_Hoque - WIND_Mobile
Symptoms
Verify Issue
Module 8 |
12
Module 8 - 12
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
13
Module 8 - 13
Kazi_Zial_Hoque - WIND_Mobile
Critical - LspDown
Module 8 |
14
(Alarm properties)
Module 8 - 14
Kazi_Zial_Hoque - WIND_Mobile
Best Practice:
When an LSP is operationally down, view the LSP-Path Bindings
Failure Code
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 8 |
15
Module 8 - 15
Kazi_Zial_Hoque - WIND_Mobile
Best Practice:
Always resync the LSP-path bindings to view the most recent
Failure Code
Module 8 |
16
Module 8 - 16
Kazi_Zial_Hoque - WIND_Mobile
Note:
Module 8 |
17
Module 8 - 17
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
18
Module 8 - 18
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
19
Module 8 - 19
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
20
Module 8 - 20
Kazi_Zial_Hoque - WIND_Mobile
r4
Loose
Strict
r1
r3
Module 8 |
21
Module 8 - 21
Kazi_Zial_Hoque - WIND_Mobile
Symptoms
Verify Issue
Module 8 |
22
Module 8 - 22
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
23
Based on the above information, we know that the Time Logged was the time the LspDown alarm
cleared.
Module 8 - 23
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
24
Module 8 - 24
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
Kazi_Zial_Hoque - WIND_Mobile
25
Module 8 - 25
r2-r4 is Shutdown
Module 8 |
26
Module 8 - 26
Kazi_Zial_Hoque - WIND_Mobile
Re-signal the
LSP-Path Binding
if desired
Alternatively,
wait until the resignal timer
expires
Module 8 |
27
Module 8 - 27
Kazi_Zial_Hoque - WIND_Mobile
Because the first hop is loose, the LSP re-signals and reverts to
the original actual path
Module 8 |
28
(Properties of Dynamic LSP -> Properties of LSP-Path Binding -> Actual Path tab)
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.
Module 8 - 28
Kazi_Zial_Hoque - WIND_Mobile
CSPF enabled
r2
r4
Loose
Strict
r1
r3
Module 8 |
29
Module 8 - 29
Kazi_Zial_Hoque - WIND_Mobile
Symptoms
Verify Issue
Module 8 |
30
Module 8 - 30
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
31
Module 8 - 31
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
32
Module 8 - 32
Kazi_Zial_Hoque - WIND_Mobile
r2-r4
r4-r3
Module 8 |
33
(Properties of Dynamic LSP -> Properties of LSP-Path Binding -> Provisioned Path tab)
(OAM ICMP test results)
Module 8 - 33
Kazi_Zial_Hoque - WIND_Mobile
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
Module 8 |
34
(Manage -> Networking -> Routing Instances, Router Site -> Protocol Site -> OSPF Site).
Module 8 - 34
Kazi_Zial_Hoque - WIND_Mobile
Change to True
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 8 |
35
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.
Module 8 - 35
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
36
Module 8 - 36
Kazi_Zial_Hoque - WIND_Mobile
r4
Loose
Strict
r1
r3
Module 8 |
37
Module 8 - 37
Kazi_Zial_Hoque - WIND_Mobile
r4
Loose
Strict
r5
r6
r1
r3
Module 8 |
38
Module 8 - 38
Kazi_Zial_Hoque - WIND_Mobile
r2
Loose
Strict
r3
r1
Module 8 |
39
Module 8 - 39
Kazi_Zial_Hoque - WIND_Mobile
Symptoms
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
40
Module 8 - 40
Module 8 |
41
Module 8 - 41
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
42
Module 8 - 42
Kazi_Zial_Hoque - WIND_Mobile
RSVP Session
RSVP sessions show that the node detour is in use (using tunnel ID
2061):
Module 8 |
43
(Properties of Dynamic LSP -> Properties of LSP-Path Binding -> Actual Path tab)
(Properties of Dynamic LSP -> RSVP Sessions tab)
(Properties of Dynamic LSP -> RSVP Session properties)
Module 8 - 43
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
44
Module 8 - 44
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
45
Module 8 - 45
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
46
Module 8 - 46
Kazi_Zial_Hoque - WIND_Mobile
LSP r2-r4-r3 and its associated binding has no failure code and
is operational with the path from r2-r4-r3
Module 8 |
47
(Properties of Dynamic LSP -> Properties of LSP-Path Binding -> Actual Path tab)
Module 8 - 47
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
48
Module 8 - 48
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
49
Module 8 - 49
Kazi_Zial_Hoque - WIND_Mobile
Module Summary
Extra Labs
Kazi_Zial_Hoque - WIND_Mobile
Appendix 8.1
r4
Strict
r1
r3
Module 8 |
51
Module 8 - 51
Kazi_Zial_Hoque - WIND_Mobile
r2
r4
r6
r1
Network and Service Troubleshooting with the 5620 SAM v1.4
r3
Module 8 |
52
Module 8 - 52
Kazi_Zial_Hoque - WIND_Mobile
Module 8 |
53
Module 8 - 53
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
www.alcatel-lucent.com
Module 9 - 1
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
Module 9 - 2
Kazi_Zial_Hoque - WIND_Mobile
Module Objectives
Services Overview
Module 9 - 3
Kazi_Zial_Hoque - WIND_Mobile
Customer
SAP
ServiceID
SDP
Service Tunnel
Service Tunnel
PE-A
SDP
PE-B
ServiceID
Customer
SAP
Subscriber
Service Site
Module 9 |
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 subscribers 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).
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 9 - 4
Service Site
Subscriber
Kazi_Zial_Hoque - WIND_Mobile
Service Components
Viewing Services
Grouped by Customer
Use a filter within the Manage Services window
Sites, SAPs and SDP bindings
Topology view
Module 9 |
Module 9 - 5
Kazi_Zial_Hoque - WIND_Mobile
Module 9 - 6
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
Module 9 - 7
Kazi_Zial_Hoque - WIND_Mobile
Viewing the State Cause indicator can save the operator from
doing unnecessary work and speed up the overall investigation
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 9 |
Module 9 - 8
Service Validation
Module 9 - 9
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
10
Module 9 - 10
Kazi_Zial_Hoque - WIND_Mobile
r5
r6
Module 9 |
11
Module 9 - 11
Kazi_Zial_Hoque - WIND_Mobile
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
Module 9 |
12
Module 9 - 12
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
13
(Manage -> Service -> Services -> Service ID # 37 properties -> Tests tab)
Module 9 - 13
On the VPLS properties form, click the Tests tab, then click
the Test Suite sub tab.
Kazi_Zial_Hoque - WIND_Mobile
Click the OK button and select the test suite created in the
previous slide.
Once selected, the test suite will run automatically.
Module 9 |
14
Module 9 - 14
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
15
Module 9 - 15
If one of the tests in the test suite fails, the service State
Cause will be set to OAM Validation Failed.
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
16
Module 9 - 16
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
17
(Service properties -> Tests tab -> Validation Results -> MAC Ping Result properties)
Module 9 - 17
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
Module 9 |
18
Kazi_Zial_Hoque - WIND_Mobile
Navigate back to the VPLS service properties form and click the Forwarding
Control tab, then click the FIB Entries sub tab
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.
Module 9 - 18
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
Module 9 |
19
Module 9 - 19
Kazi_Zial_Hoque - WIND_Mobile
r5
Kazi_Zial_Hoque - WIND_Mobile
r6
Module 9 |
20
Module 9 - 20
Policy Audit
Module 9 - 21
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
22
Module 9 - 22
Kazi_Zial_Hoque - WIND_Mobile
Policy Overview
Global Policies
Local Policies
Module 9 |
23
Module 9 - 23
Kazi_Zial_Hoque - WIND_Mobile
Global vs Local
Released
Kazi_Zial_Hoque - WIND_Mobile
Draft
Module 9 |
24
Module 9 - 24
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
25
Module 9 - 25
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
Module 9 |
26
Module 9 - 26
Kazi_Zial_Hoque - WIND_Mobile
Local Policies
Kazi_Zial_Hoque - WIND_Mobile
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.
Network and Service Troubleshooting with the 5620 SAM v1.4
Module 9 |
27
The default is false, but for best practice it should be changed to true.
Module 9 - 27
Module 9 |
28
Module 9 - 28
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
29
Kazi_Zial_Hoque - WIND_Mobile
Module 9 - 29
r5
r6
VLL Service
Module 9 |
30
Module 9 - 30
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
31
Module 9 - 31
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
32
Place an advanced filter on the Dynamic Alarm window to show only the TemplateInconsistency alarm.
Module 9 - 32
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
33
(Policies -> QoS -> SROS QoS -> Access Ingress -> Access Ingress)
Module 9 - 33
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
34
Kazi_Zial_Hoque - WIND_Mobile
If differences between the local and global are found, set the local policy to Local Edit Only
If local policy is currently set to Local Edit Only, but is no different from the global policy, set it
to Sync with Global
Module 9 - 34
Module 9 |
35
Module 9 - 35
Kazi_Zial_Hoque - WIND_Mobile
Start Audit
Kazi_Zial_Hoque - WIND_Mobile
From here, the user can choose to compare with the global
policy or another local policy.
Module 9 |
36
Clicking on Local Audit On from the local policy of a NE will pop up this dialog.
Module 9 - 36
Module 9 |
37
Module 9 - 37
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
38
Module 9 - 38
Kazi_Zial_Hoque - WIND_Mobile
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.
Module 9 |
39
(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!
Module 9 - 39
Kazi_Zial_Hoque - WIND_Mobile
2. Resync to global
3. Sync with another local definition
Module 9 |
40
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.
Module 9 - 40
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
41
Module 9 - 41
Best Practice:
Kazi_Zial_Hoque - WIND_Mobile
r5
r6
VLL Service
Module 9 |
42
Module 9 - 42
Kazi_Zial_Hoque - WIND_Mobile
Module 9 - 43
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
44
Module 9 - 44
VLL Overview
PE
VLL Service
Module 9 |
45
Module 9 - 45
PE
Kazi_Zial_Hoque - WIND_Mobile
VLL Overview
r5
Kazi_Zial_Hoque - WIND_Mobile
r6
X
VLL Service
Module 9 |
46
Module 9 - 46
Symptoms
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
47
(Manage Service -> Services -> service id #47 -> General tab)
(Manage Service -> Services -> service id #47 -> General tab -> Topology)
Module 9 - 47
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
48
Module 9 - 48
Module 9 |
49
Kazi_Zial_Hoque - WIND_Mobile
Module 9 - 49
Module 9 |
50
Module 9 - 50
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
51
Module 9 - 51
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
52
Module 9 - 52
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
53
Module 9 - 53
Kazi_Zial_Hoque - WIND_Mobile
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.
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
54
Module 9 - 54
Module 9 |
55
Module 9 - 55
Kazi_Zial_Hoque - WIND_Mobile
VPLS Overview
Blue VPLS
PE
PE
PE
PE
Red VPLS
Module 9 |
56
Module 9 - 56
Kazi_Zial_Hoque - WIND_Mobile
VPLS Overview
A
r5
r6
Module 9 |
57
Module 9 - 57
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
58
(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)
Module 9 - 58
Kazi_Zial_Hoque - WIND_Mobile
INGRESS
(R6 SAP 1/1/4)
EGRESS
(R5 SAP 1/1/4)
Module 9 |
59
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).
Module 9 - 59
Kazi_Zial_Hoque - WIND_Mobile
Can also use the plotter to view SAP Egress QoS Queue
Accounting statistics
Module 9 |
60
(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.
Module 9 - 60
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
61
Module 9 - 61
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
62
Module 9 - 62
From the service Components tab, view the properties of the SDP
binding from r6 to r5.
Module 9 |
63
Kazi_Zial_Hoque - WIND_Mobile
(Service properties -> SDP properties -> Tunnel properties -> LSPs tab -> LSP properties -> LSP-Path Bindings
tab)
Module 9 - 63
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
64
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.
Module 9 - 64
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
65
Module 9 - 65
Module 9 |
66
Kazi_Zial_Hoque - WIND_Mobile
Module 9 - 66
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
67
Module 9 - 67
Module 9 |
68
(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)
Module 9 - 68
Kazi_Zial_Hoque - WIND_Mobile
Service ID = 31
Find the cause but DO NOT fix it
A
r5
Kazi_Zial_Hoque - WIND_Mobile
r6
Module 9 |
69
Module 9 - 69
Module 9 |
70
Module 9 - 70
Best Practice:
Kazi_Zial_Hoque - WIND_Mobile
r5
Kazi_Zial_Hoque - WIND_Mobile
r6
Module 9 |
71
Module 9 - 71
Module 9 - 72
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
73
Module 9 - 73
Troubleshooting VPRNs
Kazi_Zial_Hoque - WIND_Mobile
Each VPN site must contain one or more Customer Edge (CE)
devices
Module 9 |
74
Module 9 - 74
Troubleshooting VPRNs
PE
PE
PE
Blue VPRN
Red VPRN
PE
Module 9 |
75
Module 9 - 75
MP-BGP route
exchange for
all services
Kazi_Zial_Hoque - WIND_Mobile
Troubleshooting VPRNs
YES
NO
YES
Is an RD configured?
NO
Enable VPRN
Module 9 |
76
Module 9 - 76
Kazi_Zial_Hoque - WIND_Mobile
YES
NO
Module 9 |
77
Module 9 - 77
Kazi_Zial_Hoque - WIND_Mobile
YES
NO
YES
NO
YES
NO
YES
Is a policy configured?
NO
Module 9 |
78
MP-BGP:
Multi Protocol BGP (required to support VPRNs).
To enable MP-BGP: Routing Instance -> BGP site -> VPN tab -> VPN IPv4 checked.
Module 9 - 78
Kazi_Zial_Hoque - WIND_Mobile
r3
r1
VPRN Service
Module 9 |
79
Module 9 - 79
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
80
Module 9 - 80
R1 has no
routes in
the VRF
R3 sees no
remote
routes
Module 9 |
81
It is expected that we would see local and remote routes on both routers.
(Service -> Topology -> right click on site -> Show routes)
Module 9 - 81
Show Routes on
the routers
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
82
Module 9 - 82
Module 9 |
83
Kazi_Zial_Hoque - WIND_Mobile
2. Investigation
Module 9 - 83
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
84
Module 9 - 84
Module 9 |
85
Module 9 - 85
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
86
Kazi_Zial_Hoque - WIND_Mobile
Module 9 - 86
Module 9 |
87
(Service -> Topology -> right click on site -> Show routes)
Module 9 - 87
4. Verification
Kazi_Zial_Hoque - WIND_Mobile
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
88
Module 9 - 88
Service ID = 34
Which subnet(s) on r3 cannot connect to the corporate server?
Find the cause but DO NOT fix it
10.3.3.0/24
10.2.2.0/24
Headquarters
10.4.4.0/24
r1
r3
10.5.5.0/24
Subnets
Module 9 |
89
Module 9 - 89
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
90
Module 9 - 90
Best Practice:
Kazi_Zial_Hoque - WIND_Mobile
Service ID = 33
Find the cause but DO NOT fix it
r3
r1
10.1.2.0/24
10.1.3.0/24
VPRN Service
Module 9 |
91
Module 9 - 91
Kazi_Zial_Hoque - WIND_Mobile
Mirror Services
Module 9 - 92
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
93
Module 9 - 93
Kazi_Zial_Hoque - WIND_Mobile
Mirror Services
Kazi_Zial_Hoque - WIND_Mobile
Module 9 |
94
Module 9 - 94
Mirror Services
Module 9 |
95
Module 9 - 95
Service Sites
Kazi_Zial_Hoque - WIND_Mobile
Mirror Services
Mirror
Traffic VPLS
Module 9 |
96
Kazi_Zial_Hoque - WIND_Mobile
Note that for a Mirror Service, the source SAP is not shown in the topology view, and only one SDP is used.
Module 9 - 96
Module 9 |
97
Module 9 - 97
Kazi_Zial_Hoque - WIND_Mobile
Module 9 - 98
Kazi_Zial_Hoque - WIND_Mobile
www.alcatel-lucent.com