Sei sulla pagina 1di 164
5620 SAM SERVICE AWARE MANAGER 14.0 R7 MPR User Guide 3HE-10693-AAAE-TQZZA Issue 1 December 2016

5620 SAM SERVICE AWARE MANAGER 14.0 R7

MPR User Guide

3HE-10693-AAAE-TQZZA

Issue 1 December 2016

5620 SAM

Legal notice

Nokia is a registered trademark of Nokia Corporation. Other products and company names mentioned herein may be trademarks or tradenames of their respective owners.

The information presented is subject to change without notice. No responsibility is assumed for inaccuracies contained herein.

© 2016 Nokia.

5620 SAM

Contents

About this document

7

1 Safety information

9

1.1

Structure of safety statements

9

2 What’s new?

11

 

2.1 Overview

11

2.2 What’s new in 5620 SAM Release 14.0 for 9500 MPR

11

3 9500 MPR Overview

17

3.1 9500 MPR device support

17

3.2 9500 MPR card support

19

3.3 Supported 9500 MPR device objects and auxiliary equipment

19

3.4 9500 MPR statistics support

24

3.5 To configure radio interface performance management statistics at the port level

26

3.6 To configure bulk changes for radio interface performance management statistics

27

3.7 9500 MPR NEtO support

28

 

3.8 WebCT

30

3.9 To open WebCT from the 5620 SAM

30

3.10 Workflow to manage 9500 MPR devices

31

4 9500 MPR device commissioning and management

35

4.1 General description

35

4.2 9500 MPR management

35

4.3 Workflow to commission and manage 9500 MPR devices

41

4.4 To prepare a 9500 MPR for 5620 SAM management

42

4.5 To configure polling for an 9500 MPR

44

4.6 To collect 9500 MPR statistics from a 5620 SAM auxiliary server

45

4.7 To enable 5620 SAM management of 9500 MPR devices

45

5 9500 MPR software upgrade

49

5.1 Software upgrade workflow

49

5.2 To perform an on-demand 9500 MPR software upgrade

50

5.3 To manage the 9500 MPR running software

51

5620 SAM

6 9500 MPR migration to revised service model

53

6.1 Migration workflow

53

6.2 To perform pre-upgrade tasks

53

6.3 To perform post upgrade tasks

54

7 9500 MPR SCM device management

57

7.1 Secure certification mode

57

7.2 Workflow to manage 9500 MPR SCM devices

59

7.3 To configure an SNMPv3 user account on an 9500 MPR SCM device

60

7.4 To configure 9500 MPR SCM NE mediation

61

7.5 To configure a discovery rule

62

7.6 To retrieve logs stored by 9500 MPR SCM devices

63

8 9500 MPR object configuration

65

8.1 Overview

65

8.2 Workflow to configure and manage 9500 MPR device objects

65

8.3 To configure the system settings on a 9500 MPR

66

8.4 To resolve 9500 MPR MIB inconsistencies

67

8.5 To update the software activation status for 9500 MPRe nodes

68

8.6 To configure a scope of command role for NEtO access

69

8.7 To cross-launch the NEtO from the 5620 SAM GUI

70

8.8 To configure QoS for inband TMN interfaces on the 9500 MPR

71

9 9500 MPR shelf object configuration

73

9.1 Overview

73

9.2 Workflow to manage shelf objects on 9500 MPR devices

74

9.3 To configure a 9500 MPR basic or advanced fan tray

75

9.4 To migrate the 9500 MPRe connected to a 7705 SAR from standalone mode to single NE mode

76

10 9500 MPR port object configuration

79

10.1 Overview

79

10.2 Workflow to manage port objects on 9500 MPR devices

80

10.3 To configure 9500 MPR Ethernet ports

81

10.4 To collect and view analog Radio statistics on 9500 MPR 1x Radio modem ports

82

10.5 To collect performance management statistics on 9500 MPR 1x Radio modem ports

83

10.6 To configure 9500 MPR port segregation on an EAS module

84

10.7 To configure a power source for 9500 MPR card slots

85

10.8 To configure a loopback test on 9500 MPR ports

86

5620 SAM

10.9 To configure 802.3ah EFM OAM remote loopbacks on 9500 MPR ports

87

10.10 To configure Tx mute on radio ports

88

11 9500 MPR LAG object configuration

91

11.1 Overview

91

11.2 Workflow to configure and manage 9500 MPR LAG objects

92

11.3 To create an Ethernet LAG on a 9500 MPR

92

11.4 To delete a 9500 MPR Ethernet LAG

94

12 9500 MPR synchronization management

97

12.1 Introduction

97

12.2 IEEE 1588v2 PTP clocks

97

12.3 To configure synchronization on 9500 MPR Ethernet ports

100

12.4 To configure synchronization on a CorEvo card or MSS-1 shelf using SYNC-IO SFPs

100

12.5 To configure an IEEEv2 1588 TC on a 9500 MPR shelf

101

12.6 To configure IEEEv2 1588 BC and OC PTP clocks

101

12.7 To configure the PTP clock as a synchronization source

103

12.8 To configure the ToD

105

13 9500 MPR inventory management

107

13.1 Radio port inventory — 9500 MPRe and 9500 MSS-1c

107

13.2 To list and sort inventory information

107

13.3 To save an inventory list

108

13.4 To configure radio port inventory for 9500 MPRe and 9500 MSS-1c devices

109

13.5 Radio port inventory – 9500 MPR (ANSI and ETSI) devices

110

13.6 Procedure to configure radio port inventory for 9500 MPR ANSI and ETSI devices

110

13.7 Radio LAG member inventory – 9500 MPR ANSI and ETSI devices

111

13.8 To configure radio LAG member inventory for 9500 MPR ANSI and ETSI devices

111

14 9500 MPR QoS policies

113

14.1 Overview

113

14.2 Workflow to configure 9500 MPR QoS policies

113

14.3 To configure a 9500 Radio Interface Queue Map policy

114

14.4 To configure a 9500 NE QoS policy

115

15 9500 MPR service tunnels

117

15.1 Overview

117

15.2 Configuring service tunnels on a 9500 MPR

121

5620 SAM

15.3

To create an Ethernet radio ring on a 9500 MPR

121

16 9500 MPR service management

127

16.1 Microwave backhaul service configuration

127

16.2 To configure microwave backhaul services

130

16.3 To complete ring by automatically adding the ring adjacencies

132

16.4 To copy a microwave backhaul service

. 135

16.5 To view the microwave backhaul service objects

137

16.6 Microwave backhaul service discovery

139

16.7 To discover a microwave backhaul service

140

16.8 To move 9500 MPR backhaul sites

141

16.9 To separate microwave backhaul service topologies

142

16.10 Microwave backhaul service associations

143

16.11 Microwave backhaul service — considerations/limitations

150

17 9500 MPR composite service

153

17.1 Composite service

153

17.2 To configure a composite service

154

A NEtO, WebCT and 5620 SAM management comparison

157

A.1

Overview

157

A.2

Support for 9500 MPR management features across element managers

157

5620 SAM

About this document

Purpose

The 5620 SAM MPR User Guide describes how to discover, configure, and manage 9500 MPR devices including the 9500 MPRe, 9500 MSS-1c, and 9500 MSS-O variants using the 5620 SAM. The guide is intended for network planners, administrators, and operators and is to be used in conjunction with other guides in the 5620 SAM documentation suite where management of 9500 MPR devices does not differ from other network elements. Nokia recommends that you review the entire 5620 SAM MPR User Guide before you attempt to use the 5620 SAM to manage 9500 MPR devices.

Safety information

For your safety, this document contains safety statements. Safety statements are given at points where risks of damage to personnel, equipment, and operation may exist. Failure to follow the directions in a safety statement may result in serious consequences.

Document support

Customer documentation and product support URLs:

How to comment

5620 SAM

5620 SAM

Safety information

1 Safety information

1.1 Structure of safety statements

1.1.1 Overview

This topic describes the components of safety statements that appear in this document.

1.1.2 General structure

Safety statements include the following structural elements:

Safety statements include the following structural elements: CAUTION Lifting hazard Lifting this equipment by yourself
Safety statements include the following structural elements: CAUTION Lifting hazard Lifting this equipment by yourself

CAUTION

Lifting hazard

the following structural elements: CAUTION Lifting hazard Lifting this equipment by yourself can result in injury

Lifting this equipment by yourself can result in injury

due to the size and weight of the equipment.

Always use three people or a lifting device to transport

and position this equipment.

a lifting device to transport and position this equipment. [ABC123] Item Structure element Purpose 1
a lifting device to transport and position this equipment. [ABC123] Item Structure element Purpose 1

[ABC123]

Item

Structure element

Purpose

1

Safety alert symbol

Indicates the potential for personal injury (optional)

2

Safety symbol

Indicates hazard type (optional)

3

Signal word

Indicates the severity of the hazard

4

Hazard type

Describes the source of the risk of damage or injury

5

Safety message

Consequences if protective measures fail

6

Avoidance message

Protective measures to take to avoid the hazard

7

Identifier

The reference ID of the safety statement (optional)

Structure of safety statements

5620 SAM

1.1.3 Signal words

The signal words identify the hazard severity levels as follows:

Signal word

Meaning

DANGER

Indicates an extremely hazardous situation which, if not avoided, will result in death or serious injury.

WARNING

Indicates a hazardous situation which, if not avoided, could result in death or serious injury.

CAUTION

Indicates a hazardous situation which, if not avoided, could result in minor or moderate injury.

NOTICE

Indicates a hazardous situation not related to personal injury.

5620 SAM

What’s new?

2 What’s new?

2.1 Overview

2.1.1 Purpose

This chapter provides information on the latest 9500 MPR features introduced to the 5620 SAM.

2.1.2 Contents

2.1 Overview

11

2.2 What’s new in 5620 SAM Release 14.0 for 9500 MPR

11

2.2 What’s new in 5620 SAM Release 14.0 for 9500 MPR

2.2.1 General information

This section highlights new and discontinued 9500 MPR features introduced in Release 14.0 of the 5620 SAM and provides pointers for more information. Feature lists and high- level feature descriptions are also available in the 5620 SAM Release Description.

2.2.2 Maintenance releases

Some releases may not be listed in this section, either because no new 9500 MPR features were introduced or the features introduced do not require user documentation.

2.2.3 What’s new in 5620 SAM Release 14.0 R7 for 9500 MPR

Table 1, “5620 SAM Release 14.0 R7 9500 MPR features” (p. 12) , lists the features and functions added in 5620 SAM Release 14.0 R7 for 9500 MPR support. See the 5620 SAM User Guide for more information about non-9500 MPR features and functions.

What’s new in 5620 SAM Release 14.0 for 9500 MPR

5620 SAM

Table 1 5620 SAM Release 14.0 R7 9500 MPR features

Feature

Description and Reference

SAM-60800 — MPR service model revision

Supports configuration of microwave backhaul services.

Chapter 6, “9500 MPR migration to revised service model”

 

Chapter 15, “9500 MPR service tunnels”

Chapter 16, “9500 MPR service management”

Chapter 17, “9500 MPR composite service”

SAM-79402 — 1588 BC/OC configuration

Supports IEEE 1588 BC and OC.

12.2.3

“Boundary and ordinary clocks” (p. 98)

SAM-92443 — 1588 BC/OC - Statistics

 

SAM-92443 — 1588 BC/OC - Alarms

SAM-79408 — WebCT

Support for cross-launch of WebCT.

3.8 “WebCT” (p. 30)

3.9 “To open WebCT from the 5620 SAM” (p. 30)

SAM-89158 — 9500 MPR Release 7.1 management

Support for Release 7.1 version for 9500 MSS-1c, 9500 MPRe, and 9500 MPR devices.

SAM-89160 — 9500 MPRe Release

7.1

management

SAM-89163 — 9500 MSS-1c Release

7.1

management

SAM-90919 — Optimization of historical statistics collection

The historical statistics that are collected at 15 minutes and 24 hours intervals are optimized in such a way that the 5620 SAM only collects records that are not already collected in the previous collection interval.

3.4.2 “Optimized historical statistics collection” (p. 24)

SAM-91037 — Secure certification mode

Supports management of 9500 MPR SCM devices.

Chapter 7, “9500 MPR SCM device management”

SAM-92381 — SNMPv3 management

SAM-92383 — SCM reporting

SAM-92394 — SCM trusted manager

SAM-92394 — SCM HTTPS

SAM-92401 — SCM impact on backup and restore

SAM-92403 — SCM impact on software upgrade

SAM-92430 —SCM Log retrieval

SAM-92430 — SCM alarms

SAM-92447 — IEEE 1588 ToD

Supports IEEE 1588 ToD management

12.2.4

“1588 ToD” (p. 100)

5620 SAM

What’s new in 5620 SAM Release 14.0 for 9500 MPR

Table 1 5620 SAM Release 14.0 R7 9500 MPR features (continued)

Feature

Description and Reference

SAM-93749 Separate topologies

Supports separation of microwave backhaul services.

16.6 “Microwave backhaul service discovery” (p. 139)

2.2.4 What’s new in 5620 SAM Release 14.0 R3 for 9500 MPR

Table 2, “5620 SAM Release 14.0 R3 9500 MPR features” (p. 13) , lists the features and functions added in 5620 SAM Release 14.0 R3 for 9500 MPR support. See the 5620 SAM User Guide for more information about non-9500 MPR features and functions.

Table 2 5620 SAM Release 14.0 R3 9500 MPR features

Feature

Description and Reference

SAM-75857 — Inconsistent granularity period displayed for 9500 MPR radio PM statistical records

The granularity period column of 9500 MPR radio performance management statistics reflects the expected behavior of displaying statistical records on the 5620 SAM GUI.

The granularity period column on the 5620 SAM GUI displays 15 (mins) and 24 (hrs) for 9500 MPR radio performance management statistics.

See 3.4.3 “9500 MPR specific statistic usage information” (p. 24)

SAM-77207 — Separate list for radio performance statistics collected at 15 minutes and 24 hours intervals

You can separately enable or disable the radio performance statistics collected at intervals of 15 minutes and 24 hours by configuring the specific radio performance statistics on the Radio tab of the Physical Port (Edit) form.

See 3.4.3 “9500 MPR specific statistic usage information” (p. 24)

SAM-77209 — Support for elaborated counters

The elaborated counters are supported as an extension to the following classes:

• AggrMaintTxStats (for radio, Ethernet user ports, and L1 radio LAG)

• AggrPerQueueMaintStats (for radio ports)

• AggrMaintRxStats (for Ethernet user ports)

See 3.4.3 “9500 MPR specific statistic usage information” (p. 24)

SAM-77221 — 5620 SAM support for muting the transmitter indefinitely or for a specific duration

You can mute the transmitter either indefinitely or for a specific duration by configuring the Tx mute parameters on the radio ports.

See 10.10 “To configure Tx mute on radio ports” (p. 88)

SAM-77218 — Identify the two variants of the CorEvo card in the 5620 SAM

You can distinguish the two variants, 1G and 10G, of the CorEvo card by viewing the Equipped Card Sub Type parameter on the Card Slot (Edit) form and Card Slot (Physical Equipment) inventory list.

See 9.1.4 “CorEvo card” (p. 74)

SAM-79069 — Confirmation before adding an existing Ethernet ring element to a radio ring

A confirmation dialog box appears before adding an existing Ethernet ring element in a radio ring.

See 15.3 “To create an Ethernet radio ring on a 9500 MPR” (p. 121)

What’s new in 5620 SAM Release 14.0 for 9500 MPR

5620 SAM

Table 2 5620 SAM Release 14.0 R3 9500 MPR features (continued)

Feature

Description and Reference

SAM-79071 — Configuration of TMN VLAN parameters removed from 9500 MPR global QoS policies

You can no longer configure TMN VLAN parameters associated with 9500 MPR global QoS policies; the TMN VLAN tab has been removed from the 9500 MPR Global QoS policies form. These parameters are now configured when you commission the 9500 MPR device for in-band management using NEtO.

See 14.4 “To configure a 9500 NE QoS policy” (p. 115)

See the appropriate 9500 MPR Hardware User Guide for information about commissioning 9500 MPR devices using NEtO.

You can view TMN parameter settings configured using NEtO using the 5620 SAM by selecting 9500 MPR devices in the navigation tree Equipment view, right-clicking on a 9500 MPR device, and choosing Properties. Click on the Polling tab, then on the TMN Details sub-tab. Select a 9500 MPR device and click Properties; the TMN parameters display in read-only mode.

SAM-79341 — New L1 LAG interface alarms to indicate link down and service down issues

The following new alarms are supported by the 5620 SAM to indicate if there is a link or service down condition on L1 LAG interfaces. These alarms are supported on 9500 MPR R6.1 devices or later.

• LAG L1 Radio Port Down

• Traffic Down

• TxProblem

• RxProblem

• Traffic Loss

See the 5620 SAM Alarm Reference User Guide

SAM-79375 — Inventory list of radio port parameters – 9500 MPR (ANSI and ETSI) devices

You can view the inventory list and generate a report of the 9500 MPR radio ports and L1 radio LAGs for the parameters that are displayed in the Radio tab of the Network→9500 MPR→Card Slot→Radio Port→Physical Port (Edit) form.

See Chapter 13, “9500 MPR inventory management”

SAM-79394 and SAM-79400 — IEEE 1588v2 PTP transparent clock support

You can configure the TC Enabled parameter in the Timing tab on the 1588 panel of the Network→MPR→Shelf→Shelf (Edit) form. The supported platforms, cards, and radio types are listed in “IEEE 1588v2 PTP support per platform” (p. 98).

See 12.5 “To configure an IEEEv2 1588 TC on a 9500 MPR shelf” (p. 101)

SAM-79427 — LAC management enhancements

The LAC management enhancements are:

• LAC alarms are configured only after LAC management is enabled.

 

• LAC management status is configured on a 9500 MPR device only after LAC management is enabled.

• Access Request LAC state is removed from the LAC state configuration list of parameters.

See 4.2.2 “LAC management of 9500 MPR devices” (p. 37)

5620 SAM

What’s new in 5620 SAM Release 14.0 for 9500 MPR

Table 2 5620 SAM Release 14.0 R3 9500 MPR features (continued)

Feature

Description and Reference

SAM-79429 — Unmanaging a 9500 MPR device independent of LAC status

The 5620 SAM allows you to unmanage a 9500 MPR device regardless of the LAC status.

See “LAC management status of a 9500 MPR device” (p. 37)

SAM-79609 — Bulk operation to enable or disable statistics collection for 15 minutes or 24 hours intervals.

You can perform bulk operations to enable or disable the applicable radio interface performance management statistics collected at intervals of 15 minute or 24 hours.

See 3.4.3 “9500 MPR specific statistic usage information” (p. 24)

SAM-79711 — Inventory list of radio port parameters – 9500 MPRe and 9500 MSS-1c devices

The inventory list includes the following radio port parameters for 9500 MPRe and 9500 MSS-1c devices:

• Radio Interface ID

 

• Remote Node IPV4 Address

• Remote Node Interface

See Chapter 13, “9500 MPR inventory management”

SAM-81381 — Scheduled resynchronization disabled

Scheduled resynchronization is disabled by default for specific MIB entries in the 9500 MPR and 9500 MPRe devices.

See 4.5 “To configure polling for an 9500 MPR” (p. 44)

SAM-82401 — Modify a customer associated with a VLL service

You can configure a specific customer profile and associate it with a VLL service during the service configuration. You can also modify a discovered VLL service and add a specific customer profile.

What’s new in 5620 SAM Release 14.0 for 9500 MPR

5620 SAM

5620 SAM

9500 MPR Overview

3 9500 MPR Overview

3.1 9500 MPR device support

3.1.1 9500 MPR Radio family

The Nokia 9500 MPR is a microwave digital Radio family that supports PDH and Ethernet to migrate from TDM to IP. The 9500 MPR provides a generic, modular IP platform for multiple network applications such as 2G, 3G, HSDPA, and WiMAX to accommodate broadband services to Metro Ethernet areas. This solution improves packet aggregation, increases bandwidth and optimizes Ethernet connectivity.

The 9500 MPR Radio family supports low, medium, and high capacity applications using ANSI and ETSI data rates, frequencies, channel plans, and tributary interfaces and has both indoor and outdoor applications.

The 5620 SAM also supports the native management of following variants of the 9500 MPR:

9500 MPRe

The 9500 MPRe (also referred to as the 9500 MPR-SA) is the standalone, outdoor application of the MPT-MC and MPT-HCv2 ODU without a shelf unit. The 9500 MPRe provides fixed or mobile Ethernet site backhauling and supports converged MPLS metro networks. As a native NE, the 9500 MPRe appears on 5620 SAM maps and equipment managers. All standard SNMP-based features, including discovery and alarms, are supported with the same naming as the rest of the 9500 MPR family. Some features require a cross-launch of the NEtO external element manager. See 3.7 “9500 MPR NEtO support” (p. 28) for more information. The 5620 SAM supports the native management of the following 9500 MPRe releases: 5.0, 5.1, 5.2, 6.0, 6.1, 7.0, or later.

Note: From a 5620 SAM perspective, the 9500 MPRe/MPR-SA (stand alone), and

9500

MSS-1c variants belong to same product family; both variants display on the

5620

SAM GUI as the 9500 MPRe. However, for 9500 MPR software upgrades, the

Label column allows you to distinguish between the 9500 MPRe/MPR-SA and 9500 MSS-1c variant types.

9500 MSS-1c

The 9500 Microwave Service Switch-1c (MSS-1c) is an ultra-compact indoor unit (1/2 rack size) offering 10 E1 and 4 user interfaces. The 9500 MSS-1c provides user port interface, cross-connection, and switching management. The cross-connection matrix implements all the cross-connections between the User ports (4 Ethernet ports and E1/T1 streams) and the Radio port. The matrix is a standard Ethernet switch, based on VLAN, assigned by the MCT.

9500 MPR device support

5620 SAM

The 5620 SAM supports the native management of the following 9500 MSS-1c releases: 5.0, 5.1, 5.2, 6.0, 6.1, and 7.0. The NE backup and restore functionality for this node type is only supported for the following versions: 5.2, 6.0, 6.1, 7.0. A new backup and restore policy has been added to support this device type. You can access the policy from the Administration→NE Maintenance→Backup/Restore menu. Click on the Backup/Restore Policy tab, select the MPR-SA Default Policy and click Properties. Note this policy type requires the FTP/SFTP parameters to be configured.

The following functionality is supported for the 9500 MSS-1c using the 5620 SAM:

— automatic server registration with NE discovery

— ports listed in the Navigation equipment tree

— port alarm management

— automatic radio link discovery

— automatic node S/W download managed via a policy (same as the 9500 MPR/9500 MPRe)

— automatic node MIB backup and restore managed via a policy (same as the 9500 MPR/9500 MPRe)

— microwave backhaul service termination on the radio port

9500 MSS-O

The 9500 Microwave Services Switch-Outdoor (MSS-O) is a compact, full outdoor microwave networking device, for boosting link capacity and reliability for small cell backhaul networks. The device provides both optical and electrical Ethernet interfaces and can be installed indoors or outdoors.

You can configure the following on a 9500 MSS-O using the 5620 SAM:

— three 10/100/1000Base-TX Ethernet interfaces, two with PFoE, and one optical Gigabit Ethernet SFP interface. See 10.3 “To configure 9500 MPR Ethernet ports” (p. 81) for more information about configuring Ethernet ports.

— Ethernet L2 LAGs. See 11.3 “To create an Ethernet LAG on a 9500 MPR” (p. 92) for more information about configuring Ethernet LAGs.

— synchronization on Ethernet ports. See 12.3 “To configure synchronization on 9500 MPR Ethernet ports” (p. 100) for more information about synchronization on Ethernet ports.

— port segregation. See 10.6 “To configure 9500 MPR port segregation on an EAS module” (p. 84) for more information about port segregation.

— microwave backhaul services. See Chapter 16, “9500 MPR service management” for more information about how to configure microwave backhaul services. Note: Only the P2M VLAN path type is supported.

— Ethernet ring. See 15.1.3 “Ethernet (G.8032) ring support” (p. 117) for more information about configuring Ethernet rings.

The LAG size for a 9500 MSS-O is restricted to the following:

— up to two LAG ports per NE, either Ethernet L2 LAG or Radio L1 LAG

— up to two electrical Ethernet ports per Ethernet L2 LAG. Ports can have PFoE enabled.

5620 SAM

9500 MPR card support

— ports 1, 2, and 3 on the 9500 MSS-O are available for Ethernet L2 LAG membership

3.2 9500 MPR card support

3.2.1 Supported cards

You can configure the following 9500 MPR device-specific cards:

• 1 × Radio modem

• 1 × STM (Channelized)

• 2 × DS3

• 2 × STM

• 2+2 × Ethernet (EAS)

• 4+4 × Ethernet (EAS)

• 32 × DS1

• 32 × E1

• AUX alarm

• Core-B

• Core-ENH

• CorEvo

• EASv2

See Chapter 9, “9500 MPR shelf object configuration” for detailed information of the supported cards and auxiliary equipment on 9500 MPR devices.

supported cards and auxiliary equipment on 9500 MPR devices. Note: The 5620 SAM, version 13.0 R3

Note: The 5620 SAM, version 13.0 R3 and higher, allows you to discover all the EASv2 configurations supported on the 9500 MPR device.

3.3 Supported 9500 MPR device objects and auxiliary equipment

3.3.1 General information

The 5620 SAM supports the following 9500 MPR device shelves, objects, and auxiliary equipment:

• MSS shelves

• IDU and ODU

• basic and advanced fan trays

• LAG objects

Supported 9500 MPR device objects and auxiliary equipment

5620 SAM

3.3.2 Supported MSS shelf types

The following MSS shelf types can be managed by the 5620 SAM:

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.

Note: The equipment tree in the 5620 SAM GUI displays the MSS-1 shelf as a card slot with Ethernet ports numbered from 1/1 to 1/6 and TDM ports from 1/7 to 1/22.

Note: Radio LAGs (L1 and L2) are not supported.

MSS-4 and MSS-8 shelves

Slots 1 and 2 are reserved for core-enhanced cards. Each shelf requires a core-enhanced card in slot 1 and can have an optional spare card installed in slot 2 to protect the main card.

The MSS-4 shelf supports cards in slots 3 and 4. A card in slot 3 can be protected by an identical card in slot 4.

The MSS-8 shelf supports cards in slots 3 to 8. Protected cards must be installed in slots 3, 5, or 7 and are protected by optional identical cards in slots 4, 6, and 8, respectively.

3.3.3 IDUs and ODUs support

The ODU is a microprocessor-controlled transceiver that interfaces the MSS with the microwave antenna. Each Radio modem card connects to one ODU. A 1+0 Radio modem protection scheme requires one Radio modem card and one ODU for each Radio direction. Two Radio modem cards and two associated ODUs must be provisioned in each Radio direction for the 1+1 protection scheme using NEtO.

The 5620 SAM can manage the following IDU and ODU variants:

ODU300

The ODU300 transmitter consist of a cable interface, local oscillator, up converter/mixer, power amplifier, and a diplexer. The receiver consist of a diplexer, low-noise amplifier, local oscillator, down converter/mixer, automatic gain control, and cable interface. The ODU300 is frequency dependent.

MPT-HCv2

The MPT-HCv2 ODU transports Ethernet traffic over an RF Radio channel between the MSS and the antenna according to the configured QoS and to the scheduler algorithms. The input interface is a standard Giga Ethernet interface (electrical or

5620 SAM

Supported 9500 MPR device objects and auxiliary equipment

optical). The MPT-HCv2 is XPIC-ready by the installation of a dedicated module. The MPT-HC V2 is frequency dependent.

MPT-MC

The MPT-MC is similar to MPT-HCv2 from an architecture standpoint. The differences are:

— MPT-MC is medium capacity

— MPT-MC is natively Ethernet powered through a proprietary PFoE

— MPT-MC has an optical cable length limit of 100 m

MPT-XP

The MPT-XP is a very high power version of the MPT-HCv2 and provides +7-8 dB of additional transmit power as compared to equivalent MPT-HCv2. The MPT-XP is frequency dependent.

MPT-HL

The MPT-HL transceiver card is a microprocessor controlled RF transceiver that interfaces with the Core-E card or MSS-1 shelf MPT-HL port with an antenna. The MPT-HL transceiver microprocessor manages transmit and receive frequencies, transmit power, alarms, and performance monitoring. The MPT-HL transceiver resides in the MPT-HL shelf.

The following configurations are supported:

— one or two Non-Standby (1+0) radios

— Hot Standby (1+1) and Hot Standby space

— frequency diversity

MPT-HLC

The MPT-HLC transceiver card is a microprocessor controlled RF transceiver that interfaces with the Core-E card, EASv2 card, or MSS-1 shelf MPT-HLC port with an antenna. The MPT-HLC transceiver microprocessor manages transmit and receive frequencies, transmit power, alarms, and performance monitoring. The MPT-HLC transceiver resides in the MPT-HL shelf.

The following configurations are supported:

— one or two Non-Standby (1+0) radios

— Hot Standby (1+1) and Hot Standby space

— frequency diversity

— single-shelf repeater

MPT-HLS

The MPT-HLS is a fully indoor Radio system, for long haul and cabinet requirements, and transports Ethernet traffic over an RF Radio channel. The MPT-HLS transceiver is connected to an MSS-1, MSS-4, or MSS-8. The MPT-HLS can be connected to the core-enhanced card or to an EASv2 card. The MPT-HLS is a four-rack (2200, 2000, 1700, 1300 mm) unit with two RT subracks. The subracks can be hosted with up to 10 transceivers. The TRU (always protected) is located on the top of the ETSI rack. A fan subrack is configured for each RT subrack. Two types of fan modules are available for

Supported 9500 MPR device objects and auxiliary equipment

5620 SAM

configuration, Fan 4 and Fan 8. See the 9500 MPR (Hardware) User Manual for more information about configuring the MPT-HLS Radio.

The 5620 SAM supports viewing the adaptive modulation values for the usage time 512 QAM and 1024 QAM in MPT-HLS. • MPT-HQAM

The MPT-HQAM outdoor unit is a microprocessor controlled RF transceiver that interfaces with the MSS-1/4/8/1c shelf; MPTACC, Core-E, P8ETH, and EASv2 card, or MPRe (standalone) with the antenna. Fixed and adaptive modulation schemes are supported. Channel frequency is software selectable within tuning range of the MPT-HQAM transceiver. The MPT-HQAM transceiver is frequency dependent. An MPT-HQAM connected to a Core-E, P8ETH, and EASv2 card requires a power source. The MPT-HQAM has integrated XPIC and RPS functions.

The 5620 SAM supports two operating modes in the MPT-HQAM:

— Standard mode The MPT-HQAM is used with its own capabilities and profiles. The air compatibility with another MPT-HQAM in Standard mode is supported.

— MPT-HC Compatibility mode MPT-HQAM is used with the MPT-HC capabilities and profiles. The air compatibility with another MPT-HQAM in MPT-HC Compatibility mode or with an MPT-HC is supported.

The operating modes are configured on the NEtO and the 5620 SAM supports viewing the MPTHC Compatibility parameter, with the values set to True or False, on the Radio→General tab of the Physical Port (Edit) form.

The 5620 SAM supports viewing 1+1 protection configuration for:

— two MPT-HQAMs, both configured in Standard mode

— two MPT-HQAMs, both configured in MPT-HC Compatibility mode

— two MPT-HQAMs, one configured in Standard mode and one in MPT-HCv2 Compatibility mode

— one MPT-HCv2 (with the main role as protection) and one MPT HQAM configured in Standard or MPT-HC Compatibility mode

— one MPT-HQAM configured in MPT-HC Compatibility mode (with the main role as protection) and one MPT-HCv2

The 5620 SAM supports the discovery of Radio L1 LAG by adding:

— MPT-HQAM in MPT-HC Compatibility mode to an L1 LAG of MPT-HCv2

— MPT-HQAM in Standard mode to an LAG L1 of MPT-HCv2

— MPT-HQAM in Standard or MPT-HC Compatibility mode to an L1 LAG of MPT-MC

— MPT-HQAM in Standard/MPT-HC Compatibility mode or MPT-MC to an L1 LAG of MPT-HQAM in MPT-HC Compatibility or Standard mode

The 5620 SAM supports the discovery of Radio L2 LAG by adding:

— MPT-HQAM in MPT-HC Compatibility mode to an L2 LAG of MPT-HCv2

— MPT-HQAM in Standard mode to an L2 LAG of MPT-HCv2

5620 SAM

Supported 9500 MPR device objects and auxiliary equipment

— MPT-HQAM in Standard/MPT-HC Compatibility mode to an L2 LAG of MPT-HQAM in MPT-HC Compatibility/Standard mode

See the 9500 MPR ETSI (Hardware) User Manual for more information about configuring a Radio LAG.

An MPT type conversion procedure allows the you to update an MPT-HCv2 to an MPT-HQAM on the node. For the complete procedure, see the 9500 MPR-A (Hardware) Maintenance and Trouble Clearing Guide. The node restarts after the conversion and the 5620 SAM displays the updated MPT-HQAM on the equipment tree and the Port Usage parameter value in the General tab of the Physical Port (Edit) form.

3.3.4 Fan tray support

The 9500 MPR supports two fan tray types: basic and advanced. For the advanced fan tray, you can configure four ports for housekeeping alarms. See 9.3 “To configure a 9500 MPR basic or advanced fan tray” (p. 75) for more information about configuring a 9500 MPR fan tray.

3.3.5 LAG objects support

The 5620 SAM supports the following LAG objects on 9500 MPR (ANSI and ETSI)

devices:

• L1/L2 Radio LAGs - You must use the NEtO external element manager to complete the initial LAG configuration prior to discovery by the 5620 SAM.

• L2 Ethernet LAGs - You can configure and discover L2 Ethernet LAGs using the 5620 SAM or NEtO.

See Chapter 11, “9500 MPR LAG object configuration” for more information about 9500 MPR LAG objects.

3.3.6 XPIC support

The Cross-Polarization Interference Cancellation (XPIC) function doubles the capacity of

a single frequency by using both horizontal and vertical electromagnetic polarizations on

a path. This increases capacity while also saving spectrum and antenna costs.

XPIC is required on two Radio interfaces in order to provide additional cross-polarization discrimination and to avoid co-channel interference. Only the MPT-HCv2/MPT-XP supports the XPIC function. See 10.7 “To configure a power source for 9500 MPR card slots” (p. 85) to configure power source type over Ethernet on a 2+2 × Ethernet (EAS) card. See the 9500 MPR (Hardware) User documentation for more information about how to use the NEtO software to configure XPIC.

9500 MPR statistics support

5620 SAM

3.4 9500 MPR statistics support

3.4.1 Introduction

The 5620 SAM supports the collection of network performance, accounting, and flow- based statistics for 9500 MPR devices. The 5620 SAM also provides statistics for monitoring 5620 SAM processes and functions. These statistics are typically used to monitor or troubleshoot a network, or to perform SLA or billing functions. Statistics collection can be configured with policies that are distributed to specified network objects.

See the 5620 SAM Statistics Management Guide for information about the following for

9500 MPR devices:

• configuring statistics collection

• viewing statistics data in tabular or graphical form

• creating graphical representations of statistics data using the Statistics Plotter

• the supported performance and accounting statistic counters for 9500 MPR devices

3.4.2 Optimized historical statistics collection

The 5620 SAM collects historical statistics at 15 minutes and 24 hours intervals. The first set of statistics collected after a 9500 MPR device is managed contains all the historical

statistics collected during that time interval. The subsequent historical statistics collected only contains the new statistics and the previously collected data is not duplicated. When the 9500 MPR device connectivity is lost, the 5620 SAM collects all of the uncollected records upon restoration of connectivity. When the 9500 MPR device is unmanaged or suspended no new records are generated. The first set of statistics is collected after the

9500 MPR device is managed again.

3.4.3 9500 MPR specific statistic usage information

The following provides notable statistic usage information that applies to 9500 MPR devices:

• The Total Transmitted Octets after Compression and Total Transmitted Octets after Compression Periodic statistic counters for Ethernet Aggregate Tx statistics have been added in 5620 SAM Release 13.0 R3, applicable for 9500 MPR, Release 5.2 and later. You can access these counters by selecting Properties on a 9500 MPR physical port, and selecting the Statistics tab. However, these counters also appear for earlier releases of the 9500 MPR and GNEs. Because the fields cannot be hidden, the 5620 SAM sets the counter value to 0.

• The 5620 SAM supports elaborated counters as an extension to the following classes:

— AggrMaintTxStats (for radio, Ethernet user ports, and L1 radio LAG)

— AggrPerQueueMaintStats (for radio ports)

— AggrMaintRxStats (for Ethernet user ports)

5620 SAM

9500 MPR statistics support

The elaborated counters are applicable only to scheduled statistics and not on-demand statistics. The 5620 SAM does not support real-time plotting of the elaborated counters. The elaborated counters are supported for 9500 MPR-E/A, 9500 MPRe, and MSS-1c devices from Release 5.2 and later. See the 9500 MPR performance statistics counters chapter in the 5620 SAM Statistics Management Guide for detailed information about the individual statistics counters.

• The granularity period column displays the statistic collection period based on a set time interval, for example, 15 corresponds to 15 minutes and 24 corresponds to 24 hours.

• The radio interface performance management statistics are listed separately for collection intervals of 15 minutes and 24 hours at the port level. The following table lists the radio interface performance management statistics that are collected at the port level or using the Bulk Operations tool.

Radio interface PM statistic type

Usage notes

Adaptive Modulation Current Data

Statistic is only present when AM is enabled using Adaptive Modulation Mode.

Frame Hop Current Data

Always available for the Radio interface.

Frame Link Current Data

Available for the Radio interface when RPS is enabled. See Note 1 and 2.

RSL Hop Current Data

Always available for the Radio interface.

TSL Hop Current Data

Always available for the Radio interface.

RSL Link Current Data

See Note 1 and 2.

When RPS is present, Hop stats are enabled/disabled on the protecting port along with the active port.

RSL Diversity Link Current Data

Available for NE version 5.1 and later when the space diversity (combiner) is enabled on the Radio interface along with RPS.

RSL Diversity Hop Current Data

Available for NE version 5.1 and later when the space diversity (combiner) is enabled on the Radio interface.

Note 1: When RPS is present, you can enable/disable statistics on the protecting port along with the active port.

Note 2: When RPS is present, do not edit the Radio PM statistic parameters from the 5620 SAM GUI for the spare protecting port.

• You can enable or disable performance management statistics at port level or using the Bulk Operations tool. — Port level:

You can enable or disable individual radio interface performance management statistics that are collected at intervals of 15 minutes or 24 hours. See 3.5 “To

To configure radio interface performance management statistics at the port level

5620 SAM

configure radio interface performance management statistics at the port level” (p. 27) for more information.

Bulk Operations tool:

You can perform bulk changes to enable or disable the applicable radio interface performance management statistics for statistics collection intervals of 15 minutes and 24 hours . The changes are applicable to the entire list of allowable statistics for statistics collection intervals 15 minutes and/or, 24 hours. See 3.6 “To configure bulk changes for radio interface performance management statistics” (p. 27) for more information; also see the “Bulk operations” chapter in the 5620 SAM User Guide for more information.

• Perform the following to plot the statistics for both ends of a Radio link traversing between two 9500 MPRs, between a 9500 MPR and a 7750 SR, or a 9500 MPR and a 7705 SAR:

— Select a supported Radio link on the Administration→Physical Topology map, right-click on the link and choose Plotter→New Plot. The Statistics Plotter window opens to display both link endpoints in the Monitored Object column. Select the appropriate Statistics Group, Statistics Counter, or Data Format and click the Record/Play buttons to plot the data.

— You can also plot Radio link statistics at the object level by selecting a supported device port in the navigation tree Equipment view, and choose Properties. The Physical Port — Port (Edit) form opens. Click Plotter→New Plot. The Statistics Plotter window opens to display the selected endpoint in the Monitored Object column. If the port is part of a Radio link, click on the Plot Other Endpoint(s) button to populate/view the other link endpoint. Select the appropriate Statistics Group, Statistics Counter, or Data Format parameters and click the Record/Play buttons to plot the data.See the 5620 SAM Statistics Management Guide for more information about the statistics plotter.

3.5 To configure radio interface performance management statistics at the port level

3.5.1 Before you begin

Configure the radio parameters using the MCT for the freshly brought up 9500 MPRe and 9500 MSS-1c devices, before configuring the radio PM enable and disable parameters on the 5620 SAM.

3.5.2 Steps

1

On the equipment navigation tree, right-click on a 9500 MPR port where a Radio interface is configured, for example, an MPT-MC or MPT-HC card, and choose Properties. The Physical Port (Edit) form opens.

5620 SAM

To configure bulk changes for radio interface performance management statistics

2

Click on the Radio tab and configure the appropriate PM statistics parameter(s) on the Radio PM panel.

END OF STEPS

3.6 To configure bulk changes for radio interface performance management statistics

3.6.1 Steps

1

2

Choose Tools→Bulk Operations from the 5620 SAM main menu. The Bulk Operations form opens.

3

Click Create. The Create Bulk Change (New) step form opens.

Configure the General parameters and click Next. The Specify the filter step appears.

4

4 Note: For the Object Type parameter, select Radio Equipment - (radioequipment)→Radio Port -

Note: For the Object Type parameter, select Radio Equipment - (radioequipment)→Radio Port - (radioequipmentRadioPortSpecifics).

Configure an appropriate filter and click Next. The Specify the attributes step appears.

Note:and click Next. The Specify the attributes step appears. Do not use the following attributes: •

Do not use the following attributes:

• Radio: Radio Port (Radio Equipment)→Radio PM : Radio Port (Radio Equipment)→Radio PM.

The configured filter lists only the enabled radio PM statistics and not the disabled radio PM statistics.

• Radio: Radio Port (Radio Equipment)→Radio PM : Radio Port (Radio Equipment)→Radio Bulk Radio PM Enable/Disable 15 Min

• Radio: Radio Port (Radio Equipment)→Radio PM : Radio Port (Radio Equipment)→Radio Bulk Radio PM Enable/Disable 24 Hrs

9500 MPR NEtO support

5620 SAM

5

 

Expand Attributes→Radio→Radio PM→Bulk Radio PM Enable/Disable (24 Hrs or

15

Min). The Radio PM parameter panel appears.

6

 

Choose either "Enable" or "Disable" for the Bulk RadioPM Enable/Disable (24 Hrs or

15

Min) parameter, click Next, click Finish, then close the wizard. The Bulk

7

Operations form reappears.

8

Click Search to locate the Bulk Operation task, choose an entry, and click Properties. The Bulk Change (Edit) form opens.

9

Click on the Batch Control tab and click Generate Batches. The batches are generated.

Either click Execute All or choose the required entries and click Execute Selected to enable or disable PM statistics collection intervals of 24 hours and/or 15 minutes. Close the form.

END OF STEPS

3.7 9500 MPR NEtO support

3.7.1 Element manager (NEtO) support

You can install and cross-launch the 9500 MPR external element manager, the NEtO from the 5620 SAM GUI; see 8.7 “To cross-launch the NEtO from the 5620 SAM GUI” (p. 70) for information.

For the 9500 MPRe, the NEtO cross-launch occurs only if the registration table entry has not reached the limit of 15 entries.

The NEtO multi-version auto-download or cross-launch to each IPv6 node works when the nodes are reachable (IPv6 route must exist) from the 5620 SAM Windows Client, from which the auto-download or cross-launch is being attempted.

The cross-launch task of NEtO is listed in the 5620 SAM user activity log. To view the task, choose Administration→Security→User Activity from the 5620 SAM main menu. The log indicates whether the cross-launch was successful. The auto-download of NEtO occurs when NEtO is launched for the first time and this is not specifically listed in the log.

5620 SAM

9500 MPR NEtO support

3.7.2 NEtO distribution through the 5620 SAM

The 5620 SAM manages the distribution of the NEtO application and all related profiles. Any discovered 9500 MPR has all cross-launch paths automatically configured in policies so that no user configuration is required to use the NEtO. The cross-launch function also supports the option to run TACAS+ in the network, in which case NEtO has

a NULL authentication when cross-launched, and the user is prompted for a user name and password.

The first time a user cross-launches the NEtO, the 5620 SAM Java Webstart installs the application on the 5620 SAM client system. Any update to the NEtO installation files on the 5620 SAM server results in an update to the NEtO installation on the client system.

The 5620 SAM supports the selection of user profiles to access the NEtO. The Admin NEtO launch, Viewer NEtO launch, and Default NEtO launch are listed in the scope of command roles that allows you to access the NEtO for a specific user profile. See the Appendix in the 5620 SAM System Administrator Guide for the list of scope of command roles. See 8.6 “To configure a scope of command role for NEtO access” (p. 69) for information about configuring a scope of command role to access the NEtO for the required user profile.

During an upgrade, the 5620 SAM leaves property files in place for existing NEs, retaining any user edits made to support the NEs. An operator can change the property files to change the login behavior, as described in 4.7 “To enable 5620 SAM management of 9500 MPR devices” (p. 45). The Install Directory property is a property required only by 5620 SAM releases earlier than 10.0 R5; the current 5620 SAM release manages the NEtO installation. See the applicable 9500 MPR Release Notice for the supported versions of NEtO.

3.7.3 Service management with NEtO

You can use the NEtO to manage services on the 9500 MPR. The use of an external element manager to change key network management information usually managed by the 5620 SAM (such as service IDs, SAP or site information, or VLAN information) could result in data loss or corruption. To avoid this problem, site information is persisted so that management actions (such as moving service access from one DS1 port to another) do not result in data loss.

On the 5620 SAM, Release 13.0 R3 or later, configuration of the following can only be performed using NEtO:

• cards

• port usage

• Radio LAGs

WebCT

5620 SAM

• port and card protection

The 5620 SAM takes the following additional actions to accommodate service changes made using the NEtO:

• A move between ports by the NEtO generates an alarm. The new port attachment is discovered and the deleted port is retained. The user can copy provisioning information to the new port in the 5620 SAM or manually reverse the change, if required.

• A move between Radio backhaul paths by the NEtO generates an alarm and is accepted. The alarm message retains the old and new path information, allowing the user to change the service back to its original form, if required.

• A move between Radio and Ethernet backhaul paths by the NEtO generates an alarm and is accepted. The alarm message retains the old and new path information, allowing the user to change the service back to its original form, if required.

• When using NEtO to change VLAN IDs for a service, the new service is discovered and alarms are generated for both services. An informational alarm is generated for the new service, and a major alarm is generated for the old service.

• A clean up on the service deletes all new discovery alarms and old SAPs, and accepts the new SAPs.

• Service changes from the NEtO are not supported for ERPS (Radio or fiber).

3.8 WebCT

3.8.1 Overview

WebCT is the web interface for 9500 MPR devices using the CorEvo card. WebCT provides configuration information, alarms, monitoring and administration functions. See the 9500 MPR WebCT User Manual for more information about WebCT.

3.8.2 Open WebCT from 5620 SAM

The 5620 SAM supports the cross-launch of WebCT from the equipment navigation tree and the topology map.

3.9 To open WebCT from the 5620 SAM

3.9.1 Steps

map. 3.9 To open WebCT from the 5620 SAM 3.9.1 Steps Note: The external EMS browser

Note: The external EMS browser is supported on the latest release of Firefox, IE, Chrome, and Safari.

1

Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.

5620 SAM

Workflow to manage 9500 MPR devices

2

Right-click on a 9500 MPR device that has a CoreEvo and choose Launch External EMS Browser. The WebCT main view screen appears in the secure mode (https) or normal mode (http) depending on the 9500 MPR device configuration.

END OF STEPS

3.10 Workflow to manage 9500 MPR devices

3.10.1 9500 MPR workflow sequence

The following workflow describes the high-level tasks required to commission and discover 9500 MPR devices, configure and manage the device objects, and configure and manage the policies and services associated with the device.

3.10.2 Process

1

2

Review the workflow to prepare the 5620 SAM to perform network management of devices in the 5620 SAM User Guide before starting this workflow. The steps in this workflow are common to all 5620 SAM-managed devices.

3

Commission 9500 MPR devices for 5620 SAM management; see Chapter 4, “9500 MPR device commissioning and management”.

4

Use the 5620 SAM to discover 9500 MPR devices; see the “Discovering devices using the 5620 SAM” chapter in the 5620 SAM User Guide.

5

View, manage, and configure 9500 MPR device network objects as required; see the “Working with network objects using the 5620 SAM” chapter in the 5620 SAM User Guide.

6

View, manage, and configure 9500 MPR device objects; see Chapter 8, “9500 MPR object configuration”.

View, manage, and configure 9500 MPR device LAG objects; see Chapter 11, “9500 MPR LAG object configuration”.

Workflow to manage 9500 MPR devices

5620 SAM

7

8

Modify 9500 MPR device shelf objects; see Chapter 9, “9500 MPR shelf object configuration”. You can configure cards only using NEtO. See the 9500 MPR (Hardware) User Guide for more information.

9

Modify ports on 9500 MPR devices, as required; see Chapter 10, “9500 MPR port object configuration”. You can configure ports only using NEtO. See the 9500 MPR (Hardware) User Guide for more information.

10

As required, perform bulk configuration changes on 9500 MPR devices to change the same configuration on multiple objects at the same time; see the “Bulk operations” chapter in the 5620 SAM User Guide for general guidelines. For example, configure a bulk change by choosing 9500 MPR→System Settings - (mpr.MprNeProperties) in the Object Type drop-down menu to specify the bridge type for all 9500 MPR devices. See the 5620 SAM-O XML Reference for information about all bulk change XML classes associated with the 9500 MPR objects.

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.

11

b. Create QoS device-specific policies as required for 9500 MPR devices; see Chapter 14, “9500 MPR QoS policies”.

Before configuring backhaul, or composite services and related functions on 9500 MPR devices; perform the following as required:

a. Review the “Service management and QoS” chapter in the 5620 SAM User Guide for information about configuring services on 9500 MPR devices using the 5620 SAM.

b. Review the “Customer configuration and service management” chapter in the 5620 SAM User Guide for information about, and workflow on, how to create and manage customers and the services they subscribe to. As required, create customer profiles.

c. Review the 9500 MPR service management and service tunnels chapter for specific information on supported service types; see Chapter 15, “9500 MPR service tunnels”.

d. Configure service tunnels to carry service traffic on 9500 MPR devices; see

5620 SAM

Workflow to manage 9500 MPR devices

Chapter 15, “9500 MPR service tunnels”.

12

13

Configure bachkaul services for subscribers connected to 9500 MPR devices; see Chapter 16, “9500 MPR service management”.

14

Configure composite services to connect the types of services for subscribers connected to 9500 MPR devices; see Chapter 17, “9500 MPR composite service”.

Monitor and acknowledge incoming 9500 MPR-specific alarms to check the type and characteristics of the alarms, and to resolve the network problems or physical equipment failures identified by the alarms; see the “Alarm management overview” chapter in the 5620 SAM User Guide for more information.

In addition:

• Click on the Abnormal Conditions tab of the Network Element (Edit) form to check for the abnormal conditions on the 9500 MPR such as loopback or TxMute conditions to determine the appropriate corrective action. In previous releases of the 5620 SAM, each abnormal condition on the 9500 MPR were reported as an individual alarm on the Faults tab. Abnormal conditions are now reported as a single alarm.

• Refresh the Abnormal Conditions tab to ensure the latest content is displayed.

15

• Clear the abnormal condition alarm after all the individual abnormal conditions are cleared.

Perform specific 9500 MPR device maintenance functions as required:

• on-demand or scheduled NE configuration backup and restore device configurations

• perform a 9500 MPR device on-demand software upgrade. See Chapter 5, “9500 MPR software upgrade”

• monitor deployment of configuration changes to 9500 MPR devices

• configure the OLC state on a 9500 MPR device object to specify whether the object is in maintenance or in-service mode to filter alarms in the alarm window

• perform daily, weekly, monthly, and supplemental routine maintenance to maintain hardware and system integrity and efficiencies of 9500 MPR devices

See the 5620 SAM System Administrator Guide for more information.

Workflow to manage 9500 MPR devices

5620 SAM

16

Collect 5620 SAM and NE statistics to monitor the 5620 SAM and 9500 MPR devices, network and service performance, compile equipment usage and billing data, and ensure SLA compliance; see the 5620 SAM Statistics Management Guide.

5620 SAM

9500 MPR device commissioning and management

4 9500 MPR device commissioning and management

4.1 General description

4.1.1 General description

The 9500 MPR requires commissioning and device-specific pre-configuration before the

5620 SAM can discover and manage the device. See the 4.3 “Workflow to commission

and manage 9500 MPR devices” (p. 41) for the sequence of high-level tasks required to

commission a 9500 MPR before discovery by the 5620 SAM.

The 9500 MPR requires two mediation policies be created manually as part of the discovery rule creation process: one for Read-Write mediation and a Trap mediation policy.

Note: While creating the read/write mediation policy, you must select FTP for the File Transfer Type, While creating the read/write mediation policy, you must select FTP for the File Transfer Type, and specify the FTP User Name 'ftp' and FTP User Password 'ftp'. While creating the trap mediation policy, you must specify 'SNMP-trap' as the SNMP v1/v2c Community String.

Note: To determine which version of the 9500 MPR NEs and variants are supported by the To determine which version of the 9500 MPR NEs and variants are supported by the 5620 SAM, see the 5620 SAM Network Element Compatibility Guide for information.

4.2 9500 MPR management

4.2.1 Supported management traffic types

A 9500 MPR device requires pre-configuration before 5620 SAM management of the device is possible. The 5620 SAM supports in-band and out-of-band management of devices.

When you configure in-band management only, management traffic between the 5620 SAM and a 9500 MPR is transmitted through any port that is configured for network access, but not the management port. Using in-band management, the 5620 SAM sends management traffic to the system IP address of the device, or to an optional L3 management interface.

When you configure out-of-band management only, management traffic between the

5620 SAM and a 9500 MPR is transmitted through the management port of the device.

Using out-of-band management, the 5620 SAM sends management traffic to the

9500 MPR management

5620 SAM

management IP address of the device. See the 5620 SAM User Guide for more information about device bandwidth management.

for more information about device bandwidth management. Note: A 9500 MPR device can only be managed

Note: A 9500 MPR device can only be managed by up to five instances of the 5620 SAM.

In-band management of 9500 MPR devices

To enable 9500 MPR in-band management, the 5620 SAM requires connectivity to the 9500 MPR NE, as shown in Figure 1, “Example of 9500 MPR in-band management” (p. 35) 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.

Figure 1 Example of 9500 MPR in-band management

9500 MPR network 9500 MPR A Switch or Management (TMN) port: 9500 MPR B Local
9500 MPR network
9500 MPR A
Switch or
Management (TMN) port:
9500 MPR B
Local IP: 10.10.3.9
Router
5620 SAM
2.2.2.2
server 2.2.2.1
Local IP: 10.10.3.5

20511

Perform the following initial configuration on the 9500 MPR:

1. Connect the first 9500 MPR Node 1 to the switch using the TMN port or port 4 of the 9500 MPR A.

When the 5620 SAM is connected to the 9500 MPR network via non-9500 MPR devices like the 7705 SAR or 7750 SR, expect that the TMN in-band feature is enabled on Node 1 of the 9500 MPR that is connected to non-9500 MPR devices. For example, SAM-----7705SAR_1/1/1-----port1/4_MPR1 -------(Radio)------MPR2

In the preceding example, the 9500 MPR Node 1 and port 1/4 are enabled with VLAN ID and IP addresses and the 7705 SAR is configured with the same VLAN and IP address from the same subnet.

2. Ensure that the Radio links between the 9500 MPRs are working by pinging the local IP addresses. A connection between two 9500 MPR NEs could be over an Ethernet or optical link. If the core Ethernet or core optical port is used between two 9500 MPRs, the ports should be enabled with TMN in-band on the 9500 MPR.

5620 SAM

9500 MPR management

Note: The management port IP, TMN in-band IP, and local IP can be in different subnets. The management port IP, TMN in-band IP, and local IP can be in different subnets.

Perform the following network configuration:

1. Verify that you can ping the local IP address of all the NEs from the 5620 SAM server.

2. Verify that you can ping the 5620 SAM server IP address from each of the 9500 MPR NEs.

Note: You can manage the 9500 MPR through the local IP address even though the management interface via the 5620 SAM server is not reachable.

3. The 5620 SAM should be able to discover and manage the local IP addresses of the 9500 MPRs after connectivity is established between the 5620 SAM and the 9500 MPR NEs.

4.2.2 LAC management of 9500 MPR devices

Introduction

The 5620 SAM provides a Local Access Control (LAC) management synchronization mechanism to allow or deny (inhibit) user-access to configure 9500 MPR devices using a Local Craft Terminal (LCT). This prevents multi-write access sessions on 9500 MPR devices. You can also enable or disable if the 5620 SAM receives LAC alarms from the nodes.

Enable LAC management

You can enable LAC management by configuring the Enable LAC Management parameter on the MPR tab of the Administration→System Preference→System Preference form. Enabling LAC management automatically denies LCT access to nodes that are newly managed only. There is no impact to existing managed 9500 MPR nodes.

After the Enable LAC Management parameter is configured, you can enable or disable LAC alarms by configuring the Enable LAC Alarms parameter on the MPR tab of the Administration→System Preference→System Preference form. The 5620 SAM generates a “LAC requested” alarm indicating LCT use is requesting access to the node. If disabled, no new alarms will be generated going forward. The Enable LAC Alarms parameter cannot be configured if the Enable LAC Management parameter is disabled.

Note: The Enable LAC management parameter is disabled by default. Therefore, the LAC state of any The Enable LAC management parameter is disabled by default. Therefore, the LAC state of any node which is newly managed by the 5620 SAM going forward will not be altered. This is done to allow LCT access for those users who normally provision the 9500 MPR using NEtO or the 1350 OMS.

LAC management status of a 9500 MPR device

You can configure the LAC management status of a 9500 MPR device at the node level by selecting the node in the navigation tree Equipment view, and choose Properties. The Network Element form opens. Click on the System Setting tab and verify the LAC state

9500 MPR management

5620 SAM

parameter in the LAC configuration panel. You can re-configure the LAC state parameter if required; any changes made at the NE level and will only affect that NE.

changes made at the NE level and will only affect that NE. Note: • The LAC

Note:

• The LAC configuration parameters are available for configuration only if the LAC management is enabled. See “Enable LAC management ” (p. 37) for more information about enabling LAC management.

• The 5620 SAM allows you to unmanage a 9500 MPR device irrespective of the LAC status.

If the LAC management state of the node is set to Access Denied, LCT-users can request access to the node from a LCT session to the 5620 SAM. When this request is made, a LocalAccessRequest alarm is generated after the specified wait-time and appears in the Alarm window.

You can:

• grant access to the LCT by changing the LAC state to Access Granted.

• deny access to the LCT by changing the LAC state to Access Denied.

4.2.3 Supported Radio links

Radio links between 9500 MPR devices are automatically discovered by the 5620 SAM. The auto-discovery is supported for the following Radio links:

• 1+0

• 1+1

• L2 LAG

• L1 LAG

After the auto-discovery, the 5620 SAM displays the following parameters on the Radio tab of the Physical Port (Edit) form:

• Remote IPv6/IPv4 Address

• Remote Interface

• Remote Port

The Radio interface can be:

• ODU300

• MPT-xC

• MPT-HLv1

• MPT-HLv2

Radio links between 9500 MPR devices are shown as physical links by the 5620 SAM, with ports as the endpoint type.

5620 SAM

9500 MPR management

To enable 9500 MPR Radio link discovery and management, the 5620 SAM requires connectivity between the 9500 MPR NE Radio ports, as shown in the following figure. Table 3, “Connectivity parameter details” (p. 39) lists the connectivity parameter details for each supported shelf type.

Figure 2 Connectivity example for 9500 MPR Radio link discovery and management 9500 MPR 9500
Figure 2 Connectivity example for 9500 MPR Radio link discovery and management
9500 MPR
9500 MPR
9500 MPR
Switch
1-MSS-4
3-MSS-8
4-MSS-4
5620 SAM
2x(1+0) RADIO CONFIGURATION
with:
3x(1+0) RADIO CONFIGURATION
with:
LINKGRP=2
LINKGRP=1
LINKMEMBER=3, 6
LINKMEMBER=1, 3, 5
9500 MPR
2-MSS-4
22432

Table 3 Connectivity parameter details

Shelf type

1-MSS-4

2-MSS-4

3-MSS-8

4-MSS-4

2-MSS-4

PPPRF Enabled LinkID (as assigned)

PPPRF Enabled LinkID (as assigned)

3-MSS-8

PPPRF Enabled LinkID (23, 23) PPPRF Disabled LinkID (26, 26)

PPPRF Enabled LinkID (as assigned)

PPPRF Enabled LinkID (11, 11) PPPRF Disabled LinkID (13, 13) PPPRF Disabled LinkID (15, 15)

To discover multiple Radio links, you must provision the Radio ports on the 9500 MPR based on the following criteria:

1. Only one Radio port can have PPPRF enabled. The far endpoint on the same link must have the same configuration as the first endpoint. PPPRF should be disabled on both endpoints for the second and any subsequent Radio links.

9500 MPR management

5620 SAM

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.

9500 MPR node sets the remote interface to 0 momentarily. Note: By default, the PPPRF parameter

Note: By default, the PPPRF parameter is enabled and greyed out on the 5620 SAM GUI. Use NEtO to disable or enable PPPRF parameter, if required. When you configure out-of-band management, the PPPRF and LinkID parameters need not be enabled for the 9500 MPR, Release 5.2, 6.0, and later. If the PPPRF and LinkID parameters are disabled on all the Radio ports, the Radio links are still discovered successfully and the criteria 1 and 2 are not applicable. When you configure in-band management, the 1+0, 1+1 Radio links between two 9500 MPR nodes require the PPPRF parameter to be enabled on the Radio ports for the 5620 SAM to discover the far end 9500 MPR node. The 2+0, 3+0, 4+0 Radio links between two 9500 MPR nodes require the PPRF parameter to be enabled on one of the Radio links at both ends. The PPPRF and LinkID parameters need not be enabled for other Radio links.

4.2.4 9500 MPR Radio link protection schemes

You can apply 9500 MPR Radio link protection by configuring the Protection Type parameter in NEtO. Additionally, you can switch between an in-service protected Radio link and a standby protected link to perform routine maintenance tasks using NEtO. See the 9500 MPR (Hardware) User Manual for more information.

5620 SAM

Workflow to commission and manage 9500 MPR devices

In-service protected Radio links are represented as green links on the Physical topology map; standby links are shown as blue links; out-of-service Radio links, main or spare, are represented as red links. If a mismatch of active and standby states should occur, main links are represented as green links on the Physical topology map; spare links are shown as blue links.

Physical topology map; spare links are shown as blue links. Note: The status of a protected

Note: The status of a protected link does not have a direct impact on the status of a service. See Table 7, “9500 MPR service status” (p. 149) for more information about the service status.

4.3 Workflow to commission and manage 9500 MPR devices

4.3.1 General information

The following workflow describes the high-level tasks required to commission 9500 MPR devices prior to discovery by the 5620 SAM.

4.3.2 Process

1

2

Prepare the 9500 MPR for 5620 SAM management by commissioning the device before discovery by the 5620 SAM. See the workflow to commission Nokia devices in the “Device commissioning and management” chapter in the 5620 SAM User Guide for the procedures that apply to this device type. In addition, perform the following device-specific procedures as required.

3

Configure an SNMP user, the required security mediation policy, and discovery rule for a 9500 MPR; see 4.4 “To prepare a 9500 MPR for 5620 SAM management” (p. 42).

Configure how and when the 5620 SAM polls the device for MIB changes; see

4

4.5

“To configure polling for an 9500 MPR” (p. 44).

Enable the collection of 9500 MPR statistics from a 5620 SAM auxiliary server; see

5

4.6

“To collect 9500 MPR statistics from a 5620 SAM auxiliary server ” (p. 45).

Enable the 5620 SAM to manage a 9500 MPR and to enable the opening of a NEtO session using the 5620 SAM GUI; see 4.7 “To enable 5620 SAM management of 9500 MPR devices” (p. 45).

To prepare a 9500 MPR for 5620 SAM management

5620 SAM

4.4 To prepare a 9500 MPR for 5620 SAM management

4.4.1 General information

The following procedures describe how to prepare 9500 MPR devices (and variants) for commissioning before the 5620 SAM can manage it.

Perform this procedure to configure a SNMP user, the required security mediation policy, and discovery rule for a 9500 MPR.

mediation policy, and discovery rule for a 9500 MPR. Note: Ensure that you create the mediation

Note: Ensure that you create the mediation policy based on whether the 9500 MPR device supports SNMPv2 or SNMPv3, along with the appropriate Trap mediation policy with community string.

4.4.2 Steps

1

 

Create an SNMPv3 user on the 5620 SAM.

1. Choose Administration→Security→NE User Configuration from the 5620 SAM main menu. The NE User Configuration form opens.

2. Click Create. The NE User, Global Policy (Create) form opens.

3. Configure the parameters as required. For the Access parameter, you must choose the SNMP option.

4. Click on the SNMPv3 tab and verify that the SNMPv3 user and user group have been created on the managed NE.

When a user has been assigned the appropriate SNMPv3 permissions, you can configure the following authentication parameters:

• Authentication Protocol—Choose MD5 as the authentication protocol.

• Privacy Protocol—Choose No Privacy as the privacy protocol.

• New Authentication Password

• Confirm New Auth Password

2

5. Click OK and click Search to confirm the creation of the SNMPv3 user.

Configure an SNMPv3 mediation security policy for the SNMPv3 user created in Step 1.

1. Choose Administration→Mediation from the 5620 SAM main menu. The Mediation (Edit) form opens.

2. Click on the Mediation Security tab and click Create. The Mediation Policy (Create) form opens.

5620 SAM

To prepare a 9500 MPR for 5620 SAM management

3. Configure the Displayed Name parameter to identify the policy and set the Security Model parameter to SNMP v3 (USM).

4. In the SNMP panel, set the Port parameter to 161.

5. In the SNMPv3 panel, click Select and choose the SNMPv3 user created in Step 1 and click OK. The Mediation Policy (Create) form reappears.

6. Save your change and close the form.

3

 

Perform one of the following to configure SNMP management and to create a discovery rule for 9500 MPR devices.

Note: The 5620 SAM uses the default SNMPv2 mediation security policy to discover the 9500

Note: The 5620 SAM uses the default SNMPv2 mediation security policy to discover the 9500 MPR.

a. To configure a discovery rule that uses SNMPv3 management; see the “Device discovery” chapter in the 5620 SAM User Guide.

b. To configure a discovery rule that uses SNMPv2 management:

Perform the following steps:

1. Choose Administration→Discovery Manager from the 5620 SAM main menu. The Discovery Manager (Edit) form opens.

2. Click Create. The Create Discovery Rule step form opens with the Specify General Attributes step displayed.

3. Configure the parameter as required and click Next. The Add Rule Elements step appears.

4. Click Create, configure the required parameters and click OK. The Create Discovery Rule step form reappears.

5. Click the Next. The Add Auto Discovery Rule Elements ACL step appears.

6. Optionally click Create, configure the parameter as required and click Next. The Configure Mediation Security step appears.

7. Click Select and choose the mediation security policy created in Step 2 in the Read Access, Write Access, Trap Access, and Security Access Mediation policy panels.

4

8. Click Finish and close the form. All other steps on the Create Discovery Rule step form are optional for the 9500 MPR.

Use the 5620 SAM client to discover the NE and to verify that the NE configuration allows management of the 9500 MPR; see the “Device discovery” chapter in the 5620 SAM User Guide.

END OF STEPS

To configure polling for an 9500 MPR

5620 SAM

4.5 To configure polling for an 9500 MPR

4.5.1 Steps

1

2

In the navigation tree Equipment or Routing view, right-click on a 9500 MPR and choose Properties. The 9500 MPR network element form opens.

3

If required, record the system IP address and management IP address for future configuration requirements.

4

If required, configure the Location and Current OLC State parameters.

5

Click on the Polling tab and configure the Scheduled Polling parameter.

To determine the current polling status:

The read-only parameters provide the following information.

• Resync Status indicates whether the last poll successfully completed.

• Last Resync Start Time and Last Resync End Time indicate the start and finish of the last poll.

• Scheduled Resync Status indicates whether the last scheduled poll successfully completed.

Note: Scheduled resynchronization is disabled, by default, for specific MIB entries. Click on the MIB entry policy in the MIB Entry Policies tab of the Administration→Mediation→Mediation (Edit) form, click properties, and then configure the Polling Interval parameter to enable scheduled resynchronization.

Enabling scheduled resynchronization of the MIB entries for which the scheduled resynchronization is set to disabled by default may have performance impact.

6

• Last Scheduled Resync Start Time and Last Scheduled Resync End Time indicate the start and finish of the last scheduled poll.

Save your changes and close the form.

END OF STEPS

5620 SAM

To collect 9500 MPR statistics from a 5620 SAM auxiliary server

4.6 To collect 9500 MPR statistics from a 5620 SAM auxiliary server

4.6.1 Purpose

Perform this procedure if you plan to use a 5620 SAM auxiliary server to collect 9500 MPR statistics using IPv4 or IPv6.

4.6.2 Steps

1

2

Choose Administration→System Information from the 5620 SAM main menu. The System Information form opens.

3

Click on the Auxiliary Servers tab, choose an auxiliary server from the list and click Properties. The Auxiliary Server (View) form opens.

4

Click on the Auxiliary Services tab and select the STATS_SERVICE entry from the list and click Properties. The Auxiliary Service - STATS_SERVICE (Edit) form opens.

If you are using IPv6, configure the IPv6 Address parameter and click OK.

5

5 Note: During the subsequent device discovery, the 5620 SAM registers the IPv6 address of the

Note: During the subsequent device discovery, the 5620 SAM registers the IPv6 address of the auxiliary server on each discovered 9500 MPR.

Save your changes and close the form.

END OF STEPS

4.7 To enable 5620 SAM management of 9500 MPR devices

4.7.1 Purpose

Perform this procedure to enable the 5620 SAM to manage a 9500 MPR and to enable the opening of NEtO sessions using the 5620 SAM GUI.

enable the opening of NEtO sessions using the 5620 SAM GUI. Note: The NEtO application is

Note: The NEtO application is installed and configured to open automatically for freshly brought up 9500 MPR NEs. Use this procedure only to modify properties files of 9500 MPR NE versions that are not supported in NEtO distribution in Release 10.0 R5.

To enable 5620 SAM management of 9500 MPR devices

5620 SAM

4.7.2 Steps

1

2

Log in to a 5620 SAM client station.

Discover a 9500 MPR and verify that the 5620 SAM can manage the device.

3

3 Note: If this is the first time you are enabling 5620 SAM management of a

Note: If this is the first time you are enabling 5620 SAM management of a 9500 MPR in your network, you must manually create a Read-Write mediation policy and a Trap mediation policy as part of the discovery rule creation process. Special parameter settings apply if you are enabling FTP access. See the “Device discovery” chapter in the 5620 SAM User Guide.

On a Windows client, navigate to the following directory:

path\nms\thirdparty\config

4

where path is the 5620 SAM client installation location, typically C:\5620sam\client

Find the required 9500 MPR properties file, which is named Alcatel-MPR-9500_ Release properties.

5

where Release is the appropriate 9500 MPR release identifier, for example, 3.4.0

6

Open the file using a plain-text editor.

Replace ${path} in the following line with the NEtO directory path; for example, D:\\NEtO

7

install_dir =${path}

For the 9500 MPR only: change the profile name, as required. The format is, profile_ name = <role> <community string> <user id> <password>. For example:

profile_name = admin private initial adminadmin

Note: If you do not edit the profile name, the community string is derived from the If you do not edit the profile name, the community string is derived from the mediation policy of the discovery rule.

5620 SAM

To enable 5620 SAM management of 9500 MPR devices

8

Save and close the file. See 8.7 “To cross-launch the NEtO from the 5620 SAM GUI” (p. 70) for information about how to launch the NEtO from the 5620 SAM GUI.

END OF STEPS

To enable 5620 SAM management of 9500 MPR devices

5620 SAM

5620 SAM

9500 MPR software upgrade

5 9500 MPR software upgrade

5.1 Software upgrade workflow

5.1.1 Introduction

General workflow to perform 9500 MPR device software upgrades:

5.1.2 9500 MPR software upgrade workflow

Upgrade the device software, as required.

1

 

Create a software upgrade policy that specifies MPR Node as the Policy Type; see the “To configure a software upgrade policy” procedure in the 5620 SAM User Guide.

Note:

Note:

2

The software upgrade policy also provides the NE with the location of the software image files on an FTP server.

3

Download the image package to a directory on a 5620 SAM client station. Extract the package and ensure that the software description file is in the same directory.

Import the software description file; see the “To import device software files to the

5620

SAM procedure in the 5620 SAM User Guide.

The 5620 SAM transfers the description file to a specified FTP server from which the

4

9500

MPR subsequently retrieves the image files.

5

Perform a software upgrade to transfer the files to the required NEs; see 5.2 “To perform an on-demand 9500 MPR software upgrade” (p. 50) in this guide or “To schedule an NE software upgrade” procedure in the 5620 SAM User Guide.

Activate the new software as the running software; see 5.3 “To manage the 9500 MPR running software” (p. 51).

To perform an on-demand 9500 MPR software upgrade

5620 SAM

5.2 To perform an on-demand 9500 MPR software upgrade

5.2.1 Purpose

Perform this procedure to upgrade the device software on one or more 9500 MPR NEs. Prior to performing this procedure, review the 9500 MPR software upgrade workflow steps contained in the 5.1 “Software upgrade workflow” (p. 49) for the additional procedures required to complete this procedure.

The 9500 MPR software is stored in two banks on a compact flash card:

• The committed bank contains the software that is currently running.

• The standby bank contains downloaded software that has not been activated, or software that was active before the current committed software.

that was active before the current committed software. Note: • A 9500 MPR that has never

Note:

• A 9500 MPR that has never been upgraded displays only the committed bank. The standby bank is not displayed until new software is downloaded for the first time.

• You require a 5620 SAM user account with an administrator or network element software management scope of command role, or a scope of command role with write access to the mediation package before you can perform a 9500 MPR software download.

• After a 5620 SAM system upgrade from 12.0 R7 or later, you must delete any previously imported MPR software images used to perform a 9500 MPR software upgrade and re-import the same.

5.2.2 Steps

1

2

Choose Administration→NE Maintenance→Software Upgrade from the 5620 SAM main menu. The Software Upgrade form opens.

Click on the Software Images tab, select the appropriate software upgrade policy and then the MPR 9500 Software Images tab.

3

3 Note: The 5620 SAM performs the upgrade according to the configuration in the software upgrade

Note: The 5620 SAM performs the upgrade according to the configuration in the software upgrade policy to which the NE is assigned.

4

Click Import and select a software descriptor file. A software descriptor file has a .DSC extension and must be present on the client system. Other software files do not need to be present on the client system.

5620 SAM

To manage the 9500 MPR running software

Click Upgrade Sites. A list of NEs opens. The list is filtered to display only the device type that is appropriate for the selected software image.

5

6

Select one or more NEs and click OK. The software upgrade begins.

7

Click on the Software Upgrade Status tab to view the status of the upgrade as it progresses. Verify that the files are successfully transferred.

Close the Software Upgrade form. After a successful software upgrade, you must activate the software; see 5.3 “To manage the 9500 MPR running software” (p. 50)

END OF STEPS

5.3 To manage the 9500 MPR running software

5.3.1 Purpose

Perform this procedure to manage the software in the 9500 MPR committed and standby banks. You can upgrade or downgrade the running software release on a 9500 MPR.

See “NE software upgrade overview” in the 5620 SAM User Guide for information about creating software upgrade policies and performing software upgrades.

software upgrade policies and performing software upgrades. WARNING Equipment Damage To avoid a service outage: A

WARNING

Equipment Damage

To avoid a service outage:

A 9500 MPR may require a firmware upgrade before a device software upgrade. To avoid a service outage, ensure that the device firmware version supports the software upgrade. See the device software Release Notes to obtain information about firmware and software release compatibility.

about firmware and software release compatibility. CAUTION Service Disruption Perform this procedure only in a

CAUTION

Service Disruption

Perform this procedure only in a maintenance window:

When you reboot a 9500 MPR that is in service, it is service-affecting. Ensure that the reboot activity occurs during a maintenance window.

To manage the 9500 MPR running software

5620 SAM

To manage the 9500 MPR running software 5620 SAM Note: During a software upgrade, the NE

Note: During a software upgrade, the NE audit function is not supported for 9500 MPR NEs.

5.3.2 Steps

1

2

In the navigation tree Equipment view, right-click on a 9500 MPR shelf and choose Properties. The Shelf (Edit) form opens.

3

Click on the Software Bank Details tab. The committed and standby software information is displayed. The committed software is the software currently running on the NE. The standby software is new software uploaded to the NE, or formerly committed software.

Verify that the operational state of the standby software is Enabled by examining the Operational State value.

4

You can also examine the Software Version of the standby and committed software. If the software version of the standby software is more recent than the committed software version, the NE can be upgraded. If the standby software version is older than the committed software version, the NE can be downgraded.

5

Select the standby entry and click Properties. The MPR Software Package (Edit) form opens.

6

Configure the Activation parameter and click OK. The Shelf (Edit) form reappears.

7

Save your changes and close the form. When the standby and committed software versions are different or the forced activation option is selected, the NE reboots using the standby software. If the standby and committed software versions are the same and the activation option is chosen, the NE does not reboot and the Shelf (Edit) form closes.

After the NE reboots, you can confirm that the NE is running the software stored in the former standby bank. The former standby software is the committed software and the previous committed software is the standby software.

END OF STEPS

5620 SAM

9500 MPR migration to revised service model

6

9500 MPR migration to revised service model

6.1

Migration workflow

6.1.1

Workflow

Pre-upgrade

1

Perform the pre-upgrade tasks to upgrade from any of the 5620 SAM releases earlier than 14.0 R7. See 6.2 “To perform pre-upgrade tasks ” (p. 53).

5620 SAM upgrade

2

See 5620 SAM Installation and Upgrade Guide for more information about 5620 SAM upgrade.

Post upgrade

3

Perform the post upgrade tasks to upgrade from any of the 5620 SAM releases earlier than 14.0 R7. See 6.3 “To perform post upgrade tasks” (p. 54).

6.2 To perform pre-upgrade tasks

6.2.1 Steps

Clear incomplete deployments

1

2

Choose Administration→NE Maintenance→Deployment. The Deployment form opens with the Incomplete Deployments tab displayed.

3

Select all entries in the Incomplete Deployments tab and click Clear.

Close the form.

To perform post upgrade tasks

5620 SAM

Execute script

4

5

Log in to the 5620 SAM database station as the Oracle management user.

Download the following 5620 SAM installation script to a local directory in which the Oracle management user has read, write, and execute privileges:

6

MPR_migrate.bash

Use a CLI to navigate to the script location and enter the following:

./MPR_migrate.bash

Unmanage services from 5620 SAM releases earlier than 14.0 R7

7

Choose Manage→Service→Services from the 5620 SAM main menu. The Manage Services form opens.

8

Click Search, choose the 9500 MPR services and click Unmanage MPR 9500 Services.

the 9500 MPR services and click Unmanage MPR 9500 Services. Note: Unmamage MPR 9500 Services button

Note: Unmamage MPR 9500 Services button is only available in 5620 SAM releases earlier than 14.0 R7.

9

Close the form.

END OF STEPS

6.3 To perform post upgrade tasks

6.3.1 Steps

Discover microwave backhaul services

1

Perform microwave backhaul service discovery. See 16.6 “Microwave backhaul service discovery” (p. 139) for more information.

5620 SAM

To perform post upgrade tasks

Migrate service data

2

3

Log in to the main server station as the samadmin user.

4

Navigate to the /opt/5620sam/server/nms/config directory.

5

Create a backup copy of the nms-server.xml file.

NOTICE

NOTICE

Service-disruption hazard

Contact technical support representative before you attempt to modify the nms- server.xml file.

Modifying the nms-server.xml file can have serious consequences that can include service disruption.

6

Open the nms-server.xml file using a plain-text editor.

Locate the following XML tag:

7

<mprServiceProcessing>

Modify the value as follows:

8

enableMigration= "true"

9

Save and close the nms-server.xml file.

10

Navigate to the /opt/5620sam/server/nms/bin directory.

Enter the following:

bash$ ./nmsserver.bash read_config

To perform post upgrade tasks

5620 SAM

Result: Because One-to-one relationship between 9500 MPR services in 5620 SAM Releases earlier than 14.0R7 and microwave backhaul services in 5620 SAM Release 14.0 R7 does not exist, all of the data may not be migrated from the 5620 SAM releases earlier than 14.0R7 to 5620 SAM Release 14.0 R7.

11

12

Navigate to the /opt/5620sam/server/nms/config directory.

13

Create a backup copy of the nms-server.xml file.

14

Open the nms-server.xml file using a plain-text editor.

Locate the following XML tag:

15

<mprServiceProcessing>

Delete the following parameter:

16

enableMigration= "true"

Save and close the nms-server.xml file.

END OF STEPS

5620 SAM

9500 MPR SCM device management

7 9500 MPR SCM device management

7.1 Secure certification mode

7.1.1 Introduction

The 5620 SAM supports the management of the CorEvo-based 9500 MPR devices (Release 7.1 or later) that are configured in a secure certification mode and are managed using the secure protocols. The security certification mode is configured in split-mount systems where the encryption block is installed in the radio transceiver connected to the MSS shelf over a Gigabit Ethernet interface.

The 9500 MPR devices that are configured in secure certification mode are managed from:

• 5620 SAM

• Highly Secure Key Management Tool (SMS). The SMS is a network manager that provides management of AES keys.

• WebCT as local manager

The 5620 SAM, SMS, and 9500 MPR devices are inter-connected over a secure IPSec DCN through points of presence (POP). The communication between 5620 SAM and SMS with the 9500 MPR devices is over SNMPv3. See the 9500 MPR node documentation for more information about SAS and WebCT.

7.1.2 Trusted manager

The 5620 SAM can manage a 9500 MPR SCM device only when the server IP address is configured as a trusted manager in the WebCT. The 5620 SAM generates the PollerProblem alarm when try to discover the 9500 MPR SCM device without adding the IP address in the trusted manager. You can add a maximum of five IP addresses in the trusted manager. You need to delete an entry to add another trusted manager, if the limit is exceeded. See the 9500 MPR node documentation for more information about configuring the trusted managers in the WebCT.

7.1.3 Enable HTTPS protocol

The 5620 SAM allows you to enable or disable the HTTPS protocol from the System Settings tab of the Network Element (Edit) form. When you set the HTTPS Protocol parameter as Enabled, you can access the node from the 5620 SAM and from the WebCT.

Secure certification mode

5620 SAM

7.1.4 Disable HTTPS protocol

certification mode 5620 SAM 7.1.4 Disable HTTPS protocol DANGER If the 9500 MPR SCM device is

DANGER

If the 9500 MPR SCM device is unmanaged with the HTTPS Protocol parameter set to Disabled, no other EMS or NMS that does not have the server IP address registered in trusted manager of the 9500 MPR SCM device can access the 9500 MPR SCM device.

To recover the 9500 MPR SCM device, you must remanage the device in the NMS that has the IP address added in trusted manager of the 9500 MPR SCM device and enable the HTTPS Protocol. If the 5620 SAM server is not available, you should reset the 9500 MPR SCM device to factory settings

See the 9500 MPR node documentation for more information about resetting the 9500 MPR SCM device to factory settings.

about resetting the 9500 MPR SCM device to factory settings. WARNING Disabling HTTPS protocol When you

WARNING

Disabling HTTPS protocol

When you set the HTTPS Protocol parameter as Disabled, you can access the node only from the 5620 SAM that has the IP address added in trusted manager of the 9500 MPR SCM device.

You should ensure that the HTTPS Protocol parameter is set to Enabled in the System Settings tab of the Network Element (Edit) form, before unmanaging the 9500 MPR SCM device.

7.1.5 Log retrieval

The 5620 SAM supports the retrieval of the logs stored by the 9500 MPR SCM devices.

The logs include:

• all user administration operations and the configuration changes in user activity logs in a user readable format. One entry is captured for each user action.

• all the security-related events in a security audit trail. These events include all security-related settings changes, user accounts management, exporting audit logs and user login attempt failure.

Three types of log files are stored:

• UAL LOG (user activity through WebCT is stored)

• SNMP LOG (users activity through SNMP interface is stored)

• AUDIT LOG (security log is stored)

5620 SAM

Workflow to manage 9500 MPR SCM devices

For each LOG file type, the 9500 MPR SCM device stores a maximum of five log files. More than five files are deleted. See 7.6 “To retrieve logs stored by 9500 MPR SCM devices” (p. 63) for more information about retrieving logs.

7.1.6

Backup and restore

The 5620 SAM does not support the backup and the restore function for 9500 MPR SCM devices.

7.1.7

Software upgrade

The 5620 SAM does not support the software upgrade function for 9500 MPR SCM devices.

7.1.8

Alarms

The following alarms are supported in the SCM:

• CKM (Current Key Mismatch)

• NKM (Next Key Mismatch)

• KeyUnavailable (Key Unavailable)

• ESM (Encryption State Mismatch)

• TrafficDown (Radio Traffic Down)

• AesFipsFailure (MPT AES Engine self-test failure)

7.1.9

ECFM, TACACS+, and IPv6

The 9500 MPR SCM devices do not support ECFM, TACACS+, and IPv6.

7.1.10

Protection configuration

Ensure that you power off the 9500 MPR SCM device after the protection configuration is removed from the 9500 MPR SCM device. Then, power on the 9500 MPR SCM device for the correct protection configuration to reflect in the 5620 SAM for the 9500 MPR SCM device.

7.2 Workflow to manage 9500 MPR SCM devices

7.2.1 Process

1

Configure the SNMPv3 user in the WebCT. See the 9500 MPR node documentation for more information about configuring the SNMPv3 user in the WebCT.

To configure an SNMPv3 user account on an 9500 MPR SCM device

5620 SAM

2

3

Configure the 5620 SAM server IP address in WebCT Trusted Managers. See the 9500 MPR node documentation for more information about configuring the 5620 SAM server IP address in WebCT Trusted Manager.

4

Configure the SNMPv3 user account in the 5620 SAM. See 7.3 “To configure an SNMPv3 user account on an 9500 MPR SCM device” (p. 59) for more information about configuring the SNMV3 user in the 5620 SAM.

5

Configure the 9500 MPR SCM device mediation policy. See 7.4 “To configure 9500 MPR SCM NE mediation” (p. 61) for more information about configuring the NE mediation.

Configure the discovery rule. See 7.5 “To configure a discovery rule” (p. 62) for more information about configuring the discovery rule.

7.3 To configure an SNMPv3 user account on an 9500 MPR SCM device

7.3.1 Steps

1

2

Choose Administration→Security→NE User Configuration from the 5620 SAM main menu. The NE User Configuration form opens.

3

Click Create. The NE User Global Policy (Create) form opens.

4

Configure the User Name parameter as the same SNMPv3 user name that you configured in the WebCT.

5

Select SNMP in the Access panel and click on the SNMPv3 tab.

Set the Authentication Protocol parameter to SHA.

5620 SAM

To configure 9500 MPR SCM NE mediation

6

7

Set the Privacy Protocol parameter to AES 256.

8

Configure the parameters in the Set New Authentication Password and the Set New Privacy Password panels with the same values that you provided in the WebCT.

Save your changes and close the form.

END OF STEPS

7.4 To configure 9500 MPR SCM NE mediation

7.4.1 Steps

1

2

Choose Administration→Mediation from the 5620 SAM main menu. The Mediation (Edit) form opens with the General tab displayed.

3

Click on the Mediation Security tab.

Perform one of the following:

a. Click Create to create a new mediation security policy. The Mediation Policy (Create) form opens.

4

b. Choose an existing policy and click Properties. The Mediation Policy (Edit) form opens.

5

Set the Security Model parameter as SNMP v3 (USM).

6

Select the SNMPv3 user in the SNMPv3 panel.

Retain the default values for all other parameters in the Mediation Policy (Create /Edit) form.

To configure a discovery rule

5620 SAM

7

Save your changes and close the form.

END OF STEPS

7.5 To configure a discovery rule

7.5.1 Steps

1

2

Choose Administration→Discovery Manager from the 5620 SAM main menu. The Discovery Manager form opens.

3

Click Create. The Specify General Attributes step form opens.

4

Configure the required parameters.

Select a equipment group.

5

5 Note: If the selected equipment group reaches the maximum element limit, any additional discovered NEs

Note: If the selected equipment group reaches the maximum element limit, any additional discovered NEs are automatically added to the Discovered NEs group.

6

Set the Discovery Protocol parameter as SNMP.

7

Click Next. The Add Rule Elements form opens.

8

Click Create to add a new rule element. The Topology Discovery Rule Element (Create) form opens.

9

Configure the required parameters and click OK.

Click Next. The Add Auto Discovery Rule Elements ACL form opens.

5620 SAM

To retrieve logs stored by 9500 MPR SCM devices

10

11

Retain the default values and click Next. The Configure Mediation Security form opens.

12

Select the SNMPv3 mediation security policy for read, write, and trap access and the default mediation policy for security access and click Next.

13

Retain the default values for all other parameters in the remaining step forms.

Click Finish.

14

Result: The 9500 MPR SCM device is discovered in the 5620 SAM. The device appears on the equipment navigation tree and the topology map.

Perform the following to view the device properties:

1. Right-click on the device and choose properties. The Network Element (Edit) form Opens

15

2. Click on the System Settings tab and the SNMP Mode parameter displays the read-only value as Secured Certified.

Save your changes and close the form.

E