9500 MPR management

5620 SAM
SERVICE AWARE MANAGER
14.0 R3
MPR User Guide
3HE-10693-AAAB-TQZZA
Issue 1
June 2016
5620 SAM
Legal notice
Nokia is a registered trademark of Nokia Corporation. Other products and company names mentioned herein may be trademarks or
tradenames of their respective owners.
The information presented is subject to change without notice. No responsibility is assumed for inaccuracies contained herein.
© 2016 Nokia.
2
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Contents
About this document............................................................................................................................................7
Part I: Getting started ...........................................................................................................................................9
1
Safety information........................................................................................................................................11
1.1
2
3
Structure of safety statements.............................................................................................................11
What’s new? .................................................................................................................................................13
2.1
Overview .............................................................................................................................................13
2.2
What’s new in 5620 SAM Release 14.0 for 9500 MPR .......................................................................13
9500 MPR overview......................................................................................................................................17
3.1
Overview .............................................................................................................................................17
5620 SAM management of 9500 MPR devices ..........................................................................................18
3.2
9500 MPR device support ...................................................................................................................18
3.3
9500 MPR card support ......................................................................................................................20
3.4
Supported 9500 MPR device objects and auxiliary equipment ...........................................................20
3.5
9500 MPR statistics support................................................................................................................24
3.6
9500 MPR services support ................................................................................................................28
3.7
9500 MPR NEtO support.....................................................................................................................28
3.8
Workflow to manage 9500 MPR devices ............................................................................................30
Part II: 9500 MPR management .........................................................................................................................35
4
9500 MPR device commissioning and management ................................................................................37
4.1
Overview .............................................................................................................................................37
9500 MPR commissioning and management overview............................................................................38
4.2
General description .............................................................................................................................38
4.3
9500 MPR management .....................................................................................................................38
4.4
Workflow to commission and manage 9500 MPR devices .................................................................44
9500 MPR commissioning and management procedures........................................................................45
4.5
To prepare a 9500 MPR for 5620 SAM management .........................................................................45
4.6
To configure polling for an 9500 MPR .................................................................................................47
4.7
To collect 9500 MPR statistics from a 5620 SAM auxiliary server .....................................................48
4.8
To enable 5620 SAM management of 9500 MPR devices..................................................................49
Issue 1
3HE-10693-AAAB-TQZZA
3
5620 SAM
5
9500 MPR object configuration...................................................................................................................51
5.1
Overview .............................................................................................................................................51
9500 MPR object configuration overview ..................................................................................................52
5.2
Overview .............................................................................................................................................52
5.3
Workflow to configure and manage 9500 MPR device objects ...........................................................52
9500 MPR device object configuration procedures..................................................................................54
6
5.4
To configure the system settings on a 9500 MPR ...............................................................................54
5.5
To resolve 9500 MPR MIB inconsistencies .........................................................................................54
5.6
To update the software activation status for 9500 MPRe nodes .........................................................55
5.7
To configure a scope of command role for NEtO access ....................................................................56
5.8
To cross-launch the NEtO from the 5620 SAM GUI ............................................................................57
5.9
To configure QoS for inband TMN interfaces on the 9500 MPR .........................................................58
9500 MPR LAG object configuration ..........................................................................................................61
6.1
Overview .............................................................................................................................................61
Working with 9500 MPR LAG objects ........................................................................................................62
6.2
Overview .............................................................................................................................................62
6.3
Workflow to configure and manage 9500 MPR LAG objects ..............................................................63
9500 MPR LAG configuration procedures .................................................................................................64
7
6.4
To create an Ethernet LAG on a 9500 MPR........................................................................................64
6.5
To delete a 9500 MPR Ethernet LAG ..................................................................................................66
9500 MPR shelf object configuration .........................................................................................................67
7.1
Overview .............................................................................................................................................67
9500 MPR shelf object configuration overview.........................................................................................68
7.2
Overview .............................................................................................................................................68
7.3
Workflow to manage shelf objects on 9500 MPR devices ..................................................................69
9500 MPR shelf object configuration procedures.....................................................................................71
8
7.4
To configure a 9500 MPR basic or advanced fan tray.........................................................................71
7.5
To configure synchronization on a CorEvo card or MSS-1 shelf using SYNC-IO SFPs......................72
7.6
To configure an IEEE 1588 TC on a 9500 MPR shelf .........................................................................73
7.7
To perform an on-demand 9500 MPR software upgrade ....................................................................74
7.8
To manage the 9500 MPR running software .......................................................................................75
7.9
To migrate the 9500 MPRe connected to a 7705 SAR from standalone mode to single NE mode ....77
9500 MPR port object configuration...........................................................................................................79
8.1
4
Overview .............................................................................................................................................79
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR port configuration overview......................................................................................................80
8.2
Overview .............................................................................................................................................80
8.3
Workflow to manage port objects on 9500 MPR devices ....................................................................81
Port configuration procedures ...................................................................................................................83
9
8.4
To configure 9500 MPR Ethernet ports ...............................................................................................83
8.5
To collect and view analog Radio statistics on 9500 MPR 1x Radio modem ports .............................84
8.6
To collect performance management statistics on 9500 MPR 1x Radio modem ports .......................85
8.7
To configure 9500 MPR port segregation on an EAS module.............................................................86
8.8
To configure a power source for 9500 MPR card slots........................................................................87
8.9
To configure synchronization on 9500 MPR Ethernet ports ................................................................87
8.10
To configure a loopback test on 9500 MPR ports................................................................................88
8.11
To configure 802.3ah EFM OAM remote loopbacks on 9500 MPR ports............................................89
8.12
To configure Tx mute on radio ports....................................................................................................91
9500 MPR inventory management..............................................................................................................93
9.1
Overview .............................................................................................................................................93
9.2
Radio port inventory ............................................................................................................................93
9.3
To list and sort inventory information...................................................................................................95
9.4
To save an inventory list ......................................................................................................................96
Part III: 9500 MPR policy and service management ........................................................................................97
10 9500 MPR QoS policies ...............................................................................................................................99
10.1
Overview .............................................................................................................................................99
9500 MPR QoS policies overview .............................................................................................................100
10.2
Overview ...........................................................................................................................................100
10.3
Workflow to configure 9500 MPR QoS policies.................................................................................100
9500 MPR QoS policies procedures.........................................................................................................102
10.4
To configure a 9500 Radio Interface Queue Map policy ...................................................................102
10.5
To configure a 9500 NE QoS policy ..................................................................................................103
11 9500 MPR service management and service tunnels .............................................................................105
11.1
Overview ...........................................................................................................................................105
9500 MPR service management overview ...............................................................................................106
11.2
Overview ...........................................................................................................................................106
9500 MPR service tunnel overview...........................................................................................................115
11.3
Issue 1
Overview............................................................................................................................................115
3HE-10693-AAAB-TQZZA
5
5620 SAM
Configuring service tunnels on a 9500 MPR ...........................................................................................122
11.4
Overview ...........................................................................................................................................122
11.5
To create an Ethernet Radio ring element on a 9500 MPR...............................................................122
Workflow to configure a composite service ............................................................................................127
11.6
Overview ...........................................................................................................................................127
12 9500 MPR VLAN service management.....................................................................................................129
12.1
Overview ...........................................................................................................................................129
9500 MPR VLAN service management ....................................................................................................130
12.2
Overview ...........................................................................................................................................130
12.3
Workflow to create VLAN services on 9500 MPR devices ................................................................131
9500 MPR VLAN service management procedures ................................................................................134
12.4
To create a VLAN group ....................................................................................................................134
12.5
To create a 9500 MPR VLAN path ....................................................................................................135
12.6
To create a 9500 MPR (dot1q) VLAN service ...................................................................................138
12.7
To create a 9500 MPR (dot1ad) VLAN service .................................................................................141
12.8
To apply a CoS rate limiter per VLAN on a 9500 MPR .....................................................................146
12.9
To discover 9500 MPR services ........................................................................................................147
12.10 To delete a VLAN group or group member........................................................................................148
12.11 To delete a 9500 MPR VLAN path ....................................................................................................149
13 9500 MPR VLL service management........................................................................................................151
13.1
Overview ...........................................................................................................................................151
9500 MPR VLL service management........................................................................................................152
13.2
Overview ...........................................................................................................................................152
13.3
Workflow to create VLL services on 9500 MPR devices ...................................................................152
9500 MPR VLL service management procedures ...................................................................................154
13.4
To create a VLL Cpipe service on a 9500 MPR.................................................................................154
13.5
To create a single site VLL Cpipe service on 9500 MPR connected to an MSS1c lightweight GNE.156
13.6
To discover a single-site Cpipe service on 9500 MPR connected to a 9500 MSS-1c lightweight
GNE...................................................................................................................................................158
6
13.7
To fix a failed cross-connection in a 9500 MPR Cpipe or a hop-based VLAN service ......................158
13.8
To configure a GNE site on a VLL Cpipe service ..............................................................................159
13.9
To configure a customer profile and associate it with a VLL service .................................................161
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
About this document
Purpose
The 5620 SAM MPR User Guide describes how to discover, configure, and manage
9500 MPR devices including the 9500 MPRe, 9500 MSS-1c, and 9500 MSS-O variants
using the 5620 SAM. The guide is intended for network planners, administrators, and
operators and is to be used in conjunction with other guides in the 5620 SAM
documentation suite where management of 9500 MPR devices does not differ from other
network elements. Nokia recommends that you review the entire 5620 SAM MPR User
Guide before you attempt to use the 5620 SAM to manage 9500 MPR devices.
Safety information
For your safety, this document contains safety statements. Safety statements are given
at points where risks of damage to personnel, equipment, and operation may exist.
Failure to follow the directions in a safety statement may result in serious consequences.
Document support
Customer documentation and product support URLs:
• Customer Documentation Welcome Page
• Technical support
How to comment
Documentation feedback
Issue 1
3HE-10693-AAAB-TQZZA
7
5620 SAM
8
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Part I: Getting started
Overview
Purpose
Part I describes the new and discontinued 9500 MPR features introduced in Release
14.0 of the 5620 SAM, a general overview of the 9500 MPR device and variants, and
safety related information.
Contents
Issue 1
Chapter 1, Safety information
11
Chapter 2, What’s new?
13
Chapter 3, 9500 MPR overview
17
3HE-10693-AAAB-TQZZA
9
5620 SAM
10
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Safety information
1 Safety information
1.1
1.1.1
Structure of safety statements
Overview
This topic describes the components of safety statements that appear in this document.
1.1.2
General structure
Safety statements include the following structural elements:
E
L
MP
CAUTION
Lifting hazard
SA
Lifting this equipment by yourself can result in injury
due to the size and weight of the equipment.
Always use three people or a lifting device to transport
and position this equipment.
[ABC123]
Issue 1
Item
Structure element
Purpose
1
Safety alert symbol
Indicates the potential for personal injury
(optional)
2
Safety symbol
Indicates hazard type (optional)
3
Signal word
Indicates the severity of the hazard
4
Hazard type
Describes the source of the risk of damage
or injury
5
Safety message
Consequences if protective measures fail
6
Avoidance message
Protective measures to take to avoid the
hazard
7
Identifier
The reference ID of the safety statement
(optional)
3HE-10693-AAAB-TQZZA
11
Structure of safety statements
1.1.3
5620 SAM
Signal words
The signal words identify the hazard severity levels as follows:
12
Signal word
Meaning
DANGER
Indicates an extremely hazardous situation which, if not
avoided, will result in death or serious injury.
WARNING
Indicates a hazardous situation which, if not avoided, could
result in death or serious injury.
CAUTION
Indicates a hazardous situation which, if not avoided, could
result in minor or moderate injury.
NOTICE
Indicates a hazardous situation not related to personal injury.
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
What’s new?
2 What’s new?
2.1
2.1.1
Overview
Purpose
This chapter provides information on the latest 9500 MPR features introduced to the
5620 SAM.
2.1.2
2.2
2.2.1
Contents
2.1
Overview
13
2.2
What’s new in 5620 SAM Release 14.0 for 9500 MPR
13
What’s new in 5620 SAM Release 14.0 for 9500 MPR
General information
This section highlights new and discontinued 9500 MPR features introduced in Release
14.0 of the 5620 SAM and provides pointers for more information. Feature lists and highlevel feature descriptions are also available in the 5620 SAM Release Description.
2.2.2
Maintenance releases
Some releases may not be listed in this section, either because no new 9500 MPR
features were introduced or the features introduced do not require user documentation.
2.2.3
What’s new in 5620 SAM Release 14.0 R3 for 9500 MPR
Table 1, “5620 SAM Release 14.0 R3 9500 MPR features” (p. 14) , lists the features and
functions added in 5620 SAM Release 14.0 R3 for 9500 MPR support. See the 5620
SAM User Guide for more information about non-9500 MPR features and functions.
Issue 1
3HE-10693-AAAB-TQZZA
13
What’s new in 5620 SAM Release 14.0 for 9500 MPR
5620 SAM
Table 1 5620 SAM Release 14.0 R3 9500 MPR features
Feature
Description and Reference
SAM-75857 — Inconsistent granularity
period displayed for 9500 MPR radio
PM statistical records
The granularity period column of 9500 MPR radio performance management
statistics reflects the expected behavior of displaying statistical records on the
5620 SAM GUI.
The granularity period column on the 5620 SAM GUI displays 15 (mins) and
24 (hrs) for 9500 MPR radio performance management statistics.
See “9500 MPR specific statistic usage information” (p. 25)
SAM-77207 — Separate list for radio
performance statistics collected at 15
minutes and 24 hours intervals
You can separately enable or disable the radio performance statistics collected
at intervals of 15 minutes and 24 hours by configuring the specific radio
performance statistics on the Radio tab of the Physical Port (Edit) form.
See “9500 MPR specific statistic usage information” (p. 25)
SAM-77209 — Support for elaborated
counters
The elaborated counters are supported as an extension to the following
classes:
• AggrMaintTxStats (for radio, Ethernet user ports, and L1 radio LAG)
• AggrPerQueueMaintStats (for radio ports)
• AggrMaintRxStats (for Ethernet user ports)
See “9500 MPR specific statistic usage information” (p. 25)
SAM-77221 — 5620 SAM support for
muting the transmitter indefinitely or for
a specific duration
You can mute the transmitter either indefinitely or for a specific duration by
configuring the Tx mute parameters on the radio ports.
SAM-77218 — Identify the two
variants of the CorEvo card in the
5620 SAM
You can distinguish the two variants, 1G and 10G, of the CorEvo card by
viewing the Equipped Card Sub Type parameter on the Card Slot (Edit) form
and Card Slot (Physical Equipment) inventory list.
See 8.12 “To configure Tx mute on radio ports” (p. 91)
See 7.2.4 “CorEvo card” (p. 69)
SAM-79069 — Confirmation before
adding an existing Ethernet ring
element to a radio ring
A confirmation dialog box appears before adding an existing Ethernet ring
element in a radio ring.
SAM-79071 — Configuration of TMN
VLAN parameters removed from 9500
MPR global QoS policies
You can no longer configure TMN VLAN parameters associated with 9500
MPR global QoS policies; the TMN VLAN tab has been removed from the
9500 MPR Global QoS policies form. These parameters are now configured
when you commission the 9500 MPR device for in-band management using
NEtO.
See 11.5 “To create an Ethernet Radio ring element on a 9500 MPR” (p. 122)
See 10.5 “To configure a 9500 NE QoS policy” (p. 103)
See the appropriate 9500 MPR Hardware User Guide for information about
commissioning 9500 MPR devices using NEtO.
You can view TMN parameter settings configured using NEtO using the 5620
SAM by selecting 9500 MPR devices in the navigation tree Equipment view,
right-clicking on a 9500 MPR device, and choosing Properties. Click on the
Polling tab, then on the TMN Details sub-tab. Select a 9500 MPR device and
click Properties; the TMN parameters display in read-only mode.
14
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
What’s new in 5620 SAM Release 14.0 for 9500 MPR
Table 1 5620 SAM Release 14.0 R3 9500 MPR features
(continued)
Feature
Description and Reference
SAM-79341 — New L1 LAG interface
alarms to indicate link down and
service down issues
The following new alarms are supported by the 5620 SAM to indicate if there
is a link or service down condition on L1 LAG interfaces. These alarms are
supported on 9500 MPR R6.1 devices or later.
• LAG L1 Radio Port Down
• Traffic Down
• TxProblem
• RxProblem
• Traffic Loss
See the 5620 SAM Alarm Reference User Guide
SAM-79375 — Inventory list of radio
port parameters – 9500 MPR (ANSI
and ETSI) devices
You can view the inventory list and generate a report of the 9500 MPR radio
ports and L1 radio LAGs for the parameters that are displayed in the Radio tab
of the Network→9500 MPR→Card Slot→Radio Port→Physical Port (Edit)
form.
See 9.2.4 “Radio port inventory – 9500 MPR (ANSI and ETSI) devices” (p. 94)
and 9.2.5 “Radio LAG member inventory – 9500 MPR (ANSI and
ETSI) devices” (p. 94)
SAM-79394 and SAM-79400 — IEEE
1588v2 PTP transparent clock support
You can configure the TC Enabled parameter in the Timing tab on the 1588
panel of the Network→MPR→Shelf→Shelf (Edit) form. The supported
platforms, cards, and radio types are listed in 7.6.2 “IEEE 1588v2 PTP support
per platform” (p. 73).
See 7.6 “To configure an IEEE 1588 TC on a 9500 MPR shelf” (p. 73)
SAM-79427 — LAC management
enhancements
The LAC management enhancements are:
• LAC alarms are configured only after LAC management is enabled.
• LAC management status is configured on a 9500 MPR device only after LAC
management is enabled.
• Access Request LAC state is removed from the LAC state configuration list
of parameters.
See 4.3.2 “LAC management of 9500 MPR devices” (p. 40)
SAM-79429 — Unmanaging a 9500
MPR device independent of LAC
status
The 5620 SAM allows you to unmanage a 9500 MPR device regardless of the
LAC status.
SAM-79609 — Bulk operation to
enable or disable statistics collection
for 15 minutes or 24 hours intervals.
You can perform bulk operations to enable or disable the applicable radio
interface performance management statistics collected at intervals of 15
minute or 24 hours.
See “LAC management status of a 9500 MPR device” (p. 40)
See “9500 MPR specific statistic usage information” (p. 25)
Issue 1
3HE-10693-AAAB-TQZZA
15
What’s new in 5620 SAM Release 14.0 for 9500 MPR
Table 1 5620 SAM Release 14.0 R3 9500 MPR features
5620 SAM
(continued)
Feature
Description and Reference
SAM-79711 — Inventory list of radio
port parameters – 9500 MPRe and
9500 MSS-1c devices
The inventory list includes the following radio port parameters for 9500 MPRe
and 9500 MSS-1c devices:
• Radio Interface ID
• Remote Node IPV4 Address
• Remote Node Interface
See 9.2.2 “Radio port inventory – 9500 MPRe and 9500 MSS-1c” (p. 93)
SAM-81381 — Scheduled
resynchronization disabled
Scheduled resynchronization is disabled by default for specific MIB entries in
the 9500 MPR and 9500 MPRe devices.
See 4.6 “To configure polling for an 9500 MPR” (p. 47)
SAM-82401 — Modify a customer
associated with a VLL service
You can configure a specific customer profile and associate it with a VLL
service during the service configuration. You can also modify a discovered VLL
service and add a specific customer profile.
See 13.9 “To configure a customer profile and associate it with a VLL service”
(p. 161)
16
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR overview
3 9500 MPR overview
3.1
3.1.1
Overview
Purpose
This chapter provides overview information about the 9500 MPR device including the
9500 MPRe, 9500 MSS-1c, and 9500 MSS-O variants such as the supported device
cards, auxiliary equipment, and service types.
3.1.2
Contents
3.1
Issue 1
Overview
17
5620 SAM management of 9500 MPR devices
18
3.2
9500 MPR device support
18
3.3
9500 MPR card support
20
3.4
Supported 9500 MPR device objects and auxiliary equipment
20
3.5
9500 MPR statistics support
24
3.6
9500 MPR services support
28
3.7
9500 MPR NEtO support
28
3.8
Workflow to manage 9500 MPR devices
30
3HE-10693-AAAB-TQZZA
17
9500 MPR device support
5620 SAM
5620 SAM management of 9500 MPR devices
3.2
3.2.1
9500 MPR device support
9500 MPR Radio family
The Nokia 9500 MPR is a microwave digital Radio family that supports PDH and
Ethernet to migrate from TDM to IP. The 9500 MPR provides a generic, modular IP
platform for multiple network applications such as 2G, 3G, HSDPA, and WiMAX to
accommodate broadband services to Metro Ethernet areas. This solution improves
packet aggregation, increases bandwidth and optimizes Ethernet connectivity.
The 9500 MPR Radio family supports low, medium, and high capacity applications using
ANSI and ETSI data rates, frequencies, channel plans, and tributary interfaces and has
both indoor and outdoor applications.
The 5620 SAM also supports the native management of following variants of the 9500
MPR:
• 9500 MPRe
The 9500 MPRe (also referred to as the 9500 MPR-SA) is the standalone, outdoor
application of the MPT-MC and MPT-HCv2 ODU without a shelf unit. The 9500 MPRe
provides fixed or mobile Ethernet site backhauling and supports converged MPLS
metro networks. As a native NE, the 9500 MPRe appears on 5620 SAM maps and
equipment managers. All standard SNMP-based features, including discovery and
alarms, are supported with the same naming as the rest of the 9500 MPR family.
Some features require a cross-launch of the NEtO external element manager.
See 3.7 “9500 MPR NEtO support” (p. 28) for more information. The 5620 SAM
supports the native management of the following 9500 MPRe releases: 5.0, 5.1, 5.2,
6.0, 6.1, 7.0, or later.
Note: From a 5620 SAM perspective, the 9500 MPRe/MPR-SA (stand alone), and
9500 MSS-1c variants belong to same product family; both variants display on the
5620 SAM GUI as the 9500 MPRe/MPRe. However, for 9500 MPR software upgrades,
the Label column allows you to distinguish between the 9500 MPRe/MPR-SA and
9500 MSS-1c variant types.
• 9500 MSS-1c
The 9500 Microwave Service Switch-1c (MSS-1c) is an ultra-compact indoor unit (1/2
rack size) offering 10 E1 and 4 user interfaces. The 9500 MSS-1c provides user port
interface, cross-connection, and switching management. The cross-connection matrix
implements all the cross-connections between the User ports (4 Ethernet ports and
E1/T1 streams) and the Radio port. The matrix is a standard Ethernet switch, based
on VLAN, assigned by the MCT.
The 5620 SAM supports the native management of the following 9500 MSS-1c
releases: 5.0, 5.1, 5.2, 6.0, 6.1, and 7.0. The NE backup and restore functionality for
this node type is only supported for the following versions: 5.2, 6.0, 6.1, 7.0. A new
18
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR device support
backup and restore policy has been added to support this device type. You can access
the policy from the Administration→NE Maintenance→Backup/Restore menu. Click on
the Backup/Restore Policy tab, select the MPR-SA Default Policy and click Properties.
Note this policy type requires the FTP/SFTP parameters to be configured.
The following functionality is supported for the 9500 MSS-1c using the 5620 SAM:
— automatic server registration with NE discovery
— ports listed in the Navigation equipment tree
— port alarm management
— automatic radio link discovery
— automatic node S/W download managed via a policy (same as the 9500 MPR/9500
MPRe)
— automatic node MIB backup and restore managed via a policy (same as the 9500
MPR/9500 MPRe)
— VLAN and VLL service termination on the radio port
• 9500 MSS-O
The 9500 Microwave Services Switch-Outdoor (MSS-O) is a compact, full outdoor
microwave networking device, for boosting link capacity and reliability for small cell
backhaul networks. The device provides both optical and electrical Ethernet interfaces
and can be installed indoors or outdoors.
You can configure the following on a 9500 MSS-O using the 5620 SAM:
— three 10/100/1000Base-TX Ethernet interfaces, two with PFoE, and one optical
Gigabit Ethernet SFP interface. See 8.4 “To configure 9500 MPR Ethernet ports”
(p. 83) for more information about configuring Ethernet ports.
— Ethernet L2 LAGs. See 6.4 “To create an Ethernet LAG on a 9500 MPR” (p. 64) for
more information about configuring Ethernet LAGs.
— synchronization on Ethernet ports. See 8.9 “To configure synchronization on 9500
MPR Ethernet ports” (p. 87) for more information about synchronization on
Ethernet ports.
— port segregation. See 8.7 “To configure 9500 MPR port segregation on an EAS
module” (p. 86) for more information about port segregation.
— VLAN services. See “9500 MPR VLAN service management procedures” (p. 134)
for more information about how to configure VLAN services.
Note: Only the P2M VLAN path type is supported.
— Ethernet ring. See 11.3.3 “Ethernet (G.8032) ring support” (p. 117) for more
information about configuring Ethernet rings.
The LAG size for a 9500 MSS-O is restricted to the following:
— up to two LAG ports per NE, either Ethernet L2 LAG or Radio L1 LAG
— up to two electrical Ethernet ports per Ethernet L2 LAG. Ports can have PFoE
enabled.
— ports 1, 2, and 3 on the 9500 MSS-O are available for Ethernet L2 LAG
membership
Issue 1
3HE-10693-AAAB-TQZZA
19
9500 MPR card support
3.3
3.3.1
5620 SAM
9500 MPR card support
Supported cards
You can configure the following 9500 MPR device-specific cards:
• 1 × Radio modem
• 1 × STM (Channelized)
• 2 × DS3
• 2 × STM
• 2+2 × Ethernet (EAS)
• 4+4 × Ethernet (EAS)
• 32 × DS1
• 32 × E1
• AUX alarm
• Core-B
• Core-ENH
• CorEvo
• EASv2
See Chapter 7, “9500 MPR shelf object configuration” for detailed information of the
supported cards and auxiliary equipment on 9500 MPR devices.
Note: The 5620 SAM, version 13.0 R3 and higher, allows you to discover all the EASv2
configurations supported on the 9500 MPR device.
3.4
3.4.1
Supported 9500 MPR device objects and auxiliary
equipment
General information
The 5620 SAM supports the following 9500 MPR device shelves, objects, and auxiliary
equipment:
• MSS shelves
• IDU and ODU
• basic and advanced fan trays
• LAG objects
3.4.2
Supported MSS shelf types
The following MSS shelf types can be managed by the 5620 SAM:
• MSS-1 shelf
20
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Supported 9500 MPR device objects and auxiliary equipment
The MSS-1 is a 1-rack-unit, 1-slot shelf. The first four ports of this shelf are Ethernet
ports. Ports 5 and 6 are SFP ports. The shelf also supports 16 × DS1 or 16 × E1 ports.
The MSS-1 shelf on support VLL (Cpipe only) and VLAN services on the 5620 SAM.
Note: The equipment tree in the 5620 SAM GUI displays the MSS-1 shelf as a card
slot with Ethernet ports numbered from 1/1 to 1/6 and TDM ports from 1/7 to 1/22.
Note: Radio LAGs (L1 and L2) are not supported.
• MSS-4 and MSS-8 shelves
Slots 1 and 2 are reserved for core-enhanced cards. Each shelf requires a
core-enhanced card in slot 1 and can have an optional spare card installed in slot 2 to
protect the main card.
The MSS-4 shelf supports cards in slots 3 and 4. A card in slot 3 can be protected by
an identical card in slot 4.
The MSS-8 shelf supports cards in slots 3 to 8. Protected cards must be installed in
slots 3, 5, or 7 and are protected by optional identical cards in slots 4, 6, and 8,
respectively.
3.4.3
IDUs and ODUs support
The ODU is a microprocessor-controlled transceiver that interfaces the MSS with the
microwave antenna. Each Radio modem card connects to one ODU. A 1+0 Radio
modem protection scheme requires one Radio modem card and one ODU for each
Radio direction. Two Radio modem cards and two associated ODUs must be
provisioned in each Radio direction for the 1+1 protection scheme using NEtO.
The 5620 SAM can manage the following IDU and ODU variants:
• ODU300
The ODU300 transmitter consist of a cable interface, local oscillator, up
converter/mixer, power amplifier, and a diplexer. The receiver consist of a diplexer,
low-noise amplifier, local oscillator, down converter/mixer, automatic gain control, and
cable interface. The ODU300 is frequency dependent.
• MPT-HCv2
The MPT-HCv2 ODU transports Ethernet traffic over an RF Radio channel between
the MSS and the antenna according to the configured QoS and to the scheduler
algorithms. The input interface is a standard Giga Ethernet interface (electrical or
optical). The MPT-HCv2 is XPIC-ready by the installation of a dedicated module. The
MPT-HC V2 is frequency dependent.
• MPT-MC
The MPT-MC is similar to MPT-HCv2 from an architecture standpoint. The differences
are:
— MPT-MC is medium capacity
— MPT-MC is natively Ethernet powered through a proprietary PFoE
— MPT-MC has an optical cable length limit of 100 m
• MPT-XP
Issue 1
3HE-10693-AAAB-TQZZA
21
Supported 9500 MPR device objects and auxiliary equipment
5620 SAM
The MPT-XP is a very high power version of the MPT-HCv2 and provides +7-8 dB of
additional transmit power as compared to equivalent MPT-HCv2. The MPT-XP is
frequency dependent.
• MPT-HL
The MPT-HL transceiver card is a microprocessor controlled RF transceiver that
interfaces with the Core-E card or MSS-1 shelf MPT-HL port with an antenna. The
MPT-HL transceiver microprocessor manages transmit and receive frequencies,
transmit power, alarms, and performance monitoring. The MPT-HL transceiver resides
in the MPT-HL shelf.
The following configurations are supported:
— one or two Non-Standby (1+0) radios
— Hot Standby (1+1) and Hot Standby space
— frequency diversity
• MPT-HLC
The MPT-HLC transceiver card is a microprocessor controlled RF transceiver that
interfaces with the Core-E card, EASv2 card, or MSS-1 shelf MPT-HLC port with an
antenna. The MPT-HLC transceiver microprocessor manages transmit and receive
frequencies, transmit power, alarms, and performance monitoring. The MPT-HLC
transceiver resides in the MPT-HL shelf.
The following configurations are supported:
— one or two Non-Standby (1+0) radios
— Hot Standby (1+1) and Hot Standby space
— frequency diversity
— single-shelf repeater
• MPT-HLS
The MPT-HLS is a fully indoor Radio system, for long haul and cabinet requirements,
and transports Ethernet traffic over an RF Radio channel. The MPT-HLS transceiver is
connected to an MSS-1, MSS-4, or MSS-8. The MPT-HLS can be connected to the
core-enhanced card or to an EASv2 card. The MPT-HLS is a four-rack (2200, 2000,
1700, 1300 mm) unit with two RT subracks. The subracks can be hosted with up to 10
transceivers. The TRU (always protected) is located on the top of the ETSI rack. A fan
subrack is configured for each RT subrack. Two types of fan modules are available for
configuration, Fan 4 and Fan 8. See the 9500 MPR (Hardware) User Manual for more
information about configuring the MPT-HLS Radio.
The 5620 SAM supports viewing the adaptive modulation values for the usage time
512 QAM and 1024 QAM in MPT-HLS.
• MPT-HQAM
The MPT-HQAM outdoor unit is a microprocessor controlled RF transceiver that
interfaces with the MSS-1/4/8/1c shelf; MPTACC, Core-E, P8ETH, and EASv2 card, or
MPRe (standalone) with the antenna. Fixed and adaptive modulation schemes are
supported. Channel frequency is software selectable within tuning range of the
22
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Supported 9500 MPR device objects and auxiliary equipment
MPT-HQAM transceiver. The MPT-HQAM transceiver is frequency dependent. An
MPT-HQAM connected to a Core-E, P8ETH, and EASv2 card requires a power
source. The MPT-HQAM has integrated XPIC and RPS functions.
The 5620 SAM supports two operating modes in the MPT-HQAM:
— Standard mode
The MPT-HQAM is used with its own capabilities and profiles. The air compatibility
with another MPT-HQAM in Standard mode is supported.
— MPT-HC Compatibility mode
MPT-HQAM is used with the MPT-HC capabilities and profiles. The air compatibility
with another MPT-HQAM in MPT-HC Compatibility mode or with an MPT-HC is
supported.
The operating modes are configured on the NEtO and the 5620 SAM supports viewing
the MPTHC Compatibility parameter, with the values set to True or False, on the
Radio→General tab of the Physical Port (Edit) form.
The 5620 SAM supports viewing 1+1 protection configuration for:
— two MPT-HQAMs, both configured in Standard mode
— two MPT-HQAMs, both configured in MPT-HC Compatibility mode
— two MPT-HQAMs, one configured in Standard mode and one in MPT-HCv2
Compatibility mode
— one MPT-HCv2 (with the main role as protection) and one MPT HQAM configured
in Standard or MPT-HC Compatibility mode
— one MPT-HQAM configured in MPT-HC Compatibility mode (with the main role as
protection) and one MPT-HCv2
The 5620 SAM supports the discovery of Radio L1 LAG by adding:
— MPT-HQAM in MPT-HC Compatibility mode to an L1 LAG of MPT-HCv2
— MPT-HQAM in Standard mode to an LAG L1 of MPT-HCv2
— MPT-HQAM in Standard or MPT-HC Compatibility mode to an L1 LAG of MPT-MC
— MPT-HQAM in Standard/MPT-HC Compatibility mode or MPT-MC to an L1 LAG of
MPT-HQAM in MPT-HC Compatibility or Standard mode
The 5620 SAM supports the discovery of Radio L2 LAG by adding:
— MPT-HQAM in MPT-HC Compatibility mode to an L2 LAG of MPT-HCv2
— MPT-HQAM in Standard mode to an L2 LAG of MPT-HCv2
— MPT-HQAM in Standard/MPT-HC Compatibility mode to an L2 LAG of MPT-HQAM
in MPT-HC Compatibility/Standard mode
See the 9500 MPR ETSI (Hardware) User Manual for more information about
configuring a Radio LAG.
An MPT type conversion procedure allows the you to update an MPT-HCv2 to an
MPT-HQAM on the node. For the complete procedure, see the 9500 MPR-A
(Hardware) Maintenance and Trouble Clearing Guide. The node restarts after the
conversion and the 5620 SAM displays the updated MPT-HQAM on the equipment
tree and the Port Usage parameter value in the General tab of the Physical Port (Edit)
form.
Issue 1
3HE-10693-AAAB-TQZZA
23
9500 MPR statistics support
3.4.4
5620 SAM
Fan tray support
The 9500 MPR supports two fan tray types: basic and advanced. For the advanced fan
tray, you can configure four ports for housekeeping alarms. See 7.4 “To configure a 9500
MPR basic or advanced fan tray” (p. 71) for more information about configuring a 9500
MPR fan tray.
3.4.5
LAG objects support
The 5620 SAM supports the following LAG objects on 9500 MPR (ANSI and ETSI)
devices:
• L1/L2 Radio LAGs - You must use the NEtO external element manager to complete
the initial LAG configuration prior to discovery by the 5620 SAM.
• L2 Ethernet LAGs - You can configure and discover L2 Ethernet LAGs using the 5620
SAM or NEtO.
See Chapter 6, “9500 MPR LAG object configuration” for more information about 9500
MPR LAG objects.
3.4.6
XPIC support
The Cross-Polarization Interference Cancellation (XPIC) function doubles the capacity of
a single frequency by using both horizontal and vertical electromagnetic polarizations on
a path. This increases capacity while also saving spectrum and antenna costs.
XPIC is required on two Radio interfaces in order to provide additional cross-polarization
discrimination and to avoid co-channel interference. Only the MPT-HCv2/MPT-XP
supports the XPIC function. See 8.8 “To configure a power source for 9500 MPR card
slots” (p. 87) to configure power source type over Ethernet on a 2+2 × Ethernet (EAS)
card. See the 9500 MPR (Hardware) User documentation for more information about
how to use the NEtO software to configure XPIC.
3.5
3.5.1
9500 MPR statistics support
9500 MPR statistics support
The 5620 SAM supports the collection of network performance, accounting, and flowbased statistics for 9500 MPR devices. The 5620 SAM also provides statistics for
monitoring 5620 SAM processes and functions. These statistics are typically used to
24
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR statistics support
monitor or troubleshoot a network, or to perform SLA or billing functions. Statistics
collection can be configured with policies that are distributed to specified network
objects.
See the 5620 SAM Statistics Management Guide for information about the following for
9500 MPR devices:
• configuring statistics collection
• viewing statistics data in tabular or graphical form
• creating graphical representations of statistics data using the Statistics Plotter
• the supported performance and accounting statistic counters for 9500 MPR devices
9500 MPR specific statistic usage information
The following provides notable statistic usage information that applies to 9500 MPR
devices:
• The Total Transmitted Octets after Compression and Total Transmitted Octets after
Compression Periodic statistic counters for Ethernet Aggregate Tx statistics have been
added in 5620 SAM Release 13.0 R3, applicable for 9500 MPR, Release 5.2 and later.
You can access these counters by selecting Properties on a 9500 MPR physical port,
and selecting the Statistics tab. However, these counters also appear for earlier
releases of the 9500 MPR and GNEs. Because the fields cannot be hidden, the 5620
SAM sets the counter value to 0.
• The 5620 SAM supports elaborated counters as an extension to the following classes:
— AggrMaintTxStats (for radio, Ethernet user ports, and L1 radio LAG)
— AggrPerQueueMaintStats (for radio ports)
— AggrMaintRxStats (for Ethernet user ports)
The elaborated counters are applicable only to scheduled statistics and not
on-demand statistics. The 5620 SAM does not support real-time plotting of the
elaborated counters. The elaborated counters are supported for 9500 MPR-E/A, 9500
MPRe, and MSS-1c devices from Release 5.2 and later. See the 9500 MPR
performance statistics counters chapter in the 5620 SAM Statistics Management
Guide for detailed information about the individual statistics counters.
• The granularity period column displays the statistic collection period based on a set
time interval, for example, 15 corresponds to 15 minutes and 24 corresponds to 24
hours.
• The radio interface performance management statistics are listed separately for
collection intervals of 15 minutes and 24 hours at the port level. The following table
lists the radio interface performance management statistics that are collected at the
port level or using the Bulk Operations tool.
Radio interface PM
statistic type
Usage notes
Adaptive Modulation
Current Data
Statistic is only present when AM is enabled using Adaptive Modulation Mode.
Issue 1
3HE-10693-AAAB-TQZZA
25
9500 MPR statistics support
5620 SAM
Radio interface PM
statistic type
Usage notes
Frame Hop Current Data
Always available for the Radio interface.
Frame Link Current Data
Available for the Radio interface when RPS is enabled. See Note 1 and 2.
RSL Hop Current Data
Always available for the Radio interface.
TSL Hop Current Data
Always available for the Radio interface.
RSL Link Current Data
See Note 1 and 2.
When RPS is present, Hop stats are enabled/disabled on the protecting port
along with the active port.
RSL Diversity Link Current
Data
Available for NE version 5.1 and later when the space diversity (combiner) is
enabled on the Radio interface along with RPS.
RSL Diversity Hop Current
Data
Available for NE version 5.1 and later when the space diversity (combiner) is
enabled on the Radio interface.
Note 1: When RPS is present, you can enable/disable statistics on the protecting port along with the active
port.
Note 2: When RPS is present, do not edit the Radio PM statistic parameters from the 5620 SAM GUI for the
spare protecting port.
• You can enable or disable performance management statistics at port level or using
the Bulk Operations tool.
— Port level:
You can enable or disable individual radio interface performance management
statistics that are collected at intervals of 15 minutes or 24 hours.
Required action
Resultant
On the equipment Navigation tree, right-click on a
9500 MPR port where a Radio interface is
configured, for example, an MPT-MC or MPT-HC
card, and choose Properties.
The Physical Port (Edit) form opens.
Click on the Radio tab and configure the appropriate
PM statistics parameter(s) on the Radio PM panel.
-
— Bulk Operations tool:
You can perform bulk changes to enable or disable the applicable radio interface
performance management statistics for statistics collection intervals of 15 minutes
and 24 hours . The changes are applicable to the entire list of allowable statistics
for statistics collection intervals 15 minutes and/or, 24 hours.
Refer to the following table for the general configuration procedure; also see the
“Bulk Operations” chapter in the 5620 SAM User Guide for more information.
26
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR statistics support
Required action
Resultant
Choose Tools→Bulk Operations from the 5620 SAM main menu.
The Bulk Operations form opens.
Click Create.
The Create Bulk Change (New)
wizard opens.
Configure the General parameters and click Next.
The Specify the filter step appears.
For the Object Type parameter, select Radio Equipment (radioequipment)→Radio Port (radioequipmentRadioPortSpecifics).
Configure an appropriate filter.
Note:
Do not use the following attributes:
• Radio: Radio Port (Radio Equipment)→Radio PM : Radio Port
(Radio Equipment)→Radio PM.
The configured filter lists only the enabled radio PM statistics and
not the disabled radio PM statistics.
• Radio: Radio Port (Radio Equipment)→Radio PM : Radio Port
(Radio Equipment)→Radio Bulk Radio PM Enable/Disable 15 Min
• Radio: Radio Port (Radio Equipment)→Radio PM : Radio Port
(Radio Equipment)→Radio Bulk Radio PM Enable/Disable 24 Hrs
-
Click Next.
The Specify the attributes step
appears.
Expand Attributes→Radio→Radio PM→Bulk Radio PM
Enable/Disable (24 Hrs or 15 Min).
The Radio PM parameter panel
appears.
Choose either "Enable" or "Disable" for the Bulk RadioPM
Enable/Disable (24 Hrs or 15 Min) parameter, click Next, click
Finish, then close the wizard.
The Bulk Operations form reappears.
Click Search to locate the Bulk Operation task, choose an entry,
and click Properties.
The Bulk Change (Edit) form opens.
Click on the Batch Control tab and click Generate Batches.
_
Click Execute All or Execute Selected to enable or disable PM
statistics collection intervals of 24 hours and/or 15 minutes. Close
the form.
_
• Perform the following to plot the statistics for both ends of a Radio link traversing
between two 9500 MPRs, between a 9500 MPR and a 7750 SR, or a 9500 MPR and a
7705 SAR:
— Select a supported Radio link on the Administration→Physical Topology map,
right-click on the link and choose Plotter→New Plot. The Statistics Plotter window
opens to display both link endpoints in the Monitored Object column. Select the
Issue 1
3HE-10693-AAAB-TQZZA
27
9500 MPR services support
5620 SAM
appropriate Statistics Group, Statistics Counter, or Data Format and click the
Record/Play buttons to plot the data.
— You can also plot Radio link statistics at the object level by selecting a supported
device port in the navigation tree Equipment view, and choose Properties. The
Physical Port — Port (Edit) form opens. Click Plotter→New Plot. The Statistics
Plotter window opens to display the selected endpoint in the Monitored Object
column. If the port is part of a Radio link, click on the Plot Other Endpoint(s) button
to populate/view the other link endpoint. Select the appropriate Statistics Group,
Statistics Counter, or Data Format parameters and click the Record/Play buttons to
plot the data.
See the 5620 SAM Statistics Management Guide for more information about the
statistics plotter.
3.6
3.6.1
9500 MPR services support
Supported services
The 5620 SAM supports the configuration of VLANs, VLLs, and composite services on
9500 MPR devices. See Chapter 11, “9500 MPR service management and service
tunnels” for an overview of supported services.
See Chapter 12, “9500 MPR VLAN service management” for information about
configuring VLAN services on the 9500 MPR. See Chapter 13, “9500 MPR VLL service
management” for information about configuring VLL services on the 9500 MPR. See the
“Composite service management” chapter 5620 SAM User Guide in the about
configuring composite services on 9500 MPR.
3.7
3.7.1
9500 MPR NEtO support
Element manager (NEtO) support
You can install and cross-launch the 9500 MPR external element manager, the NEtO
from the 5620 SAM GUI; see 5.8 “To cross-launch the NEtO from the 5620 SAM GUI”
(p. 57) for information.
For the 9500 MPRe, the NEtO cross-launch occurs only if the registration table entry has
not reached the limit of 15 entries.
The NEtO multi-version auto-download or cross-launch to each IPv6 node works when
the nodes are reachable (IPv6 route must exist) from the 5620 SAM Windows Client,
from which the auto-download or cross-launch is being attempted.
The cross-launch task of NEtO is listed in the 5620 SAM user activity log. To view the
task, choose Administration→Security→User Activity from the 5620 SAM main menu.
28
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR NEtO support
The log indicates whether the cross-launch was successful. The auto-download of NEtO
occurs when NEtO is launched for the first time and this is not specifically listed in the
log.
3.7.2
NEtO distribution through the 5620 SAM
The 5620 SAM manages the distribution of the NEtO application and all related profiles.
Any discovered 9500 MPR has all cross-launch paths automatically configured in
policies so that no user configuration is required to use the NEtO. The cross-launch
function also supports the option to run TACAS+ in the network, in which case NEtO has
a NULL authentication when cross-launched, and the user is prompted for a user name
and password.
The first time a user cross-launches the NEtO, the 5620 SAM Java Webstart installs the
application on the 5620 SAM client system. Any update to the NEtO installation files on
the 5620 SAM server results in an update to the NEtO installation on the client system.
The 5620 SAM supports the selection of user profiles to access the NEtO. The Admin
NEtO launch, Viewer NEtO launch, and Default NEtO launch are listed in the scope of
command roles that allows you to access the NEtO for a specific user profile. See the
Appendix in the 5620 SAM System Administrator Guide for the list of scope of command
roles. See 5.7 “To configure a scope of command role for NEtO access” (p. 56) for
information about configuring a scope of command role to access the NEtO for the
required user profile.
During an upgrade, the 5620 SAM leaves property files in place for existing NEs,
retaining any user edits made to support the NEs. An operator can change the property
files to change the login behavior, as described in 4.8 “To enable 5620 SAM
management of 9500 MPR devices” (p. 49). The Install Directory property is a property
required only by 5620 SAM releases earlier than 10.0 R5; the current 5620 SAM release
manages the NEtO installation. See the applicable 9500 MPR Release Notice for the
supported versions of NEtO.
3.7.3
Service management with NEtO
You can use the NEtO to manage services on the 9500 MPR. The use of an external
element manager to change key network management information usually managed by
the 5620 SAM (such as service IDs, SAP or site information, or VLAN information) could
result in data loss or corruption. To avoid this problem, site information is persisted so
that management actions (such as moving service access from one DS1 port to another)
do not result in data loss.
On the 5620 SAM, Release 13.0 R3 or later, configuration of the following can only be
performed using NEtO:
• cards
• port usage
Issue 1
3HE-10693-AAAB-TQZZA
29
Workflow to manage 9500 MPR devices
5620 SAM
• Radio LAGs
• port and card protection
The 5620 SAM takes the following additional actions to accommodate service changes
made using the NEtO:
• A move between ports by the NEtO generates an alarm. The new port attachment is
discovered and the deleted port is retained. The user can copy provisioning
information to the new port in the 5620 SAM or manually reverse the change, if
required.
• A move between Radio backhaul paths by the NEtO generates an alarm and is
accepted. The alarm message retains the old and new path information, allowing the
user to change the service back to its original form, if required.
• A move between Radio and Ethernet backhaul paths by the NEtO generates an alarm
and is accepted. The alarm message retains the old and new path information,
allowing the user to change the service back to its original form, if required.
• When using NEtO to change VLAN IDs for a service, the new service is discovered
and alarms are generated for both services. An informational alarm is generated for
the new service, and a major alarm is generated for the old service.
• A clean up on the service deletes all new discovery alarms and old SAPs, and accepts
the new SAPs.
• Service changes from the NEtO are not supported for ERPS (Radio or fiber).
3.8
3.8.1
Workflow to manage 9500 MPR devices
9500 MPR workflow sequence
The following workflow describes the high-level tasks required to commission and
discover 9500 MPR devices, configure and manage the device objects, and configure
and manage the policies and services associated with the device.
3.8.2
Process
1
Review the workflow to prepare the 5620 SAM to perform network management of
devices in the 5620 SAM User Guide before starting this workflow. The steps in this
workflow are common to all 5620 SAM-managed devices.
2
Commission 9500 MPR devices for 5620 SAM management; see Chapter 4, “9500
MPR device commissioning and management”.
30
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Workflow to manage 9500 MPR devices
3
Use the 5620 SAM to discover 9500 MPR devices; see the “Discovering devices
using the 5620 SAM” chapter in the 5620 SAM User Guide.
4
View, manage, and configure 9500 MPR device network objects as required; see the
“Working with network objects using the 5620 SAM” chapter in the 5620 SAM User
Guide.
5
View, manage, and configure 9500 MPR device objects; see Chapter 5, “9500 MPR
object configuration”.
6
View, manage, and configure 9500 MPR device LAG objects; see Chapter 6, “9500
MPR LAG object configuration”.
7
Modify 9500 MPR device shelf objects; see Chapter 7, “9500 MPR shelf object
configuration”. You can configure cards only using NEtO. See the 9500 MPR
(Hardware) User Guide for more information.
8
Modify ports on 9500 MPR devices, as required; see Chapter 8, “9500 MPR port
object configuration”. You can configure ports only using NEtO. See the 9500 MPR
(Hardware) User Guide for more information.
9
As required, perform bulk configuration changes on 9500 MPR devices to change
the same configuration on multiple objects at the same time; see the “Bulk
Operations” chapter in the 5620 SAM User Guide for general guidelines. For
example, configure a bulk change by choosing 9500 MPR→System Settings (mpr.MprNeProperties) in the Object Type drop-down menu to specify the bridge
type for all 9500 MPR devices. See the 5620 SAM-O XML Reference for information
about all bulk change XML classes associated with the 9500 MPR objects.
10
Create 5620 SAM policies that define the conditions for 5620 SAM management
functions on 9500 MPR devices.
a. Before creating policies for 9500 MPR devices, review the “Policies overview”
chapter in the 5620 SAM User Guide for information about 5620 SAM policy
management and the workflow on how to create and distribute policies.
Issue 1
3HE-10693-AAAB-TQZZA
31
Workflow to manage 9500 MPR devices
5620 SAM
b. Create QoS device-specific policies as required for 9500 MPR devices; see
Chapter 10, “9500 MPR QoS policies”.
11
Before configuring VLAN, VLL, or composite services and related functions on 9500
MPR devices; perform the following as required:
a. Review the “Service management and QoS” chapter in the 5620 SAM User Guide
for information about configuring services on 9500 MPR devices using the 5620
SAM.
b. Review the “Customer configuration and service management” chapter in the
5620 SAM User Guide for information about, and workflow on, how to create and
manage customers and the services they subscribe to. As required, create
customer profiles.
c. Review the 9500 MPR service management and service tunnels chapter for
specific information on supported service types; see Chapter 11, “9500 MPR
service management and service tunnels”.
d. Configure service tunnels to carry service traffic on 9500 MPR devices; see
Chapter 11, “9500 MPR service management and service tunnels”.
12
Configure VLAN groups, paths, and services for subscribers connected to 9500
MPR devices; see Chapter 12, “9500 MPR VLAN service management”.
13
Configure VLL Cpipe services for subscribers connected to 9500 MPR devices; see
Chapter 13, “9500 MPR VLL service management”.
14
Configure composite services to connect the types of services for subscribers
connected to 9500 MPR devices; see the “Composite service management” chapter
in the 5620 SAM User Guide.
15
Monitor and acknowledge incoming 9500 MPR-specific alarms to check the type and
characteristics of the alarms, and to resolve the network problems or physical
equipment failures identified by the alarms; see the “Alarm management overview”
chapter in the 5620 SAM User Guide for more information.
In addition:
• Click on the Abnormal Conditions tab of the Network Element (Edit) form to check
for the abnormal conditions on the 9500 MPR such as loopback or TxMute
conditions to determine the appropriate corrective action. In previous releases of
32
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Workflow to manage 9500 MPR devices
the 5620 SAM, each abnormal condition on the 9500 MPR were reported as an
individual alarm on the Faults tab. Abnormal conditions are now reported as a
single alarm.
• Refresh the Abnormal Conditions tab to ensure the latest content is displayed.
• Clear the abnormal condition alarm after all the individual abnormal conditions are
cleared.
16
Perform specific 9500 MPR device maintenance functions as required:
• on-demand or scheduled NE configuration backup and restore device
configurations
• perform a 9500 MPR device on-demand software upgrade
• monitor deployment of configuration changes to 9500 MPR devices
• configure the OLC state on a 9500 MPR device object to specify whether the
object is in maintenance or in-service mode to filter alarms in the alarm window
• perform daily, weekly, monthly, and supplemental routine maintenance to maintain
hardware and system integrity and efficiencies of 9500 MPR devices
See the 5620 SAM System Administrator Guide for more information.
17
Collect 5620 SAM and NE statistics to monitor the 5620 SAM and 9500 MPR
devices, network and service performance, compile equipment usage and billing
data, and ensure SLA compliance; see the 5620 SAM Statistics Management Guide.
Issue 1
3HE-10693-AAAB-TQZZA
33
Workflow to manage 9500 MPR devices
34
5620 SAM
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Part II: 9500 MPR management
Overview
Purpose
Part II provides information about the pre-configuration and device commissioning
requirements that are necessary before the 5620 SAM can manage 9500 MPR devices.
It also provides information about how to configure 9500 MPR device objects including
LAG objects, shelf objects, and port objects.
Contents
Issue 1
Chapter 4, 9500 MPR device commissioning and management
37
Chapter 5, 9500 MPR object configuration
51
Chapter 6, 9500 MPR LAG object configuration
61
Chapter 7, 9500 MPR shelf object configuration
67
Chapter 8, 9500 MPR port object configuration
79
Chapter 9, 9500 MPR inventory management
93
3HE-10693-AAAB-TQZZA
35
5620 SAM
36
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR device commissioning and management
4 9500 MPR device commissioning and
management
4.1
4.1.1
Overview
Purpose
This chapter provides information about the pre-configuration and device commissioning
requirements before the 5620 SAM can manage 9500 MPR devices.
4.1.2
Contents
4.1
Issue 1
Overview
37
9500 MPR commissioning and management overview
38
4.2
General description
38
4.3
9500 MPR management
38
4.4
Workflow to commission and manage 9500 MPR devices
44
9500 MPR commissioning and management procedures
45
4.5
To prepare a 9500 MPR for 5620 SAM management
45
4.6
To configure polling for an 9500 MPR
47
4.7
To collect 9500 MPR statistics from a 5620 SAM auxiliary server
48
4.8
To enable 5620 SAM management of 9500 MPR devices
49
3HE-10693-AAAB-TQZZA
37
General description
5620 SAM
9500 MPR commissioning and management overview
4.2
4.2.1
General description
General description
The 9500 MPR requires commissioning and device-specific pre-configuration before the
5620 SAM can discover and manage the device. See the 4.4 “Workflow to commission
and manage 9500 MPR devices” (p. 44) for the sequence of high-level tasks required to
commission a 9500 MPR before discovery by the 5620 SAM.
The 9500 MPR requires two mediation policies be created manually as part of the
discovery rule creation process: one for Read-Write mediation and a Trap mediation
policy.
Note: While creating the read/write mediation policy, you must select FTP for the File
Transfer Type, and specify the FTP User Name 'ftp' and FTP User Password 'ftp'. While
creating the trap mediation policy, you must specify 'SNMP-trap' as the SNMP v1/v2c
Community String.
Note: To determine which version of the 9500 MPR NEs and variants are supported by
the 5620 SAM, see the 5620 SAM Network Element Compatibility Guide for information.
4.3
4.3.1
9500 MPR management
Supported management traffic types
A 9500 MPR device requires pre-configuration before 5620 SAM management of the
device is possible. The 5620 SAM supports in-band and out-of-band management of
devices.
When you configure in-band management only, management traffic between the 5620
SAM and a 9500 MPR is transmitted through any port that is configured for network
access, but not the management port. Using in-band management, the 5620 SAM sends
management traffic to the system IP address of the device, or to an optional L3
management interface.
When you configure out-of-band management only, management traffic between the
5620 SAM and a 9500 MPR is transmitted through the management port of the device.
Using out-of-band management, the 5620 SAM sends management traffic to the
management IP address of the device. See the 5620 SAM User Guide for more
information about device bandwidth management.
Note: A 9500 MPR device can only be managed by up to five instances of the 5620
SAM.
38
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR management
In-band management of 9500 MPR devices
To enable 9500 MPR in-band management, the 5620 SAM requires connectivity to the
9500 MPR NE, as shown in Figure 1, “Example of 9500 MPR in-band management”
(p. 38) and described in the associated example configuration steps. Ensure that the trap
receiving interface on the 5620 SAM server is configured with the IP address of the inband NIC that connects to the 9500 MPR network.
Figure 1
Example of 9500 MPR in-band management
9500 MPR network
5620 SAM
server 2.2.2.1
Switch or
Router
9500 MPR A
Management (TMN) port:
2.2.2.2
Local IP: 10.10.3.5
9500 MPR B
Local IP: 10.10.3.9
20511
Perform the following initial configuration on the 9500 MPR:
1. Connect the first 9500 MPR Node 1 to the switch using the TMN port or port 4 of the
9500 MPR A.
When the 5620 SAM is connected to the 9500 MPR network via non-9500 MPR
devices like the 7705 SAR or 7750 SR, expect that the TMN in-band feature is
enabled on Node 1 of the 9500 MPR that is connected to non-9500 MPR devices. For
example, SAM-----7705SAR_1/1/1-----port1/4_MPR1 -------(Radio)------MPR2.......
In the preceding example, the 9500 MPR Node 1 and port 1/4 are enabled with VLAN
ID and IP addresses and the 7705 SAR is configured with the same VLAN and IP
address from the same subnet.
2. Ensure that the Radio links between the 9500 MPRs are working by pinging the local
IP addresses. A connection between two 9500 MPR NEs could be over an Ethernet
or optical link. If the core Ethernet or core optical port is used between two 9500
MPRs, the ports should be enabled with TMN in-band on the 9500 MPR.
Note: The management port IP, TMN in-band IP, and local IP can be in different subnets.
Perform the following network configuration:
1. Verify that you can ping the local IP address of all the NEs from the 5620 SAM server.
2. Verify that you can ping the 5620 SAM server IP address from each of the 9500 MPR
NEs.
Note: You can manage the 9500 MPR through the local IP address even though the
management interface via the 5620 SAM server is not reachable.
Issue 1
3HE-10693-AAAB-TQZZA
39
9500 MPR management
5620 SAM
3. The 5620 SAM should be able to discover and manage the local IP addresses of the
9500 MPRs after connectivity is established between the 5620 SAM and the 9500
MPR NEs.
4.3.2
LAC management of 9500 MPR devices
Introduction
The 5620 SAM provides a Local Access Control (LAC) management synchronization
mechanism to allow or deny (inhibit) user-access to configure 9500 MPR devices using a
Local Craft Terminal (LCT). This prevents multi-write access sessions on 9500 MPR
devices. You can also enable or disable if the 5620 SAM receives LAC alarms from the
nodes.
Enable LAC management
You can enable LAC management by configuring the Enable LAC Management
parameter on the MPR tab of the Administration→System Preference→System
Preference form. Enabling LAC management automatically denies LCT access to nodes
that are newly managed only. There is no impact to existing managed 9500 MPR nodes.
After the Enable LAC Management parameter is configured, you can enable or disable
LAC alarms by configuring the Enable LAC Alarms parameter on the MPR tab of the
Administration→System Preference→System Preference form. The 5620 SAM
generates a “LAC requested” alarm indicating LCT use is requesting access to the node.
If disabled, no new alarms will be generated going forward. The Enable LAC Alarms
parameter cannot be configured if the Enable LAC Management parameter is disabled.
Note: The Enable LAC management parameter is disabled by default. Therefore, the
LAC state of any node which is newly managed by the 5620 SAM going forward will not
be altered. This is done to allow LCT access for those users who normally provision the
9500 MPR using NEtO or the 1350 OMS.
LAC management status of a 9500 MPR device
You can configure the LAC management status of a 9500 MPR device at the node level
by selecting the node in the navigation tree Equipment view, and choose Properties. The
Network Element form opens. Click on the System Setting tab and verify the LAC state
parameter in the LAC configuration panel. You can re-configure the LAC state parameter
if required; any changes made at the NE level and will only affect that NE.
Note:
• The LAC configuration parameters are available for configuration only if the LAC
management is enabled. See “Enable LAC management ” (p. 40) for more information
about enabling LAC management.
40
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR management
• The 5620 SAM allows you to unmanage a 9500 MPR device irrespective of the LAC
status.
If the LAC management state of the node is set to Access Denied, LCT-users can
request access to the node from a LCT session to the 5620 SAM. When this request is
made, a LocalAccessRequest alarm is generated after the specified wait-time and
appears in the Alarm window.
You can:
• grant access to the LCT by changing the LAC state to Access Granted.
• deny access to the LCT by changing the LAC state to Access Denied.
4.3.3
Supported Radio links
Radio links between 9500 MPR devices are automatically discovered by the 5620 SAM.
The auto-discovery is supported for the following Radio links:
• 1+0
• 1+1
• L2 LAG
• L1 LAG
After the auto-discovery, the 5620 SAM displays the following parameters on the Radio
tab of the Physical Port (Edit) form:
• Remote IPv6/IPv4 Address
• Remote Interface
• Remote Port
The Radio interface can be:
• ODU300
• MPT-xC
• MPT-HLv1
• MPT-HLv2
Radio links between 9500 MPR devices are shown as physical links by the 5620 SAM,
with ports as the endpoint type.
To enable 9500 MPR Radio link discovery and management, the 5620 SAM requires
connectivity between the 9500 MPR NE Radio ports, as shown in the following figure.
Table 4–1 provides connectivity parameter details for each supported shelf type.
Issue 1
3HE-10693-AAAB-TQZZA
41
9500 MPR management
5620 SAM
Figure 2
Connectivity example for 9500 MPR Radio link discovery and management
9500 MPR
1-MSS-4
Switch
5620 SAM
9500 MPR
3-MSS-8
2x(1+0) RADIO CONFIGURATION
with:
LINKGRP=2
LINKMEMBER=3, 6
9500 MPR
4-MSS-4
3x(1+0) RADIO CONFIGURATION
with:
LINKGRP=1
LINKMEMBER=1, 3, 5
9500 MPR
2-MSS-4
22432
Table 2 Connectivity parameter details
Shelf type
1-MSS-4
2-MSS-4
3-MSS-8
4-MSS-4
2-MSS-4
PPPRF Enabled
—
PPPRF Enabled
—
LinkID (as assigned)
3-MSS-8
LinkID (as assigned)
PPPRF Enabled
PPPRF Enabled
LinkID (23, 23)
LinkID (as assigned)
—
PPPRF Enabled
LinkID (11, 11)
PPPRF Disabled
PPPRF Disabled
LinkID (26, 26)
LinkID (13, 13)
PPPRF Disabled
LinkID (15, 15)
To discover multiple Radio links, you must provision the Radio ports on the 9500 MPR
based on the following criteria:
1. Only one Radio port can have PPPRF enabled. The far endpoint on the same link
must have the same configuration as the first endpoint. PPPRF should be disabled on
both endpoints for the second and any subsequent Radio links.
2. LinkID requirements include:
• The LinkID must be enabled for all of the port members of the configuration that
have the same LINKGRP, and a different LINKMEMBER that matches the far
endpoint.
• Expected and Sent values must be equal (for example, 11, 11 or 13, 13).
• For a multiple N × (1+x) Radio configurations on the same NE, the LINKGRP must
be unique without overlapping (for example, 1 and 2).
42
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR management
• LinkID should be formatted as LINKGRP:LINKMEMBER in a hexadecimal format
where LINKGRP is the first character and LINKMEMBER are the members.
• Any mismatch between the LinkID at the link level (for example, Send is not equal
to Expected) mutes the Radio connection (MPT case).
3. As a requirement for the first Radio link to be discovered, the remote address must be
present at both endpoints. For subsequent links, alarms cannot be present on the
Radio port.
4. When Radio link aggregation is enabled for any of the Radio links between two 9500
MPRs, all Radio links must belong to the same LAG.
5. When 1+1 configuration is deleted resulting in two 1+0 Radio links, the 5620 SAM
can display incorrect information for the remote interfaces. The Remote interface for
previously Spare port can be set to Main port or 0. The incorrect information occurs
because the 9500 MPR node sends incorrect values in the transient phase.
6. When the LAG member links are deleted, the 5620 SAM does not update the display
of the link. For example, the LAG configuration with links to two members can display
as one link or no link even after the two links are deleted. The incorrect information
occurs because the 9500 MPR node sets the remote interface to 0 momentarily.
Note: By default, the PPPRF parameter is enabled and greyed out on the 5620 SAM
GUI. Use NEtO to disable or enable PPPRF parameter, if required.
When you configure out-of-band management, the PPPRF and LinkID parameters need
not be enabled for the 9500 MPR, Release 5.2, 6.0, and later. If the PPPRF and LinkID
parameters are disabled on all the Radio ports, the Radio links are still discovered
successfully and the criteria 1 and 2 are not applicable.
When you configure in-band management, the 1+0, 1+1 Radio links between two 9500
MPR nodes require the PPPRF parameter to be enabled on the Radio ports for the 5620
SAM to discover the far end 9500 MPR node. The 2+0, 3+0, 4+0 Radio links between
two 9500 MPR nodes require the PPRF parameter to be enabled on one of the Radio
links at both ends. The PPPRF and LinkID parameters need not be enabled for other
Radio links.
4.3.4
9500 MPR Radio link protection schemes
You can apply 9500 MPR Radio link protection by configuring the Protection Type
parameter in NEtO. Additionally, you can switch between an in-service protected Radio
link and a standby protected link to perform routine maintenance tasks using NEtO. See
the 9500 MPR (Hardware) User Manual for more information.
In-service protected Radio links are represented as green links on the Physical topology
map; standby links are shown as blue links; out-of-service Radio links, main or spare,
are represented as red links. If a mismatch of active and standby states should occur,
main links are represented as green links on the Physical topology map; spare links are
shown as blue links.
Issue 1
3HE-10693-AAAB-TQZZA
43
Workflow to commission and manage 9500 MPR devices
5620 SAM
Note: The status of a protected link does not have a direct impact on the status of a
service. See Table 4, “9500 MPR service status” (p. 110) for more information about the
service status.
4.4
4.4.1
Workflow to commission and manage 9500 MPR devices
General information
The following workflow describes the high-level tasks required to commission 9500 MPR
devices prior to discovery by the 5620 SAM.
4.4.2
Process
1
Prepare the 9500 MPR for 5620 SAM management by commissioning the device
before discovery by the 5620 SAM. See the workflow to commission Nokia devices
in the “Device commissioning and management” chapter in the 5620 SAM User
Guide for the procedures that apply to this device type. In addition, perform the
following device-specific procedures as required.
2
Configure an SNMP user, the required security mediation policy, and discovery rule
for a 9500 MPR; see 4.5 “To prepare a 9500 MPR for 5620 SAM management”
(p. 45).
3
Configure how and when the 5620 SAM polls the device for MIB changes; see
4.6 “To configure polling for an 9500 MPR” (p. 47).
4
Enable the collection of 9500 MPR statistics from a 5620 SAM auxiliary server; see
4.7 “To collect 9500 MPR statistics from a 5620 SAM auxiliary server ” (p. 48).
5
Enable the 5620 SAM to manage a 9500 MPR and to enable the opening of a NEtO
session using the 5620 SAM GUI; see 4.8 “To enable 5620 SAM management of
9500 MPR devices” (p. 49).
44
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To prepare a 9500 MPR for 5620 SAM management
9500 MPR commissioning and management procedures
4.5
4.5.1
To prepare a 9500 MPR for 5620 SAM management
General information
The following procedures describe how to prepare 9500 MPR devices (and variants) for
commissioning before the 5620 SAM can manage it.
Perform this procedure to configure a SNMP user, the required security mediation policy,
and discovery rule for a 9500 MPR.
Note: Ensure that you create the mediation policy based on whether the 9500 MPR
device supports SNMPv2 or SNMPv3, along with the appropriate Trap mediation policy
with community string.
4.5.2
Steps
1
Create an SNMPv3 user on the 5620 SAM.
1. Choose Administration→Security→NE User Configuration from the 5620 SAM
main menu. The NE User Configuration form opens.
2. Click Create. The NE User, Global Policy (Create) form opens.
3. Configure the parameters as required. For the Access parameter, you must
choose the SNMP option.
4. Click on the SNMPv3 tab and verify that the SNMPv3 user and user group have
been created on the managed NE.
When a user has been assigned the appropriate SNMPv3 permissions, you can
configure the following authentication parameters:
• Authentication Protocol—Choose MD5 as the authentication protocol.
• Privacy Protocol—Choose No Privacy as the privacy protocol.
• New Authentication Password
• Confirm New Auth Password
5. Click OK and click Search to confirm the creation of the SNMPv3 user.
2
Configure an SNMPv3 mediation security policy for the SNMPv3 user created in
Step 1.
1. Choose Administration→Mediation from the 5620 SAM main menu. The
Mediation (Edit) form opens.
Issue 1
3HE-10693-AAAB-TQZZA
45
To prepare a 9500 MPR for 5620 SAM management
5620 SAM
2. Click on the Mediation Security tab and click Create. The Mediation Policy
(Create) form opens.
3. Configure the Displayed Name parameter to identify the policy and set the
Security Model parameter to SNMP v3 (USM).
4. In the SNMP panel, set the Port parameter to 161.
5. In the SNMPv3 panel, click Select and choose the SNMPv3 user created in Step
1 and click OK. The Mediation Policy (Create) form reappears.
6. Save your change and close the form.
3
Perform one of the following to configure SNMP management and to create a
discovery rule for 9500 MPR devices.
Note: The 5620 SAM uses the default SNMPv2 mediation security policy to
discover the 9500 MPR.
a. To configure a discovery rule that uses SNMPv3 management; see the “Device
discovery” chapter in the 5620 SAM User Guide.
b. To configure a discovery rule that uses SNMPv2 management:
Perform the following steps:
1. Choose Administration→Discovery Manager from the 5620 SAM main menu.
The Discovery Manager (Edit) form opens.
2. Click Create. The Create Discovery Rule step form opens with the Specify
General Attributes step displayed.
3. Configure the parameter as required and click Next. The Add Rule Elements
step appears.
4. Click Create, configure the required parameters and click OK. The Create
Discovery Rule step form reappears.
5. Click the Next. The Add Auto Discovery Rule Elements ACL step appears.
6. Optionally click Create, configure the parameter as required and click Next.
The Configure Mediation Security step appears.
7. Click Select and choose the mediation security policy created in Step 2 in the
Read Access, Write Access, Trap Access, and Security Access Mediation
policy panels.
8. Click Finish and close the form. All other steps on the Create Discovery Rule
step form are optional for the 9500 MPR.
46
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To configure polling for an 9500 MPR
4
Use the 5620 SAM client to discover the NE and to verify that the NE configuration
allows management of the 9500 MPR; see the “Device discovery” chapter in the
5620 SAM User Guide.
END OF STEPS
4.6
4.6.1
To configure polling for an 9500 MPR
Steps
1
In the navigation tree Equipment or Routing view, right-click on a 9500 MPR and
choose Properties. The 9500 MPR network element form opens.
2
If required, record the system IP address and management IP address for future
configuration requirements.
3
If required, configure the Location and Current OLC State parameters.
4
Click on the Polling tab and configure the Scheduled Polling parameter.
5
To determine the current polling status:
The read-only parameters provide the following information.
• Resync Status indicates whether the last poll successfully completed.
• Last Resync Start Time and Last Resync End Time indicate the start and finish of
the last poll.
• Scheduled Resync Status indicates whether the last scheduled poll successfully
completed.
Note: Scheduled resynchronization is disabled, by default, for specific MIB entries.
Click on the MIB entry policy in the MIB Entry Policies tab of the
Administration→Mediation→Mediation (Edit) form, click properties, and then
configure the Polling Interval parameter to enable scheduled resynchronization.
Enabling scheduled resynchronization of the MIB entries for which the scheduled
resynchronization is set to disabled by default may have performance impact.
• Last Scheduled Resync Start Time and Last Scheduled Resync End Time indicate
the start and finish of the last scheduled poll.
Issue 1
3HE-10693-AAAB-TQZZA
47
To collect 9500 MPR statistics from a 5620 SAM auxiliary server
5620 SAM
6
Save your changes and close the form.
END OF STEPS
4.7
4.7.1
To collect 9500 MPR statistics from a 5620 SAM auxiliary
server
Purpose
Perform this procedure if you plan to use a 5620 SAM auxiliary server to collect 9500
MPR statistics using IPv4 or IPv6.
4.7.2
Steps
1
Choose Administration→System Information from the 5620 SAM main menu. The
System Information form opens.
2
Click on the Auxiliary Servers tab, choose an auxiliary server from the list and click
Properties. The Auxiliary Server (View) form opens.
3
Click on the Auxiliary Services tab and select the STATS_SERVICE entry from the
list and click Properties. The Auxiliary Service - STATS_SERVICE (Edit) form opens.
4
If you are using IPv6, configure the IPv6 Address parameter and click OK.
Note: During the subsequent device discovery, the 5620 SAM registers the
IPv6 address of the auxiliary server on each discovered 9500 MPR.
5
Save your changes and close the form.
END OF STEPS
48
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To enable 5620 SAM management of 9500 MPR devices
4.8
4.8.1
To enable 5620 SAM management of 9500 MPR devices
Purpose
Perform this procedure to enable the 5620 SAM to manage a 9500 MPR and to enable
the opening of NEtO sessions using the 5620 SAM GUI.
Note: The NEtO application is installed and configured to open automatically for newly
discovered 9500 MPR NEs. Use this procedure only to modify properties files of 9500
MPR NE versions that are not supported in NEtO distribution in Release 10.0 R5.
4.8.2
Steps
1
Log in to a 5620 SAM client station.
2
Discover a 9500 MPR and verify that the 5620 SAM can manage the device.
Note: If this is the first time you are enabling 5620 SAM management of a
9500 MPR in your network, you must manually create a Read-Write mediation
policy and a Trap mediation policy as part of the discovery rule creation
process. Special parameter settings apply if you are enabling FTP access. See
the “Device discovery” chapter in the 5620 SAM User Guide.
3
On a Windows client, navigate to the following directory:
path\nms\thirdparty\config
where path is the 5620 SAM client installation location, typically C:\5620sam\client
4
Find the required 9500 MPR properties file, which is named Alcatel-MPR-9500_
Release properties.
where Release is the appropriate 9500 MPR release identifier, for example, 3.4.0
5
Open the file using a plain-text editor.
6
Replace ${path} in the following line with the NEtO directory path; for example,
D:\\NEtO
install_dir =${path}
Issue 1
3HE-10693-AAAB-TQZZA
49
To enable 5620 SAM management of 9500 MPR devices
5620 SAM
7
For the 9500 MPR only: change the profile name, as required. The format is, profile_
name = <role> <community string> <user id> <password>. For example:
profile_name = admin private initial adminadmin
Note: If you do not edit the profile name, the community string is derived from
the mediation policy of the discovery rule.
8
Save and close the file. See 5.8 “To cross-launch the NEtO from the 5620 SAM GUI”
(p. 57) for information about how to launch the NEtO from the 5620 SAM GUI.
END OF STEPS
50
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR object configuration
5 9500 MPR object configuration
5.1
5.1.1
Overview
Purpose
This chapter contains information about how to configure 9500 MPR objects using the
5620 SAM navigation tree.
5.1.2
Contents
5.1
Issue 1
Overview
51
9500 MPR object configuration overview
52
5.2
Overview
52
5.3
Workflow to configure and manage 9500 MPR device objects
52
9500 MPR device object configuration procedures
54
5.4
To configure the system settings on a 9500 MPR
54
5.5
To resolve 9500 MPR MIB inconsistencies
54
5.6
To update the software activation status for 9500 MPRe nodes
55
5.7
To configure a scope of command role for NEtO access
56
5.8
To cross-launch the NEtO from the 5620 SAM GUI
57
5.9
To configure QoS for inband TMN interfaces on the 9500 MPR
58
3HE-10693-AAAB-TQZZA
51
Overview
5620 SAM
9500 MPR object configuration overview
5.2
5.2.1
Overview
General information
The device object is the discovered device at the top of the hierarchy in the navigation
tree, directly below the network icon.
This chapter contains the procedures to configure 9500 MPR device objects using the
navigation tree. Device object properties forms, which are used to configure specific
parameters for discovered devices, are accessed using objects on the 5620 SAM
navigation tree. See the “5620 SAM navigation tree” chapter in the 5620 SAM User
Guide for more information.
5.3
5.3.1
Workflow to configure and manage 9500 MPR device
objects
Workflow sequence
The following workflow describes the sequence of high-level tasks required to configure
and manage 9500 MPR device objects; see the “Device object configuration” chapter in
the 5620 SAM User Guide for the generic procedures that apply to this device type. Also,
configure the following device-specific tasks and functions.
5.3.2
Process
1
Configure the system settings for a 9500 MPR device; see 5.4 “To configure the
system settings on a 9500 MPR” (p. 54).
2
Remove any inconsistencies created due to MIB population failures that can occur
during service creation on a 9500 MPR NE; see 5.5 “To resolve 9500 MPR MIB
inconsistencies” (p. 54).
3
Update the software activation status for 9500 MPRe nodes; see 5.6 “To update the
software activation status for 9500 MPRe nodes” (p. 55).
4
Configure a scope of command role for NEtO access; see 5.7 “To configure a scope
of command role for NEtO access” (p. 56).
52
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Workflow to configure and manage 9500 MPR device objects
5
Start the 9500 MPR external element manager from the 5620 SAM GUI; see 5.8 “To
cross-launch the NEtO from the 5620 SAM GUI” (p. 57).
6
As required, configure or modify the DSCP value for TMN in-band interfaces on the
9500 MPR; see 5.9 “To configure QoS for inband TMN interfaces on the 9500 MPR”
(p. 58).
7
As required, review the specific network management features or functions that can
be performed on 9500 MPR devices using either the 5620 SAM GUI or using a craft
tool such as NEtO.
Issue 1
3HE-10693-AAAB-TQZZA
53
To configure the system settings on a 9500 MPR
5620 SAM
9500 MPR device object configuration procedures
5.4
5.4.1
To configure the system settings on a 9500 MPR
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR and choose
Properties. The 9500 MPR network element form opens.
2
Click on the System Settings tab, configure the parameters as required and click
OK.
Note: 802.1D bridge type is not supported if a CorEvo card is configured on
the 9500 MPR device, version 6.0 or later.
3
Save your changes and close the form.
END OF STEPS
5.5
5.5.1
To resolve 9500 MPR MIB inconsistencies
Purpose
Perform this procedure to resolve NE inconsistencies created due to MIB population
failures that can occur during service creation on a 9500 MPR NE. If there are NE
inconsistencies, the Cleanup Inconsistencies button on the 9500 MPR network element
form becomes active to provide a visual cue that action is required to resolve them.
Nokia recommends that inconsistencies be resolved before any service creation. For
failures during 9500 MPR service creation, perform a resynchronization of the NE in
order to restore existing NE entries. Inconsistencies are detected during NE
synchronization or when opening the NE Properties form. If there are inconsistencies, an
alarm with a Warning severity level on the NE appears.
5.5.2
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR and choose
Properties. The 9500 MPR network element form opens.
54
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To update the software activation status for 9500 MPRe nodes
2
Click Cleanup Inconsistencies. The 5620 SAM attempts to resolve the NE MIB
inconsistencies.
3
To verify all MIB NE inconsistencies are resolved, click on the Faults tab to check for
any remaining inconsistency alarms.
4
Click on the Abnormal Conditions tab to check for the abnormal conditions on the
9500 MPR, such as loopback or TxMute conditions and to determine the appropriate
corrective actions.
Note: You must refresh the Abnormal Conditions tab to ensure the latest
content is displayed.
Note: You can clear the abnormal condition alarm after all the individual
abnormal conditions are cleared.
5
Close the form.
END OF STEPS
5.6
5.6.1
To update the software activation status for 9500 MPRe
nodes
Purpose
When software activation is performed via an MCT (microwave craft terminal) on a
managed 9500 MPRe node, the 5620 SAM does not indicate if the software activation
was successful. Perform this procedure to update the software activation status by
applying a forced activation to the node. This procedure causes the 9500 MPRe node to
reboot.
CAUTION
Service Disruption
Perform this procedure only in a maintenance window:
When you reboot a 9500 MPR that is in service, it is service-affecting. Ensure that the
reboot activity occurs during a maintenance window.
Issue 1
3HE-10693-AAAB-TQZZA
55
To configure a scope of command role for NEtO access
5.6.2
5620 SAM
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPRe shelf and choose
Properties. The Shelf (Edit) form opens.
2
Click on the Software Bank Details tab, select the Standby Bank and click
Properties. The MPRSoftware Package (Edit) form opens.
3
Set the Activation parameter to Forced Activation and click Apply. The node reboots.
4
Close the form.
END OF STEPS
5.7
5.7.1
To configure a scope of command role for NEtO access
Steps
1
Using an account with an assigned security scope of command role, choose
Administration→Security→5620 SAM User Security from the 5620 SAM main menu.
The 5620 SAM User Security - Security Management (Edit) form opens.
2
Click on the Scope of Command tab, click Create and choose Profile. The Scope of
Command Profile (Create) form opens
3
Configure the required parameters.
4
Click on the Roles tab and click Add. The Select Role - Role form opens.
5
Choose one of the following and click OK.
a. Admin NEtO launch to open the NEtO with the administration profile.
b. Viewer NEtO launch to open the NEtO with the viewer profile.
56
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To cross-launch the NEtO from the 5620 SAM GUI
c. Default NEtO launch to open the NEtO with the null profile.
Note: If the option to run TACACS+ in the network is enabled, choose the
Default NEtO launch.
6
Save your changes and close the form.
END OF STEPS
5.8
5.8.1
To cross-launch the NEtO from the 5620 SAM GUI
Purpose
To cross-launch the NEtO, you must belong to a user group that includes one of the
following scope of command profiles that is configured with the Administrator role, or
another role that has the following permissions set to Update/Execute:
• netw.NetworkElement.method_GUICrossLaunch
• mediation
• security.MediationPolicy
Note:
• For the 9500 MPRe, the NEtO cross-launch only occurs if the 9500 MPRe registration
table entry has not reached the limit of 15 entries.
• NEtO cross-launch only occurs on windows based 5620 SAM client.
For general information about user security, creating a scope of command role, and
creating a scope of command profile, see the 5620 SAM System Administrator Guide.
For specific information about creating a scope of command role for NEtO access, see
5.7 “To configure a scope of command role for NEtO access” (p. 56).
5.8.2
Steps
1
Perform one of the following:
a. In the navigation tree Equipment view, right-click on a 9500 MPR and choose
External Element Manager.
Note:
• If the NEtO is not installed on your client system, the NEtO Auto Update
Client window opens. Click Yes to download the client.
Issue 1
3HE-10693-AAAB-TQZZA
57
To configure QoS for inband TMN interfaces on the 9500 MPR
5620 SAM
• After the NEtO installation completes, the NEtO main view screen appears
for all subsequent launches, with the NEtO version adjusted to the NE
version from which the NEtO launched.
b. Perform the following for TACAS+:
1. In the navigation tree Equipment view, right-click on a 9500 MPR and choose
External Element Manager. A login prompt appears.
2. Type your login credentials. The NEtO main view screen appears.
Note: See the appropriate 9500 MPR (Hardware) User Guide for information
about configuring and using the NEtO external element manager.
END OF STEPS
5.9
5.9.1
To configure QoS for inband TMN interfaces on the 9500
MPR
General information
You can configure QoS for TMN inband interfaces on 9500 MPR devices via DSCP or
802.1p/802.1q following this procedure or using a 9500 MPR NE QoS policy. See
10.5 “To configure a 9500 NE QoS policy” (p. 103) for the 9500 MPR NE QoS policy
method.
5.9.2
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR device and choose
Properties. The 9500 MPR network element form opens.
2
Click on the Polling tab, then on the TMN Details tab. The current setting of TMN
interface are displayed in the TMN Working Mode column (either Enabled or
Disabled).
Note: You cannot change the QoS value (DSCP, VLAN ID, and PCP
parameters) if the in-band TMN interface is set to enabled.
3
Select one of the following for an TMN in-band interface:
a. To configure new QoS settings, double-click on an appropriate Disabled TMN
interface. Go to Step 4.
b. To modify an existing new QoS settings, double-click on the appropriate Enabled
58
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To configure QoS for inband TMN interfaces on the 9500 MPR
TMN interface. Go to Step 5. The MPR TMN - TMN In-band (Edit) form opens.
4
As required, configure the DSCP, VLAN ID, and PCP parameters to the appropriate
QoS level.
5
Configure the TMN Working Mode parameter to one of the following options:
a. Enabled to configure a new DSCP value. Go to Step 6.
b. Disabled to modify an existing DSCP value. Go back to Step 4.
Note: To modify an existing DSCP values for an in-band TMN interface, the
TMN Working Mode parameter must be set to Disabled before you reconfigure the DSCP parameter to the appropriate level.
6
Save your changes and close the form.
7
As required, repeat Step 3 to Step 6 to configure the QoS value for a second in-band
TMN interface.
END OF STEPS
Issue 1
3HE-10693-AAAB-TQZZA
59
To configure QoS for inband TMN interfaces on the 9500 MPR
60
3HE-10693-AAAB-TQZZA
5620 SAM
Issue 1
5620 SAM
9500 MPR LAG object configuration
6 9500 MPR LAG object configuration
6.1
6.1.1
Overview
Purpose
This chapter provides information about how to configure LAGs on the 9500 MPR.
6.1.2
Contents
6.1
Issue 1
Overview
61
Working with 9500 MPR LAG objects
62
6.2
Overview
62
6.3
Workflow to configure and manage 9500 MPR LAG objects
63
9500 MPR LAG configuration procedures
64
6.4
To create an Ethernet LAG on a 9500 MPR
64
6.5
To delete a 9500 MPR Ethernet LAG
66
3HE-10693-AAAB-TQZZA
61
Overview
5620 SAM
Working with 9500 MPR LAG objects
6.2
6.2.1
Overview
9500 MPR LAGs
Link Aggregation groups (LAGs) are a set of ports used to interconnect network nodes
using multiple links to increase link capacity and availability between them. LAGs also
provide redundancy between the aggregated links. If a link fails, traffic is redirected onto
the remaining link, or links.
LAGs on the 5620 SAM GUI are represented as part of the navigation tree objects and
are located below a device icon.
You can configure LAGs using the configuration forms available when you choose
Create LAG from the LAG object navigation tree contextual menu. See the “Logical
group object configuration” chapter in the 5620 SAM User Guide for more information.
6.2.2
Supported LAG types
The 5620 SAM supports the discovery of the LAG associations from the 5620 SAM or
NEtO external element manager for equipment functions on the 9500 MPR.
You can configure the following LAG types for the 9500 MPR:
• L1 Radio LAG (both static and adaptive modulation are supported) using NEtO
• L2 Radio LAG (only static modulation is supported) using NEtO
• L2 Ethernet LAG (supported modulation type does not apply to this LAG type) using
NEtO or 5620 SAM
Service configuration is supported across L1 and L2 Radio LAGs using the suite of
current service functionality. For example, support is provided for detection of end-to-end
bandwidth on the VLAN path or correlation of link level alarms up to paths that include
L1 Radio LAGs.
The 5620 SAM supports:
• discovery of the L1 and L2 Radio LAGs
• configuration and discovery of Ethernet LAGs
L1 LAGs can be created in the following configurations using NEtO:
• Intra plug-in LAG
• Cross plug-in LAG
An intra plug-in LAG is a LAG with MPT-HLS configured on the same card. A cross
plug-in LAG is a LAG with MPT-HLS configured on two EASv2 cards on the same MSS
row.
62
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Workflow to configure and manage 9500 MPR LAG objects
6.2.3
L1 Radio port deployment guidelines
An L1 Radio LAG follows a similar deployment model as an L2 Radio LAG except that
the L1 Radio LAG functions are deployed at the Radio layer. As a result, the L1 Radio
LAG has different port associations, cross-connections, and validations from the L2
Radio LAG. The advantage of a L1 Radio LAG is that highly correlated upper-layer traffic
can be hashed. For example, an LSP hashes to the same port in an L2 Radio LAG. Both
L1 and L2 Radio LAGs can be configured using NEtO only. See the 9500 MPR
(Hardware) User Manual for more information.
6.3
6.3.1
Workflow to configure and manage 9500 MPR LAG objects
Workflow sequence
The following workflow describes the sequence of high-level tasks required to configure
and manage 9500 MPR LAG objects; see the “Logical group object configuration”
chapter in the 5620 SAM User Guide for the generic procedures that apply to this device
type. Also, configure the following device-specific tasks and functions.
6.3.2
Process
1
Configure an Ethernet LAG on the 9500 MPR; see 6.4 “To create an Ethernet LAG
on a 9500 MPR” (p. 64).
2
Delete an Ethernet 9500 MPR LAG; see 6.5 “To delete a 9500 MPR Ethernet LAG”
(p. 66).
Issue 1
3HE-10693-AAAB-TQZZA
63
To create an Ethernet LAG on a 9500 MPR
5620 SAM
9500 MPR LAG configuration procedures
6.4
6.4.1
To create an Ethernet LAG on a 9500 MPR
General information
A link aggregation group, or LAG, is a group of physical ports that form one logical link
between two NEs to increase bandwidth, allow load balancing, and provide seamless
redundancy. LAG support over multiple devices provides NE-level redundancy in
addition. Use the following procedure to create manage LAGs on 9500 MPR devices.
Note: By default, Ethernet LAG is in access mode and can be used as a SAP. If a
physical link is created using Ethernet LAGs as the endpoints, the mode automatically
changes from access to network mode. If a physical link is created between MPR and
non-MPR LAG ports, and the MPR LAG port must be used as a SAP, the user must
change the mode to access. See Step 11 for more information about how to change the
mode.
Note: An Ethernet member port with a physical link or Radio port with protection cannot
be added to a LAG. To add the port, you must delete the physical link and then add the
port to the LAG. See the “5620 SAM topology map management” chapter in the 5620
SAM User Guide for more information about how to delete a physical link.
Note: For Fast Ethernet LAGs, electrical ports cannot be grouped with the optical ports.
6.4.2
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR Ethernet LAG and
choose Create LAG. The Create LAG step form open displaying the Define General
Properties step.
2
Configure the parameters as required and click Next. The Configure LAG
Parameters step displays.
3
Configure the parameters as required and click Next. The Configure LACP step
displays.
Note: The Name parameter configuration must be limited to a maximum of 15
characters.
64
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To create an Ethernet LAG on a 9500 MPR
4
Configure the parameters and click Next. The Configure LAG Members step
displays.
5
Click Create to add ports to the LAG. The Create LAG Member form opens
displaying the Only show compatible ports step.
Note: The Show Only Compatible Ports parameter on this form does not apply
to the 9500 MPR. The Class parameter depends on the Lag Aggregation Type
specified in Step 3.
6
Click Next. The Select Ports step displays.
7
Choose one or more ports from the list and click Finish. The Create LAG step form
reappears.
8
Click Finish. The Create LAG - Wizard Completed form opens.
9
If required, select the View the newly created Port Termination check box to view the
LAG properties, otherwise click Close. The LAG appears under the LAGs icon in the
navigation tree.
10
Right-click on the LAG, choose Turn Up and click Yes.
11
As required, right-click on the LAG and choose Properties to view information about
the created LAG or to modify the LAG parameters.
The LAG (Edit) form opens and displays the LAG ID and description.
• Choose one of the following Mode parameter values: Access (Ethernet LAG only)
or Network.
• The Link Aggregation Group tab displays the Name of the LAG, the number of
ports associated with the LAG member ports, and the Lag Aggregation Type. For
Ethernet LAG, choose Hash and Size from the drop-down menu
• LACP parameters can be modified from the LACP tab.
• LAG member ports can be added from the LAG Members tab.
Issue 1
3HE-10693-AAAB-TQZZA
65
To delete a 9500 MPR Ethernet LAG
5620 SAM
• The Administrative State parameter can be configured to Up in the States tab, only
if at least one port is associated with a LAG. The LAG state cannot be set to Down
if a service is associated with the LAG.
END OF STEPS
6.5
6.5.1
To delete a 9500 MPR Ethernet LAG
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR Ethernet LAG and
choose Delete LAG.
2
Click Yes to complete the deletion.
Note: A LAG can be deleted only if a member is not associated with the LAG.
To delete the last member from a LAG, the Administrative State of the LAG
must be set to Down. A LAG can be shut down only when the LAG is not a part
of any service or physical link.
Use NEtO to delete L1 and L2 Radio LAGs and LAG members. See Nokia
9500 MPR User Manual for more information.
END OF STEPS
66
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR shelf object configuration
7 9500 MPR shelf object configuration
7.1
7.1.1
Overview
Purpose
This chapter provides information about how to create and manage shelf objects on
9500 MPR devices.
7.1.2
Contents
7.1
Issue 1
Overview
67
9500 MPR shelf object configuration overview
68
7.2
Overview
68
7.3
Workflow to manage shelf objects on 9500 MPR devices
69
9500 MPR shelf object configuration procedures
71
7.4
To configure a 9500 MPR basic or advanced fan tray
71
7.5
To configure synchronization on a CorEvo card or MSS-1 shelf using
SYNC-IO SFPs
72
7.6
To configure an IEEE 1588 TC on a 9500 MPR shelf
73
7.7
To perform an on-demand 9500 MPR software upgrade
74
7.8
To manage the 9500 MPR running software
75
7.9
To migrate the 9500 MPRe connected to a 7705 SAR from standalone
mode to single NE mode
77
3HE-10693-AAAB-TQZZA
67
Overview
5620 SAM
9500 MPR shelf object configuration overview
7.2
7.2.1
Overview
General information
In the equipment navigation tree, shelf objects are children of device objects. Shelf
objects appear below logical group objects in the navigation tree. Card slot objects are
children of shelf objects, and as such appear below the shelf object in the navigation
tree.
7.2.2
9500 MPR shelf information
Shelf objects represent the hardware that is configured on a shelf. When you choose the
shelf object in the navigation tree and click on Properties in the contextual menu, you
can view the states and conditions of the 9500 MPR shelf including:
9500 MPR supported shelf states and
conditions
• general information
• fan tray state and speed
• card slots
• timing
• faults
9500 MPR supported shelf states and
conditions
• port segregation
• software control module
• software bank information
• cross connects
For 9500 MPRe devices, you can view the following states and conditions on the shelf:
9500 MPRe supported shelf states and
conditions
• general information
• display
• card slots
9500 MPRe supported shelf states and
conditions
• software control module
• software bank information
• faults
The Display tab displays a graphical representation of the device shelf and its equipment
components, such as the empty card slots and the cards that are installed on the device.
You can double-click on an object in the tab to open its Properties configuration form.
Right-click on the object and you have access to the contextual menus for the object and
any child objects; for example the ports of a card (dynamic graphical representation
only).
7.2.3
Working with cards and card slot objects on 9500 MPR devices
When you click on the plus sign beside a shelf object, the card slots in the shelf appear
in the navigation tree. They can appear as empty card slots when a card is not
provisioned for the slot.
68
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Workflow to manage shelf objects on 9500 MPR devices
Card slot objects for 9500 MPR devices can be configured using NEtO only. See the
Nokia 9500 MPR User Manual for more information.
7.2.4
CorEvo card
The CorEvo card is an extended version of the Core-ENH card. The card has eight
ports. Ports 1 to 4 are electrical ports. Ports 5 and 6 are only used for SFPs. Ports 7 and
8 can be used as a Radio port or an SFP. The electrical ports do not support half-duplex
operation. You can view CorEvo cards configured on an MSS shelf using the 5620 SAM
GUI. To configure ports on the CorEvo card, you require NEtO.
The two variants of the CorEvo card are 1G and 10G. The CorEvo 10G variant has 10
GigE Ethernet interfaces in the SFP ports (port 5 and port 6). The CorEvo 1G variant has
1 GigE Ethernet interfaces in the SFP ports (port 7 and port 8).
The 5620 SAM provides the following way to view the variants:
• from the equipment tree — Equipped Card Sub Type parameter value on the General
tab of the Network→9500 MPR→Shelf→Card Slot→Card Slot (Edit) form.
• from the inventory list — Equipped Card Sub Type column of the
Manage→Equipment→Equipment→Slot (Physical Equipment)→Card Slot (Physical
Equipment).
7.3
7.3.1
Workflow to manage shelf objects on 9500 MPR devices
Workflow sequence
The following workflow describes the sequence of high-level tasks required to manage
9500 MPR device shelf objects. For general shelf object management information, see
the “Shelf and card object configuration” chapter in the 5620 SAM User Guide.
7.3.2
Process
1
Configure NTP; see the “Shelf and card object configuration” chapter in the 5620
SAM User Guide.
2
Configure a basic or advanced fan tray on the 9500 MPR; see 7.4 “To configure a
9500 MPR basic or advanced fan tray” (p. 71).
3
Configure the card and card slot objects, and card and port protection using NEtO.
See the Nokia 9500 MPR User Manual.
Issue 1
3HE-10693-AAAB-TQZZA
69
Workflow to manage shelf objects on 9500 MPR devices
5620 SAM
4
If required, configure synchronization using SYNC-IO SFPs on the CorEvo card or
MSS-1 shelf; see 7.5 “To configure synchronization on a CorEvo card or MSS-1 shelf
using SYNC-IO SFPs” (p. 72).
5
If required, configure a 1588 transparent clock; see 7.6 “To configure an IEEE 1588
TC on a 9500 MPR shelf” (p. 73).
6
Upgrade the device software, as required.
General workflow to perform 9500 MPR device software upgrades:
1. Create a software upgrade policy that specifies MPR Node as the Policy Type;
see the “To configure a software upgrade policy” procedure in the 5620 SAM
User Guide.
Note: The software upgrade policy also provides the NE with the location of the
software image files on an FTP server.
2. Download the image package to a directory on a 5620 SAM client station. Extract
the package and ensure that the software description file is in the same directory.
3. Import the software description file; see the “To import device software files to the
5620 SAM procedure in the 5620 SAM User Guide.
The 5620 SAM transfers the description file to a specified FTP server from which
the 9500 MPR subsequently retrieves the image files.
4. Perform a software upgrade to transfer the files to the required NEs; see 7.7 “To
perform an on-demand 9500 MPR software upgrade” (p. 74) in this guide or “To
schedule an NE software upgrade” procedure in the 5620 SAM User Guide.
5. Activate the new software as the running software; see 7.8 “To manage the 9500
MPR running software” (p. 75).
7
As required, migrate a 9500 MPRe connected to a 7705 SAR from standalone mode
to single NE mode; see 7.9 “To migrate the 9500 MPRe connected to a 7705 SAR
from standalone mode to single NE mode” (p. 77).
8
As required, switch between an in-service protected Radio link and a standby
protected Radio link for 9500 MPR devices using NEtO.
70
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To configure a 9500 MPR basic or advanced fan tray
9500 MPR shelf object configuration procedures
7.4
7.4.1
To configure a 9500 MPR basic or advanced fan tray
General information
For the advanced fan tray, you can configure four ports for housekeeping alarms. If you
configured a basic fan and you need to change to an advanced fan, you do not need to
decommission the basic fan first.
The advanced fan is only supported on the 9500 MPR Release 5.0, or later.
7.4.2
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR shelf and choose
Properties. The Shelf (Edit) form opens.
2
Click on the Fan Trays tab and click Create. The Fan Tray (Create) form opens.
3
Configure the parameters as required.
4
If you configured the Fan Type parameter as A-Fan, go to Step 5. Otherwise, go to
Step 8.
5
Click on the External Point Inputs tab and click Properties. The Auxiliary Inputs (Edit)
form opens.
6
Configure the parameters as required and click OK. The Fan Tray (Edit) form
reappears.
7
As required, repeat Step 5 and Step 6 to configure more ports for housekeeping
alarms.
Issue 1
3HE-10693-AAAB-TQZZA
71
To configure synchronization on a CorEvo card or MSS-1 shelf using SYNC-IO SFPs
5620 SAM
8
Save your changes and close the form.
END OF STEPS
7.5
7.5.1
To configure synchronization on a CorEvo card or MSS-1
shelf using SYNC-IO SFPs
General information
The CorEvo card and MSS-1 shelf do not have dedicated synchronization ports. The
SFPs configured on the CorEvo card or the MSS-1 provide Sync-In/Out ports. The SFPs
are installed in ports 5 and 6 of an MSS-1 and ports 7 and 8 of a CorEvo card.
Note: Before configuring synchronization, you must configure the required SFPs on the
CorEvo card or MSS-1 shelf with a value of SYNC-IO using NEtO.
7.5.2
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR shelf equipped with
a CorEvo card or the MSS-1 shelf and choose Properties. The Shelf (Edit) form
opens.
2
Click on the Timing tab and configure the Secondary Reference Type parameter as
Sync-In Port. The Sync In panel is displayed.
3
Select the timing reference in the Sync In panel and click Apply.
4
Click Properties in the Sync In panel. The Physical Port (Edit) form opens.
5
Click on the Timing tab and configure the parameters in the Sync In/Out SFPs panel.
6
Click Apply to save your changes and close the forms.
END OF STEPS
72
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To configure an IEEE 1588 TC on a 9500 MPR shelf
7.6
7.6.1
To configure an IEEE 1588 TC on a 9500 MPR shelf
General information
You can enable an IEEE 1588 transparent clock (TC) on a 9500 MPR shelf if the SW
License parameter value in the System Settings tab of the corresponding Network
Element (Edit) form contains the string 1588TC.
You can also perform a bulk operation to enable 1588 transparent clock on many
shelves at once. Choose Tools→Bulk Operations from the 5620 SAM main menu and
select SONET Sync in the object drop-down menu of the Create Bulk Change form to
configure bulk changes for 1588 TC. See the “Bulk Operations” chapter in the 5620 SAM
User Guide for more information.
7.6.2
IEEE 1588v2 PTP support per platform
The platforms that are supported include:
• MSS-O
• MSS-1
• MSS-4
• MSS-8
IEEE 1588v2 PTP support is enabled or disabled at node level then automatically
applied by the node to the following MPT type of the node, if equipped:
• MPT HC V2
• MPT HLS
• MPT HLC
• MPT MC
• MPT HQAM
Note:
• IEEE 1588v2 PTP is not supported for ODU300 and MPT-HL v1.
• IEEE 1588v2 PTP is not supported for MPRe and MSS-1c. However, 1588TC fail
alarm reporting is supported.
7.6.3
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR shelf and choose
Properties. The Shelf (Edit) form opens.
Issue 1
3HE-10693-AAAB-TQZZA
73
To perform an on-demand 9500 MPR software upgrade
5620 SAM
2
Click on the Timing tab, select the Enabled check box in the 1588 panel and click
Apply to save the changes and close the form.
Note: By default, the 1588 panel is present in the Shelf (Edit) form. However, if
the corresponding 9500 MPR device does not have the 1588 TC license, then
you cannot modify 1588 on the shelf.
END OF STEPS
7.7
7.7.1
To perform an on-demand 9500 MPR software upgrade
Purpose
Perform this procedure to upgrade the device software on one or more 9500 MPR NEs.
Prior to performing this procedure, review the 9500 MPR software upgrade workflow
steps contained in the 7.3 “Workflow to manage shelf objects on 9500 MPR devices”
(p. 69) for the additional procedures required to complete this procedure.
The 9500 MPR software is stored in two banks on a compact flash card:
• The committed bank contains the software that is currently running.
• The standby bank contains downloaded software that has not been activated, or
software that was active before the current committed software.
Note:
• A 9500 MPR that has never been upgraded displays only the committed bank. The
standby bank is not displayed until new software is downloaded for the first time.
• You require a 5620 SAM user account with an administrator or network element
software management scope of command role, or a scope of command role with write
access to the mediation package before you can perform a 9500 MPR software
download.
• After a 5620 SAM system upgrade from 12.0 R7 or later, you must delete any
previously imported MPR software images used to perform a 9500 MPR software
upgrade and re-import the same.
7.7.2
Steps
1
Choose Administration→NE Maintenance→Software Upgrade from the 5620 SAM
main menu. The Software Upgrade form opens.
2
Click on the Software Images tab, select the appropriate software upgrade policy
and then the MPR 9500 Software Images tab.
74
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To manage the 9500 MPR running software
Note: The 5620 SAM performs the upgrade according to the configuration in
the software upgrade policy to which the NE is assigned.
3
Click Import and select a software descriptor file. A software descriptor file has a
.DSC extension and must be present on the client system. Other software files do
not need to be present on the client system.
4
Click Upgrade Sites. A list of NEs opens. The list is filtered to display only the device
type that is appropriate for the selected software image.
5
Select one or more NEs and click OK. The software upgrade begins.
6
Click on the Software Upgrade Status tab to view the status of the upgrade as it
progresses. Verify that the files are successfully transferred.
7
Close the Software Upgrade form. After a successful software upgrade, you must
activate the software; see 7.8 “To manage the 9500 MPR running software” (p. 74)
END OF STEPS
7.8
7.8.1
To manage the 9500 MPR running software
Purpose
Perform this procedure to manage the software in the 9500 MPR committed and standby
banks. You can upgrade or downgrade the running software release on a 9500 MPR.
See “NE software upgrade overview” in the 5620 SAM User Guide for information about
creating software upgrade policies and performing software upgrades.
Issue 1
3HE-10693-AAAB-TQZZA
75
To manage the 9500 MPR running software
5620 SAM
WARNING
Equipment Damage
To avoid a service outage:
A 9500 MPR may require a firmware upgrade before a device software upgrade. To
avoid a service outage, ensure that the device firmware version supports the software
upgrade. See the device software Release Notes to obtain information about firmware
and software release compatibility.
CAUTION
Service Disruption
Perform this procedure only in a maintenance window:
When you reboot a 9500 MPR that is in service, it is service-affecting. Ensure that the
reboot activity occurs during a maintenance window.
Note: During a software upgrade, the NE audit function is not supported for 9500 MPR
NEs.
7.8.2
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR shelf and choose
Properties. The Shelf (Edit) form opens.
2
Click on the Software Bank Details tab. The committed and standby software
information is displayed. The committed software is the software currently running on
the NE. The standby software is new software uploaded to the NE, or formerly
committed software.
3
Verify that the operational state of the standby software is Enabled by examining the
Operational State value.
You can also examine the Software Version of the standby and committed software.
If the software version of the standby software is more recent than the committed
software version, the NE can be upgraded. If the standby software version is older
than the committed software version, the NE can be downgraded.
4
Select the standby entry and click Properties. The MPR Software Package (Edit)
form opens.
76
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To migrate the 9500 MPRe connected to a 7705 SAR from standalone mode to single NE mode
5
Configure the Activation parameter and click OK. The Shelf (Edit) form reappears.
6
Save your changes and close the form. When the standby and committed software
versions are different or the forced activation option is selected, the NE reboots
using the standby software. If the standby and committed software versions are the
same and the activation option is chosen, the NE does not reboot and the Shelf
(Edit) form closes.
7
After the NE reboots, you can confirm that the NE is running the software stored in
the former standby bank. The former standby software is the committed software
and the previous committed software is the standby software.
END OF STEPS
7.9
7.9.1
To migrate the 9500 MPRe connected to a 7705 SAR from
standalone mode to single NE mode
Prerequisites
This procedure assumes you have configured a 7705 SAR MW link and link member
before starting this procedure; see the “Shelf and card object configuration” chapter in
the 5620 SAM User Guide.
Note: If the 9500 MPRe is discovered as a standalone device on the 5620 SAM, then
later changed to single NE mode, you must manually remove the 9500 MPRe node from
the database because it shows as unreachable on the 5620 SAM.
For information about the 7705 SAR and 9500 MPRe, see the 9500 MPRe 5.0, 5.1, 5.2,
6.0, 6.1, 7.0, or later and 7705 SAR 6.0 R1 hardware guides.
The following requirements must be met before you change the 9500 MPRe from
standalone mode to single NE mode:
• Ensure that the 7705 SAR is upgraded to Release 6.0 R1 and the 9500 MPRe is
upgraded to Release 5.0, 5.1, 5.2, 6.0, 6.1, 7.0, or later.
• Ensure that the MPT software packages are in the cf3:/images/<Timos.xx.xx>
directory on the 7705 SAR NE.
• Ensure that the MWA converted database (*.tar) file is in the cf3:<config file path> on
the 7705 SAR NE.
• Ensure that the MPT state is operationally up when it is in standalone mode by
connecting it to the 7705 SAR.
Issue 1
3HE-10693-AAAB-TQZZA
77
To migrate the 9500 MPRe connected to a 7705 SAR from standalone mode to single NE mode
7.9.2
5620 SAM
Steps
1
In the navigation tree Equipment view, right-click on a 7705 SAR port that you
associated with the MW link and choose Properties. The MW Link Member (Edit)
form opens.
2
Configure the parameters as required.
Note: For migration, restart the MPT using the MCT and deselect the
Standalone check box within 30 to 60 s of the Radio restart or the MPT may
not function as expected. If the restart fails to change the MPT to single NE
mode, the MPT must be physically restarted.
You can use the MCT only if the 9500 MPRe is in standalone mode and
managed by the 5620 SAM. If the 9500 MPRe is connected to the 7705 SAR in
standalone mode, but not managed by 5620 SAM, you must use the NEtO
/MCT.
3
Click on the Radio tab and configure the parameter as required.
4
Save your changes and close the form.
END OF STEPS
78
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR port object configuration
8 9500 MPR port object configuration
8.1
8.1.1
Overview
Purpose
This chapter provides information about to configure 9500 MPR ports, the supported
QoS protection schemes, and other port configuration procedures such as configuring a
power source or performing synchronization or a loopback test on 9500 MPR ports.
8.1.2
Contents
8.1
Issue 1
Overview
79
9500 MPR port configuration overview
80
8.2
Overview
80
8.3
Workflow to manage port objects on 9500 MPR devices
81
Port configuration procedures
83
8.4
To configure 9500 MPR Ethernet ports
83
8.5
To collect and view analog Radio statistics on 9500 MPR 1x Radio
modem ports
84
8.6
To collect performance management statistics on 9500 MPR 1x Radio
modem ports
85
8.7
To configure 9500 MPR port segregation on an EAS module
86
8.8
To configure a power source for 9500 MPR card slots
87
8.9
To configure synchronization on 9500 MPR Ethernet ports
87
8.10
To configure a loopback test on 9500 MPR ports
88
8.11
To configure 802.3ah EFM OAM remote loopbacks on 9500 MPR ports
89
8.12
To configure Tx mute on radio ports
91
3HE-10693-AAAB-TQZZA
79
Overview
5620 SAM
9500 MPR port configuration overview
8.2
8.2.1
Overview
General information
Port objects are children of card slot objects. Port objects appear below the card slot
after the card is configured. Properties forms for port objects are accessed using the
5620 SAM navigation tree.
8.2.2
QoS protection schemes for Ethernet ports
You can configure the following QoS protection schemes on 9500 MPR Ethernet ports:
• traffic storm control
A traffic storm occurs when packets flood a LAN creating excessive traffic and
degrading network performance. You can use traffic storm control to prevent Ethernet
ports from being disrupted by a broadcast, multicast, or unicast traffic storm on the
physical interfaces, and limit the impact of VLAN misconfigurations.
Traffic storm control monitors the incoming traffic levels over a 1-s interval and, during
the interval, compares the traffic level with the traffic storm control level that you
configure on the 5620 SAM. The traffic storm control level is a percentage of the total
available bandwidth of the Ethernet port. For example, if traffic storm control is
enabled for ingress traffic and it reaches the configured level on the port with the
interval, the traffic is dropped until the traffic storm control interval ends.
• port rate limiting
You can use port rate limiting to protect the Radio-side bandwidth from being
overloaded by an ingress or egress port. A common application for port rate limiting is
when a 9500 MPR provides the backhaul service for multiple 7705 SAR devices
whose queues do not have the visibility of the bandwidth available of the Radio side.
• dot1q VLAN rate limiting
You can use dot1q VLAN rate limiting to protect the Radio side bandwidth on the 9500
MPR from being overloaded by an ingress port when transporting IP/MPLS over MPR
transport services on dot1q VLANs. A common application of the VLAN rate limiting
feature is to monitor the 9500 MPR backhaul services providing transport to multiple
7705 SAR devices whose queues could individually exceed the available Radio
bandwidth.
Traffic storm control, port rate limiting, and dot1q VLAN rate limiting are supported on the
core-enhanced card and the 4+4 × Ethernet (EAS) card on the 9500 MPR.
See 8.4 “To configure 9500 MPR Ethernet ports” (p. 83) for information about enabling
traffic storm control, port rate limiting, and dot1q VLAN rate limiting on the 9500 MPR.
80
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Workflow to manage port objects on 9500 MPR devices
8.2.3
Monitoring 9500 MPR ports using 802.3ah EFM OAM remote
loopbacks
You can monitor 9500 MPR Ethernet or SFP ports using the 802.3ah EFM OAM remote
loopback diagnostic test on a Core-E, CorEvo, EASv1 and EASv2 cards, and on an
MSS-1 or MSS-O shelf. See 8.11 “To configure 802.3ah EFM OAM remote loopbacks on
9500 MPR ports” (p. 89).
Note: The link monitoring and fault signaling operational aspects of the 802.3ah EFM
OAM diagnostic test are not supported on the 9500 MPR.
When enabled, the remote loopback allows a local DTE to locate a remote DTE and put
a into a state whereby all inbound traffic is immediately reflected back onto the link. The
802.3ah EFM OAM remote loopback information is carried by the OAMPDUs.
OAMPDUs contain the control and status information to monitor, test, and troubleshoot
OAM-enabled links.
8.3
8.3.1
Workflow to manage port objects on 9500 MPR devices
General information
The following workflow describes the sequence of high-level tasks required to manage
9500 MPR ports. See the Nokia 9500 MPR (hardware) User Manual for more
information.
8.3.2
Process
1
As required, change the port mode between Network, Access, and Hybrid modes
using NEtO.
2
As required, configure the ports on 9500 MPR devices using NEtO.
a. Ethernet ports; see 8.4 “To configure 9500 MPR Ethernet ports” (p. 83)
b. 2 × STM card ports
c. 1 × STM (Channelized) card port
d. E1 and DS1 ports
e. DS3 ports
f. AUX alarm ports
g. 9500 MPRe ports
Issue 1
3HE-10693-AAAB-TQZZA
81
Workflow to manage port objects on 9500 MPR devices
5620 SAM
3
As required, configure or perform the following on 9500 MPR device ports:
a. analog performance management on 9500 MPR 1x Radio modem ports; see
8.5 “To collect and view analog Radio statistics on 9500 MPR 1x Radio modem
ports” (p. 84)
b. power level performance management on 9500 MPR 1x Radio modem ports; see
8.6 “To collect performance management statistics on 9500 MPR 1x Radio
modem ports” (p. 85)
c. 9500 MPR port segregation; see 8.7 “To configure 9500 MPR port segregation on
an EAS module” (p. 86)
d. power source type on 2+2 × Ethernet (EAS) card slots for 9500 MPR; see 8.8 “To
configure a power source for 9500 MPR card slots” (p. 87)
e. synchronization on Ethernet ports; see 8.9 “To configure synchronization on 9500
MPR Ethernet ports” (p. 87)
f. loopback test on a 9500 MPR DS1, ES1, or 1x Radio modem port; see 8.10 “To
configure a loopback test on 9500 MPR ports” (p. 88)
g. enable 802.3ah EFM OAM loopbacks on Ethernet or SFP ports; see 8.11 “To
configure 802.3ah EFM OAM remote loopbacks on 9500 MPR ports” (p. 89)
h. configure Tx mute on the radio ports; see 8.12 “To configure Tx mute on radio
ports” (p. 91)
82
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To configure 9500 MPR Ethernet ports
Port configuration procedures
8.4
8.4.1
To configure 9500 MPR Ethernet ports
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR Ethernet port and
choose Properties. The Physical Port (Edit) form opens.
2
Configure the parameters as required.
Note: The User Label parameter configuration must be limited to a maximum
of 15 characters.
3
Click on the States tab and configure the Administrative State parameter.
4
Click on the Ethernet tab and configure the parameters as required.
Note: Before configuring the Advertised Capability parameter, click Turn Up on
the Physical Port (Edit) form to display the value of the Egress Rate parameter
correctly under the Ethernet tab of the Physical Port (Edit) form.
Check the combinations that are supported for the Advertised Capability
parameter in the 9500 MPR (Hardware) User Guide.
5
Perform the following step if you need to enable one or more protection schemes on
the Ethernet port, otherwise go to Step 6. See 8.2.2 “QoS protection schemes for
Ethernet ports” (p. 80) in this section for more information.
a. To enable traffic storm control on the port, configure the parameters in the Storm
control panel.
b. To enable port rate limiting on the ports, configure the parameters in the Port Rate
Limiter panel.
c. To enable dotq VLAN rate limiting on the port:
Issue 1
3HE-10693-AAAB-TQZZA
83
To collect and view analog Radio statistics on 9500 MPR 1x Radio modem ports
5620 SAM
Note: VLAN rate limiting should not be activated in conjunction with port
rate limiting.
You can enable up to eight VLAN rate limits on an Ethernet port.
1. Click on the VLAN Rate Limiter tab, choose an Ethernet port and click
Properties. The VLAN Rate Limiter (Edit) form opens.
2. Configure the parameters as required.
3. Save your changes and close the form,
6
Save your changes and close the form.
END OF STEPS
8.5
To collect and view analog Radio statistics on 9500 MPR
1x Radio modem ports
Note: When per-queue statistics are collected, Q1 record is not available for the
collected statistics.
Note: When per-queue statistics are collected, nothing is returned by the NE.
Note: When plotting is performed real-time, a data missing exception occurs for the
specific interval.
Note: The retrieve time is not correctly updated.
8.5.1
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR 1x Radio modem
port and choose Properties. The Physical Port (Edit) form opens.
2
Click on the Statistics tab and choose Radio Analog Statistics (Radio Equipment)
from the Select Object Type contextual menu.
3
Click Collect. A statistics record appears in the Physical Port (Edit) form.
4
Select the record and click Properties. The Statistics Record - Radio Analog
Statistics form opens.
84
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To collect performance management statistics on 9500 MPR 1x Radio modem ports
5
View the read-only analog performance values for the 1x Radio modem port.
6
Close the forms.
END OF STEPS
8.6
To collect performance management statistics on 9500
MPR 1x Radio modem ports
Note: When per-queue statistics are collected, Q1 record is not available for the
collected statistics.
Note: When per-queue statistics are collected, nothing is returned by the NE.
Note: When plotting is performed real-time, a data missing exception occurs for the
specific interval.
Note: The retrieve time is not correctly updated.
8.6.1
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR 1x Radio modem
port and choose Properties. The Physical Port (Edit) form opens.
2
Click on the Statistics tab.
Choose one of the following performance management statistics from the Select
Object Type contextual menu:
• Hop Current Data Stats
• Link Current Data Stats
• RSL Hop Current Data Stats
• TSL Hop Current Data Stats
3
Click Collect. A statistics record appears in the Physical Port (Edit) form.
4
Select the record and click Properties. The Statistics Record <selected performance
management stats type> Current Data Stats form opens.
Issue 1
3HE-10693-AAAB-TQZZA
85
To configure 9500 MPR port segregation on an EAS module
5620 SAM
5
View the read-only performance values for the 1x Radio modem port.
6
Close the forms.
END OF STEPS
8.7
8.7.1
To configure 9500 MPR port segregation on an EAS
module
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR shelf and choose
Properties. The Shelf (Edit) form opens.
2
Click on the Port Segregation tab and click Create. The Add Member - Shelf step
form opens with the Select From Type step displayed.
3
Configure the From Type parameter and click Next. The From step appears.
4
Click Select, choose a port from the list and click OK. The Add Member step form
reappears.
5
Click Next. The Select To Type step displays.
6
Configure the To Type parameter and click Next. The To step displays.
7
Choose a port, click Finish, then OK. The Shelf (Edit) form reappears.
8
Close the form.
END OF STEPS
86
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To configure a power source for 9500 MPR card slots
8.8
8.8.1
To configure a power source for 9500 MPR card slots
Supported card slots
You can configure a power source on the following card slots:
• 2+2 x Ethernet (EAS)
• EASv2
• MSS1
8.8.2
Steps
1
In the navigation tree Equipment view, right-click on a supported 9500 MPR card slot
and choose Properties. The Card Slot (Edit) form opens.
2
Click on the Power Source tab and double-click on a displayed interface. The Power
Source (edit) form opens.
3
Configure the Type parameter and click OK. The Card Slot (Edit) form reappears.
4
Save your changes and close the form.
END OF STEPS
8.9
8.9.1
To configure synchronization on 9500 MPR Ethernet ports
General information
PDH and SDH data flow is fragmented and the fragments are transmitted over a packetswitched network. The data rates are controlled by the terminating sites using clocks.
The rate at which the fragments are transferred varies based on the variations in these
Issue 1
3HE-10693-AAAB-TQZZA
87
To configure a loopback test on 9500 MPR ports
5620 SAM
clocks. By synchronizing the clocks on the terminating devices, the received fragments
are reassembled in the original PDH or SDH data flow at the original bit rate.
You can configure synchronization on the Ethernet ports on the following cards:
• Core-enhanced
• EASv2
Before configuring synchronous Ethernet, ensure the following:
• SFP must be configured on ports 5 and 6 on a core-enhanced card using NEtO.
• SFP must be configured on ports 5 to 8 on an EASv2 card using NEtO.
• Ethernet ports and SFPs must be administratively up.
8.9.2
Steps
1
In the navigation tree Equipment view, right-click on a supported 9500 MPR Ethernet
port and choose Properties. The Physical Port (Edit) form opens.
2
Click on the Timing tab and configure the SSM parameter to disable or enable the
transmission of the synchronization status message over the Radio channel.
3
Save your changes and close the form.
END OF STEPS
8.10
8.10.1
To configure a loopback test on 9500 MPR ports
Supported card ports
You can configure a loopback test on 9500 MPR ports on the following cards:
9500 MPR ports supporting loopback test
• 1 x Radio modem
• DS1
• ES1
• MPT-HCv2
• MPT-HLC
9500 MPR ports supporting loopback test
• MPT-HLS
• MPT-HLv1
• MPT-HQAM
• STM
Note: If the card containing the ports is configured but not equipped, a loopback test
cannot be performed on the physical ports of the card.
88
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To configure 802.3ah EFM OAM remote loopbacks on 9500 MPR ports
8.10.2
Steps
1
In the navigation tree Equipment view, right-click on a supported 9500 MPR port and
choose Properties. The Physical Port (Edit) form opens.
2
Click on the Loopback tab, select an interface and click Properties. The Loopback
(Edit) form opens.
3
Configure the parameters as required and click OK. The Physical Port (Edit) form
reappears.
4
Save your changes and close the form.
END OF STEPS
8.11
8.11.1
To configure 802.3ah EFM OAM remote loopbacks on 9500
MPR ports
Supported card ports
You can configure a 802.3ah EFM OAM remote loopback on an Ethernet or SFP port on
Core-E, CorEvo, EASv1 and EASv2 cards that reside on a MSS-1 or MSS-O shelf.
Note: To configure a 802.3ah EFM OAM remote loopback on a port, the administrative
state of a port must be up.
8.11.2
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR Ethernet port and
choose Properties. The Physical Port (Edit) form opens.
2
Click on the Ethernet tab, then on the EFM OAM tab.
3
Configure the Mode parameter as Active.
Issue 1
3HE-10693-AAAB-TQZZA
89
To configure 802.3ah EFM OAM remote loopbacks on 9500 MPR ports
5620 SAM
4
Configure the Administrative State parameter as Enabled. The value of the
Operational Status parameter changes to Operational.
Note: You must not modify the Mode parameter when the Administrative State
parameter is configured as Disabled, even though the Mode parameter is
configurable.
The Operational Status parameter has intermediate values, before changing to
Operational. The Operational Status can be Operational only when the remote
DTE has the same settings as the local DTE for the 802.3ah EFM OAM remote
loopback.
5
Perform 8.2.2 a to enable a remote loopback or 8.2.2 b to disable a remote
loopback:
a. Select the Set Remote Loopback check box to enable a remote loopback. The
value of the Loopback Status parameter changes to Remote Loopback after
displaying some intermediate values.
Note: Ensure that the value for the Operational Status parameter is
Operational before you select the Set Remote Loopback check box.
When remote loopback is enabled on a port, you cannot modify port
segregation of the corresponding card.
b. Deselect the Set Remote Loopback check box to disable the remote loopback.
Note:
You can disable remote loopback on a port when the value of the Loopback
Status parameter is one of the following:
• Remote Loopback
• Initiating Loopback
• Terminating Loopback
6
Save your changes and close the form.
END OF STEPS
90
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To configure Tx mute on radio ports
8.12
8.12.1
To configure Tx mute on radio ports
Steps
1
On the equipment tree, expand Network→9500 MPR→Card Slot.
2
Right-click on the radio port object and choose Properties. The Physical Port (Edit)
form opens.
3
Click on the Radio tab and perform one of the following:
a. Set the Manual Local Tx Mute parameter on the Tx Mute panel to On and the
transmitter is muted indefinitely.
b. Perform the following to provide a duration during which the transmitter is muted:
1. Set the Manual Local Tx Mute parameter to Timed.
2. Configure the Manual Local Timeout (minutes) parameter. The maximum
duration is 2880 minutes (2 days).
Note: You cannot set the Manual Local Timeout (minutes) to zero.
Note: It is not possible to change the Tx mute parameter values from Timed to
On and On to Timed. Change the Tx mute parameter values from Timed to Off,
then to On.
4
Save the changes and close the form.
END OF STEPS
Issue 1
3HE-10693-AAAB-TQZZA
91
To configure Tx mute on radio ports
92
5620 SAM
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR inventory management
9 9500 MPR inventory management
9.1
9.1.1
Overview
Purpose
This chapter describes the 9500 MPR inventory management
9.1.2
9.2
9.2.1
Contents
9.1
Overview
93
9.2
Radio port inventory
93
9.3
To list and sort inventory information
95
9.4
To save an inventory list
96
Radio port inventory
Introduction
You can view the inventory of the 9500 MPR radio ports using the 5620 SAM Equipment
Manager.
9.2.2
Radio port inventory – 9500 MPRe and 9500 MSS-1c
Choose Manage→Equipment→Equipment and the Manage Equipment form opens.
Choose Port (Physical Equipment)→Radio Port (Radio Equipment) from the object dropdown menu. A list of radio ports appears. Remove all columns from the list except the
following columns, which display the accurate values.
• Radio Interface ID
• Remote Node IPV4 Address
• Remote Node Interface
Note:
• The 5620 SAM does not support the display of accurate values for those columns
other than the ones listed here:
• Performance monitoring status and remote inventory data are not part of the inventory
report.
See 9.3 “To list and sort inventory information” (p. 95) and 9.4 “To save an inventory list”
(p. 96) for more information.
Issue 1
3HE-10693-AAAB-TQZZA
93
Radio port inventory
9.2.3
5620 SAM
Radio interface IDs
The radio interface IDs are defined as follows:
• Radio LAG – 50122 to 50135
• MPT Port – 500001 to 599999
• ODU Port – 50001 to 59999 except the IDs from 50122 to 50135 that are the radio
LAG IDs
9.2.4
Radio port inventory – 9500 MPR (ANSI and ETSI) devices
Choose Manage→Equipment→Equipment and the Manage Equipment form opens.
Choose Port (Physical Equipment)→Radio Port (Radio Equipment) from the object dropdown menu. A list of radio ports and L1 radio LAGs appears. Remove all columns from
the list except the parameters that are displayed in the Radio tab of the Network→9500
MPR→Card Slot→Radio Port→Physical Port (Edit) form.
Note:
• The 5620 SAM does not support the display of accurate values for the columns other
than the parameters that are displayed in the Radio tab of the Network→9500
MPR→Card Slot→Radio Port→Physical Port (Edit) form.
• The User Label column displays the accurate values for radio ports but not for L1 radio
LAGs.
• Performance monitoring status and remote inventory data are not part of the inventory
report.
See 9.3 “To list and sort inventory information” (p. 95) and 9.4 “To save an inventory list”
(p. 96) for more information.
9.2.5
Radio LAG member inventory – 9500 MPR (ANSI and ETSI) devices
Choose Manage→Equipment→Equipment and the Manage Equipment form opens.
Choose Port (Physical Equipment)→Logical Port (Physical Equipment)→Port Group
(Network)→Port Group (aggregation)→LAG (LAG) from the object drop-down menu. A
list of LAGs appears. Choose a specific radio LAG using the range of radio interface
values listed in 9.2.3 “Radio interface IDs” (p. 94) and click Properties. The LAG (Edit)
form opens. Click on the LAG Members tab to list the members of the LAG.
Note: Performance monitoring status and remote inventory data are not part of the
inventory report.
94
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To list and sort inventory information
9.3
9.3.1
To list and sort inventory information
Steps
1
Choose Manage→Equipment→Equipment from the 5620 SAM main menu. The
Manage Equipment form opens.
2
Perform one of the following to generate a list of equipment.
a. List the equipment on one NE.
1. Choose Network Element (Network) from the object drop-down menu and click
Search. A list of NEs is displayed.
2. Select an NE and click Properties. The Network Element (Edit) form opens.
3. Click on the Inventory tab and choose an object type from the object dropdown menu. A list of objects is displayed.
b. List the equipment in the entire network.
1. Choose an object type from the object drop-down menu.
2. Configure the filter criteria and click Search. A list of objects is displayed.
3
Perform one or more of the following to format the results:
a. To display the number of items in the list, right-click on the list heading and view
the Count value.
b. To sort the list, click on a column heading. The column heading displays an arrow
that indicates the sort order.
c. To move a column, drag the column to a different position.
d. To remove a column, perform the following steps:
1. Right-click on the column heading and choose Column Display. The Column
Display form opens.
2. Select the columns to remove in the Displayed on Table list, then click on the
left arrow. The columns move to the Available for Table list.
3. Click OK. The columns are removed from the table.
e. To sort multiple columns, perform the following steps:
1. Right-click on a column heading and choose Show Sorting. The Show Sorting
form opens.
2. Select one or more properties in the Available for Sorting panel, then click on
the right arrow button. The properties move to the Used for Sorting panel.
Issue 1
3HE-10693-AAAB-TQZZA
95
To save an inventory list
5620 SAM
3. Click Sort Ascending or Sort Descending, as required.
4. Close the Show Sorting form.
4
Save your column display and sorting preferences:
1. Right-click on any column heading and choose Save Table Preferences.
2. Confirm the action. The configured display preferences are applied whenever you
open a list table for the same object type.
5
Save the inventory output, as required. See 9.4 “To save an inventory list” (p. 95).
6
Close the form.
END OF STEPS
9.4
9.4.1
To save an inventory list
Steps
1
Right-click on a column heading of the inventory output and choose Save to File.
The Save As file browser form opens.
2
Navigate to the directory in which you want to save the file.
3
Configure the File Name and Files of Type parameters.
4
Click Save. The 5620 SAM saves the inventory list.
END OF STEPS
96
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Part III: 9500 MPR policy and service management
Overview
Purpose
Part III provides information about how to configure QoS policies, service tunnels, and
VLAN/VLL services on the 9500 MPR.
Contents
Chapter 10, 9500 MPR QoS policies
Issue 1
99
Chapter 11, 9500 MPR service management and service tunnels
105
Chapter 12, 9500 MPR VLAN service management
129
Chapter 13, 9500 MPR VLL service management
151
3HE-10693-AAAB-TQZZA
97
5620 SAM
98
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR QoS policies
10 9500 MPR QoS policies
10.1
10.1.1
Overview
Purpose
The chapter provides information about how to configure NE QoS policies, and Radio
Interface Queue Map policies.
10.1.2
Contents
10.1
Issue 1
Overview
99
9500 MPR QoS policies overview
100
10.2
Overview
100
10.3
Workflow to configure 9500 MPR QoS policies
100
9500 MPR QoS policies procedures
102
10.4
To configure a 9500 Radio Interface Queue Map policy
102
10.5
To configure a 9500 NE QoS policy
103
3HE-10693-AAAB-TQZZA
99
Overview
5620 SAM
9500 MPR QoS policies overview
10.2
10.2.1
Overview
Supported QoS policies
QoS policies define how network traffic is shaped and queued on one or more 9500
MPR device ports and to regulate data throughput. You can use the 5620 SAM to create
the following 9500 MPR-specific QoS policies:
• 9500 NE QoS policies
9500 NE QoS policies define the QoS classification used for network traffic that
traverse 9500 MPR device ports and to apply the 9500 Radio Interface Queue Map
policy.
• 9500 Radio interface queue map policies
9500 Radio Interface Queue Map policies specify the queue size and queue delay for
all queues for the Radio interface that connect to 9500 MPR ports. This policy is
applied when the 9500 NE QoS policy is configured.
The following variants are supported for this policy type:
— ODU
— MPT-HL
— MPT-HC/MPT-MC
— MPT-HLS (9500 MPR version 5.1, 5.2, 6.0, and higher)
— MPT-HLC (9500 MPR version 5.1, 5.2, 6.0, and higher)
— MPT-HQAM (9500 MPR version 5.2, 6.0, and higher)
10.3
10.3.1
Workflow to configure 9500 MPR QoS policies
Process
1
Review the “Policies overview” chapter in the 5620 SAM User Guide for information
about 5620 SAM policy management and for the workflow to create and distribute
policies.
2
Review the “QoS policies” chapter in the 5620 SAM User Guide for information
about how to create and distribute QoS policies.
3
Create the following QoS device-specific policies as required:
a. 9500 Radio Interface Queue Map policy; see 10.4 “To configure a 9500 Radio
100
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Workflow to configure 9500 MPR QoS policies
Interface Queue Map policy” (p. 103).
b. 9500 NE QoS policies; see 10.5 “To configure a 9500 NE QoS policy” (p. 103).
Issue 1
3HE-10693-AAAB-TQZZA
101
To configure a 9500 Radio Interface Queue Map policy
5620 SAM
9500 MPR QoS policies procedures
10.4
10.4.1
To configure a 9500 Radio Interface Queue Map policy
General information
When configuring a 9500 Radio Interface Queue Map policy, the following QoS variants
are supported: ODU, MPT-HL, MPT-HC/MPT-MC.
10.4.2
Steps
1
Choose Policies→QoS→9500 MPR QoS→ 9500 Radio Interface Queue Map from
the 5620 SAM main menu. The 9500 Radio Interface Map Policies form opens.
2
Perform one of the following:
a. Configure the Policy scope parameter to Global. Go to Step 3.
b. Configure the Policy scope parameter to Local.
If required:
1. Click Select to configure the Local Node IP Address parameter. The Select a
Network Element form opens.
2. Choose a device and click OK. The 9500 Radio Interface Map Policies form
reappears.
3
Click Create. The 9500 Radio Interface Queue Map, Global Policy (Create) form
opens.
4
Configure the parameters as required.
5
Click on the Radio Interface Queue Map tab and click Create. The Radio Interface
Queue Map, 9500 Radio Interface Queue Map Global Policy (Create) form opens.
6
Configure the parameters as required and click OK. The 9500 Radio Interface
Queue Map, Global Policy (Create) form reappears.
Note: You cannot configure the queue size parameters when the Reset all
102
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To configure a 9500 NE QoS policy
Queues parameter is selected.
7
Save your changes and close the form. The 9500 Radio Interface Map Policies form
reappears.
8
Click Search to display the created policy. To distribute the 9500 Radio Interface
Map policy, see the “Policies overview” chapter in the 5620 SAM User Guide.
END OF STEPS
10.5
10.5.1
To configure a 9500 NE QoS policy
Steps
1
Choose Policies→QoS→9500 MPR QoS→9500 NE QoS from the 5620 SAM main
menu. The 9500 NE QoS Policies form opens.
2
Perform one of the following:
a. Configure the Policy scope parameter to Global. Go to Step 3.
b. Configure the Policy scope parameter to Local.
If required:
1. Click Select to configure the Local Node IP Address parameter. The Select a
Network Element form opens.
2. Choose a device and click OK. The 9500 NE QoS Policies form reappears.
3
Click Create. The 9500 NE QOS, Global Policy (Create) form opens.
4
Configure the parameters as required.
The QoS Classification parameter default setting is Disabled. If you configure the
QoS Classification parameter to 802.1p, the Dot1p tab appears. If you configure the
QoS Classification parameter to DiffServ, the DSCP tab appears.
Issue 1
3HE-10693-AAAB-TQZZA
103
To configure a 9500 NE QoS policy
5620 SAM
5
Click on the Queue Map Policy tab, click Select to choose a 9500 Radio Interface
Queue Map Policy, and click OK. The 9500 NE QoS, Global Policy (Create) form
reappears.
6
Click Apply. The 9500 NE QoS Global Policy (Edit) form opens.
7
Click on the Global Queue Setting tab, choose a Queue number and click
Properties. The RadioQ, Global Policy (Edit) form opens.
8
Configure the parameters as required.
9
Save your changes and close the form. The 9500 NE QoS Policies form reappears.
10
Click Search to display the created policy. To distribute the 9500 NE QoS policy, see
the “Policies overview” chapter in the 5620 SAM User Guide.
END OF STEPS
104
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR service management and service tunnels
11 9500 MPR service management and service
tunnels
11.1
11.1.1
Overview
Purpose
The chapter provides information about 9500 MPR-specific service provisioning
considerations, supported service types, and how to configure service tunnels.
11.1.2
Contents
11.1
Issue 1
Overview
105
9500 MPR service management overview
106
11.2
106
Overview
9500 MPR service tunnel overview
115
11.3
115
Overview
Configuring service tunnels on a 9500 MPR
122
11.4
Overview
122
11.5
To create an Ethernet Radio ring element on a 9500 MPR
122
Workflow to configure a composite service
127
11.6
127
Overview
3HE-10693-AAAB-TQZZA
105
Overview
5620 SAM
9500 MPR service management overview
11.2
11.2.1
Overview
General information
The 5620 SAM supports the configuration of VLANs, VLLs, and composite services on
9500 MPR devices.
A 9500 MPR service with a VLAN path is created by configuring sites and access
interfaces. The 5620 SAM creates cross-connects between the physical ports on all
9500 MPRs along the VLAN path. These paths with cross-connects are called VLAN
path instances. VLAN path instances are specific to a service, and each VLAN service
has its own underlying VLAN path instance. A VLAN path can have multiple VLAN path
instances. The VLAN path instance and all of the cross-connects on the service can be
viewed along with other service properties.
All 9500 MPR services use the default customer and are identified by a VLAN ID
assigned at each inflow interface and a service ID. The service ID and VLAN ID have
different values. The VLAN ID can be automatically assigned by the 5620 SAM or
assigned by the user. When the 5620 SAM assigns the VLAN ID, the ID is based on the
VLAN group that the endpoint 9500 MPR belongs to.
11.2.2
Supported service types
You can configure the following service type on 9500 MPR devices:
• P2P or P2MP (dot1q) VLAN services; see 12.6 “To create a 9500 MPR (dot1q) VLAN
service” (p. 138)
• P2P or P2MP (dot1ad) VLAN services; see 12.7 “To create a 9500 MPR (dot1ad)
VLAN service” (p. 141)
• VLL services and VLL Cpipe (ANSI and ETSI) services; see Chapter 13, “9500 MPR
VLL service management”
• Composite services; see the “Composite service management” chapter in the 5620
SAM User Guide
The following table summarizes the hop-based services the 9500 MPR supports.
Table 3 Summary of 9500 MPR hop-based services support
Profile
type
Node profile
type
VLAN path
type
VLAN path
creation type
Extension
of VLAN
path
Terminates on
Radio
NEtO
service
interworking
Service
Discovery
Hop-based services related to Radio ports
106
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Overview
Table 3 Summary of 9500 MPR hop-based services support
(continued)
Profile
type
Node profile
type
VLAN path
type
VLAN path
creation type
Extension
of VLAN
path
Terminates on
Radio
NEtO
service
interworking
Service
Discovery
Cpipe
TDM2TDM
P2P
(hopbased)
Manual
No
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
P2P
(hopbased)
Manual
No
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
P2MP
(hopbased)
Auto (point
to multipoint)
Yes
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
P2P
(hopbased)
Manual
No
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
P2P
(hopbased)
Manual
No
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
P2MP
(hopbased)
Auto (point
to multipoint)
Yes
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
TDM2ETH
TDM2TDMoETH
Auto
P2P
SDH2SDH
VLAN
Dot1Q
Dot1AD
VLAN
Dot1Q
Dot1AD
Auto
P2P
Hop-based services related to L1 LAGS
Cpipe
TDM2TDM
TDM2ETH
TDM2TDMoETH
VLAN
Dot1Q
Dot1AD
VLAN
Dot1Q
Dot1AD
Auto
P2P
Auto
P2P
Hop-based services related to L2 LAGs
Issue 1
3HE-10693-AAAB-TQZZA
107
Overview
5620 SAM
Table 3 Summary of 9500 MPR hop-based services support
(continued)
Profile
type
Node profile
type
VLAN path
type
VLAN path
creation type
Extension
of VLAN
path
Terminates on
Radio
NEtO
service
interworking
Service
Discovery
Cpipe
TDM2TDM
P2P
(hopbased)
Manual
No
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
P2P
(hopbased)
Manual
No
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
P2MP
(hopbased)
Auto (point
to multipoint)
Yes
No
Limited
Discover
MPR 9500
Services
button from
10.0R5 or
later
No
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
No
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
Yes
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
TDM2ETH
TDM2TDMoETH
Auto
P2P
SDH2SDH
(L2 on MPT
HC)
VLAN
Dot1Q
Dot1AD
VLAN
Dot1Q
Dot1AD
Auto
P2P
Hop-based services related to Ethernet LAGs
Cpipe
VLAN
TDM2ETH
P2P
TDM2TDMoETH (hopbased)
Manual
Dot1Q
P2P
(hopbased)
Manual
P2MP
(hopbased)
Auto (point
to multipoint)
Dot1AD
VLAN
Dot1Q
Dot1AD
Auto
P2P
Auto
P2P
Hop-based services related to Ethernet links
108
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Overview
Table 3 Summary of 9500 MPR hop-based services support
Profile
type
Node profile
type
Cpipe
TDM2ETH
VLAN
VLAN path
creation type
Extension
of VLAN
path
Terminates on
Radio
NEtO
service
interworking
Service
Discovery
P2P
TDM2TDMoETH (hopbased)
Manual
No
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
Dot1Q
P2P
(hopbased)
Manual
No
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
P2MP
(hopbased)
Auto (point
to multipoint)
Yes
No
Limited
Discover
MPR 9500
Services
button from
10.0 R5 or
later
Dot1AD
VLAN
Dot1Q
Dot1AD
11.2.3
VLAN path
type
(continued)
Auto
P2P
Auto
P2P
Service-in-service automatic discovery
The 5620 SAM supports automatic discovery for service-in-service associations created
with the 9500 MPR. Service-in-service refers to a transport service that carries services
for network routers. Automatic discovery allows the 5620 SAM to automatically associate
a transport service with a service tunnel when a physical link is created between the
9500 MPR and a non-MPR NE. Service faults generated on either of the associated
services become cross-correlated in the 5620 SAM.
Note: Service-in-service automatic discovery will not overwrite a service that is already
associated with a service tunnel. Users can, however, manually overwrite an automatic
association with another service. Only one service can be associated with a service
tunnel. See the “Service tunnels” chapter in the 5620 SAM User Guide for more
information about associating a service to a service tunnel.
Note: If the physical link between the 9500 MPR and the network router is removed, the
5620 SAM automatically disassociates the service from the service tunnel.
In-service protected Radio links are represented as green links on the Physical topology
map; standby Radio links are shown as blue links. The status of a 9500 MPR service,
spanning over any protected link, does not depend on the status of the link. The status of
the service depends on the Radio Direction Operative Status. See the following table for
more information about the service status.
Issue 1
3HE-10693-AAAB-TQZZA
109
Overview
5620 SAM
Table 4 9500 MPR service status
Protection Type
Main switching
criteria /
command
Spare switching
criteria /
command
Main status
Spare status
Radio Direction
Operative
Status1
EPS
Auto (Equipment
Failure)
None
Standby
Active
Up
None
Auto (Equipment
Failure)
Active
Standby
Up
Auto (Equipment
Failure)
Auto (Equipment
Failure)
Active/Standby
Standby/Active
Down
Forced Switch
None
Standby
Active
Up
Forced Switch
Auto (Equipment
Failure)
Standby
Active
Down
None
Lockout
Active
Standby
Up
Auto (Equipment
Failure)
Lockout
Active
Standby
Down
Manual Switch
None
Standby
Active
Up
None
Manual Switch
Active
Standby
Up
Auto (Equipment
Failure)
None
Standby
Active
Up
None
Auto (Equipment
Failure)
Active
Standby
Up
Auto (Equipment
Failure)
Auto (Equipment
Failure)
Active/Standby
Standby/Active
Down
Forced Switch
None
Standby
Active
Up
Forced Switch
Auto (Equipment
Failure)
Standby
Active
Down
None
Lockout
Active
Standby
Up
Auto (Equipment
Failure)
Lockout
Active
Standby
Down
Manual Switch
None
Standby
Active
Up
None
Manual Switch
Active
Standby
Up
TPS
110
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Overview
Table 4 9500 MPR service status
(continued)
Protection Type
Main switching
criteria /
command
Spare switching
criteria /
command
Main status
Spare status
Radio Direction
Operative
Status1
RPS
Auto (Signal
Fail/HBER)
Auto (EW)
Standby
Active
Up
Auto (Signal Fail)
Auto (HBER)
Standby
Active
Errors
Auto (Signal Fail)
Auto (Signal Fail)
Active/Standby
Standby/Active
Down
None
Auto (Signal
Fail/HBER/EW)
Active
Standby
Up
Auto (EW)
Auto (Signal
Fail/HBER)
Active
Standby
Up
Auto (HBER)
Auto (Signal Fail)
Active
Standby
Errors
Auto (EW)
Auto (EW)
Active/Standby
Standby/Active
Up
Auto (HBER)
Auto (HBER)
Active/Standby
Standby/Active
Errors
Forced Switch
None
Standby
Active
Up
Forced Switch
Auto (Signal
Fail/HBER/EW)
Standby
Active
Down
None
Lockout
Active
Standby
Up
Auto (Signal
Fail/HBER/EW)
Lockout
Active
Standby
Down
Manual Switch
None
Standby
Active
Up
None
Manual Switch
Active
Standby
Up
Notes:
1. If the Radio direction operative status is Up, the services are not affected. If the Radio direction operative
status is down, the services are affected. The traffic status is Rx operative Up, if the status is Up for all the
protection types (EPS and RPS). The traffic status is Tx operative Up, if the status is Up for all the protection
types (EPS and TPS).
11.2.4
Supported transport services
The complete transport service action can be performed for:
• hop-based VLAN service
• hop-based Cpipe service
Issue 1
3HE-10693-AAAB-TQZZA
111
Overview
5620 SAM
• ring-based Cpipe service
The complete transport service action is performed when:
• the 5620 SAM fails to establish one or more cross-connections of the intermediate and
terminating nodes, during or after a hop-based VLL and VLAN service configuration
• one or more cross-connects on the intermediate nodes are deleted from NEtO. The
action is performed for hop and ring based VLL Cpipe services. The MAC address
deployments for the missing cross-connects are based on the 5620 SAM algorithm.
The complete transport service action cannot be performed when the topology is
changed.
Complete transport service feature support is limited to only services provisioned from
the 5620 SAM. Nokia does not recommend provisioning services in tandem with the
NEtO. See 13.7 “To fix a failed cross-connection in a 9500 MPR Cpipe or a hop-based
VLAN service” (p. 158) for more information about configuring the complete transport
service function.
11.2.5
9500 MPR-specific service provisioning considerations/limitations
The following table provides notable services provisioning considerations and limitations
for 9500 MPR devices.
Table 5 9500 MPR service provisioning considerations and limitations
Service type
Considerations/limitations
All service types
• When configuring services with the 5620 SAM that are cross-connected,
see the node documentation for configuration information.
• NEtO services support is limited to the scenarios described in the 5620
SAM release description.
• The 5620 SAM does not restrict you from creating a physical link between a
9500 MPR Ethernet port and a GNE (9500 MSS-1c). However, this is not a
valid configuration for creation or discovery of a single site VLL or VLAN
service.
• The MAC address for services involving the TDM2TDMoETH service profile
is automatically calculated and populated based on Unicast or Multicast.
Manual configuration is not supported.
• The administrative state of the VLL and VLAN service is Up during service
configuration.
Configuring services over VLAN groups
• You can only discover VLAN services with the 5620 SAM if the nodes are
part of a VLAN group.
• The creation of 9500 MPR services across different VLAN groups is not
supported.
• VLAN groups are not mandatory for VLL services; if VLL services are not
added to a VLAN group, VLAN space management is not supported.
112
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Overview
Table 5 9500 MPR service provisioning considerations and limitations
(continued)
Service type
Considerations/limitations
Configuring services over VLAN paths
•
•
•
•
Configuring VLAN services
• Use P2P VLAN services to restrict a VLAN service to two sites. Therefore,
adding sites to the P2P VLAN service is restricted.
• Use P2MP VLAN services if need to have a VLAN service with two or more
sites.
• To convert P2P VLAN services to P2MP VLAN services, you must
unmanage the service using the Unmanage MPR 9500 Services button on
the Manage Services form. Reactivate the service by clicking on the
Discover MPR 9500 Services button.
• Alarms are not generated for VLAN services when the node reboots.
• The operational state of VLAN services over rings does not consider the
state of the working or protected ring path; the operational state service is
calculated based on the network and access port state.
• Any new VLAN services discovered by the 5620 SAM will be associated
with a P2MP VLAN path, however, existing VLAN services using P2P
endpoints are untouched.
• The 5620 SAM supports the creation of a VLAN service only when all of the
nodes are in dot1q or dot1ad mode. VLAN services across nodes with
mixed dot1q or dot1ad modes are not supported.
• The 9500 MPR VLAN service displays the Admin State parameter as Up in
the 5620 SAM service topology map even when the requirement of having
minimum of two access interfaces is not met.
Configuring VLL services
• Alarms are not generated for the VLL services when the node reboots.
• Adjacent Ethernet links are not supported for VLL services.
• The 5620 SAM supports the TDM2TDMoETH service profile using the
TDM2TDM service profile for VLL services over Ethernet links.
Configuring complete transport services
• Complete transport service feature support is limited to only services
provisioned from the 5620 SAM. Nokia does not recommend provisioning
services in tandem with the NEtO.
Issue 1
You cannot convert P2P VLAN paths to P2MP VLAN path and vice versa.
Services over VLAN paths are only supported on the MSS-x shelf.
VLAN path creation is limited to one Radio/fiber ring.
If the VLAN paths are associated with a VLL service, two P2P paths for VLL
and P2M paths for a VLAN are discovered.
• For the 9500 MPR MSS-O, only hop-based VLAN paths are supported.
• P2MP VLAN paths are not supported between a MSS-8 shelf and a MSS-O
shelf.
• The discovery of VLAN paths and services by the 5620 SAM is based on
the service components deployed on the nodes.
3HE-10693-AAAB-TQZZA
113
Overview
5620 SAM
Table 5 9500 MPR service provisioning considerations and limitations
(continued)
Service type
Considerations/limitations
Configuring ERPS/Fiber ring and
tail-based services
• You cannot configure the Radio-end of the service using the 5620 SAM.
• You can discover ERPS/Fiber ring and tail-based services using the
Discover MPR 9500 Services button on the Manage Services form for
Release 11.0R3 or later.
• The conversion of ring path to tail-based ring path is not supported.
• If the VLAN group or VLAN path are configured with ERPS ring and tails
using the 5620 SAM, hop-based VLAN and VLL service discovery is
restricted for ERPS with tail nodes.
• Service creation/discovery spanning across two or more rings is not
supported except in the case of fiber microwave daisy chain, where the
creation/discovery of VLAN service is allowed as tail(s)-based services.
• Radio termination is not supported for ring node for VLL/VLAN service
creation/discovery.
• The tail termination can only be one site in the case of VLL (Cpipe service)
for ring and tail-based service.
• Complete transport service action is not supported for ring-based services.
• If a Radio port that is connected to a 9500 MPR is added as access in a
hop-based VLAN service, the 5620 SAM does not list the Radio port as
access upon service discovery. If a Radio port that is connected to 9500
MPRe is added as access in a hop-based VLAN service, the 5620 SAM
lists the Radio port as access upon service discovery.
• Tail termination with LAGs is not supported.
• The 5620 SAM does not validate whether inflow is present on the node or
whether the same TDM channel is used for Cpipe L2 access, which could
cause inconsistencies. The 5620 SAM does not validate unsupported node
cross-connect deployment, which could cause inconsistencies. Cpipe single
L2 access is not supported. A Cpipe service must be created with both L2
access endpoints. Hop-based Cpipe services do not support Radio
termination. However, you can configure or discover a hop-based Cpipe
service, in which one endpoint is an E1 port and the other is a Radio port
connected to an MSS-1c GNE or MPRe.
114
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Overview
9500 MPR service tunnel overview
11.3
11.3.1
Overview
General information
A service tunnel is an entity used to unidirectionally direct traffic from one device to
another device. The service tunnel is provisioned to use a specific encapsulation
method, such as GRE or MPLS, and the services are then mapped to the service tunnel.
The 9500 MPR devices can use the following service tunnel types:
• Ethernet Radio ring (G.8032): Discovery adds the Ethernet Radio ring that the
Ethernet Element is a member of.
• Mobile backhaul (applicable to 9500 MPR and 7705 SAR on MPLS-based services
running over a VLAN): Discovery adds MPR VLL services that are associated with an
SDP tunnel or are traversing through network interfaces that are being used by an
L2/L3 VPN through any static or dynamic LSPs that are bound to SDPs on the service.
See the “Service tunnels” chapter in the 5620 SAM User Guide for the complete list of
supported objects that service tunnels can be configured for.
11.3.2
9500 MPR service tunnel (ERPS) support
You can configure the 9500 MPR using an ERPS topology to create a collection of
Ethernet ring nodes to form a closed physical loop. Between two and sixteen Ethernet
ring nodes are supported per ERPS topology. The 9500 MPR ERPS support includes tail
nodes that connect to ERPS ring nodes. Multiple tail node configurations are supported
by the 5620 SAM.
Table 6, “Summary of 9500 MPR ERPS services support” (p. 116) provides a summary
of the ERPS service types that are supported on the 9500 MPR. See the 11.2.5 “9500
MPR-specific service provisioning considerations/limitations” (p. 112) subsection in this
chapter.
See the “Service tunnels” chapter in the 5620 SAM User Guide for information about
Ethernet (G.8032) rings and the 9500 MPR ERPS tail node support, and the service
types supported. See 11.5 “To create an Ethernet Radio ring element on a 9500 MPR”
(p. 122) for information about how to create an Ethernet Radio ring element on a 9500
MPR.
Issue 1
3HE-10693-AAAB-TQZZA
115
Overview
5620 SAM
Table 6 Summary of 9500 MPR ERPS services support
Profile
type
Node profile
type
VLAN path
type
VLAN path
creation type
Extension
of VLAN
path
Terminates
on Radio
NEtO
service
interworking
Service
Discovery
ERPS services - without tail (Radio Ring type)
Cpipe
VLAN
Ring based
with tail
Manual
No
No
None
TDM2ETH
TDM2TDM
On adding
ring
elements to
ring
Dot1Q
Ring based
Manual
Yes
Yes
None
On adding
ring
elements to
ring
ERPS services - without tail (Fiber Microwave type)
Cpipe
TDM2TDM
Ring based
Manual
No
No
None
On adding
ring
elements to
ring
Ring based
Manual
No
No
None
On adding
ring
elements to
ring
TDM2ETH
TDM2TDMoETH
VLAN
Dot1Q
ERPS services - Ring tail based (Radio Ring type)
Cpipe
TDM2TDM
TDM2ETH
Ring based
with tail
Manual
No
Yes
None
On adding
ring
elements to
ring
Ring based
with tail
multipoint
Manual
Yes
Yes
None
On adding
ring
elements to
ring
TDM2TDMoETH
VLAN
Dot1Q
ERPS services - Ring tail based (L1 LAG as tail type)
Cpipe
TDM2TDM
TDM2ETH
Ring based
with tail
Manual
No
Yes
None
On adding
ring
elements to
ring
Ring based
with tail
multipoint
Manual
Yes
Yes
None
On adding
ring
elements to
ring
TDM2TDMoETH
VLAN
Dot1Q
ERPS services - Ring tail based (Ethernet link as tail type)
116
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Overview
Table 6 Summary of 9500 MPR ERPS services support
(continued)
Profile
type
Node profile
type
VLAN path
type
VLAN path
creation type
Extension
of VLAN
path
Terminates
on Radio
NEtO
service
interworking
Service
Discovery
Cpipe
TDM2ETH
Ring based
with tail
Manual
No
Yes
None
On adding
ring
elements to
ring
VLAN
Dot1Q
Ring based
with tail
multipoint
Manual
Yes
Yes
None
On adding
ring
elements to
ring
ERPS services - Ring tail based (Fiber Microwave as tail type)
Cpipe
TDM2TDM
TDM2ETH
Ring based
with tail
Manual
No
Yes
None
On adding
ring
elements to
ring
Ring based
with tail
multipoint
Manual
Yes
Yes
None
On adding
ring
elements to
ring
TDM2TDMoETH
VLAN
Dot1Q
11.3.3
Ethernet (G.8032) ring support
Ethernet Ring Protection (ERP), as specified in ITU-T G.8032, is a protection
mechanism for Ethernet ring topologies that provides a resilient Ethernet network. ERP
provides sub-50 ms protection and recovery switching for Ethernet traffic in a ring
topology while ensuring that loops are not formed at the Ethernet layer. G.8032v1
supports a single ring topology; G.8032v2 supports multiple rings/ladder topology. For
more information about Ethernet (G.8032) rings, see the ITU website at http://itu.int.
11.3.4
ERP topology support
An ERP topology is a collection of Ethernet ring nodes that forms a closed physical loop.
Between two and sixteen Ethernet ring nodes are supported per ERP topology. One
ERP topology is supported per NE. Up to two ERP instances are supported per ERP
topology. Ethernet ring links connect two adjacent Ethernet ring nodes participating in
the same ERP topology.
Loop avoidance in the ring is achieved by guaranteeing that at anytime, traffic may flow
on all but one of the ring links. This link is called the ring protection link (RPL). One
designated node, the RPL Owner (also referred to as the master node), is responsible to
block traffic over the RPL.
Issue 1
3HE-10693-AAAB-TQZZA
117
Overview
5620 SAM
11.3.5
9500 MPR ERPS tail node support on Ethernet (G.8032) rings
Previous releases of the 5620 SAM had a limitation that all services could only begin and
end on Ethernet (G.8032) rings on the 9500 MPR. The 5620 SAM extends EPS support
to include tail nodes that connect to ERPS ring nodes.
You can configure several tail network configurations (see sample 1 and 2 below) on the
9500 MPR including:
• a tail network of one or more MSS-4 or MSS-8 shelves attached to the ring to create,
for example, a tree or linear chain
• a tail network of one 9500 MPRe attached to the ring to create an 9500 MPRe
extension
• a head-end network of one or more MSS-4 or MSS-8 shelves
Figure 3
9500 MPR ERPS tail node service configuration types (sample 1)
IP/
MPLS
TDM
TDM
ERPS
Ring
Eth
Eth
MPLS
7705 SAR
Ring Tail
TDM
Composite service
23061
Figure 4
9500 MPR ERPS tail node service configuration types (sample 2)
IP/
MPLS
Eth
MPLS
Eth
ERPS
Ring
TDM
7705 SAR
TDM
Integrated
Tail
23069
118
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Overview
11.3.6
9500 MPR ERPS tail node service provisioning
On 9500 MPR MSS-4 and MSS-8 shelves, you can provision any service on a tail node;
for example, TDM-over-Ethernet using a hybrid path. The services can terminate on a
ERPS ring node or on another tail node.
For the service workflow, you must choose the hybrid paths/rings and the service
endpoint delivery node.
For the 9500 MPRe, a single hop is supported by allowing a service to terminate on a
network Radio port. The service terminates on the Radio port as a network attachment
with a remote node is the target. You can add a manual link for the 9500 MPRe on the
5620 SAM map to provide a representation of the 9500 MPRe-to-MSS relationship on
the ring. A one-hop 9500 MPRe tail node can also be used in a more traditional 9500
MPR network.
11.3.7
9500 MPR ERPS fiber-microwave protection
You can configure fiber-microwave protection for services that traverse 9500 MPR NEs,
to protect a fiber link with a microwave link when you create the Ethernet Radio ring
element for a Radio ring, fiber ring, or mixed ring configuration. See 11.5 “To create an
Ethernet Radio ring element on a 9500 MPR” (p. 122).
The fiber link can be a fiber connection between two 9500 MPR NEs or a wireline
network connection between two 9500 MPR NEs, where the 9500 MPR access to that
wireline network uses a fiber connection.
Figure 5
Fiber-microwave protection on the 9500 MPR
Microwave
TDM
Eth
TMN
Fiber
Microwave
TDM
Eth
TMN
Wireline
network
23948
Issue 1
3HE-10693-AAAB-TQZZA
119
Overview
5620 SAM
Figure 6
Fiber-microwave protection - operation
Microwave
Fiber/Primary
Microwave
Fiber/Primary
X
LOS
LOS
Fiber/Primary
23949
When you create a VLAN service over a single point-to-multipoint VLAN path that
traverses multiple ERPS ring and tail nodes, the 5620 SAM verifies the presence of the
second ring element and deploys the VLAN service appropriately on all nodes. No
additional configuration is required to apply the fiber-microwave protection to the service.
See 12.3 “Workflow to create VLAN services on 9500 MPR devices” (p. 131) for the
workflow to create VLAN services on 9500 MPR devices.
120
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Overview
Figure 7
Fiber-microwave protection on tail nodes
NODE
Microwave
Microwave
TAIL_1
TAIL_2
Fiber
Fiber
23950
11.3.8
Supported ERP service types
You can configure the following service types in an ERP (G.8032) topology using the
5620 SAM on 9500 MPR devices:
• VLAN service
• VLL Cpipe service
Issue 1
3HE-10693-AAAB-TQZZA
121
Overview
5620 SAM
Configuring service tunnels on a 9500 MPR
11.4
11.4.1
Overview
Purpose
Use the following procedure to configure service tunnels for 9500 MPR devices. See the
“Service tunnels” chapter in the 5620 SAM User Guide for the generic procedures that
apply to this device type.
11.5
11.5.1
To create an Ethernet Radio ring element on a 9500 MPR
Purpose
You can use this procedure to create an Ethernet Radio ring element for a Radio ring,
fiber ring, or mixed ring on the 9500 MPR. Ethernet Radio ring elements are supported
on the 9500 MPR, Release 3.1 or later devices.
Note:
• The Radio ring operation status is not correctly displayed when an NE that is part of a
ring is not reachable.
• The state cause of Provisioning Mismatch is not displayed for MEG ID/level mismatch
parameter of the Radio ring.
• Ring operation state is not updated correctly when multiple Radio links are down.
• The Ring Down state cause is not displayed for 9500 MPR VLAN Services.
• The Link Down state cause for 9500 MPR VLL and VLAN services is not displayed
when a link in a ring is down.
11.5.2
Steps
Create the ERP topology
1
In the navigation tree Equipment view, right-click on a 9500 MPR and choose
Properties. The 9500 MPR network element form opens.
2
Click on the Radio Ring Component tab and click Create. The Radio Ring
Component (Create) form opens.
122
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To create an Ethernet Radio ring element on a 9500 MPR
3
To configure the Radio Ring Component (Create) form.
Perform the following:
1. Configure the Topology Name parameter.
2. Click Select, choose an East port and click OK.
3. Click Select, choose a West Port and click OK.
4. Save your changes and close the form.
Note: The Type field is updated automatically to Radio or Fiber based on the
selected East Port and West Port.
4
Repeat Step 1 to Step 3 for each 9500 MPR NE that you want to add to your ERSP
topology.
Create the Radio ring representation
5
Choose Manage→Service Tunnels from the 5620 SAM main menu. The Manage
Service Tunnels form opens.
6
Click Create and choose Radio Ring. The Radio Ring [Create] form opens.
7
Configure the parameters as required and click Apply. The Radio Ring, new Object
(Edit) form opens.
Define the elements in the Radio ring
8
Click on the Components tab, right-click on the Ring Elements icon in the navigation
tree and choose one of the following:
a. Create Ethernet Ring Element. The Select Network Elements form opens. Go to
Step 9.
b. Add Existing Element. Go to Step 19.
9
Double-click on a network element. The Ethernet Ring Element (Create) form opens.
Issue 1
3HE-10693-AAAB-TQZZA
123
To create an Ethernet Radio ring element on a 9500 MPR
5620 SAM
10
Configure the parameters as required.
11
Click Select in Radio Ring Topology panel and choose the appropriate ERP topology
created in Step 1 to Step 3. The Ethernet Ring Element (Create) form reappears.
12
Click on the Path Endpoints tab and double-click to select path A endpoint. The
Ethernet Ring Path Endpoint - (Create) form opens.
13
Configure the MEG ID parameter and save the form.
14
Repeat Step 12 and Step 13 to configure path B endpoint.
Note: The MEG ID parameter for path B endpoint must be a different value
than the one used for the path A endpoint.
15
If required, select the CLE/ODNC check box in the OAM Switch Criteria panel.
Note: If a port with the 802.3ah EFM OAM remote loopback is enabled is
selected as the endpoint of the ring instance, the OAM Switch criteria panel is
displayed.
If the ring instance is in idle state, the 802.3ah EFM OAM remote loopback
enabled, and CLE/ODNC is selected, the ring instance changes to protected
state.
If the CLE/ODNC parameter is selected for one ring instance, it is applicable to
other ring instances also for that topology.
16
Save your changes and close the form.
Configure a ring protection link for the Radio ring
17
As required, configure a ring protection link for the Radio ring.
Perform the following:
1. Select a site located under Ring Elements icon on the Radio Ring (Edit) form and
choose Properties. The Ethernet Ring Element (Edit) form opens.
124
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To create an Ethernet Radio ring element on a 9500 MPR
2. Set the Ring Protection Link Type parameter to Owner.
3. Click on the Path Endpoints tab and double-click on the endpoint that you want to
delegate as the ring protection link. The Ethernet Ring Path Endpoint - Element Node form opens.
4. Set the Path Endpoint Type parameter to the Ring Protection Link End.
5. Save your changes and close the form.
Add other ring elements as required to the Radio ring
18
Repeat Step 8 to Step 16 to create additional new ring element to add to the Radio
ring.
19
As required, add existing ring elements to the Radio ring.
Perform the following:
1. Right-click on the Ring Elements icon on the Radio Ring (Edit) form and choose
Add Existing Element. The Select Elements form opens.
2. Click Search, choose a Radio ring element, and click OK. A dialog box opens.
3. Click Yes to confirm.
Turn up all the ring elements
20
As required, turn up the Radio ring elements in your Radio ring.
Perform the following:
1. Select all the sites located under Ring Elements icon on the Radio Ring (Edit)
form and choose Turn Up.
2. Click Yes to proceed.
Add the Radio ring to a VLAN path
21
Perform 12.5 “To create a 9500 MPR VLAN path” (p. 135) to create a VLAN path.
Choose Ring Based as the VLAN path type to add the Radio ring to the VLAN.
Note: When you add the Radio ring to a VLAN path, you can optionally extend
ERPS (G.8032) support to include tail nodes that connect to the ERPS ring
nodes.
Issue 1
3HE-10693-AAAB-TQZZA
125
To create an Ethernet Radio ring element on a 9500 MPR
5620 SAM
Create a service on the ERPS topology
22
Perform one of the following to create a service for the 9500 MPR:
a. Perform 12.6 “To create a 9500 MPR (dot1q) VLAN service” (p. 138) to create a
9500 MPR (dot1q) VLAN service.
b. Perform 13.4 “To create a VLL Cpipe service on a 9500 MPR” (p. 154) to create a
VLL Cpipe service.
Note:
• For VLL services, terminating sites must be manually added to the
service. For VLAN services, the sites are auto–populated.
• When you create a VLL or VLAN service for the 9500 MPR, select the
Ring Based path type.
• The 5620 SAM allows you to discover fiber Ethernet rings created by the
NEtO.
END OF STEPS
126
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Overview
Workflow to configure a composite service
11.6
11.6.1
Overview
General information
The following workflow describes the sequence of high-level tasks required to configure
a composite service with a VLAN service on a 9500 MPR, and VPLS on a 7210 SAS or
7750 SR.
Note: To create a VLAN service on a 9500 MPR, configure the ports which are
connected to the 7210 SAS or the 7750 SR as a SAP in access mode, otherwise these
ports cannot be used in SCP. If all ring elements in a ring are not 9500 MPR, service
discovery for VLAN services is not supported. On the physical topology map, the color
yellow indicates a composite service in which SCP port is RPL blocked on 7210 SAS or
7750 SR.
If the 7750 SR is configured as the RPL owner in the ERP service, the corresponding
RPL link is down.
If one of the access interface links on the 9500 MPR VLAN service is down, the status of
the VLAN service is displayed as down in the service topology map, even though there is
an alternate path.
11.6.2
Process
1
Configure an Ethernet Radio ring on a 9500 MPR. See 11.5 “To create an Ethernet
Radio ring element on a 9500 MPR” (p. 122).
2
Configure Ethernet CFM MD, MEG, NE MEG, and MEP. See “To configure an
Ethernet CFM MD policy and subordinate objects” in the 5620 SAM User Guide.
3
Configure an Ethernet (G.8032) ring on the 7210 SAS or the 7750 SR. See “To
create an Ethernet (G.8032) ring” in the 5620 SAM User Guide.
4
Configure a VPLS on 7210 SAS or 7750 SR. See “To create a VPLS” in the in the
5620 SAM User Guide.
5
Configure a VLAN service on a 9500 MPR. See 12.6 “To create a 9500 MPR (dot1q)
VLAN service” (p. 138).
Issue 1
3HE-10693-AAAB-TQZZA
127
Overview
5620 SAM
6
Configure a composite service between the services created in Stage 4 and Stage 5.
See the “Composite service management procedures” in the 5620 SAM User Guide.
128
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR VLAN service management
12 9500 MPR VLAN service management
12.1
12.1.1
Overview
Purpose
The chapter provides information about the supported VLAN services types for 9500
MPR devices, and the associate VLAN groups and paths that are required to provision
the service.
12.1.2
Contents
12.1
Issue 1
Overview
129
9500 MPR VLAN service management
130
12.2
Overview
130
12.3
Workflow to create VLAN services on 9500 MPR devices
131
9500 MPR VLAN service management procedures
134
12.4
To create a VLAN group
134
12.5
To create a 9500 MPR VLAN path
135
12.6
To create a 9500 MPR (dot1q) VLAN service
138
12.7
To create a 9500 MPR (dot1ad) VLAN service
141
12.8
To apply a CoS rate limiter per VLAN on a 9500 MPR
146
12.9
To discover 9500 MPR services
147
12.10 To delete a VLAN group or group member
148
12.11 To delete a 9500 MPR VLAN path
149
3HE-10693-AAAB-TQZZA
129
Overview
5620 SAM
9500 MPR VLAN service management
12.2
12.2.1
Overview
General information
VLAN services provide the segmentation services traditionally provided by routers in
LAN configurations. VLANs address issues such as scalability, security, and network
management. Routers in VLAN topologies provide broadcast filtering, security, address
summarization, and traffic flow management.
See Chapter 11, “9500 MPR service management and service tunnels” for service
creation information for 9500 MPR devices.
See the “VLAN service management” chapter in the 5620 SAM User Guide for more
information about VLAN service creation.
12.2.2
Supported VLAN services types for 9500 MPR devices
The 5620 SAM supports the creation of the following VLAN service types for 9500 MPR
devices:
• 9500 MPR (dot1ad) VLAN
• 9500 MPR P2P (dot1q) VLAN
• 9500 MPR P2MP (dot1q) VLAN
12.2.3
VLAN groups and paths
The 5620 SAM supports the configuration and provisioning of VLAN groups and paths
that are used by 9500 MPR devices to configure VLAN and VLL services.
9500 MPR VLAN groups
You can use VLAN groups to:
• logically group 9500 MPR devices to represent a typical network topology. A 9500
MPR device cannot belong to more than one VLAN group.
• manage the VLAN IDs that are assigned to 9500 MPR VLAN group members
Note: When you create a 9500 MPR service, it can only be configured between 9500
MPRs that belong to the same VLAN group.
See 12.4 “To create a VLAN group” (p. 134) for more information about creating VLAN
groups.
130
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Workflow to create VLAN services on 9500 MPR devices
9500 MPR VLAN paths
A VLAN path is a bidirectional service provision path that is used to support alarm
correlation and turn up Radio backhaul services on 9500 MPR devices. VLAN paths use
a tree topology. The paths can span NEs that are connected by both Radio links and
physical links.
You can configure a VLAN path as follows:
• Ring based—An ERPS topology is a collection of Ethernet ring nodes that form a
closed physical loop. Each Ethernet ring node is connected to two adjacent Ethernet
ring nodes via a duplex communications facility. An Ethernet ring can contain from 2 to
16 Ethernet ring nodes.
• Hop based—Users specify the number of hops from a source 9500 MPR to a
destination 9500 MPR. Each hop in the path is a 9500 MPR that belongs to the same
VLAN group.
The following hop-based VLAN path variants are supported.
— Auto—A user defines the head end of the VLAN path, the hops the VLAN path
takes, and optionally, the bandwidth requirements, and whether the shortest path
should be used. The 5620 SAM determines the appropriate available route for the
VLAN path.
— Manual—A user defines the source 9500 MPR, the hops and links the VLAN path
takes, and optionally, the bandwidth requirements.
— Point 2 Point—A user defines the source and destination 9500 MPR, the number of
allowed hops and, optionally, the bandwidth requirements, and whether the
shortest path should be used.
See 12.5 “To create a 9500 MPR VLAN path” (p. 135) for more information about
creating VLAN paths.
12.3
12.3.1
Workflow to create VLAN services on 9500 MPR devices
General information
Configure VLAN services for subscribers connected to 9500 MPR devices; see the
“VLAN service management” chapter in the 5620 SAM User Guide for the generic
procedures that apply to this device type. Also, configure the following device-specific
VLAN service types and functions.
12.3.2
Process
1
Remove any inconsistencies created due to MIB population failures that can occur
during service creation on a 9500 MPR NE; see 5.5 “To resolve 9500 MPR MIB
inconsistencies” (p. 54).
Issue 1
3HE-10693-AAAB-TQZZA
131
Workflow to create VLAN services on 9500 MPR devices
5620 SAM
2
Create VLAN groups and add members to each group; see 12.4 “To create a VLAN
group” (p. 134).
3
Create the VLAN paths that are required between the 9500 MPR group members.
The VLAN path can be hop based or ring based. See 12.5 “To create a 9500 MPR
VLAN path” (p. 135).
4
Create one of the following VLAN service types:
a. 9500 MPR (dot1q) VLAN services; see 12.6 “To create a 9500 MPR (dot1q) VLAN
service” (p. 138).
b. 9500 MPR (dot1ad) VLAN services; see 12.7 “To create a 9500 MPR (dot1ad)
VLAN service” (p. 141).
5
Configure the VLAN endpoints for traffic storm control, VLAN rate limiting, or dot1q
VLAN rate limiting if you need to monitor the input bandwidth; see 8.4 “To configure
9500 MPR Ethernet ports” (p. 83).
6
Associate access interfaces (the physical ports to which end users connect, similar
to SAPs) with the VLAN services. Use the L2 Interfaces tab on the VLAN Properties
form to associate VLAN services with the ports used by end users. See the “VLAN
service management” chapter in the 5620 SAM User Guide.
7
Create a CoS rate limiter for 9500 MPR VLANs, if required; see 12.8 “To apply a
CoS rate limiter per VLAN on a 9500 MPR ” (p. 146).
8
Discover 9500 MPR VLAN services; see 12.9 “To discover 9500 MPR services”
(p. 147).
9
Perform the following, as required:
a. View the VLAN service operational status or view the service topology map
associated with a VLAN service; see the 5620 SAM User Guide.
b. Delete a VLAN group or group member; see 12.10 “To delete a VLAN group or
group member” (p. 148).
132
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Workflow to create VLAN services on 9500 MPR devices
c. Delete a 9500 MPR VLAN path; see 12.11 “To delete a 9500 MPR VLAN path”
(p. 149).
d. Modify or delete a VLAN service; see the 5620 SAM User Guide.
Issue 1
3HE-10693-AAAB-TQZZA
133
To create a VLAN group
5620 SAM
9500 MPR VLAN service management procedures
12.4
12.4.1
To create a VLAN group
Steps
1
Choose Manage→VLAN→VLAN Groups from the 5620 SAM main menu. The
Manage VLAN Groups form opens.
2
Click Create. The VLAN Group (Create) form opens.
3
Configure the parameters as required and click Apply.
You can configure the VLAN Space Management by SAM parameter when the Node
Type parameter is set to 9500.
4
Click on the Group Members tab and click Create. The Select Network Elements
form opens.
5
Choose one or more network elements and save the form. The selected NEs are
listed in the VLAN Group (Edit) form.
6
Perform this step if you need to apply a span of control to the VLAN group other than
the default group span. Otherwise, go to Step 7.
1. Click on the Spans tab and click Add. The Select Span(s) - Vlan Group form
opens with a list of available spans.
2. Choose one or more spans of control to apply to the VLAN group and click OK.
3. Save your changes and close the form. The VLAN Group (Create) form
reappears.
7
Save your changes and close the form.
END OF STEPS
134
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To create a 9500 MPR VLAN path
12.5
To create a 9500 MPR VLAN path
Note: When you create an Auto or P2P variant of a hop-based VLAN path, all 9500 MPR
NEs that traverse the VLAN path must be part of the same VLAN group. For manually
created VLAN paths, a VLAN group is not required. See 12.4 “To create a VLAN group”
(p. 134) for information about creating VLAN groups.
You can also use this procedure to provision a VLAN path for a tail node.
12.5.1
Steps
1
Choose Manage→VLAN→Paths from the 5620 SAM main menu. The Manage
VLAN Paths form opens.
2
Click Create. The Create VLAN Path step form opens.
3
Configure the Path Type parameter as required and click Next. The Identification
step appears.
4
Configure the parameters as required and click Next.
Note: When creating a hop-based VLAN path that traverses a 9500 MSS-O,
you must select Auto for the Creation Type parameter.
For ring-based VLAN paths, the Select Ring step appears; go to Step 5. To create a
ring-based VLAN path, you need a Radio ring element; see 11.5 “To create an
Ethernet Radio ring element on a 9500 MPR” (p. 122).
For hop-based VLAN paths, the Specify Vlan Path Constraints step appears; go to
Step 12.
5
Click Select and choose a Radio ring on the Select Ring - VLAN Path form and click
OK. The Create VLAN Path step form reappears.
6
Configure the Has Tail and Is Point to Multipoint parameters if the tail node needs to
be attached to the ring element; otherwise, go to Step 29.
Note: Configure the Has Tail parameter if you need standard VLAN paths for
the tail node.
Issue 1
3HE-10693-AAAB-TQZZA
135
To create a 9500 MPR VLAN path
5620 SAM
Configure the Is Point to Multipoint parameter if you need dot1q VLAN paths
for the tail node.
7
Click Next. The Define the Provisioned Path step appears.
8
Click Insert Hop. The Hop for New Vlan Path [Create] form opens.
9
Click Select to add a network element to the VLAN path and click OK. The Define
the Provisioned Path step reappears.
10
Click Select to add a Radio link to the VLAN path and click OK. The Define the
Provisioned Path step reappears.
11
Perform one of the following:
a. Repeat Step 8 to Step 10 add another tail node to the ring element.
b. Click Finish to complete the provisioning of the VLAN path on a tail node. Go to
Step 29.
12
Configure the parameters in the Specify Vlan Path Constraints step as required and
click Next.
If you set the Creation Type parameter to Auto, the Specify if the Vlan Path is Point
to Multipoint step appears; go to Step 13.
If you set the Creation Type parameter to Manual or Point 2 Point, the Defined
Source Site step appears; go to Step 20.
13
Configure the Is Point to Multipoint parameter as required and click Next. The Define
Head step appears.
Note: When creating a hop-based VLAN path that traverses a 9500 MSS-O,
you must check off the Is Point to Multipoint parameter.
14
Click Select, choose a 9500 MPR and click OK. The IP address of the selected 9500
MPR appears in the Head End parameter.
136
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To create a 9500 MPR VLAN path
15
Click Next. The Possible Vlan Paths step appears.
16
Click Insert Hop to insert a VLAN path hop. The Hop for New VLAN Path (Create)
form opens.
17
Click Select to choose a 9500 MPR site and click OK.
18
Click Select, choose a link and click OK.
19
If you need to add another hop, click Apply and repeat Step 16 to Step 18.
Otherwise go to Step 29.
20
Configure the Minimum Bandwidth (kbps) parameter and click Next.
For Manual VLAN paths, the Defined the Provisioned Path step appears. Go to Step
16.
For Point 2 Point VLAN paths, the Defined Destination Site step appears. Go to Step
21.
21
Perform one of the following:
a. Enter the IP address of the starting VLAN path endpoint in the Starting Network
Element parameter.
b. Click on the Select button. The Select a Network Element - Define Source Site
form opens. Choose a 9500 MPR from the list and click on the OK button. The
Select a Network Element - Define Source Site form closes and the IP address of
the selected 9500 MPR appears in the Starting Network Element parameter.
22
Click on the Next button. The Define Destination Site step appears.
23
Click on the Select button. The Select a Network Element - Define Destination Site
form opens. Choose a 9500 MPR from the list and click on the OK button. The
Select a Network Element - Define Destination Site form closes and the IP address
of the selected 9500 MPR appears in the Destination Network Element parameter.
Issue 1
3HE-10693-AAAB-TQZZA
137
To create a 9500 MPR (dot1q) VLAN service
5620 SAM
24
Click on the Next button. The Possible Vlan Paths step appears.
25
Click on the Insert Hop button to insert a VLAN path hop. The Hop for New VLAN
Path (Create) form opens.
26
Click on the Select Network Element button. The Select a Network Element - New
VLAN Path form opens.
27
Choose a 9500 MPR from the list and click on the OK button. The New VLAN Path
form closes and the IP address of the NE appears in the Network Element
parameter.
28
If you need to add another hop, click on the Apply button and repeat Step 26
and Step 27. Click on the OK button after you add all hops.
29
Save your changes and close all open forms.
END OF STEPS
12.6
12.6.1
To create a 9500 MPR (dot1q) VLAN service
Prerequisites
Perform the following procedures before creating a 9500 MPR (dot1q) VLAN service, as
required:
• Create a customer profile; see the “Customer configuration and service management”
chapter in the 5620 SAM User Guide.
• Create a VLAN group; see 12.4 “To create a VLAN group” (p. 134).
• Create a VLAN path if you need to assign a specific VLAN path to the 9500 MPR
(dot1q) VLAN service; see 12.5 “To create a 9500 MPR VLAN path” (p. 135).
• Configure the VLAN endpoints for traffic storm control, VLAN rate limiting, or dot1q
VLAN rate limiting if you need to monitor the input bandwidth; see 8.4 “To configure
9500 MPR Ethernet ports” (p. 83).
138
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To create a 9500 MPR (dot1q) VLAN service
12.6.2
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR and choose
Properties. The 9500 MPR network element form opens.
2
Click on the System Settings tab, set the Bridge Type parameter to 802.1AD and
click OK.
3
Choose Create→Service→VLAN from the 5620 SAM main menu. The VLAN
Service (Create) form opens.
4
Click Select in the Customer panel, choose a customer for the 9500 MPR (dot1aq)
VLAN service and click OK. The VLAN (Create) Service form reappears.
5
Configure the parameters on the General tab as required.
The Service ID parameter is configurable when the Auto-Assign ID parameter is
disabled.
The SVC Mgr Service ID parameter is configurable when the Auto-Assign ID
parameter is disabled.
The Current OLC State and Revert OLC State parameters are configurable when
you click Apply on the VLAN Service (Create) form.
6
Click on the VLAN tab and set the Application parameter to 9500 VLAN.
7
Click Select in the Group panel, choose a VLAN group and click OK. The VLAN
(Create) form reappears.
8
Configure the parameters in the 9500 VLAN panel as required.
The Point to Point VLAN parameter is configurable when the Path Type parameter is
set to Hop Based.
To create a 9500 MPR VLAN service on an ERPS tail node, set the Path Type
parameter to Ring Based.
Issue 1
3HE-10693-AAAB-TQZZA
139
To create a 9500 MPR (dot1q) VLAN service
5620 SAM
The service created using point-to-point VLAN service is discovered as a standard
VLAN service without the point-to-point option.
You cannot reconfigure the point-to-point VLAN parameter after you choose a VLAN
path. To change the parameter, you need to delete the selected VLAN path.
9
Click Select in the VLAN Path panel, choose a VLAN Path and click OK. The VLAN
(Create) form reappears. The service is created and VLAN service appears in the
navigation tree.
Note: If you choose the Ring Based option for the Path Type parameter, only
P2MP paths are listed. You cannot use a P2P path with a tail VLAN Path on a
9500 MPR Ring Based VLAN.
Note: The VLAN path may consist of a P2P, P2MP, or Has Tail VLAN path,
consecutive physical links, non-consecutive physical links, or Radio links
spanning NEs.
10
In the navigation tree, right-click on the VLAN Service and choose Create VLAN
Site. The Select Network Elements - VLAN Service form opens.
Note: The service navigation tree is auto-populated with sites that correspond
to the hops in the specified VLAN Path.
11
Choose a site and click OK. The Site (Create) form opens with the site information
displayed.
12
Configure the parameters as required.
13
Save your changes and close the forms.
Note: During the creation of VLAN services, intermediate sites are
automatically added to the service topology view.
14
In the navigation tree, click on the site that you need to associate the new access
interface and expand the entries for the site.
140
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To create a 9500 MPR (dot1ad) VLAN service
15
Right-click on L2 Access Interfaces and choose Create VLAN Access Interface. The
VLAN Access Interface (Create) form opens.
16
Configure the parameters as required.
17
Click on the Port tab, click Select to choose a port for the VLAN access interface,
and click OK. The VLAN Access Interface (Create) form reappears.
Note: The form lists Ethernet ports in access or hybrid mode and also Radio
ports. To choose an Ethernet port that is not listed, you must set the Mode
parameter for the port to Access or Hybrid and click on the Search button.
For a hop-based VLAN service, you can add a Radio port as an access
interface. A network port that is used in a VLAN path cannot be added as an
access interface.
For a ring-based VLAN service, you can add a Radio port of a ring or tail node
as an access interface.
18
Click on the VLAN tab and configure the parameters as required.
19
Save your changes and close the form.
END OF STEPS
12.7
12.7.1
To create a 9500 MPR (dot1ad) VLAN service
Prerequisites
Perform the following procedures before you create a 9500 MPR (dot1ad) VLAN service.
• Create a customer profile; see the Customer configuration and service management
chapter in the 5620 SAM User Guide.
• Create a VLAN group; see 12.4 “To create a VLAN group” (p. 134).
• Create a VLAN path if you need to assign a specific VLAN path to the 9500 MPR
(dot1ad) VLAN service; see 12.5 “To create a 9500 MPR VLAN path” (p. 135).
• Configure the VLAN endpoints for traffic storm control, VLAN rate limiting, or dot1ad
VLAN rate limiting if you need to monitor the input bandwidth; see 8.4 “To configure
9500 MPR Ethernet ports” (p. 83).
Issue 1
3HE-10693-AAAB-TQZZA
141
To create a 9500 MPR (dot1ad) VLAN service
12.7.2
5620 SAM
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR and choose
Properties. The 9500 MPR network element form opens.
2
Click on the System Settings tab, set the Bridge Type parameter to 802.1AD and
click OK.
3
In the navigation tree Equipment view, right-click on a 9500 MPR Ethernet port and
choose Properties. The Physical Port (Edit) form opens.
4
Click on the Ethernet tab and configure the parameters in the Provider Bridge
Configurations panel as required.
The Provider Bridge Configuration parameters are available only on Ethernet ports.
When the Provider Bridge Type parameter is set to NNI, the S-VLAN TPID
parameter can be configured.
When the Provider Bridge Type parameter is set to UNI, UNI priority parameter can
be configured.
When the Provider Bridge Type parameter is set to UNI (C-VLAN), the Untag
C-VLAN check box appears. The Untag C-Vlan check box cannot be selected if the
ingress mapping has no entry.
5
Perform the following step if you set the Provider Bridge Type parameter in Step 4 to
UNI (C-Vlan), otherwise, go to Step 6.
1. Click on the Ingress Mapping tab and click Create. The Ingress C-VLAN/S-VLAN
Mapping (Create) form opens.
2. Configure the parameters as required and click OK. The new C-VLAN/S-VLAN
mapping entry appears in the ingress mapping list.
Note: The value for the S Vlan ID parameter is set to 1 and cannot be configured.
Note: Only one of the ingress mapping entries can have the Remove C-Vlan ID
check box selected.
3. Click on the Egress Mapping tab. The C-VLAN/S-VLAN mapping entry appears in
the egress mapping list.
4. Choose the entry and click Properties. The Egress C-VLAN/S-VLAN Mapping
(Edit) form opens.
142
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To create a 9500 MPR (dot1ad) VLAN service
5. Configure the C Vlan ID parameter.
Note: The value for the S Vlan ID parameter is set to 1 and cannot be configured.
6. Save your changes and close the form.
6
Choose Create→Service→VLAN from the 5620 SAM main menu. The VLAN
(Create) Service form opens.
7
Click Select in the Customer panel, choose a customer for the 9500 MPR (dot1ad)
VLAN service and click OK. The VLAN (Create) Service form reappears.
8
Configure the parameters on the General tab as required.
The Service ID parameter is configurable when the Auto-Assign ID parameter is
disabled.
The SVC Mgr Service ID parameter is configurable when the Auto-Assign ID
parameter is disabled.
9
Click on the VLAN tab and set the Application parameter to 9500 VLAN.
10
Click Select in the Group panel, choose a VLAN group and click OK. The VLAN
(Create) form reappears.
11
Configure the parameters in the 9500 VLAN panel as required.
The Point to Point VLAN parameter is configurable when the Path Type parameter is
set to Hop Based.
Note: The service that is created using point-to-point VLAN service is
discovered as a standard VLAN service without the point-to-point option.
Note: You cannot reconfigure the Point to Point VLAN parameter after you
choose a VLAN path. To change the parameter, you need to delete the
selected VLAN path.
Note: During the creation of VLAN services, intermediate sites are
automatically added to the service topology view.
Issue 1
3HE-10693-AAAB-TQZZA
143
To create a 9500 MPR (dot1ad) VLAN service
5620 SAM
12
Click Select in the VLAN Path panel, choose a VLAN Path and click OK. The VLAN
(Create) form reappears.
Note: The VLAN path may consist of a P2P, P2MP, or Has Tail VLAN path,
consecutive physical links, non-consecutive physical links, or Radio links
spanning NEs.
13
Choose 802.1AD for the Bridge Type parameter and click Apply. The service is
created and VLAN service appears in the navigation tree.
14
In the navigation tree, right-click on VLAN Service and choose Create VLAN Site.
The Select Network Elements - VLAN Service form opens.
Note: The service navigation tree is auto-populated with sites that correspond
to the hops in the specified VLAN path.
15
Choose a site and click OK. The Site (Create) form opens with the site information
displayed.
16
Configure the parameters as required.
17
Save your changes and close the forms.
Note: During the creation of VLAN services, intermediate sites are
automatically added to the service topology view.
18
In the navigation tree, click on the site that you need to associate the new access
interface and expand the entries for the site.
19
Right-click on a L2 Access Interface and choose Create VLAN Access Interface. The
VLAN Access Interface (Create) form opens.
20
Configure the parameters as required.
144
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To create a 9500 MPR (dot1ad) VLAN service
21
Click on the Port tab, click Select to choose a port for the VLAN access interface,
and click OK. The VLAN Access Interface (Create) form reappears.
Note: The form lists Ethernet ports in access or hybrid mode and also Radio
ports. To choose an Ethernet port that is not listed, you must set the Mode
parameter for the port to Access or Hybrid and click on the Search button.
For a hop-based VLAN service, you can add a Radio port as an access
interface. A network port that is used in a VLAN path cannot be added as an
access interface.
For a ring-based VLAN service, you can add a Radio port of a ring or tail node
as an access interface.
22
Click on the VLAN tab and configure the parameters as required.
23
Perform the following step if you set the VLAN Tagging parameter to Untagged and
the Provider Bridge Type parameter to UNI (C-Vlan Based) in Step 22, otherwise, go
to Step 24.
Note: You can configure C-VLAN/S-VLAN mapping also for LAG and ringbased services.
1. Click on the Ingress Mapping tab and click Create. The Ingress C-VLAN/S-VLAN
Mapping (Create) form opens.
2. Configure the parameters as required and click OK. The new C-VLAN/S-VLAN
mapping entry appears in the ingress mapping list.
Note: Select the Remove C-Vlan ID check box for any one of the ingress
mapping entries.
3. Click on the Egress Mapping tab. The C-VLAN/S-VLAN mapping entry appears in
the egress mapping list.
4. Choose the entry and click Properties. The Egress C-VLAN/S-VLAN Mapping
(Edit) form opens.
5. Configure the C Vlan ID parameter.
Note: The value for the S Vlan ID parameter is set to 1 and cannot be configured.
6. Save your changes and close the form. The VLAN - Service Name (Edit) form
reappears with the new interface displayed in the service navigation tree under
Access Interfaces for the specified site.
24
Save your changes and close the form. The provider bridge is configured.
END OF STEPS
Issue 1
3HE-10693-AAAB-TQZZA
145
To apply a CoS rate limiter per VLAN on a 9500 MPR
12.8
12.8.1
5620 SAM
To apply a CoS rate limiter per VLAN on a 9500 MPR
Supported application
A CoS rate limiter per VLAN can be applied to each user Ethernet interface for the
ingress direction. The rate limiter is applied to a tagged Ethernet flow. The combination
of the values of one VLAN ID and one PCP identifies a specific VLAN Ethernet flow.
12.8.2
Steps
1
In the navigation tree Equipment view, right-click on a 9500 MPR Ethernet port and
choose Properties. The Physical Port (Edit) form opens.
2
Click on the CoS Rate Limiter tab and click Create. The CoS Rate Limiter, (New
Instance) (Create) form opens.
3
Click Select in the Vlan Port Binding panel, choose a Port Binding VLAN ID to assign
to the port, and click OK.
4
Configure the remaining parameters on the CoS Rate Limiter (Create) form as
required and click OK.
Note: To change the PCP or Port Binding VLAN ID parameter value once the
form is saved, you must delete the CoS Rate Limiter Instance and create a
new entry. This is a 5620 SAM limitation; you can modify these parameter
values using the 9500 MPR NEtO. This limitation applies to 9500 MPR (chassis
8/4/1) and 9500 MSS-O devices.
5
Save your changes and close the form.
END OF STEPS
146
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To discover 9500 MPR services
12.9
12.9.1
To discover 9500 MPR services
Prerequisites/general info
Services that traverse the 9500 MPR are not discovered automatically during NE
discovery. Perform this procedure after all 9500 MPR NEs are synchronized in the 5620
SAM.
Note: A prerequisite for discovering VLAN services on the 9500 MPR is that the nodes
that are part of the VLAN service must be contained in a VLAN group. If any of the
discovered nodes contain ring instances, they should be added to ring elements before
using the hop or ring-based discovery button.
VLAN groups are not mandatory for VLL services; if VLL services are not added to a
VLAN group, VLAN space management is not supported. If any of the discovered nodes
contain ring instances, they should be added to ring elements before using the hop or
ring-based option on the Discover MPR 9500 Services button.
For a ring-based service, the ring element must be added to the ring. See 12.4 “To
create a VLAN group” (p. 134) for information about creating VLAN groups. See 11.5 “To
create an Ethernet Radio ring element on a 9500 MPR” (p. 122) for information about
creating an Ethernet Radio ring element.
12.9.2
Steps
1
Choose Manage→Service→Services from the 5620 SAM main menu. The Manage
Services form opens.
2
Click Discover MPR 9500 Services and choose either the Hop Based or Ring Based
option. The Discover MPR 9500 Services form opens.
Note: The Ring Based option discovers both VLL and VLAN services
associated with the ring and tail.
3
Choose a network group and click OK. The Manage Services form reappears.
Note: If you created network subgroups and the nodes are split over different
subgroups, you must select all of the subgroups and click on the OK button to
discover all of the services.
4
Apply a filter as required and click Search. The discovered services appear in the
Manage Services form.
Issue 1
3HE-10693-AAAB-TQZZA
147
To delete a VLAN group or group member
5620 SAM
Note: You can optionally exclude a 9500 MPR VLAN from 5620 SAM
management without having to unmanage the entire 9500 MPR device by
clicking on the Unmanage MPR 9500 Services button. Service configurations
are maintained in the 5620 SAM database during this operational state. You
can reactivate the VLAN services using the Discover MPR 9500 Services
button on the Manage Services form.
5
Close the Manage Services form.
END OF STEPS
12.10
12.10.1
To delete a VLAN group or group member
Steps
1
Choose Manage→VLAN→VLAN Groups from the 5620 SAM main menu. The
Manage VLAN Groups form opens.
2
Apply a filter as required and click Search. A list of VLAN groups appears.
3
Choose a VLAN group and click properties. The VLAN Groups (Edit) form opens.
4
Perform this step If the VLAN group contain any members. You must delete all of the
members from a group before you can delete the group. Otherwise, go to Step 5.
Note: A 9500 MPR group member cannot be deleted if it is part of a VLAN
path.
1. Click on the Group Members tab.
2. Choose one or more members of the VLAN group and click Delete. A dialog box
appears.
3. Click OK to delete the group members and close the VLAN Groups (Edit) form.
The Manage VLAN Groups form reappears.
5
Choose the VLAN group that you need to delete and click Delete.
148
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To delete a 9500 MPR VLAN path
6
Save your changes and close the form.
END OF STEPS
12.11
To delete a 9500 MPR VLAN path
Note: You cannot delete a VLAN path if the path is being used by a service.
12.11.1
Steps
1
Choose Manage→VLAN→Paths from the 5620 SAM main menu. The Manage
VLAN Paths form opens.
2
Apply a filter as required and click Search. A list of VLAN paths appears.
Note: If VLAN paths are already in your network, the 9500 MPR NE that the
path traverses is auto-discovered by the 5620 SAM. The paths appear in the
Manage VLAN Paths form with a name with the following syntax: DiscoveredVLANPath-<IP address of the source 9500 MPR>-<IP address of the
destination 9500 MPR.
3
Choose a VLAN path and click Delete. The VLAN path and all of the associated
hops are deleted.
4
Save your changes and close the form.
END OF STEPS
Issue 1
3HE-10693-AAAB-TQZZA
149
To delete a 9500 MPR VLAN path
150
5620 SAM
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
9500 MPR VLL service management
13 9500 MPR VLL service management
13.1
13.1.1
Overview
Purpose
The chapter provides information about the supported VLL services types for 9500 MPR
devices, and the procedures required to discover the service.
13.1.2
Contents
13.1
Issue 1
Overview
151
9500 MPR VLL service management
152
13.2
Overview
152
13.3
Workflow to create VLL services on 9500 MPR devices
152
9500 MPR VLL service management procedures
154
13.4
To create a VLL Cpipe service on a 9500 MPR
154
13.5
To create a single site VLL Cpipe service on 9500 MPR connected to an
MSS1c lightweight GNE
156
13.6
To discover a single-site Cpipe service on 9500 MPR connected to a
9500 MSS-1c lightweight GNE
158
13.7
To fix a failed cross-connection in a 9500 MPR Cpipe or a hop-based
VLAN service
158
13.8
To configure a GNE site on a VLL Cpipe service
159
13.9
To configure a customer profile and associate it with a VLL service
161
3HE-10693-AAAB-TQZZA
151
Overview
5620 SAM
9500 MPR VLL service management
13.2
13.2.1
Overview
Supported VLL services
The 5620 SAM supports the provisioning of VLL Cpipe services on 9500 MPR devices. A
VLL service is an L2 point-to-point service that connects access interfaces. A VLL
service is completely transparent to customer or subscriber data and to control protocols.
Because of this transparency, the device performs no MAC learning in a VLL service.
See the “VLL service management”chapter in the 5620 SAM User Guide for detailed
information about VLL service creation.
13.3
13.3.1
Workflow to create VLL services on 9500 MPR devices
Prerequisites
Configure VLL services for subscribers connected to 9500 MPR devices; see the “VLL
service management” chapter in the 5620 SAM User Guide for the generic procedures
that apply to this device type. Also, configure the following 9500 MPR device-specific
VLL service types and functions:
13.3.2
Process
1
Remove any inconsistencies created due to MIB population failures that can occur
during service creation on a 9500 MPR NE; see 5.5 “To resolve 9500 MPR MIB
inconsistencies” (p. 54).
2
Create VLAN groups and add members to each group; see 12.4 “To create a VLAN
group” (p. 134).
3
Create the VLAN paths that are required between the 9500 MPR group members.
The VLAN path can be hop based or ring based. See 12.5 “To create a 9500 MPR
VLAN path” (p. 135).
4
Create the following VLL service types as required:
152
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
Workflow to create VLL services on 9500 MPR devices
a. 9500 MPR VLL Cpipe services; see 13.4 “To create a VLL Cpipe service on a
9500 MPR” (p. 154).
b. Single site VLL Cpipe service on a 9500 MPR connected to an MSS1c lightweight
GNE; see 13.5 “To create a single site VLL Cpipe service on 9500 MPR
connected to an MSS1c lightweight GNE” (p. 156).
c. Discover a single-site VLL Cpipe service on a 9500 MPR connected to a 9500
MSS-1c lightweight GNE; see 13.6 “To discover a single-site Cpipe service on
9500 MPR connected to a 9500 MSS-1c lightweight GNE” (p. 158).
5
Fix failed cross-connections on a 9500 MPR VLL Cpipe service, as required; see
13.7 “To fix a failed cross-connection in a 9500 MPR Cpipe or a hop-based VLAN
service” (p. 158).
6
Configure a GNE site on a 9500 MPR Cpipe service; see 13.8 “To configure a GNE
site on a VLL Cpipe service” (p. 159).
7
Discover 9500 MPR VLL services; see 12.9 “To discover 9500 MPR services”
(p. 147).
8
Turn up the VLL service as required by configuring the Administrative State
parameter in the Create Services form to Up.
9
Perform the following, as required:
a. View the VLL service operational status or view the service topology map
associated with a VLL service; see the “5620 SAM topology map management”
chapter in the 5620 SAM User Guide.
b. Delete a VLAN group or group member; see 12.10 “To delete a VLAN group or
group member” (p. 148).
c. Delete a 9500 MPR VLAN path; see 12.11 “To delete a 9500 MPR VLAN path”
(p. 149).
d. Modify or delete a VLL service; see the 5620 SAM User Guide.
Issue 1
3HE-10693-AAAB-TQZZA
153
To create a VLL Cpipe service on a 9500 MPR
5620 SAM
9500 MPR VLL service management procedures
13.4
13.4.1
To create a VLL Cpipe service on a 9500 MPR
Steps
1
Choose Create→Service→9500 Cpipe from the 5620 SAM main menu. The Cpipe
Service (Create) form opens.
2
Click Select in the Customer panel and choose a customer to associate with the
Cpipe service and click OK.
3
Configure the parameters on the General tab as required.
The Service ID parameter is configurable when the Auto-Assign ID parameter is
disabled.
The SVC Mgr Service ID parameter is configurable when the Auto-Assign ID
parameter is disabled.
The Current OLC State parameter is configurable when you click Apply.
The VLAN ID parameter is enabled when the Auto-Assign ID parameter is disabled.
Note: To create a 9500 MPR Cpipe service with an ERPS tail node, set the
Path Type parameter to Ring Based.
4
Perform the following step if the Specify VLAN Path parameter was enabled in Stage
3.
1. Click Select in the VLAN Path panel and choose a VLAN path to associate with
the Cpipe service. The Select VLAN Path - 9500 MPR Cpipe Service form opens.
2. Choose a VLAN path and click OK.
Note: If no VLAN path exists, see 12.5 “To create a 9500 MPR VLAN path”
(p. 135).
Note: You cannot create VLL Cpipe services on a 9500 MPR using the 5620
SAM if the associated VLAN path spans across adjacent physical links. The VLL
Cpipe service must have at least one Radio link. If required, contact your Nokia
technical support representative for alternative VLL Cpipe service configuration
options.
154
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To create a VLL Cpipe service on a 9500 MPR
5
Perform the following step if you configured the Service Class parameter to one of
the following options in Stage 3.
a. If you specified the CEM to Eth option, configure the CEM to Eth Details panel
parameters.
b. If you specified the SDH to SDH option. configure the SDH Details panel
parameters.
6
In the 9500 MPR Cpipe Service navigation tree, right-click on the service icon and
choose Create Cpipe Site. The Select Network Element form opens.
For information about adding a GNE site to a VLL service, see 13.8 “To configure a
GNE site on a VLL Cpipe service” (p. 159).
7
Choose a network element from the list and click OK. The 9500 MPR Cpipe Site
(Create) form opens.
8
Configure the parameters as required.
9
Click on the Components tab, right-click on a L2 Access Interface and choose
Create L2 Access Interface. The 9500 MPR L2 Access Interface (Create) form
opens.
10
Configure the required parameters.
11
Click on the Port tab, click Select to choose a terminating port and click OK. The
9500 MPR L2 Access Interface (Create) reappears.
Note: The form lists only ports in access or hybrid mode. To choose a port that
is not listed, you must set the Mode parameter for the port to Access or Hybrid.
12
Perform the following step if the 9500 MPR Cpipe service is for an ERPS tail node. A
Radio or Ethernet termination port is required for the site.
1. Click on the Tail Terminating Port tab.
2. Click Select to choose an ERPS tail terminating port and click OK.
Issue 1
3HE-10693-AAAB-TQZZA
155
To create a single site VLL Cpipe service on 9500 MPR connected to an MSS1c lightweight GNE
5620 SAM
13
Save your changes and close the form. The Cpipe Site (Create) form reappears with
the new interface information displayed in the service navigation tree.
14
If required, repeat Step 6 to Step 13 to create another site for the VLL service,
otherwise, go to Step 15.
15
Save your changes and close the form. You can use the service topology maps to
view the service. See the “5620 SAM topology map management” chapter in the
5620 SAM User Guide for more information.
Note: If service creation fails or generated NE inconsistencies occur, see
5.5 “To resolve 9500 MPR MIB inconsistencies” (p. 54).
END OF STEPS
13.5
13.5.1
To create a single site VLL Cpipe service on 9500 MPR
connected to an MSS1c lightweight GNE
Prerequisites
You must configure a physical link between the 9500 MPR MSS-8, MSS-4, or MSS-1
port and the MSS1c lightweight GNE before performing this procedure. See the
procedure “To create a physical link” in the 5620 SAM User Guide for more information.
13.5.2
Steps
1
Choose Create→Service→9500 Cpipe from the 5620 SAM main menu. The 9500
MPR Cpipe Service (Create) form opens.
2
Click Select in the Customer panel and choose a customer to associate with the
Cpipe service and click OK.
3
Configure the parameters on the General tab as required.
The Service ID parameter is configurable when the Auto-Assign ID parameter is
disabled.
156
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To create a single site VLL Cpipe service on 9500 MPR connected to an MSS1c lightweight GNE
The SVC Mgr Service ID parameter is configurable when the Auto-Assign ID
parameter is disabled.
The Current OLC State parameter is configurable when you click Apply.
The VLAN ID parameter is enabled when the Auto-Assign ID parameter is disabled.
4
Deselect the Specify VLAN Path checkbox.
5
In the 9500 MPR Cpipe Service navigation tree, right-click on the service icon and
choose Create Cpipe Site. The Select Network Element form opens.
6
Choose a network element from the list and click OK. The 9500 MPR Cpipe Site
(Create) form opens.
7
Configure the parameters as required.
8
Click on the Network Port tab and click Select to choose a Radio port. The Select
Network Port form opens.
9
Choose a Radio port that is configured with the physical link to the MSS1c
lightweight GNE and click OK.
10
Click on the Interfaces tab and click Create. The 9500 MPR Cpipe L2 Access
Interface (Create) form opens
11
Configure the parameters as required.
12
Click on the Port tab, click Select to choose a port for the L2 access interface and
click OK.
Issue 1
3HE-10693-AAAB-TQZZA
157
To discover a single-site Cpipe service on 9500 MPR connected to a 9500 MSS-1c lightweight GNE 5620 SAM
13
Save your changes and close the form. The Cpipe Site (Create) form reappears with
the new interface information displayed in the 9500 MPR Cpipe Service navigation
tree.
END OF STEPS
13.6
13.6.1
To discover a single-site Cpipe service on 9500 MPR
connected to a 9500 MSS-1c lightweight GNE
Steps
1
Choose Manage→Service→Services from the 5620 SAM main menu. The Manage
Services form opens.
2
Click Discover MPR 9500 Services and choose Hop Based from the contextual
menu. The Discover MPR 9500 Services form opens.
3
Choose the equipment group containing the 9500 MPR devices and click OK. The
Manage Service form reappears with a list of discovered services.
END OF STEPS
13.7
13.7.1
To fix a failed cross-connection in a 9500 MPR Cpipe or a
hop-based VLAN service
General information
The 5620 SAM may fail to establish one or more cross-connects when you deploy or
create a 9500 MPR Cpipe service or a hop-based VLAN service. If you determine that a
service is down because of a failed cross-connect, you can try to re-establish the crossconnect.
Note: You must clear the deployment error that is associated with the failed crossconnect before you attempt to re-establish the cross-connect.
158
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To configure a GNE site on a VLL Cpipe service
13.7.2
Steps
1
Choose Manage→Service→Services from the 5620 SAM main menu. The Manage
Services form opens.
2
Configure the filter criteria for the required service type and click Search. A list of
services appears.
3
Choose a 9500 MPR Cpipe or hop-based VLAN service and click Properties. The
VLL_type Service (Edit) form opens.
4
Choose Complete Transport Service to re-establish the cross-connections.
5
Verify that the cross-connects are operational. You can use the topology maps to
view the service. See the “5620 SAM topology map management” chapter in the
5620 SAM User Guide for more information.
6
Save your changes and close the form.
END OF STEPS
13.8
13.8.1
To configure a GNE site on a VLL Cpipe service
Steps
1
Choose Manage→Service→Services from the 5620 SAM main menu. The Manage
Services form opens.
2
Configure the filter criteria for the required service type and click Search. A list of
services appears.
3
Choose a Cpipe service and click Properties. The VLL_type Service (Edit) form
opens.
Issue 1
3HE-10693-AAAB-TQZZA
159
To configure a GNE site on a VLL Cpipe service
5620 SAM
4
In the VLL_type Service navigation tree, right-click on the sites icon and choose
Create GNE Site. The Select Network Element form opens.
5
Choose a network element from the list and click OK. The GNE Site (Create) form
opens.
6
Configure the parameters as required.
7
Perform the following step to configure an interface for the GNE site:
1. Click on the GNE Service Interfaces tab and click Create. The GNE Service
Interface (Create) form opens.
2. Configure the parameters on the General tab as required.
3. Click on the Port tab, click Select to choose an interface and click OK.
4. Configure the parameters on the Port tab as required.
5. Save your changes and close the form. The GNE Site (Create) form reappears
with the interface information displayed in the VLL_type Service navigation tree.
8
Perform the following step to attach or run configuration scripts for the GNE site:
1. Click on the Scripts tab. The Scripts tab displays the script instances and
versions that apply to the device.
2. Attach or run the required configuration script for the GNE site. See the 5620
SAM Scripts and Templates Developer Guide for more information.
3. Save your changes and close the form. The GNE Site (Create) form reappears
with the new information displayed in the VLL_type Service navigation tree.
9
Save your changes and close the form. You can use the topology maps to view the
service. See the “5620 SAM topology map management” chapter in the 5620 SAM
User Guide for more information.
END OF STEPS
160
3HE-10693-AAAB-TQZZA
Issue 1
5620 SAM
To configure a customer profile and associate it with a VLL service
13.9
13.9.1
To configure a customer profile and associate it with a VLL
service
Steps
Configure a customer profile
1
Choose Manage→Service→Customers from the 5620 SAM main menu.
2
Click Create. The Customer (Create) form opens.
3
Configure the required general parameters.
4
Click on the Sites tab and click Create. The Select Network Elements — Customer
form opens.
5
Choose the site that requires specific customer details.
6
Repeat Step 5 to add more sites.
7
Save the changes and close the forms.
Configure a VLL service with a specific customer profile
8
Choose Manage→Service→Services from the 5620 SAM main menu.
9
Choose Create→Service→9500 Cpipe from the 5620 SAM main menu. The Cpipe
Service (Create) form opens.
10
Choose the newly configured customer in the Customer panel.
Issue 1
3HE-10693-AAAB-TQZZA
161
To configure a customer profile and associate it with a VLL service
5620 SAM
11
Configure the VLL Cpipe service. See Procedure 13.4 “To create a VLL Cpipe
service on a 9500 MPR” (p. 154) for more information about configuring a VLL Cpipe
service.
Modify a discovered VLL service to add a specific customer profile
12
Choose Manage→Service→Services from the 5620 SAM main menu.
13
Click Discover MPR 9500 Services→Hop Based or Ring Based.
Note: The discovered service has the default customer associated with it.
14
Choose the discovered service and click Properties. The 9500 MPR Cpipe Service
(Edit) form opens.
15
Clear the default customer in the Customer panel and choose the newly configured
customer.
Note: The 5620 SAM does not validate and generate error messages if a
specific site is not added in the customer profile associated with a particular
VLL service.
16
Save the changes and close the forms.
END OF STEPS
162
3HE-10693-AAAB-TQZZA
Issue 1
Download PDF
Similar pages