Professional Documents
Culture Documents
Alcatel-Lucent 5620
SERVICE AWARE MANAGER
MPR USER GUIDE
Alcatel-Lucent Proprietary
This document contains proprietary information of Alcatel-Lucent and is not to be disclosed
or used except in accordance with applicable agreements.
Copyright 2015 © Alcatel-Lucent. All rights reserved.
Release 13.0 R2 | May 2015 | 3HE 09803 AAAB TQZZA Edition 01
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is
subject to change without notice.
Alcatel, Lucent, Alcatel-Lucent, the Alcatel-Lucent logo, lightRadio, and TiMetra are registered
trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.
Disclaimers
Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design
engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous
environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft
navigation or communication systems, air traffic control, direct life-support machines, or weapons
systems, in which the failure of products could lead directly to death, personal injury, or severe physical
or environmental damage. The customer hereby agrees that the use, sale, license or other distribution
of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at
the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from
any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the
use, sale, license or other distribution of the products in such applications.
This document may contain information regarding the use and installation of non-Alcatel-Lucent
products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent
tries to ensure that this information accurately reflects information provided by the supplier, please refer
to the materials provided with any non-Alcatel-Lucent product and contact the supplier for
confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete
information provided about non-Alcatel-Lucent products.
However, this does not constitute a representation or warranty. The warranties provided for
Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by
Alcatel-Lucent and its customers.
This document was originally written in English. If there is any conflict or inconsistency between the
English version and any other version of a document, the English version shall prevail.
Contents
Getting started
Contents
Contents
6.5 9500 MPR/9500 MPRe shelf object configuration procedures .................... 6-9
Procedure 6-1 To migrate the 9500 MPRe connected to a
7705 SAR from standalone mode to single NE mode ...................... 6-9
Procedure 6-2 To manage the 9500 MPR/9500 MPRe running
software ........................................................................ 6-11
Procedure 6-3 To configure a 9500 MPR basic or advanced fan tray ....... 6-12
Procedure 6-4 To configure 9500 MPR card protection....................... 6-13
Procedure 6-5 To remove 9500 MPR card protection ......................... 6-14
Procedure 6-6 To switch between a 9500 MPR in-service
protected radio link and a standby protected radio link................ 6-14
Procedure 6-7 To configure MPT-HLS radio .................................... 6-16
Contents
8.2 Workflow to configure 9500 MPR/9500 MPRe QoS policies ....................... 8-3
8.3 9500 MPR/9500 MPRe QoS policies procedures ..................................... 8-3
Procedure 8-1 To configure and distribute a 9500 MPR ATM QoS
policy............................................................................. 8-3
Procedure 8-2 To configure and distribute a 9500 Radio Interface
Queue Map policy .............................................................. 8-4
Procedure 8-3 To configure and distribute a 9500 NE QoS policy ........... 8-5
Contents
11.3 VLL service management procedures for 9500 MPR devices .................... 11-3
Procedure 11-1 To create a VLL Apipe service on the 9500 MPR
(ETSI only) ...................................................................... 11-3
Procedure 11-2 To create a VLL Cpipe service on a 9500 MPR .............. 11-6
Procedure 11-3 To create a single site VLL Cpipe service on
9500 MPR connected to an MSS1c........................................... 11-9
Procedure 11-4 To discover a single-site Cpipe service on 9500 MPR
connected to an MSS-1c .................................................... 11-11
Procedure 11-5 To fix a failed cross-connection in a 9500 MPR
Cpipe or a hop-based VLAN service....................................... 11-11
Procedure 11-6 To configure a GNE site on a VLL service ................. 11-12
Appendices
Contents
Getting started
1 — What’s new?
1— What’s new?
1.1 What’s new in 5620 SAM Release 13.0 for 9500 MPR and
9500 MPRe devices 1-2
1.1 What’s new in 5620 SAM Release 13.0 for 9500 MPR and
9500 MPRe devices
This section highlights new 9500 MPR and 9500 MPRe features for 5620 SAM
Release 13.0 and provides pointers into the documentation for more information
about using the features. Feature lists and high-level feature descriptions are also
available in the 5620 SAM Release Description.
Maintenance releases
Some releases may not be listed in this section, either because no new 9500 MPR or
9500 MPRe features were introduced or the features introduced do not require
documentation.
The Alcatel-Lucent 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.
• XPIC
• NEtO
The 5620 SAM also supports the native management of the 9500 MPRe, a variant of
the 9500 MPR. See “9500 MPRe support” in this section.
MSS-1 shelf
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 supports only the following types of services on the 5620 SAM:
• VLL (Cpipe only)
• VLAN
Note 1 — 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 2 — Radio LAG (L1 and L2) are not supported.
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.
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-XP
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-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-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 Procedure 6-7 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 MPR-e (stand-alone) with the antenna. Fixed and adaptive modulation
schemes are supported. Channel frequency is software selectable within tuning range
of the 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 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
Fan tray
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 Procedure 6-3
for more information about configuring a 9500 MPR fan tray.
Note — The service changes from the NEtO in the preceding list are
not supported for ERPS (radio or fiber).
XPIC
The XPIC function is required on the two radio interfaces in order to provide
additional cross polarization discrimination, avoiding co-channel interference. Only
the MPT-HCv2/MPT-XP supports the XPIC function. See Procedure 7-11 to
configure power source type over Ethernet on a 2+2 × Ethernet (EAS) card. See the
9500 MPR user documentation for more information about how to use the NEtO
software to configure XPIC.
The 5620 SAM supports native management of the 9500 MPRe, R3.3 or later. 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 “9500 MPR/9500 MPRe
NEtO support”.
See Procedure 7-7 for information about configuring ports on the 9500 MPRe.
The following workflow describes the high-level tasks required to commission and
discover 9500 MPR and 9500 MPRe devices, configure and manage the device objects,
and configure and manage the policies and services associated with the devices.
1 Review the workflow to prepare the 5620 SAM to perform network management
described in the supported devices chapter in 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/9500 MPRe devices for 5620 SAM management; see
chapter 3.
3 Use the 5620 SAM to discover 9500 MPR/9500 MPRe devices; see the ”Device
discovery” chapter in the 5620 SAM User Guide.
4 View, manage, and configure 9500 MPR/9500 MPRe device network objects as
required; see the Working with network objects chapter in the 5620 SAM User
Guide.
5 View, manage, and configure 9500 MPR/9500 MPRe device objects; see chapter 4.
6 View, manage, and configure 9500 MPR device LAG objects; see chapter 5.
7 View, manage, and configure 9500 MPR/9500 MPRe device shelf objects; see
chapter 6.
9 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.
b Create QoS device-specific policies as required for 9500 MPR devices; see
chapter 8.
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.
c Review the 9500 MPR service management and service tunnels chapter for
specific information on supported service types; see chapter 9.
d Configure service tunnels to carry service traffic on 9500 MPR devices; see
chapter 9.
11 Configure VLAN groups, paths, and services for subscribers connected to 9500 MPR
devices; see chapter 10.
12 Configure VLL Apipe, Cpipe, and Epipe services for subscribers connected to
9500 MPR/9500 MPRe devices; see chapter 11.
14 Perform specific 9500 MPR device maintenance functions, as required, such as:
See the 5620 SAM System Administrator Guide for more information.
15 Collect 5620 SAM and NE statistics to monitor the 5620 SAM and
9500 MPR/9500 MPRe devices, network and service performance, compile
equipment usage and billing data, and ensure SLA compliance; see the 5620 SAM
Statistics Management Guide.
To enable 9500 MPR in-band management, the 5620 SAM requires connectivity to
the 9500 MPR NE, as shown in Figure 3-1 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 in-band NIC that connects to the 9500 MPR
network.
Note — The management port IP, TMN in-band IP, and local IP can
be in different subnets.
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.
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.
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 Figure 3-2 and
described in Table 3-1.
Figure 3-2 Connectivity example for 9500 MPR/9500 MPRe radio link discovery and management
22432
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).
• 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 — The status of a protected link does not have a direct impact
on the status of a service. See Table 9-1 for more information about
the service status.
Prepare the 9500 MPR for 5620 SAM management by commissioning the device before
discovery by the 5620 SAM; see the “Device commissioning and management” chapter
in the 5620 SAM User Guide for the generic procedures that apply to this device type.
In addition, perform the following device-specific procedures as required:
1 Enable and configure SNMP on a 9500 MPR device and configure a 5620 SAM
mediation policy and discovery rule; see Procedure 3-1.
2 Configure how and when the 5620 SAM polls the device for MIB changes; see
Procedure 3-2.
3 If required, modify the properties files of 9500 MPR NEs originally discovered using
the 5620 SAM, Release 10.0 R4 or earlier, to enable the opening of NEtO sessions
using the 5620 SAM GUI. See Procedure 3-3.
Perform this procedure to configure a 5620 SAM 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.
Note — The 5620 SAM uses the default SNMPv2 mediation security
policy to discover the 9500 MPR.
ii Click on the Create button. The Create Discovery Rule step form opens.
iii Enter a description in the Description field for the discovery rule. Click on
the Next button.
iv In step 2 of the step form (Add Rule Elements), click on the Create button.
The Topology Discovery Rule Element (Create) form opens.
v Enter the 9500 MPR management IP address as the rule element for the
discovery rule and click on the OK button. A warning message appears.
viii Click on the Select button in the Read Access Mediation Policy panel. The
Configure Mediation Security – Topology Discovery Rule form appears.
ix Select a mediation security policy and click on the OK button. The form
closes and the selected policy displays in the Read Policy Name parameter
field.
x Repeat steps 1 viii and 1 ix to select a Write Access Mediation Policy and Trap
Access Mediation Policy.
xi Click on the Finish button to save and close the Create Discovery Rule step
form. A warning message appears.
xii Click on the OK button to acknowledge and dismiss the warning message.
xiii Click on the OK button. The Discovery Manager (Edit) form opens with the
new discovery rule displayed.
xiv Click on the OK button. The Discovery Manager (Edit) form closes.
xv Go to step 7.
ii Click on the Create button. The NE User, Global Policy (Create) form opens
with the General tab displayed.
v When a user has SNMPv3 permissions, you can configure the authentication
parameters. Verify that the SNMPv3 user and user group have been created
on the managed NE. Configure the parameters:
vi Click on the OK button. The NE User, Global Policy (Create) form closes.
vii Click on the Search button on the NE User Configuration form to confirm the
creation of the SNMPv3 user.
4 Configure an SNMPv3 mediation security policy for the SNMPv3 user created in
step 3.
iii Click on the Create button to create a mediation security policy. The
Mediation Policy (Create) form opens.
vii In the SNMPv3 panel, click on the Select button. The Select User Mediation
Policy form opens.
viii Choose the SNMPv3 user created in step 3 and click on the OK button. The
user is added to the SNMPv3 panel on the Mediation Policy (Create) form.
5 Create a discovery rule for the 9500 MPR on the 5620 SAM.
ii In step 4 of the step form (the Configure Mediation Security step), click on
the Select button and choose the mediation security policy that you created
in step 4 in this procedure for the Read Policy ID, Write Policy ID, and Trap
Policy ID parameters.
6 If you plan to use a 5620 SAM auxiliary server to collect 9500 MPR statistics using
IPv4 or IPv6, perform the following steps.
iii Choose the auxiliary server from the list and click on the Properties button.
The Auxiliary Server (View) form opens.
v Select the STATS_SERVICE entry from the list and click on the Properties
button. The Auxiliary Service - STATS_SERVICE (Edit) form opens.
vii Click on the OK button. The Auxiliary Service - STATS_SERVICE (Edit) form
closes.
During the subsequent device discovery, the 5620 SAM registers the IPv6
address of the auxiliary server on each discovered 9500 MPR or 9500 MPRe.
viii Click on the OK button. The Auxiliary Server (View) form closes.
7 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.
2 Right-click on an icon that represents a 9500 MPR and choose Properties. The
Network Element (Edit) form opens with the General tab displayed.
5 Configure the Scheduled Polling parameter if you are configuring a 9500 MPR.
Scheduled polling is configured using the Mediation configuration form. See the
“Device discovery” chapter in the 5620 SAM User Guide.
8 Click on the Yes button to confirm the action. The Network Element (Edit) form
closes.
Perform this procedure to enable the 5620 SAM to manage a 9500 MPR or 9500 MPRe,
and to enable the opening of NEtO sessions using the 5620 SAM GUI.
See Procedure 4-4 for information about how to install or launch the NEtO from the
5620 SAM GUI.
2 Discover a 9500 MPR or 9500 MPRe NE 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 or 9500 MPRe 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
where Release is the appropriate 9500 MPR release identifier, for example, 3.3.0
6 Replace ${path} in the following line with the NEtO directory path; for example,
D:\\NEtO
install_dir =${path}
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:
Note — If you do not edit the profile name, the community string is
derived from the mediation policy of the discovery rule.
9 Select the equipment view of the navigation tree on the 5620 SAM GUI. Right-click
on a 9500 MPR or 9500 MPRe NE, and select External Element Manager from the
menu.
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/9500 MPRe 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 “Navigation tree overview” chapter in the
5620 SAM User Guide.
The following workflow describes the sequence of high-level tasks required to configure
and manage 9500 MPR/9500 MPRe 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.
1 Configure the system settings for a 9500 MPR/9500 MPRe device; see
Procedure 4-1.
2 Remove any inconsistencies created due to MIB population failures that can occur
during service creation on a 9500 MPR NE; see Procedure 4-2.
3 Configure a scope of command role for NEtO access; see Procedure 4-3.
4 Start the 9500 MPR external element manager from the 5620 SAM GUI; see
Procedure 4-4.
5 As required, configure or modify the DSCP value for TMN in-band interfaces on the
9500 MPR. See Procedure 4-5.
6 As required, review the list of the specific functionality for a 9500 MPR SAM-E
license compared to management functions available in the NEtO. See
Appendix A.
Use the following procedures to configure devices using the navigation tree.
5 Click on the Yes button. The Network Element (Edit) form closes.
1 Right-click on a 9500 MPR NE device in the navigation tree, and choose Properties
from the contextual menu. The Network Element (Edit) form opens with the
General tab displayed.
4 Click on the Faults tab of the Network Element (Edit) form to check for any
remaining NE inconsistency alarms.
3 Click on the Create button and choose Profile. The Scope of Command Profile
(Create) form opens with the General tab displayed.
• Auto-Assign ID
• Profile ID
• Profile Name
• Description
5 Click on the Roles tab and click on the Add button. The Select Role - Role form
opens.
a Choose Admin NEtO launch to open the NEtO with the administration profile.
b Choose Viewer NEtO launch to open the NEtO with the viewer profile.
c Choose Default NEtO launch to open the NEtO with the null profile.
7 Click on the OK button. The Select Role - Role form closes and a dialog box
appears.
9 Click on the OK button. The Scope of Command Profile (Create) form closes.
10 Close the 5620 SAM User Security - Security Management (Edit) form.
To cross-launch the NEtO, you must belong to a user group that includes a scope of
command profile 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.
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
Procedure 4-3.
1 Choose Equipment from the view selector in the navigation tree. The navigation
tree displays the Equipment view.
2 Right-click on a discovered 9500 MPR or 9500 MPRe and choose External Element
Manager.
3 Type your login credentials. The NEtO main view screen appears.
Note — If the NEtO is not installed on your client system, the NEtO
installer window opens. 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.
See the appropriate 9500 MPR User Guide for information about configuring and using
the NEtO external element manager.
You can configure or modify the DSCP value for TMN in-band interfaces following this
procedure or specified as part of a global 9500 MPR NE QoS policy. See Procedure 8-3
for the 9500 MPR NE QoS policy method.
Note — You cannot change the DSCP value if the in-band TMN interface
is set to enabled.
1 Right-click on a 9500 MPR device on the navigation tree and choose Properties
from the pull-down menu. The Network Element [Edit] form opens with the
General tab displayed.
3 Click on the TMN Details tab. The current setting of TMN interface on the selected
device are displayed in the TMN Working Mode column (either Enabled or
Disabled).
7 Configure the TMN Working Mode parameter to one of the following options:
8 Click on the OK button. The MPR TMN - TMN In-band [Edit] form closes.
9 Click on the Apply button on the devices properties form. A confirmation box
appears.
11 As required, repeat steps 4 to 10 to configure the DSCP value for the second
in-band TMN interface.
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 provides 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.
The recommended settings for the aggregation of radio links configured in adaptive
modulation mode are:
• Minimal channel spacing for:
• ETSI = 14 MHz
• ANSI = 10 MHz
• Minimal modulation scheme = 16 QAM
Note — You must use the 4+4 Ethernet (EAS) card for L1 radio LAG
endpoints configured with adaptive modulation.
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.
1 Configure a L1 radio LAG or L2 radio LAG or Ethernet LAG on the 9500 MPR; see
Procedure 5-1.
Use the following procedures to manage LAGs using the navigation tree.
You can create a L1 radio LAG, L2 radio LAG or Ethernet LAG on the 9500 MPR, Release
3.4 or later.
3 Right-click on the LAGs icon and choose Create LAG from the contextual menu.
The Create LAG - Define General Properties form opens.
• LAG ID
• Auto-Assign ID
5 Click on the Next button. The Create LAG - Configure LAG Parameters form opens.
• Name
Note — The Name parameter configuration must be limited to a
maximum of 15 characters.
7 Click on the Next button. The Create LAG - Configure LACP form opens.
9 Click on the Next button. The Create LAG - Configure LAG Members form opens.
10 Click on the Create button to add ports to the LAG. The Create LAG Member - Only
show compatible ports form opens.
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 6.
11 Click on the Next button. The Create LAG Member - Select Ports form opens.
12 Click on the Search button to display a list of compatible ports. Choose one or
more ports from the list.
Note — For L1 radio LAG port members, see the “L1 radio LAG port
modulation configuration guidelines” for the required configuration
guidelines.
14 Click on the OK button. The Create LAG - Configure LAG Members form displays
the LAG members.
15 Click on the Finish button. The Create LAG - Wizard Completed form opens.
16 If required, select the View the newly created Port Termination check box to view
the LAG properties.
17 Click on the Close button to close the form. The LAG appears under the LAGs icon
in the navigation tree.
i Right-click on the LAG and choose Turn Up from the contextual menu. A
dialog box appears.
19 As required, right-click on the LAG and choose Properties from the contextual
menu to view information about the created LAG or to modify the LAG
parameters. The LAG (Edit) form opens.
• The General tab displays the LAG ID and description. For a radio LAG and
Ethernet LAG, choose one of the following Mode parameter values:
• Access (Ethernet LAG only)
• Network (radio LAG only)
• 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.
• For radio LAG, choose Size and Wait to Restore (ms) from the drop-down
menu.
• LACP parameters can be modified from the LACP tab. See step 8.
• LAG member ports can be added from the LAG Members tab. See steps 9 to 15.
• 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.
3 On the Network Element (Edit) form navigation tree, expand the Logical Groups
icon.
4 Expand the LAGs icon, right-click on a LAG object, and choose Delete from the
contextual menu. A dialog box appears.
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.
This chapter contains the procedures to configure shelf and card slots using the
navigation tree on 9500 MPR/9500 MPRe devices.
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:
For 9500 MPRe devices, you can view the following states and conditions on the
shelf:
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).
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.
Card slot objects for 9500 MPR/9500 MPRe devices can be configured for plug-in
cards; there are no daughter cards associated with these devices.
Core-enhanced MSS-8 ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ __
MSS-4
1 × radio MSS-8 ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ __
modem MSS-4
EASv2 MSS-8 ✓
MSS-4
2 × STM MSS-8 ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ __
MSS-4
Ancillary equipment
Core-enhanced card
The core-enhanced card in slot 1 provides the following:
• device management and control functions
• DC power
• a plug-in flash memory card to store device configuration and license data
• an Ethernet switch that implements the cross-connections between the radio
modem or 32 × DS1 / 32 × E1 cards, between the Ethernet user ports, and between
the Ethernet ports and the radio modem or 32 × DS1 / 32 × E1 cards
• four electrical Ethernet ports; port 4 can be used as another management port, if
required
• two SFP Ethernet ports; the ports are supported by the 5620 SAM when an SFP
MDA is installed
• up to six MPT radio ports; ports 1 to 4 support MPT-HCv2, and MPT-MC; ports
5 and 6 support MPT-HCv2, MPT-HL, MPT-HLC, MPT-HLS, and SFP
An optional identical core-enhanced card can be installed in card slot 2. The card
provides protection if the card in slot 1 fails.
The MPT-HL does not support radio LAGs or 1+1 protection configurations. See the
9500 MPR user documentation for information about supported cross-connections
for the MPT-HL and core-enhanced card.
When an MPT pair (MPT-HCv2 with RPS module, or MPT-MC) is used for a
protected configuration, both MPTs must use the same type of GigE port (optical or
electrical) to use the same IDU-ODU synchronization method.
A protected configuration is only allowed between ports 1 - 2, 3 - 4, and 5 - 6.
The following protection types are supported when MPT-HCv2 or MPT-MC is used
as an ODU in a split-mount configuration and directly connected to a core-enhanced
card:
• radio protection switching (RPS)
RPS is always supported in 1+1 radio configurations (FD and HSB). RPS is
implemented directly on a pair of MPTs.
• transmission protection switching (TPS)
TPS is always supported in 1+1 HSB radio configurations.
• equipment protection switching (EPS)
EPS protects the MPT and cables connecting the MPT to the IDU. RPS protection
always assumes the MPT EPS.
See Procedure 7-13 for information about adding 9500 MPR port protection.
Core-B card
The core-B card in slot 1 provides the following:
• device management and control functions
• DC power
• a plug-in flash memory card to store device configuration and license data
• an Ethernet switch that implements the cross-connections between the radio
modem or 32 × DS1 / 32 × E1 cards, between the Ethernet user ports, and between
the Ethernet ports and the radio modem or 32 × DS1 / 32 × E1 cards
• four GigE electrical interfaces and one GigE SFP optical interface
See Procedure 7-8 for information about configuring analog radio statistics on 1 ×
radio modem ports. See Procedure 7-9 for information about configuring power level
performance management on 1 × radio modem ports.
EASv2 card
The EASv2 card is used as an interface card to interconnect up to eight MPTs. The
card can be configured in card slots 3 to 8 on the 9500 MPR. The card provides eight
ports used for the following traffic interfaces:
• Ports 1 to 4
• Ethernet 10/100/1000 Base-T
• configuration of MPT-HC and MPT-MC
• Ports 5 to 8
• Ethernet SFP 1000 Base-X optical; 1000BASE-LX, 1000BASE-SX,
1000BASE-CX
• configuration of MPT-HC and MPT-HLS in ETSI and configuration of MPT-HC,
MPT-HL, and MPT-HLC in ANSI
Protection is not supported for MPT-HLC in 5620 SAM R12.0. However, 1+1 cross
configuration is supported on an MPT-HCv2 and MPT-HQAM connected to one of
ports 5 to 8.
See Procedure 7-11 for more information about configuring the power source
type of an EASv2 card.
Table 6-2 lists the supported EASv2 features in the corresponding 5620 SAM
release.
12.0 R1 9500 MPR 5.1 version with EASv2 at the level of EASv1
12.0 R2 9500 MPR 5.1 version with MPT-HLS and LAG support
2 × STM card
The 2 × STM card supports optical signaling on the 9500 MPR. The 2 × STM card
can be configured in all card slots on the 9500 MPR. Up to two ports can be
configured. A card in a 9500 MPR ETSI or a 9500 MPR ANSI, Release 4.0 or later,
supports the SFP-O and the SFP-E port usage types. See Procedure 7-2 for
information about configuring ports on a 2 × STM card.
16 × E1 (ASAP) card
The 16 × E1 (ASAP) card enables the management of ATM services on the
9500 MPR, through collecting IMA traffic, terminating the IMA groups, and
encapsulating and extracting the ATM cells into and from ATM PW packets toward
the core board. ATM interfaces are established over PDH physical interfaces. ATM
traffic is transported by the ATM PW service and encapsulated in Ethernet frames.
2 × DS3 card
Two DS3 ports are available:
• support up to six units per shelf
• provide 1+1 EPS protection
See Procedure 7-5 for information about configuring ports on the 2 × DS3 card.
See the 5620 SAM Alarm Reference for the alarm descriptions, the generating and
clearing conditions of alarms, and the remedial actions to fix the problems.
Only one AUX alarm card is supported per 9500 MPR MSS shelf. On the MSS-4
shelf, the AUX alarm card is supported in slot 4. On the MSS-8 shelf, the AUX alarm
card is supported in slot 8. See Procedure 7-6 for information about configuring ports
on the AUX alarm card.
The following workflow describes the sequence of high-level tasks required to configure
and manage 9500 MPR/9500 MPRe device shelf objects; see the “Shelf 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 or
functions:
a Configure NTP on 9500 MPR devices; see the “Shelf object configuration”
chapter in the 5620 SAM User Guide.
Note — When adding an NTP server, 5620 SAM can allow invalid
configuration in the form. Close the form and re-open it to retry the
operation with correct values.
d Configure a basic or advanced fan tray on the 9500 MPR; see Procedure 6-3.
a Assign a card type to a chassis slot; see the “Shelf object configuration”
chapter in the 5620 SAM User Guide.
Use the following procedures to configure shelf objects using the navigation tree.
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 4.1.0.
• 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.
Note 3 — For information about the 7705 SAR and 9500 MPRe, see the
9500 MPRe 4.1.0 user documentation and the appropriate 7705 SAR 6.0
R1 hardware guides.
1 Choose Equipment from the navigation tree view selector. The navigation tree
displays the Equipment view.
4 Right-click on the port that you associated with the MW link and choose
Properties. The MW Link Member (Edit) form opens with the General tab
displayed.
• Radio Name
• StandAlone
• Database Filename
Note 1 — 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.
Note 2 — 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.
9 Click on the Yes button. The MW Link Member (Edit) form closes.
Perform this procedure to manage the software in the 9500 MPR/9500 MPRe committed
and standby banks. You can upgrade or downgrade the running software release on a
9500 MPR/9500 MPRe. See “NE maintenance overview” in the 5620 SAM System
Administrator Guide for information about creating software upgrade policies and
performing software upgrades. During the software upgrade, the NE audit process is not
supported for 9500 MPR NEs.
1 Choose Equipment from the navigation tree view selector. The navigation tree
displays the Equipment view.
3 Right-click on the 9500 MPR/9500 MPRe device that you need to upgrade or
downgrade and choose Properties from the contextual menu. The Network
Element (Edit) form opens with the General tab displayed.
4 Click on a shelf object. The Shelf (Edit) form opens with the General tab
displayed.
5 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 9500 MPR/9500 MPRe. The standby software is new software
uploaded to the 9500 MPR/9500 MPRe or formerly committed software.
6 Verify that the operational state of the standby software is Enabled, by examining
the Operational State column of the displayed list.
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 9500 MPR/9500 MPRe can be upgraded. If the
standby software version is older than the committed software version, the
9500 MPR/9500 MPRe can be downgraded.
9 The MPRSoftwarePackage (Edit) form opens with the Software Bank Details tab
displayed.
11 Click on the OK button. The MPRSoftwarePackage (Edit) form closes. The entry in
the Activation column for the standby software should be the same as the option
chosen in step 10.
13 Click on the Yes button. When the standby and committed software versions are
different or the forced activation option is selected, the 9500 MPR/9500 MPRe
reboots using the standby software. If the standby and committed software
versions are the same and the activation option is chosen, the
9500 MPR/9500 MPRe does not reboot and the Shelf (Edit) form closes.
14 When the 9500 MPR/9500 MPRe reboots, you can confirm that the
9500 MPR/9500 MPRe 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.
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 4.2 or later.
1 Choose Equipment from the navigation tree view selector. The navigation tree
displays the Equipment view.
3 RIght-click on a shelf object. The Shelf (Edit) form opens with the General tab
displayed.
5 Click on the Create button. The Fan Tray (Create) form opens.
• Tray ID
• Fan Type
9 Click on the Properties button. The Auxiliary Inputs (Edit) form opens with the Aux
Input tab displayed.
• User Label
• Polarity
11 Click on the OK button. The Auxiliary Inputs (Edit) form closes and the Fan Tray
(Edit) form reappears.
14 Click on the Yes button. The Fan Tray (Edit) form closes.
The 9500 MPR supports card protection for all card types. EPS card protection for the
CORE-ENH card in slot 1 is automatically configured by the system when an optional
spare CORE-ENH card is provisioned into slot 2. Radio modem and 32 x DS1/E1 cards in
slots 3, 5, and 7 can be protected by corresponding identical cards in slots 4, 6, and 8.
Protection for cards in slots 3, 5, and 7 must be configured. The protected card is
referred to as the main card and the protecting card is referred to as the spare card.
Use the following procedure to configure optional card protection for radio modem and
32 x DS1/E1 cards.
2 Right-click on the 9500 MPR object and choose Properties from the contextual
menu. The Network Element (Edit) form opens with the General tab displayed.
3 On the Network Element (Edit) form navigation tree, expand the Shelf object.
4 Click on the card slot object that you need to configure. The Card Slot (Edit) form
opens with the General tab displayed.
• Protection Type
• Restoration Criteria
• Commands
8 Click on the Yes button. The Card Slot (Create) form closes.
9 Verify that the protection is enabled. The status of the main card should be Active
and the status of the spare card should be Standby.
Note — If 1+1 HSB is configured as the protection type for a radio card,
the transmitter must be muted from the NEtO to remove the protection.
1 Choose Equipment from the navigation tree view selector. The navigation tree
displays the Equipment view.
2 Right-click on the 9500 MPR object and choose Properties from the contextual
menu. The Network Element (Edit) form opens with the General tab displayed.
3 On the Network Element (Edit) form navigation tree, expand the Shelf object.
4 Click on the card slot object that you need to configure. The Card Slot (Edit) form
opens with the General tab displayed.
8 Click on the Yes button. The Card Slot (Create) form closes.
9 Verify that the protection is removed from the previously main and spare cards.
You can switch between an in-service protected radio link and a standby protected
radio link on 9500 MPR devices to reroute traffic when you need to perform routine
maintenance on the radio link.
This procedure assumes that link protection has been configured prior to starting this
procedure; see Procedure 7-13. This procedure only applies to switching radio links that
terminate on port endpoints.
1 On the Physical topology map, select a radio link group between two 9500 MPR
NEs. The plus sign on the link group highlights.
2 Right-click on the plus sign and choose Expand Group to view all radio links.
In-service protected radio links are represented as green links; standby links are
shown as blue links.
To switch radio links that terminate on Radio Modem cards, go to step 3. The
configuration to perform the switchover for this card type is done at the card
level.
To switch radio links that terminate on 2+2 (EAS), 4+4 (EAS), or CORE-ENH cards,
go to step 11. The configuration to perform the switchover for these card types is
done at the port level.
3 Expand the Shelf icon to display the available Radio Modem cards.
4 Right-click on one of the 9500 MPR link endpoints and choose Properties. The
Network Elements [Edit form] opens.
5 Right-click on the Radio Modem-MAIN card and choose Properties. The Card Slot,
Radio Modem [Edit] form opens with the General tab displayed.
6 Click on the Protection tab and choose one of the following Commands parameter
options on the Equipment Protection Scheme Parameters panel to initiate the
switchover:
7 Click on the OK button to make the changes and close the Card Slot, Radio Modem
[Edit] form.
9 Repeat steps 4 to 8 on the second 9500 MPR link endpoint to complete the
switchover. The standby radio link becomes the in-service radio link and traffic is
re-routed over this link.
11 Right-click on an in-service radio link port and choose Properties. The Radio
Link-Physical Port (Edit) form opens with the General tab displayed.
12 Click on the Properties button for Endpoint A-Port. The Physical Port (Edit) form
opens with the General tab displayed.
13 Click on the Protection tab and choose one of the following Commands parameter
options on the Receiver Protection Scheme Parameters panel to initiate the
switchover:
14 Click on the OK button to make the changes and close the Physical Port (Edit)
form. A confirmation box appears. Click the Yes button to proceed.
15 Repeat steps 11 to 14 for Endpoint B - Port on the same radio link to complete the
switchover. The standby radio link becomes the in-service radio link and traffic is
re-routed over this link.
16 Verify the switchover occurred by repeating steps 11 to 12 for the card and
clicking on the Protection tab and verifying that the Status parameter on the
Receiver Protection Scheme Parameters panel reads “Active”.
The MPT-HLS is configured on the core-enhanced card or an EASv2 card. The MPT-HLS
radio is configured in an ETSI rack. Inside the ETSI rack two different RT subracks are
available with up to 10 transceivers in each. For each RT subrack two fan subracks can
be configured.
Enable subracks
1 Choose Equipment from the navigation tree view selector. The navigation tree
displays the Equipment view.
2 Right-click on the 9500 MPR object and choose Properties from the contextual
menu. The Network Element (Edit) form opens with the General tab displayed.
3 Click on the Subracks tab. The bottom and top subracks are listed.
4 Choose a subrack and click on the Properties button. The Sub Racks (Edit) form
opens with the General tab displayed.
7 Click on the OK button. The dialog box closes and the Sub Racks (Edit) form
reappears.
8 Click on the OK button. The Sub Racks (Edit) form closes and the Network Element
(Edit) form reappears.
10 Click on the Yes button. The dialog box closes and the Network Element (Edit)
form reappears.
13 Right-click on the port object and choose Properties from the contextual menu.
The Physical Port (Edit) form opens with the General tab displayed.
14 Set the Port Usage parameter to MPT-HLS. The Subrack Connection Panel appears.
15 Click on the Select button beside the Slot parameter in the Subrack Connection
panel. The Select Subrack Connection form opens with a list of subracks.
16 Choose a subrack where the MPT-HLS needs to be configured and click on the OK
button. The Select Subrack Connection form closes and the Physical Port (Edit)
form reappears with the Subrack Connection panel updated with the subrack
information.
18 Click on the Yes button to complete the configuration. Deployment icons appear
beside parameters for which a deployment is in progress.
19 Wait for the deployment to be completed and close the Physical Port (Edit) form.
21 Click on the Subracks tab. The bottom and top subracks are listed.
22 Choose the subrack where MPT-HLS is configured and click on the Properties
button. The Sub Racks (Edit) form opens with the General tab displayed.
23 Click on the Subrack Elements tab. The subracks where MPT-HLS can be configured
are listed from Slot 1 to 10 and the subracks where fans can be configured are
listed from Slot 11 to 12.
24 Choose Slot 11 or 12 subrack and click on the Properties button. The Subrack
Elements (Edit) form opens with the Subrack Elements tab displayed.
25 Configure the Equipment Type parameter. The Fan details panel appears.
• Empty
• SR-Fan4
• SR-Fan8
27 Choose a port and click on the OK button. The Select First Fan Handler form closes
and the Subrack Elements (Edit) form reappears.
Note 1 — Optionally, you can configure two fan handlers, First Fan
Handler and Second Fan Handler. A minimum of one fan handler
configuration is mandatory.
29 Click on the OK button. The dialog box closes and Subrack Element (Edit) form
reappears.
31 Click on the OK button. The Subrack Elements (Edit) form closes and the Sub Racks
(Edit) form appears with the updated list of subracks.
33 Click on the OK button. The dialog box closes and Sub Racks (Edit) form reappears.
35 Click on the OK button. The Sub Racks (Edit) form closes and the Network Element
(Edit) form reappears.
Port objects are children of card slot objects. Port objects appear below the card slot
after the card is configured. Port objects for 9500 MPR/9500 MPRe devices can be
configured for plug-in cards; there are no daughter cards associated with these
devices. Properties forms for port objects are accessed using the 5620 SAM
navigation tree.
You can configure the following 9500 MPR device ports:
• Ethernet ports
• 2 × STM card ports
• 1 × STM (Channelized) card port
• E1 and DS1 ports
• DS3 ports
• 1 × radio modem ports
• AUX alarm ports
• 9500 MPRe ports
See the “Port and channel object configuration” chapter in the 5620 SAM User Guide
for more information about working with port objects.
IMA support
For 9500 MPR/9500 MPRe devices, IMA is supported on the 16 × E1 ASAP Access
(ETSI) card. Each IMA group bundle can have up to 16 links and there can be up to
8 IMA groups on a card.
Each ATM interface supports up to 48 VP/VC connection points. Each 16 × E1
ASAP Access (ETSI) board supports up to 128 VP/VC connection points.
An IMA group bundle has the following common interface properties:
• ATM encapsulation type is displayed in the ATM Interface form by clicking on
the Edit ATM button.
• ATM interface characteristics can be viewed by clicking on the Edit ATM button
on the Bundle Properties form.
• Interface mode is access only for the 9500 MPR.
• MTU value (of the primary link)
Combiner support
You can enable or disable a combiner (space diversity) on the port by configuring the
Combiner parameter on the Port Usage panel in the port properties form of the
following types of radio ports:
• MPT-HLC
• MPT-HLS
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 Procedure 7-1 for information about enabling traffic storm control, port rate
limiting, and dot1q VLAN rate limiting on the 9500 MPR.
The following workflow describes the sequence of high-level tasks required to configure
and manage 9500 MPR or 9500 MPRe device ports; see the “Port and channel object
configuration” chapter in the 5620 SAM User Guide for the generic procedures that
apply to this device type. In addition, configure the following device-specific
procedures as required:
1 As required, change the port mode between Network, Access, and Hybrid modes.
See the “Port and channel object configuration” chapter in the 5620 SAM User
Guide for the generic procedures that apply to this device type.
3 As required, configure or perform the following on 9500 MPR or 9500 MPRe device
ports:
d power source type on 2+2 × Ethernet (EAS) card slots for 9500 MPR; see
Procedure 7-11
f loopback test on a 9500 MPR DS1, ES1, or 1x radio modem port; see
Procedure 7-15
Use the following procedures to manage 9500 MPR or 9500 MPRe device ports
using the navigation tree.
3 Right-click on the device where you need to configure an 9500 MPR Ethernet port
and choose Properties from the contextual menu. The Network Element (Edit)
form opens with the General tab displayed.
4 On the Network Element (Edit) form navigation tree, expand the Shelf icon.
5 Expand to the port level and click on a port object. The Physical Port (Edit) form
opens with the General tab displayed.
6 Configure the Port Usage parameter if you are provisioning the following ports:
10 Click on the Ethernet tab. The Ethernet port configuration form opens with the
General tab displayed.
• Duplex
• Auto-negotiate
• Advertised Capability
Note — Check the combinations that are supported for the Advertised
Capability parameter in the 9500 MPR User Guide.
12 Configure the following parameters if you need to enable traffic storm control on
the ports. See “9500 MPR Ethernet port QoS schemes” in this section.
• Enable
• Unicast Frame Rate (Frames/sec)
• Multicast Frame Rate (Frames/sec)
• Broadcast Frame Rate (Frames/sec)
13 Configure the following parameters if you need to enable port rate limiting on the
ports. See “9500 MPR Ethernet port QoS schemes” in this section.
14 Click on the VLAN Rate Limiter tab if you need to police the input bandwidth on
dot1q VLANs. The Ethernet ports that support VLAN rate limiting are listed.
See “9500 MPR Ethernet port QoS schemes” in this section.
17 Repeat steps 15 and 16, as required, to configure more Ethernet ports for VLAN
rate limiting.
3 Right-click on the card where you need to configure the 2 × STM card type and
choose Configure card from the contextual menu. The Card Slot (Create) form
opens with the General tab displayed.
4 Set the Assigned Card Type parameter to 2xSTM. The card is configured and two
ports are displayed.
5 Expand to the port level and right-click on Properties. The Physical Port (Edit)
form opens with the General tab displayed.
Note 1 — To configure the User Label parameter, you need to set the
port usage type to SFP-O or SFP-E in step 7.
• EMPTY
• SFP-O
• SFP-E
a When you set the port to SFP-O, the 2 × STM port is configured and the
Protection tab is enabled. See Procedure 6-4 for more information about card
protection.
b When you set the port to SFP-E, the 2 × STM port is configured but the
Protection tab is disabled.
c When you set the port to EMPTY, all the configured ports revert to an empty
slot after the port is shut down.
Note 1 — You need to shut down the configured port to remove the
port. Select the port and choose Port→Shut Down. Choose
Port→Properties. Configure the Port Usage parameter to EMPTY. The
SFP-O ports are removed. You can now configure other ports.
9 Set the Protection Type parameter to 1+1 EPS protection. All of the SFP-O ports
are protected.
3 Right-click on the card where you need to configure the 1 × STM (Channelized)
card type and choose Configure card from the contextual menu. The Card Slot
[Create] form opens with the General tab displayed.
5 Expand to the port level and right-click on Properties. The Physical Port [Edit]
form opens with the General tab displayed.
6 In the Port Usage panel, configure the ports by choosing one of the following:
• EMPTY
• SFP-O
• SFP-E
a When you set the port to SFP-O, the 1 × STM port is configured and the
Protection tab is enabled. See Procedure 6-4 for more information about card
protection.
b When you set the port to SFP-E, the 1 × STM port is configured but the
Protection tab is disabled.
c When you set the port to EMPTY, all the configured ports revert to an empty
slot after the port is shut down.
Note 1 — You need to shut down the configured port to remove the
port. Select the port and choose Port→Shut Down. Choose
Port→Properties. Configure the Port Usage parameter to EMPTY. The
SFP-O ports are removed. You can now configure other ports.
8 From the Protection Type drop-down menu, select 1+1 EPS protection. The SFP-O
port is protected.
9 Expand to the channel level and right-click on a channel. The Channel [Edit] form
opens.
Note 1 — To configure the User Label parameter, you need to set the
port usage type to SFP-O or SFP-E. See step 6.
Note 2 — For channels, the user label can be configured only for the
channels, and not for ports.
3 Right-click on the device where you need to configure a 9500 MPR E1 or DS1 port
and choose Properties from the contextual menu. The Network Element (Edit)
form opens with the General tab displayed.
4 On the Network Element (Edit) form navigation tree, expand the Shelf icon.
5 Expand to the port level and click on a port object. The Physical Port (Edit) form
opens with the General tab displayed.
• Signal Mode
• Line Code
If you are configuring an E1 port, you can only configure the Signal Mode
parameter.
11 Click on the other tabs in the properties form to view more port information.
13 Click on the Yes button. The Physical Port (Edit) form closes.
3 Right-click on the device where you need to configure a 9500 MPR DS3 port and
choose Properties from the contextual menu. The Network Element (Edit) form
opens with the General tab displayed.
4 On the Network Element (Edit) form navigation tree, expand the Shelf icon.
5 Expand to the port level and click on a port object. The Physical Port (Edit) form
opens with the General tab displayed.
• Signal Mode
• Line Code
• AIS Signal Type
11 Click on the other tabs in the properties form to view more port information.
13 Click on the Yes button. The Physical Port (Edit) form closes.
This procedure applies only to ports on 9500 MPR, Release 3.0 and later, AUX alarm
cards.
1 Choose Equipment from the navigation tree view selector. The navigation tree
displays the Equipment view.
3 Right-click on an empty card slot and choose Configure Card from the contextual
menu. The Card Slot - Shelf (Create) form opens with the General tab displayed.
Note — Only one AUX alarm card is supported per 9500 MPR MSS shelf.
On the MSS-4 shelf, the AUX alarm card is supported in slot 4. On the
MSS-8 shelf, the AUX alarm card is supported in slot 8.
4 Set the Assigned Card Type parameter to AUX and click on the OK button to apply
the changes.
5 Right-click on the AUX alarm card and choose Properties from the contextual
menu. The Card Slot [Port Number], AUX, Shelf (Edit) form opens with the General
tab displayed.
• User Label
Note — The User Label parameter configuration must be limited to a
maximum of 15 characters.
• Polarity
• User Label
Note — The User Label parameter configuration must be limited to a
maximum of 15 characters.
• Polarity
• External State
14 Optionally, click on the Aux Card Specifics tab or IO Card tab to display more
read-only AUX alarm card properties.
15 Click on the OK button to apply the changes and close the Card Slot [Port Number],
AUX, Shelf (Edit) form.
Perform this procedure to configure the OLC parameters and administrative state of a
9500 MPRe port. All other radio port parameters must be configured using the MCT.
1 Choose Equipment from the navigation tree view selector. The navigation tree
displays the Equipment view.
2 Expand the 9500 MPRe icon to the port level and click on a port object. The
Physical Port (Edit) form opens with the General tab displayed.
3 Right-click on the device where you need to configure a 9500 MPRe port and
choose Properties from the contextual menu. The Network Element (Edit) form
opens with the General tab displayed.
4 Configure the Current OLC State and Revert OLC State parameters.
This procedure provides the analog radio statistics for 9500 MPR 1x radio modem ports.
4 On the Network Element (Edit) form navigation tree, expand the Shelf icon.
5 Expand to the port level and click on a port object. The Physical Port (Edit) form
opens with the General tab displayed.
7 In the Select Object Type area, choose Radio Analog Statistics (Radio Equipment)
from the contextual menu.
9 A statistics record appears in the Physical Port (Edit) form. Select the record.
10 Click on the Properties button. The Statistics Record - Radio Analog Statistics form
opens.
11 View the read-only analog performance parameter values for the 1x radio modem
port.
12 Click on the Close button. The Statistics Record - Radio Analog Statistics form
closes.
3 Right-click on the device on which you want to configure power level performance
management and choose Properties from the contextual menu. The Network
Element (Edit) form opens with the General tab displayed.
4 On the Network Element (Edit) form navigation tree, expand the Shelf icon.
5 Expand to the port level and click on a port object. The Physical Port (Edit) form
opens with the General tab displayed.
7 In the Select Object Type area, choose one of the following from the contextual
menu:
9 A statistics record appears in the Physical Port (Edit) form. Select the record.
10 Click on the Properties button. The Statistics Record - RSL/TSL Hop Current Data
Stats form opens.
11 View the read-only power level performance parameter values for the 1x radio
modem port.
12 Click on the Close button. The Statistics Record - RSL/TSL Hop Current Data Stats
form closes.
3 Right-click on the device where you need to configure port segregation and choose
Properties from the contextual menu. The Network Element (Edit) form opens
with the General tab displayed.
4 Click on a shelf object. The Shelf (Edit) form opens with the General tab
displayed.
6 Click on the Create button. The Add Member step form opens.
7 For an EAS module, the Select From Type step is displayed. Choose a value for the
From Type parameter from the drop-down menu and click on the Next button.
8 In the From Port step, click on the Select button beside the From Port field. The
Select From Port - Port Segregation form opens.
10 Click on the OK button. The Select From Port - Port Segregation form closes and
the Add Member step form reappears.
11 For an EAS module, the Select To Type step is displayed. Choose a value for the
To Type parameter from the drop-down menu, and click on the Next button.
12 In the To Port step, choose a port from the list and click on the Finish button. A
dialog box appears.
You can configure the power source type on the following card slots:
1 Choose Equipment from the navigation tree view selector. The navigation tree
displays the Equipment view.
3 Right-click on the device on which you want to configure a power source type and
choose Properties from the contextual menu. The Network Element (Edit) form
opens with the General tab displayed.
4 On the Network Element (Edit) form navigation tree, expand Shelf icon.
5 Expand to the card level and click on a 2+2 × Ethernet (EAS), EASv2, or MSS1 card
slot object. The Card Slot (Edit) form opens with the General tab displayed.
10 The Card Slot (Edit) form reappears. Click on the OK button. A dialog box appears.
11 Click on the Yes button. The Card Slot (Edit) form closes.
PDH and SDH data flow is fragmented and the fragments are transmitted over a
packet-switched 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 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
1 Choose Equipment from the navigation tree view selector. The navigation tree
displays the Equipment view.
2 Expand to the required port level on the required 9500 MPR device.
3 Right-click on the port and choose Properties from the contextual menu. The
Physical Port (Edit) form opens.
• Operation Mode
• Operation Role
8 Click on the Yes button. The Physical Port (Edit) form closes.
Note 1 — The Protection tab only appears for MPT-type ports of EAS
modules if the corresponding spare port is configured as MPT.
Note 4 — In Release 3.0.0, for the 2+2 EAS MPT ports, the protect port
can be chosen as the consecutive port of the same card or the same port
of the corresponding even slot.
2 Expand the 9500 MPR icon, right-click on the 9500 MPR object you need to
configure as the main port of the protection pair, and choose Properties from the
contextual menu. The Network Element (Edit) form opens with the General tab
displayed.
3 On the Network Element (Edit) form navigation tree, expand the Shelf icon.
4 Expand the Card Slot icon and click on the port object that you need to configure.
The Port (Edit) form opens with the General tab displayed.
10 Verify that the protection is enabled. The status of the main port should be Active
and the status of the spare port should be Standby.
Note — If 1+1 HSB is configured as the protection type for an MPT port,
the transmitter must be muted from the NEtO to remove the protection.
1 Choose Equipment from the navigation tree view selector. The navigation tree
displays the Equipment view.
2 Expand the 9500 MPR icon, right-click on the 9500 MPR spare port object, and
choose Properties from the contextual menu. The Network Element (Edit) form
opens with the General tab displayed.
3 On the Network Element (Edit) form navigation tree, expand the Shelf icon.
4 Expand the Card Slot icon and click on the port object that you need to configure.
The Port (Edit) form opens with the General tab displayed.
9 Verify that the protection is removed from the previously main and spare ports.
Perform the steps in this procedure as required on the port type that you are
configuring.
1 Choose Equipment from the navigation tree view selector. The navigation tree
displays the Equipment view.
3 Right-click on the device on which you want to configure a loopback test and
choose Properties from the contextual menu. The Network Element (Edit) form
opens with the General tab displayed.
4 On the Network Element (Edit) form navigation tree, expand the Shelf icon.
5 Expand to the port level and click on a 9500 MPR port object (DS1, ES1, or 1x radio
modem). The Physical Port (Edit) form opens with the General tab displayed.
7 Two interfaces are available - line facing and core facing. Select an interface.
Click on the Properties button.
• Activation
• Timeout Period (Days)
• Timeout Period (Hrs)
• Timeout Period (Mins)
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.
QoS policies define how network traffic is shaped and queued on one or more
9500 MPR and 9500 MPRe devices. You can use the 5620 SAM to create the
following 9500 MPR/9500 MPRe-specific QoS policies to define how network
traffic is shaped and queued and to regulate data throughput on 9500 MPR and
9500 MPRe device ports:
• 9500 ATM QoS policies
• 9500 NE QoS policies
• 9500 Radio interface queue map policies
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.
This section contains procedures relating to the configuration of QoS policies for
9500 MPR and 9500 MPRe devices.
3 Click on the Create button. The 9500 ATM QoS Policy, Global Policy (Create) form
opens with the General tab displayed.
• Auto-Assign ID
• Displayed Name
7 Click on the OK button to save the policy. The ATM QoS Policy (Create) form closes
and the 9500 ATM QoS Policies form reappears.
9 To distribute the 9500 ATM QoS policy, see the “Policies overview” chapter in the
5620 SAM User Guide.
When configuring a 9500 Radio Interface Queue Map policy, the following QoS variants
are supported: ODU, MPT-HL, MPT-HC/MPT-MC.
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.
3 Click on the Create button. The 9500 Radio Interface Queue Map Global Policy
(Create) form opens with the General tab displayed.
• Auto-Assign ID
• ID
• Description
6 Click on the Create button. The 9500 Radio Interface Queue Map Global Policy
(Create) form opens.
7 Configure the parameters in the Radio Interface and Queue Size Settings panels:
Note — You cannot configure the queue size parameters when the
Reset all Queues parameter is selected.
9 Click on the Yes button. The 9500 Radio Interface Queue Map Global Policy
(Create) form closes.
10 Click on the Search button on the 9500 Radio Interface Map Policies form to display
the created policy or policies.
11 To distribute the 9500 Radio Interface Map policy, see the “Policies overview”
chapter in the 5620 SAM User Guide.
3 Click on the Create button. The 9500 NE QOS Global Policy (Create) form opens
with the General tab displayed.
• Auto-Assign ID
• ID
• QoS Classification
• Description
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.
5 Click on the QueueMap policy tab to associate a 9500 Radio Interface Queue Map
Policy.
i Click on the Select button. The Select 9500 Radio Interface Queue Map Policy
form opens.
ii Choose a policy and click on the OK button. The 9500 NE QoS Global Policy
(Create) form reappears.
6 Click on the Apply button. The 9500 NE QoS Global Policy (Create) form closes and
the 9500 NE QOS Global Policy (Edit) form opens.
7 Optionally click on the TMN VLAN tab if you want to configure the DSCP value for
the TMN in-band interfaces, otherwise go to step 8. Configure the following
parameters for both TMN Inband interfaces:
• Enable In-band
• TMN VLAN ID (2 - 4080)
• DSCP
9 Choose a Queue number and click on the Properties button. The RadioQ, Global
Policy (Edit) form opens.
• Queue Number
• Algorithm
• Weight
11 Click on the OK button. The RadioQ, Global Policy (Edit) form closes.
14 Click on the Search button on the 9500 NE QoS Policies form to display the created
policy or policies.
15 To distribute the 9500 NE QoS policy, see the “Policies overview” chapter in the
5620 SAM User Guide.
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.
Note 1 — P2P VLAN services are for users who need to restrict a
VLAN service to two sites. Therefore, adding sites to the P2P VLAN
service is restricted.
Note 2 — P2MP VLAN services are for users who need to have a
VLAN service with two or more sites.
Note 3 — 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.
Protection Type Main switching Spare switching Main status Spare status Radio Direction
criteria/ criteria/ Operative
command command Status(1)
(1 of 2)
Protection Type Main switching Spare switching Main status Spare status Radio Direction
criteria/ criteria/ Operative
command command Status(1)
(2 of 2)
Note
(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).
See Procedure 11-5 for more information about configuring the complete transport
service function.
Profile Node profile VLAN path VLAN path Extension of Terminates NEtO service Service
type type type creation type VLAN path on radio interworking Discovery
(1 of 3)
Profile Node profile VLAN path VLAN path Extension of Terminates NEtO service Service
type type type creation type VLAN path on radio interworking Discovery
(2 of 3)
Profile Node profile VLAN path VLAN path Extension of Terminates NEtO service Service
type type type creation type VLAN path on radio interworking Discovery
(3 of 3)
Notes
(1) Deprecated from the 5620 SAM in Release 11.0R1.
(2) Only supported on ANSI nodes.
• VLAN groups are not mandatory for VLL services; if VLL services are not added
to a VLAN group, VLAN space management is not supported.
• 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.
• The conversion of ring path to tail-based ring path is not supported
• The discovery of VLAN paths and services by the 5620 SAM is based on the
service components deployed on the nodes.
• 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.
• 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.
• You can only discover VLAN services with the 5620 SAM if the nodes are part
of a VLAN group.
• 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.
• Any new VLAN services discovered by the 5620 SAM will be associated with a
P2MP VLAN path, however, existing VLAN services using P2P are untouched.
• 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.
• If a physical link exists between an Ethernet port and a GNE, the Ethernet port
cannot be used as an access or termination port for a hop based VLAN service.
• If the VLAN paths are associated with VLL services, two paths P2P for VLL and
P2M for VLAN are discovered.
• 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.
• 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.
• 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.
• 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.
• Tail termination with LAG is not supported.
• Alarms are not generated for the VLL and VLAN services when the node reboots.
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, and for more service
tunnel information.
Profile Node profile VLAN path VLAN path Extension of Terminates NEtO service Service
type type type creation type VLAN path on radio interworking Discovery
ERP topology
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.
Figure 9-1 9500 MPR ERPS tail node service configuration types (sample 1)
IP/
MPLS
TDM TDM MPLS
ERPS
Eth Ring
Eth 7705 SAR
Ring Tail
TDM
Composite service
23061
Figure 9-2 9500 MPR ERPS tail node service configuration types (sample 2)
IP/
MPLS
Eth ERPS Eth MPLS
Ring
TDM 7705 SAR
TDM
Integrated
Tail
23069
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.
Microwave
TDM
Eth
TMN Fiber
Microwave
TDM
Eth Wireline
TMN network
23948
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 section 10.2 for the workflow to create VLAN services on
9500 MPR devices.
NODE
Microwave Microwave
TAIL_1 TAIL_2
Fiber Fiber
23950
Use the following procedures 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.
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 4 — The Ring Down state cause is not displayed for 9500 MPR
VLAN Services.
Note 5 — The Link Down state cause for 9500 MPR VLL and VLAN
services is not displayed when a link in a ring is down.
3 Click on the Create button. The Radio Ring Component (Create) form opens.
5 Click on the Select button beside the East Port Name parameter. The Select East
Port - Radio Ring Component - new Object form opens.
6 Choose a port for the east port and click on the OK button.
7 Click on the Select button beside the West Port Name parameter. The Select West
Port - Radio Ring Component - new Object form opens.
8 Choose a port for the west port and click on the OK button.
10 Click on the OK button to acknowledge the warning message and to close the Radio
Ring Component new Object (Create) form.
12 Click on the Yes button to proceed. The Network Element (Edit) form closes.
13 Repeat steps 1 to 12 for each 9500 MPR NE that you want to add to your ERSP
topology.
15 Choose Radio Ring (Ethernet Ring) from the Tunnel (Service Tunnel Management)
contextual menu.
16 Click on the Create button and choose Radio Ring from the contextual menu. The
Radio Ring [Create] form opens with the General tab displayed.
• Mgr ID
• Auto-Assign ID
• Name
• Description
• Hold Time Down
• Guard Time
18 Click on the Apply button to make the changes. The Radio Ring, new Object (Edit)
form opens with the General tab displayed.
20 Right-click on the Ring Elements object on the navigation tree and choose one of
the following from the contextual menu:
a Create Ethernet Ring Element. The Select Network Elements form opens. Go
to step 21.
23 Click on the Select button beside the Topology Name parameter. The Select Radio
Ring Topology - Ethernet Ring Element - new object form opens.
24 Select the appropriate ERP topology created in steps 1 to 12. The Ethernet Ring
Element - new object (Create) form opens with the General tab displayed.
26 Double-click on the path A endpoint. The Ethernet Ring Path Endpoint - (Create)
form opens.
29 Click on the OK button to acknowledge the warning message and to close the
Ethernet Ring Path Endpoint - new object (Create) form.
31 Click on the OK button to save the change and close the Ethernet Ring Element
new Object (Create) form.
i Select a site located under Ring Elements icon on the Radio Ring (Edit) form
and choose Properties from the contextual menu. The Ethernet Ring Element
(Edit) form opens with the General tab displayed.
iv Double-click on the endpoint that you want to delegate as the ring protection
link. The Ethernet Ring Path Endpoint - Element - Node form opens with the
General tab displayed.
v Set the Path Endpoint Type parameter to the Ring Protection Link End.
vi Click on the OK button to save the changes and close the Ethernet Ring Path
Endpoint - Element - Node form. The Ethernet Ring Element (Edit) form
reappears.
vii Click on the OK button to save the changes and close the Ethernet Ring
Element (Edit) form. A confirmation window appears.
34 As required, add existing ring elements to the radio ring by performing the
following:
i Right-click on the Ring Elements icon on the Radio Ring (Edit) form and
choose Add Existing Element from the contextual menu. The Select Elements
form opens.
i Select all the sites located under Ring Elements icon on the Radio Ring (Edit)
form and choose Turn Up from the contextual menu. A confirmation window
appears.
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.
Note 2 — When you create a VLL or VLAN service for the 9500 MPR,
select the Ring Based path type.
Note 3 — The 5620 SAM allows you to discover fiber Ethernet rings
created by the NEtO.
The following workflow describes the sequence of high-level tasks required to configure
a composite service with VLAN service on a 9500 MPR device and VPLS on a 7210 SAS
device.
2 Configure Ethernet CFM MD, MEG, NE MEG, and MEP. See “To configure an
Ethernet CFM MD and subordinate objects associated with the MD” in the
5620 SAM User Guide.
3 Configure an Ethernet (G.8032) ring on the 7210 SAS device. See “To create an
Ethernet (G.8032) ring” in the 5620 SAM User Guide.
4 Configure a VPLS on 7210 SAS device. See “To create a VPLS” in the 5620 SAM User
Guide.
6 Configure a composite service between the services created in step 4 and step 5.
See “Composite service management procedures” in the 5620 SAM User Guide.
See Procedure 10-1 for more information about creating VLAN groups.
See Procedure 10-2 for more information about creating VLAN paths.
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.
1 Remove any inconsistencies created due to MIB population failures that can occur
during service creation on a 9500 MPR NE; see Procedure 4-2.
2 Create VLAN groups and add members to each group; see Procedure 10-1.
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 Procedure 10-2.
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
Procedure 7-1.
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 Procedure 10-5.
a View the VLAN service operational status or view the service topology map
associated with a VLAN service; see the 5620 SAM User Guide.
d Modify or delete a VLAN service; see the 5620 SAM User Guide.
Use the following procedures to perform VLAN service creation and management
tasks for 9500 MPR devices.
2 Click on the Create button. The VLAN Group (Create) form opens with the General
tab displayed.
• Group Name
• Description
• Node Type
• Topology
• VLAN Space Management by SAM
You can configure the VLAN Space Management by SAM parameter when the Node
Type parameter is set to 9500.
6 Click on the Create button. The Select Network Elements form opens and a list of
available NEs appears. Only NE types specified by the Node Type parameter are
displayed in the list.
7 Choose one or more NEs and click on the OK button. A dialog box appears.
8 Click on the OK button. The selected NEs are listed in the VLAN Group (Edit) form.
9 If you need to apply a span of control to a group, other than the default, click on
the Spans tab. Otherwise, go to step 10.
i Click on the Add button. The Select Span(s) - VLan Group form opens with a
list of available spans.
iii Click on the OK button. The Select Span(s) - VLan Group form closes and a
dialog box appears.
11 Click on the Yes button. The VLAN Group (Edit) form closes.
Note 3 — You can also use this procedure to provision a VLAN path for
a tail node.
1 Choose Manage→VLAN→Paths from the 5620 SAM main menu. The Manage VLAN
Paths form opens.
2 Click on the Create button. The Create VLAN Path step form opens with the Path
Type step displayed.
• Name
• Description
• Creation Type
The Creation Type parameter appears when the Path Type parameter is set to
Hop Based.
6 Click on the Next button. For ring-based VLAN paths, the Select Ring step appears.
For hop-based VLAN paths, the Specify Vlan Path Constraints step appears.
a If you set the Path Type parameter option to Ring Based, go to step 8.
b If you set the Path Type parameter option to Hop Based, go to step 18.
8 Click on the Select button. The Select Ring - VLAN Path form opens.
9 Choose a radio ring from the list and click on the OK button. The Select Ring - VLAN
Path form closes and the ID of the selected Radio Ring appears in the Mgr ID
parameter.
10 Configure the following parameters if a tail node needs to be attached to the ring
element; otherwise, go to step 48.
• Has Tail
• Is Point to Multipoint
Configure the Has Tail parameter if you need standard VLAN paths for the tail
node. Configure the Is Point to Multipoint parameter if you need dot1q VLAN paths
for the tail node.
11 Click on the Next button. The Define the Provisioned Path step opens.
12 Click on the Insert Hop button. The Hop for New Vlan Path [Create] form opens.
13 Click on the Select button to add a network element to the VLAN path. The Select
a Network Element - New VLAN Path form opens.
14 Choose a Network Element and click on the OK button. The Hop for New Vlan Path
[Create] form reappears.
15 Click on the Select button to add a radio link to the VLAN path. The Select Links -
New VLAN Path form appears.
16 Choose a radio link and click on the OK button. The Hop for New Vlan Path [Create]
form closes and the Define the Provisioned Path step reappears.
b Click on the Finish button and close button to complete the provisioning of
the VLAN path on a tail node.
a Set the Creation Type parameter option to Manual. The Specify Vlan Path
Constraints step opens. Go to step 19.
b Set the Creation Type parameter option to Auto or Point 2 Point. The Specify
Vlan Path Constraints step opens. Go to step 30.
20 Click on the Next button. The Define Source Site step appears.
21 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 the Provisioned Path step appears.
23 Click on the Insert Hop button to insert a VLAN path hop. The Hop for New VLAN
Path (Create) form opens.
24 Click on the Select Network Element button. The Select a Network Element - New
VLAN Path form opens.
25 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.
26 Click on the Select Link button. The Select Links - New Vlan Path form opens.
28 If you need to add another hop, click on the Apply button and repeat steps 23
to 27. Click on the OK button after you add the required hops.
29 Close the Hop for New VLAN Path (Create) form. Go to step 48.
• Max Sites
• Minimum Bandwidth (kbps)
• Select Shortest Path
b If you set the Creation Type parameter option in step 5 to Point 2 Point, go
to step 38.
32 Click on the Next button. The Specify if the Vlan Path is a Point to Multipoint step
appears.
35 Click on the Select button. The Select a Network Element - Define Head End form
opens. Choose a 9500 MPR from the list and click on the OK button. The Select a
Network Element - Define Head End form closes and the IP address of the selected
9500 MPR appears in the Head End parameter.
36 Click on the Next button. The Possible Vlan Paths step appears.
37 Choose one or more possible VLAN paths and click on the OK button. Go to Step 48.
38 Click on the Next button. The Define Source Site step appears.
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.
40 Click on the Next button. The Define Destination Site step appears.
41 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.
42 Click on the Next button. The Possible Vlan Paths step appears.
43 Click on the Insert Hop button to insert a VLAN path hop. The Hop for New VLAN
Path (Create) form opens.
44 Click on the Select Network Element button. The Select a Network Element - New
VLAN Path form opens.
45 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.
46 If you need to add another hop, click on the Apply button and repeat steps 44
and 45. Click on the OK button after you add all hops.
49 Click on the Close button. The Create VLAN Path form closes.
Perform the following procedures before creating a 9500 MPR (dot1q) VLAN service, as
required:
• Create a VLAN path if you need to assign a specific VLAN path to the 9500 MPR
(dot1q) VLAN service; see Procedure 10-2.
• 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
Procedure 7-1.
1 Right-click on a 9500 MPR object in the navigation tree and choose Properties from
the contextual menu. The Network Element (Edit) form opens with the General
tab displayed.
2 Click on the System Settings tab and set the Bridge Type parameter to 802.1Q.
4 Choose Create→Service→VLAN from the 5620 SAM main menu. The VLAN Service
(Create) form opens with the General tab displayed.
5 Click on the Select button to choose a customer to associate with the 9500 (dot1q)
VLAN service. The Select Customer - VLAN Service form opens.
6 Choose a customer for the 9500 MPR (dot1q) VLAN service and click on the OK
button. The Select Customer - VLAN Service form closes and the VLAN Service
(Create) Service form reappears with the customer information displayed on the
General tab.
The Current OLC State and Revert OLC State parameters are configurable when
you click on the Apply button on the VLAN Service (Create) form.
8 Click on the VLAN tab and set the Application parameter to 9500 VLAN.
9 Click on the Select button in the Group panel to choose a VLAN group to associate
with the 9500 MPR (dot1q) VLAN service. The Select Group - VLAN Service form
opens.
10 Choose a VLAN group and click on the OK button. The Select Group - VLAN Service
form closes and the VLAN Service (Create) form reappears with the group
information displayed.
a Enable the Auto-Assign ID parameter. The 5620 SAM chooses the VLAN ID
when the Auto-Assign ID parameter is enabled.
b Disable the Specify VLAN Path parameter to specify a VLAN path by clicking
on the Select button in the VLAN path panel. Go to step 15.
• Path Type
• Point to Point VLAN
The Point to Point VLAN parameter is configurable when the Path Type
parameter is set to Hop Based.
Note 1 — To create a 9500 MPR VLAN service on an ERPS tail node, set
the Path Type parameter to Ring Based.
Note — If you choose the Ring Based option for the Path Type
parameter in step 13, only P2MP paths are listed. You cannot use a P2P
path with a tail VLAN Path on a 9500 MPR Ring Based VLAN.
15 Choose a VLAN Path and click on the OK button. The Select VLAN Path - VLAN
Service form closes and the VLAN Service (Create) form reappears with the group
information displayed.
Note — The VLAN path may consist of a P2P, P2MP, or Has Tail VLAN
path, and consecutive physical links, non-consecutive physical links, or
radio links spanning NEs.
16 In the navigation tree, right-click on VLAN Service and choose Create VLAN Site.
The Select Network Elements - VLAN Service form opens.
17 Choose a site and click on the OK button. The Select Network Elements - VLAN
Service form closes and the VLAN Site (Create) form opens with the site
information displayed on the General tab.
• Description
• Administrative State
• Monitor Access Interface Operational State
19 Click on the OK button. The VLAN Site (Create) form closes and a dialog box
appears.
20 Click on the OK button. The VLAN Service (Create) form reappears with the new
site information displayed in the service navigation tree.
21 In the navigation tree, click on the site with which you need to associate the new
access interface; expand the entries for the site.
22 Right-click on L2 Access Interfaces and choose Create VLAN Access Interface. The
VLAN Access Interface (Create) form opens with the General tab displayed.
• Description
• Administrative State
25 Click on the Select button to choose a port for the VLAN access interface. The
Select Terminating Port - VLAN Access Interface form opens.
Note 1 — 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.
Note 2 — 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.
Note 3 — For a ring-based VLAN service, you can add a radio port of a
ring or tail node as an access interface.
26 Use the configurable filter and Search button to choose a port for the VLAN access
interface, and click on the OK button. The Select Terminating Port - VLAN Access
Interface form closes, and the VLAN Access Interface (Create) form displays the
port information.
• VLAN Tagging
• Provider Bridge Type
• S-VLAN TPID
• Priority of UNI
28 Click on the OK button. The VLAN Access Interface (Create) form closes, and a
dialog box appears.
29 Click on the Apply button to save the changes. The VLAN Service (Create) form
closes.
Perform the following procedures before you create a 9500 MPR (dot1ad) VLAN service.
1 Right-click on a 9500 MPR in the navigation tree and choose Properties from the
contextual menu. The 9500 MPR properties form opens with the General tab
displayed.
2 Click on the System Settings tab and set the Bridge Type parameter to 802.1ad.
4 Right-click on the 9500 MPR Ethernet port and choose Properties from the
contextual menu. The Physical Port (Edit) form opens with the General tab
displayed.
5 Click on the Ethernet tab and configure the provider bridge configuration
parameters:
Note 1 — When the Provider Bridge Type parameter is set to NNI, the
S-VLAN TPID parameter can be configured.
Note 2 — When the Provider Bridge Type parameter is set to UNI, UNI
priority parameter can be configured.
i Click on the Ingress Mapping tab and click on the Create button. The Ingress
C-VLAN/S-VLAN Mapping (Create) form opens.
• C Vlan ID
• SVlan Priority Inherited
• Remove C-Vlan ID
Note 1 — The value for the S Vlan ID parameter is set to 1 and cannot
be configured.
Note 2 — Only one of the ingress mapping entries can have the Remove
C-Vlan ID check box selected.
iii Click on the OK button. The Ingress C-VLAN/S-VLAN Mapping (Create) form
closes and the Ingress Mapping tab and a dialog box appears.
vii Click on the Egress Mapping tab. The C-VLAN/S-VLAN mapping entry appears
in the egress mapping list.
viii Choose the entry and click on the Properties button. The Egress
C-VLAN/S-VLAN Mapping (Edit) form opens.
Note — The value for the S Vlan ID parameter is set to 1 and cannot be
configured.
9 Choose Create→Service→VLAN from the 5620 SAM main menu. The VLAN (Create)
Service form opens with the General tab displayed.
10 Click on the Select button to choose a customer to associate with the 9500 MPR
(dot1ad) VLAN service. The Select Customer - VLAN Service form opens.
11 Choose a customer for the 9500 MPR (dot1ad) VLAN service and click on the OK
button. The Select Customer - VLAN Service form closes and the VLAN (Create)
Service form reappears with the customer information displayed on the General
tab.
• Service ID • Description
• Service ID • Service Tier
• SVC Mgr Service ID • Service Priority
• Service Name • Administrative State
13 Click on the VLAN tab and set the Application parameter to 9500 VLAN.
14 Click on the Select button in the Group panel to choose a VLAN group to associate
with the 9500 MPR (dot1ad) VLAN service. The Select Group - VLAN Service form
opens.
15 Choose a VLAN group and click on the OK button. The Select Group - VLAN Service
form closes and the VLAN (Create) form reappears with the group information
displayed.
a Enable the Auto-Assign ID parameter. The 5620 SAM chooses the VLAN ID
when the Auto-Assign ID parameter is enabled.
b Disable the Specify VLAN Path parameter to specify a VLAN path by clicking
on the Select button in the VLAN path panel. Go to step 20.
• Path Type
• Point to Point VLAN
The Point to Point VLAN parameter is configurable when the Path Type
parameter is set to Hop Based.
20 Choose a VLAN Path and click on the OK button. The Select VLAN Path - VLAN
Service form closes and the VLAN (Create) form reappears with the group
information displayed.
• P2P
• P2MP
• Tail VLAN path
• consecutive physical links
• non-consecutive physical links
• radio links spanning NEs
21 Choose 802.1AD as the bridge type from the Bridge Type drop-down menu and
click on the Apply button. The service is created and VLAN Path Instance appears
in the navigation tree.
22 In the navigation tree, right-click on VLAN and choose Create VLAN Site. The
Select Network Elements - VLAN form opens.
23 Choose a site and click on the OK button. The Select Network Elements - VLAN
form closes and the Site (Create) form opens with the site information displayed
on the General tab.
• Description
• Administrative State
• Monitor Access Interface Operational State
25 Click on the OK button. The Site (Create) form closes and a dialog box appears.
26 Click on the OK button. The VLAN (Create) form reappears with the new site
information displayed in the service navigation tree.
28 In the navigation tree, click on the site with which you need to associate the new
access interface; expand the entries for the site.
29 Right-click on L2 Access Interfaces and choose Create VLAN Access Interface. The
VLAN Access Interface (Create) form opens with the General tab displayed.
• Description
• Administrative State
32 Click on the Select button to choose a port for the VLAN access interface. The
Select Terminating Port - VLAN Access Interface form opens.
Note 1 — 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.
Note 2 — 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.
33 Use the configurable filter and Search button to choose a port for the VLAN access
interface, and click on the OK button. The Select Terminating Port - VLAN Access
Interface form closes, and the VLAN Access Interface (Create) form displays the
port information.
• VLAN Tagging
• Provider Bridge Type
• S-VLAN TPID
• Priority of UNI
When the Provider Bridge Type is set to NNI, the UNI Priority parameter options
are dimmed. When the Provider Bridge Type is set to UNI, the S-VLAN TPID
parameter options are dimmed.
35 If you set the VLAN Tagging parameter to Untagged and the Provider Bridge Type
parameter to UNI (C-Vlan Based) in step 34, perform the following steps to
configure the C-VLAN/S-VLAN mapping.
Note — You can configure C-VLAN/S-VLAN mapping also for LAG and
ring-based services.
i Click on the Ingress Mapping tab and click on the Create button. The Ingress
C-VLAN/S-VLAN Mapping (Create) form opens.
• C Vlan ID
• SVlan Priority Inherited
• Remove C-Vlan ID
Note — Select the Remove C-Vlan ID check box for any one of the
ingress mapping entries.
iii Click on the OK button. The Ingress C-VLAN/S-VLAN Mapping (Create) form
closes. The new C-VLAN/S-VLAN mapping entry appears in the ingress
mapping list upon clicking the Search button.
iv Click on the Egress Mapping tab. The C-VLAN/S-VLAN mapping entry appears
in the egress mapping list.
v Choose the entry and click on the Properties button. The Egress
C-VLAN/S-VLAN Mapping (Edit) form opens.
vii Click on the OK button. The Egress C-VLAN/S-VLAN Mapping (Edit) form
closes and the Egress Mapping tab reappears.
36 Click on the OK button. The VLAN Access Interface (Create) form closes, and a
dialog box appears.
37 Click on the OK button. The VLAN - Service Name (Edit) form reappears with the
new interface displayed in the service navigation tree under Access Interfaces for
the specified site.
38 Click on the Apply button to complete the configuration. The provider bridge is
configured.
Procedure 10-5 To create a CoS rate limiter per VLAN on a 9500 MPR
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.
1 Choose Equipment from the navigation tree view selector. The navigation tree
displays the Equipment view.
3 Right-click on the port object and choose Properties from the contextual menu.
The Physical Port (Edit) form opens with the General tab displayed.
4 Click on the CoS Rate Limiter tab and click on the Create button. The CoS Rate
Limiter (Create) form opens.
5 Click on the Select button and choose a Port Binding VLAN ID from the list. Click
on the OK button.
• PCP
• Ingress CIR (kbps)
• Ingress Max Burst (Kbytes)
8 Click on the OK button. The CoS Rate Limiter (Create) form closes.
The 9500 MPR services are not discovered automatically during NE discovery. Perform
this procedure after all 9500 MPR NEs are synchronized in the 5620 SAM.
Note 2 — 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.
2 Click on the Discover MPR 9500 Services button and choose one of the following
options:
• Hop Based
• Ring Based
The Ring Based option discovers both VLL and VLAN services associated with
the ring and tail.
The Discover MPR 9500 Services form opens with the network groups in the list.
3 Choose a network group and click on the OK button. The Discover MPR 9500
Services form closes and the Manage Services form reappears.
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 Click on the Search button. The discovered services appear in the Manage Services
form.
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.
Note 1 — You must delete all of the members from a group before you
can delete the group.
2 Apply a filter, or create and apply a filter, and click on the Search button. A list
of VLAN groups appears.
4 Click on the Properties button. The VLAN Groups (Edit) form opens with the
General tab displayed.
6 If the group does not contain any members, go to step 9. Otherwise, go to step 7.
7 Choose one or more members of the VLAN group and click on the Delete button.
A dialog box appears.
9 Close the VLAN Groups (Edit) form. The Manage VLAN Groups form reappears.
10 Choose the VLAN group that you need to delete from the displayed list.
Note — You cannot delete a VLAN path if the path is being used by a
service.
1 Choose Manage→VLAN→Paths from the 5620 SAM main menu. The Manage VLAN
Paths form opens.
2 Apply a filter, or create and apply a filter, and click on the Search button. 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: Discovered-VLANPath-<IP address of the source 9500 MPR>-<IP
address of the destination 9500 MPR.
3 Choose a VLAN path and click on the Delete button. The VLAN path and all of the
associated hops are deleted.
The 5620 SAM supports the provisioning of VLL 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 VLAN service creation.
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 device-specific VLL service
types and functions:
1 Remove any inconsistencies created due to MIB population failures that can occur
during service creation on a 9500 MPR NE; see Procedure 4-2.
2 Create VLAN groups and add members to each group; see Procedure 10-1.
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 Procedure 10-2.
a 9500 MPR (ETSI only) VLL Apipe services; see Procedure 11-1.
5 Fix failed cross-connections on a 9500 MPR VLL Cpipe service, as required; see
Procedure 11-5.
6 Configure a GNE site on a 9500 MPR VLL Apipe or Cpipe service; see
Procedure 11-6.
a View the VLL service operational status or view the service topology map
associated with a VLL service; see the 5620 SAM User Guide.
d Modify or delete a VLL service; see the 5620 SAM User Guide.
Use the following procedures to perform VLL service creation and management
tasks for 9500 MPR devices.
Procedure 11-1 To create a VLL Apipe service on the 9500 MPR (ETSI
only)
1 Choose Create→Service→9500 VLL→Apipe (ATM to ATM/Eth) from the 5620 SAM
main menu. The 9500 MPR Apipe Service (Create) form opens with the General tab
displayed.
2 Click on the Select button to choose a customer to associate with the Apipe
service. The Select Customer - 9500 MPR Apipe Service form opens.
3 Choose the Default Customer as the customer for the Apipe service and click on
the OK button. The Select Customer - 9500 MPR Apipe Service form closes and the
9500 MPR Apipe Service (Create) form reappears with the customer information
displayed.
The Current OLC State parameter is configurable when you click on the Apply
button.
5 Perform the following procedure if the Specify VLAN Path parameter check-box is
selected in step 4.
i Click on the Select button to choose a VLAN path to associate with the Apipe
service. The Select VLAN Path - 9500 MPR Apipe Service form opens.
ii Choose a VLAN path and click on the OK button. The Select VLAN Path -
9500 MPR Apipe Service form closes and the 9500 MPR Apipe Service (Create)
form reappears with the VLAN path information displayed on the General
tab.
• VLAN ID
• Auto-Assign ID
• Service Class
• PW Label
• Auto-Assign ID
• VC Type
The VLAN ID and PW Label parameters are enabled when the Auto-Assign ID
parameters are disabled.
7 Configure the MAC Address parameter, if you configured the Service Class
parameter as ATM to Eth in step 6.
8 Right-click on the 9500 MPR Apipe Service on the navigation tree and choose
Create 9500 MPR Apipe Site from the contextual menu. The Select Network
Element form opens.
For information about adding a GNE site to a VLL service, see Procedure 11-6.
9 Choose an NE from the list and click on the OK button. The Select Network
Element form closes and the 9500 MPR Apipe Site (Create) form opens with the
General tab displayed.
• Name
• Description
12 Right-click on L2 Access Interfaces and choose Create 9500 MPR Apipe L2 Access
Interface. The 9500 MPR Apipe L2 Access Interface (Create) form opens with the
General tab displayed.
• Name
• Description
15 Click on the Select button to choose a terminating port for the L2 access interface.
The Select Terminating Port - 9500 MPR Apipe L2 Access Interface form opens.
16 Use the configurable filter and Search button to choose a port, and click on the
OK button. The Select Terminating Port - 9500 MPR Apipe L2 Access Interface form
closes, and the 9500 MPR Apipe L2 Access Interface (Create) form displays the port
information.
Note 1 — If ports on a card slot of the 2+2 × Ethernet (EAS) card are
used to create the Apipe service, first configure the Profile Name
parameter on the card slot. See Procedure 7-11 for information about
how to configure this parameter.
a If you selected a value of VCC for the VC Type parameter, go to step 18.
b If you selected a value of VPC for the VC Type parameter, go to step 19.
21 Click on the Select button to choose an Ingress ATM Policy. The Select Ingress ATM
Policy - ATM Configuration form opens.
22 Use the configurable filter and Search button to choose a policy, and click on the
OK button. The Select Ingress ATM Policy - ATM Configuration form closes, and the
L2 Access Interface (Create) form displays the policy information.
23 Click on the Select button to choose an Egress ATM Policy. The Select Egress ATM
Policy - ATM Configuration form opens.
24 Use the configurable filter and Search button to choose a policy, and click on the
OK button. The Select Egress ATM Policy - ATM Configuration form closes, and the
L2 Access Interface (Create) form displays the policy information.
26 Click on the OK button. The L2 Access Interface (Create) form closes, and the
Apipe Site (Create) form reappears with the new interface information displayed
in the service navigation tree.
a Create another site for the VLL service, if required. Repeat steps 8 to 26.
b Go to step 28.
You can use the service topology maps to view the service.
2 Click on the Select button to choose a customer to associate with the Cpipe
service. The Select Customer - Cpipe Service form opens.
3 Choose the Default Customer as the customer for the Cpipe service and click on
the OK button. The Select Customer - Cpipe Service form closes and the Cpipe
Service (Create) form reappears with the customer information displayed.
The Current OLC State parameter is configurable when you click on the Apply
button.
Note — To create a 9500 MPR Cpipe service with an ERPS tail node, set
the Path Type parameter to Ring Based.
5 Click on the Select button to choose a VLAN path to associate with the Cpipe
service. The Select VLAN Path - Cpipe Service form opens.
Note 2 — 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 Alcatel-Lucent technical support representative
for alternative VLL Cpipe service configuration options.
6 Choose a VLAN path and click on the OK button. The Select VLAN Path - Cpipe
Service form closes and the Cpipe Service (Create) form reappears with the VLAN
path information displayed on the General tab.
• Auto-Assign ID
• VLAN ID
9 If you specified the CEM to Eth option in step 8, configure the parameters:
• EC ID Tx/Rx
• Auto-Assign ID
• Clock Source
• Mac Address
10 If you set the Service Class parameter to the SDH to SDH option in step 8, configure
the parameters:
• Clock Source
• Jitter Buffer Depth
11 In the navigation tree, right-click on a 9500 MPR Cpipe Service and choose Create
Cpipe Site. The Select Network Elements - Cpipe Service form opens with a list of
available 9500 MPR sites.
For information about adding a GNE site to a VLL service, see Procedure 11-6.
12 Choose a site and click on the OK button. The Select Network Elements - Cpipe
Service form closes and the Cpipe Site (Create) form opens with the General tab
displayed.
• Name
• Description
• Administrative State
• Monitor Access Interface Operational State
• Name
• Description
18 Click on the Select button to choose a port for the L2 access interface. The Select
Terminating Port - L2 Access Interface form opens.
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.
19 Use the configurable filter and Search button to choose a port, and click on the
OK button. The Select Terminating Port - L2 Access Interface form closes, and the
L2 Access Interface (Create) form displays the port information.
21 Click on the OK button. The L2 Access Interface (Create) form closes, and the
Cpipe Site (Create) form reappears with the new interface information displayed
in the service navigation tree.
22 If the 9500 MPR Cpipe service is for an ERPS tail node, a radio or Ethernet
termination port is required for the site:
ii Click on the Select button to choose an ERPS tail terminating port. The Select
ERPS Tail Terminating Port - Cpipe Site form opens.
iii Choose an ERPS tail terminating port and click on the OK button. The Cpipe
Site (Create) form reappears.
23 If you need to create another L2 access interface for the site in the Cpipe service,
repeat steps 15 to 21.
a Create an another site for the VLL service, if required. Repeat steps 11
to 21 .
b Go to step 25.
You can use the service topology maps to view the service.
You must configure a physical link between the 9500 MPR MSS-8, MSS-4, or MSS-1 port
and the MSS1c before performing this procedure. See the procedure “To create a
physical link” in the 5620 SAM User Guide for more information about configuring a
physical link.
2 Click on the Select button to choose a customer to associate with the Cpipe
service. The Select Customer - 9500 MPR Cpipe Service form opens.
3 Choose the Default Customer as the customer for the Cpipe service and click on
the OK button. The Select Customer - Cpipe Service form closes and the Cpipe
Service (Create) form reappears with the customer information displayed.
• Service ID
• Auto-Assign ID
• SVC Mgr Service ID
• Service Name
• Description
• Service Priority
6 In the navigation tree, right-click on a 9500 MPR Cpipe Service and choose Create
9500 MPR Cpipe Site. The Select Network Elements - 9500 MPR Cpipe Service form
opens with a list of available 9500 MPR sites.
7 Choose a 9500 MPR site and click on the OK button. The Select Network Elements
- Cpipe Service form closes and the 9500 MPR Cpipe Site (Create) form opens with
the General tab displayed.
• Name
• Description
10 Click on the Select button to choose a port. The Select Network Port form opens.
11 Choose a port that is configured with the physical link to the MSS1c and click on
the OK button. The Select Network Port form closes and the port information
appears in the 9500 MPR Cpipe Site (Create) form.
12 Click on the Interfaces tab and click on the Create button. The 9500 MPR Cpipe L2
Access Interface (Create) form opens with the General tab displayed.
• Name
• Description
15 Click on the Select button to choose a port for the L2 access interface. The Select
Terminating Port - 9500 MPR Cpipe L2 Access Interface form opens.
16 Choose a port and click on the OK button. The Select Terminating Port - 9500 MPR
Cpipe L2 Access Interface form closes and the 9500 MPR Cpipe L2 Access Interface
(Create) form displays the port information.
18 Click on the OK button. The L2 Access Interface (Create) form closes, and the
Cpipe Site (Create) form reappears with the new interface information displayed
in the service navigation tree.
2 Click on the Discover MPR 9500 Services and choose Hop Based from the contextual
menu. The Discover MPR 9500 Services form opens with a list of equipment groups.
3 Choose the equipment group containing the 9500 MPR devices and click on the OK
button. The Discover MPR 9500 Services form closes and the Manage Service form
reappears with a list of services.
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
cross-connect.
Note — You must clear deployment errors that are associated with a
failed cross-connect before you attempt to re-establish the
cross-connect.
1 Choose Manage→Service→Services from the 5620 SAM main menu. The Manage
Services form opens.
2 Configure the filter criteria for the service type that you need to find and click on
the Search button. A list of services appears.
3 Choose a 9500 MPR Cpipe service and click on the Properties button. The Cpipe
Service (Edit) form opens with the General tab displayed.
Perform this procedure to add a GNE site and GNE service interfaces to a VLL service.
This procedure applies to 9500 MPR VLL Apipe and Cpipe services.
1 Choose Manage→Service→Services from the 5620 SAM main menu. The Manage
Services form opens.
3 Select a VLL service and click on the Properties button. The VLL_type Service
(Edit) form opens with the General tab displayed.
4 On the component tree, right-click on VLL_type Service and choose Create GNE
Site. The Select Network Elements - VLL_type Service form opens with a list of
available NEs.
5 Choose a site and click on the OK button. The GNE Site (Create) form opens with
the General tab displayed.
• Name
• Description
8 To configure an interface for the GNE site, perform the following steps:
i Click on the GNE Service Interfaces tab and click on the Create button. The
GNE Service Interface (Create) form opens with the general tab displayed.
• Name
• Description
• Type
iii Click on the Ports tab and click on the Select button beside the Interface
Index field. The Select Generic NE Interface form opens.
iv Choose an interface from the list and click on the OK button. The GNE Service
Interface (Create) form reappears with the interface information displayed.
• Encapsulation Type
• Outer Encapsulation Value
• Inner Encapsulation Value
vi Click on the OK button. The GNE Site (Create) form reappears with the
interface information displayed in the service component tree.
9 Click on the Scripts tab to attach or run configuration scripts on the GNE site.
The Scripts tab displays the script instances and versions that are applied to the
device. See the 5620 SAM Scripts and Templates Developer Guide.
10 Click on the OK button. The VLL_type Service (Edit) form reappears with the new
information displayed in the service component tree.
You can use the topology maps to view the service. See the topology map
management chapter in the 5620 SAM User Guide for more information.
Appendices
System administration
Scalable system Y Y
Security management (user profiles, login Y Y (see note) Same profile as 5620 SAM user Y
check, password rules etc.)
User access profiles Y Y (see note) Same profile as 5620 SAM user Y
Community string Y Y Y
NEtO TACACS+ support Y Y (see note) NEtO cross launch with null for Y
TACACS+
SNMPv3 support Y Y Y
Graphic environment
NE creation/discovery N/A Y Y
Map: automatic radio link discovery N/A Y Maps are a 5620 SAM-EAP feature N
Map: automatic traffic ports discovery (LLDP) N/A Y Maps are a 5620 SAM-EAP feature N
NE administration
(1 of 5)
Port segregation Y Y Y
Loopbacks Y Y Y
SWDL on NE base Y Y Y
Backup on NE base Y Y Y
Restore on NE base Y Y Y
Alarms
Representation in NE Y Y Y
Alarm synthesis Y Y Y
Alarm severity assignment profile Y Y (see note) since 9500 MPR Release 3.0; Y
requires opening NEtO
Vertical correlation (9500 MPR transport - N Y 5620 SAM-EAP E2E services and N
7705 SAR services) transport
Performance management
PM visualization Y Y Y
- PM radio: G.826 Y Y Y
- PM E1 framed Y Y Y
- PM adaptive modulation Y Y Y
(2 of 5)
- PM plotter Y Y N
- PM AM/radio/Ethernet elaboration Y N N
- PM AM/radio/Ethernet TCA Y N N
Specific protections
Status/configuration - XPIC (1+1 redundancy) Y Y (see note) XPIC configuration form; status Y
and labels through NEtO
Status/configuration - virtual protection links Y Y (see note) VPC configuration form / status Y
(VCL) and labels through NEtO
Status/configuration - ERP 8032 ring Y Y (see note) Ring (No Services) - Release 3.3 Y
and Release 3.4
Network management (up to thousands of NEs) N (see Y Limited to few NEs of the same Y
note) type
Centralized management of PM N Y Y
Service Provisioning
Service profiles
(3 of 5)
L2 BRIDGED - E2E DOT1Q PTP service NE Y Full 5620 SAM E2E services and N
based automated X-connection
L2 BRIDGED - E2E DOT1Q P2MP service NE Y Full 5620 SAM E2E services and N
based automated X-connection
L2 BRIDGED - E2E DOT1Q P2MP service NE Y Full 5620 SAM E2E services and N
based automated X-connection
L2 service maps (eg. transport service N/A Y Full 5620 SAM E2E services N
connectivity)
L2 per service alarms (filtered per view) N/A Y Full 5620 SAM E2E services N
NEtO - 5620 SAM service interworking N/A Y Allows NEtO and 5620 SAM N
service configuration
P2P path creation and visualization N Y Network L2 Route & metric / hop N
cost - e2e correlation
(4 of 5)
P2MP Path (bridging) creation and visualization N Y Network L2 Route & metric / hop N
cost - e2e correlation
QoS policy distribution and audit N Y starting with 9500 MPR Release N
3.2 including policy bundling
CAC management N Y N
Service in service - path to 7705 SAR service N Y Alarm correlation from radio / N
impact path to services
(5 of 5)
Customer documentation
Customer Documentation Welcome Page
Technical Support
http://support.alcatel-lucent.com
Documentation feedback
documentation.feedback@alcatel-lucent.com
Release 13.0 R2 | May 2015 | 3HE 09803 AAAB TQZZA Edition 01
www.alcatel-lucent.com