unims r4.2 technology driver omnibas8w r5.1 rm ed2.1 en

Reference Manual

Edition 2.1Confidential

Driver for OmniBAS-8W(R.5.1 for Core 4.2)

GDC-003/33

INTRACOM TELECOM19.7 km Markopoulou Ave., Peania, Athens, GR 19002

T +30 210 667 1000, F +30 210 667 1001http://www.intracom-telecom.com

email (product support): [email protected]

The information contained in this document is subject to change without prior notice.

INTRACOM S.A. TELECOM SOLUTIONS, 2013. All rights reserved.

All copyright, intellectual and industrial rights in this document and in the technical knowledge it containsare owned by INTRACOM S.A. TELECOM SOLUTIONS and/or their respective owners.

This document is made available to the end users only for their internal use.No part of this document nor any data herein may be published, disclosed, copied, reproduced,redistributed by any form or means, electronically or mechanically, or used for any other purposewhatsoever without the prior written approval of INTRACOM S.A. TELECOM SOLUTIONS.Information as well as drawings and specifications contained in this document are subject to changewithout prior notice.

All trademarks and copyrights mentioned herein are the property of INTRACOM S.A. TELECOMSOLUTIONS and/or their respective owners.Any rights not expressly granted herein are reserved.

Printed in Greece.

uni|MS Driver for OmniBAS-8WReference Manual - Edition 2.1

1

Table of Contents

1 About this Document.......................................................................................... 5

2 Discovering & Modelling .................................................................................... 72.1 Discovery........................................................................................................................ 7

Physically Connecting uni|MS to OmniBAS-8W NEs....................................................... 8Discovering the OmniBAS-8W NEs............................................................................... 11

2.2 User Interface............................................................................................................... 12OmniBAS NEs Photorealistic View................................................................................ 13OmniBAS State Indicators in Photorealistic View .......................................................... 15

2.3 Modelling...................................................................................................................... 17Summary Information of an OmniBAS-8W NE .............................................................. 17

3 Configuration..................................................................................................... 193.1 Management ................................................................................................................ 19

Changing the Outband IP Address................................................................................ 21Configuring the Inband Management ............................................................................ 22Setting the Real Time Clock (RTC) ............................................................................... 24Configuring Trap Destinations ....................................................................................... 25Configuring Trap Profiles............................................................................................... 27Adding/ Removing Static Routes................................................................................... 30Modifying Communication Credentials .......................................................................... 32

3.2 OmniBAS-8W NE (Basic) ............................................................................................ 34Configuring Synchronization Source ............................................................................. 35Configuring GbE (electrical) / GbE (SFP) Ports............................................................. 44Configuring Modem Parameters.................................................................................... 48Configuring Radio Parameters ...................................................................................... 52Configuring Hot Standby (HSB) Protection.................................................................... 54Enabling / Disabling APS Operation of SDH Interface Card .......................................... 57Configuring 16/32 E1 Interface Card ............................................................................. 64Setting OmniBAS-8W NE Thresholds............................................................................ 67Activating/ Deactivating External Devices & Monitoring External Alarms....................... 70Recording Site Information............................................................................................ 71

3.3 Bridge ........................................................................................................................... 72Configuring Bridge Parameters ..................................................................................... 72Configuring L2 Ports...................................................................................................... 74Adding (or Removing) VLANs / VLAN Ports .................................................................. 81Configuring a VLAN Transparent Port ........................................................................... 85Configuring Static Ethernet LAG.................................................................................... 86Configuring RSTP ......................................................................................................... 88

3.4 Ethernet QoS ............................................................................................................... 95Configuring 802.1q Priorities ......................................................................................... 96Configuring DSCP Remarking to p-bit ........................................................................... 99Configuring Policer Parameters................................................................................... 102

Table of Contents

2

Configuring Service Flows........................................................................................... 108Configuring Forwarding Process ................................................................................. 113

3.5 Saving Configuration .................................................................................................118

4 Provisioning Service Fragments ................................................................... 1194.1 Ethernet......................................................................................................................120

4.2 PWE TDM (E1) ..........................................................................................................122

4.3 PWE TDM (VC-12) ....................................................................................................126

5 Status ............................................................................................................... 1305.1 Inventory.....................................................................................................................131

5.2 Link Summary Status.................................................................................................134

5.3 Equipment Status....................................................................................................... 137

5.4 Cards..........................................................................................................................140Power Supply of Control Card Status .......................................................................... 141Modem Card Status .................................................................................................... 14316/32 E1 Interface Card Status ................................................................................... 148SDH Interface Card Status.......................................................................................... 150

5.5 Ports / Lines ...............................................................................................................152ODU Status................................................................................................................. 153GbE (Electrical / SFP) Port Status............................................................................... 157E1 Line Status............................................................................................................. 159STM-1 (VC-12) Port Status ......................................................................................... 161

6 Testing & Maintenance Procedures .............................................................. 1646.1 Testing........................................................................................................................164

Performing Loopback Test on an Ethernet L2 Port...................................................... 165Performing Loopback Test on an E1 Line.................................................................... 168Performing Loopback Test on an STM-1 (VC-12) Port ................................................ 171Performing DC Power Off Test on ODU ...................................................................... 174

6.2 Maintenance...............................................................................................................176Performing Reset Actions............................................................................................ 177Backing up Configuration ............................................................................................ 180Restoring Configuration............................................................................................... 182Upgrading NE Software............................................................................................... 184Upgrading ODU Software............................................................................................ 187Collecting Logs............................................................................................................ 189Clearing the Whole Configuration of OmniBAS-8W NE............................................... 191

7 Performance .................................................................................................... 1927.1 Real-Time Performance.............................................................................................192

Monitoring Link Availability (in Rx Path)....................................................................... 193Monitoring Link Performance via Graphs..................................................................... 194Monitoring Link Performance via G.826 Counters ....................................................... 196Monitoring Link Performance via Graphs based on G.826........................................... 198


3

Monitoring ODU Performance ..................................................................................... 200Monitoring Ethernet Traffic Performance (via Modem) ................................................ 201Monitoring Performance of L2 Ports ............................................................................ 206Monitoring RMON Counters of GbE Port..................................................................... 209Monitoring Performance of GbE Port (via Traffic Graphs)............................................ 214Monitoring Current Temperature of Control / Modem Cards........................................ 215Monitoring Current Performance of PWE Service Fragment........................................ 217

7.2 Historical Performance ..............................................................................................219Monitoring Historical Performance of PWE Service Fragment..................................... 219

8 Monitoring Alarms & Events .......................................................................... 2228.1 Actions / Information provided by uni|MS..................................................................223

8.2 Alarms List .................................................................................................................224

8.3 Events List..................................................................................................................237

Appendix A - IEEE 802.1q / ad Ethernet Frames..................................................... 239

Appendix B - OmniBAS S/W Version Names.......................................................... 241

Glossary..................................................................................................................... 243

Table of Contents

4

(Page intentionally left blank)


5

1 About this Document

Scope ofdocument

The scope of this document is to provide detailed instructions on themanagement of OmniBAS-8W Network Elements (NEs), through the uni|MSDriver for OmniBAS.

S/W versions This document refers to the following OmniBAS-8W NE and uni|MSManagement Suite software versions:

Component S/W version (1)

OmniBAS-8W R-5.1.1821.2.0.0uni|MS 4.2

TargetAudience

This document is addressed to field technicians responsible for setting-up,configuring, monitoring, testing or troubleshooting an OmniBAS-8W NEthrough uni|MS Node Manager.

Referencemanuals

Kindly refer to the uni|MS Documentation Catalog, also available byIntracom Telecom, denoting the list with all existing uni|MS documentstogether with their scope.

DocumentConventions

This document applies the following conventions: Bold fonts are used for buttons, menus/ sub-menus, wizards, actions

selected by Smart Menu, tabs, group/ text/ check boxes and drop-downlists.

Italic fonts are used for window/ view names, values of an attribute, uni|MSapplications and references to other documents.

Blue underline fonts are used for references within this document.

NOTE A note calls your attention to important supplementaryinformation.

This symbol means CAUTION. The purpose of this symbol is toprevent you from performing an action that might result in damageof the equipment or management / traffic loss.

Continued on next page

(1) For the naming format of S/W versions, see Appendix B - OmniBAS S/W Version Names.

Chapter 1. About this Document

6

About this Document, Continued

DocumentWarranty

The uni|MS screenshots in this manual are only examples. Screenshots willvary according to equipment configurations, equipment operation modes,settings/ parameters, uni|MS application program version, etc. Screensshown in this manual are current at the time of publication and may differ fromthe actual windows of your uni|MS.


7

2 Discovering & Modelling

This chapter provides the information that you need to discover and modelOmniBAS-8W NEs so that you will be able to starting NEs managementthrough uni|MS Driver for OmniBAS.The chapter groups Discovering & Modelling information into the followingsections: Discovery User Interface Modelling

2.1 Discovery

This section provides the information that you need to discoverOmniBAS-8W NEs. The section includes the following topics: Physically Connecting uni|MS to OmniBAS-8W NEs Discovering the OmniBAS-8W NEs

Chapter 2. Discovering & Modelling

8

Physically Connecting uni|MS to OmniBAS-8W NEs

Introduction This paragraph provides the necessary information for making the physicalconnection of the uni|MS to an OmniBAS-8W NE. The connection of theuni|MS with an OmniBAS-8W NE can be inband or outband and it is madethrough the Control Card.

Outbandmanagementconnection

The outband management of an OmniBAS-8W NE can be applied eitherdirectly on your PC/ Laptop (for initial configuration or commissioningpurposes) (A) or through a DCN (B).For the outband management connection, see below the physical connectionrequirements: Use an Ethernet CAT5 (or better) cable in case of OmniBAS-8W. Connect one end of the cable to MNG port (10/100 Mbps) of Control

Card 1 (Control Card fitted in slot 9). Note that you can connect to ControlCard 2 only when Control Card 1 is extracted.

Connect the other end of the cable directly to your PC/ laptop or to anavailable LAN port.

NOTE For detailed instructions on the outband management cabling ofOmniBAS-8W equipment, please refer to the correspondingInstallation & Cabling Manual of OmniBAS-8W.

NOTE 192.168.1.100 is the default (outband) IP address of the OmniBASNEs. Also, 192.168.255.254 is the debug IP address that can beused when operator does not know / remember the outband orinband IP address of the NE.

NOTE To establish a successful connection, both, PC/ Laptop runninguni|MS Node Manager application and OmniBAS-8W managementinterface must be in the same subnet. To allow this, changetemporarily the IP address of your PC/ Laptop to an appropriate one(for example, change to 192.168.1.110 when OmniBAS-8Wmanagement interface uses its default (or debug) IP address).



9

Physically Connecting uni|MS to OmniBAS-8W NEs, Continued

Outband management connection (continued)

(A) Outband Management Connection - Directly on PC/ Laptop

(B) Outband Management Connection - Through DCN



10

Physically Connecting uni|MS to OmniBAS-8W NEs, Continued

Inbandmanagementconnection

The inband management connection on an OmniBAS NE is implementedthrough one of the six GbE ports of Control Card: 2 x electrical GbE (GbE1 and GbE2) 4 x GbE (SFP) (GbE3, GbE4, GbE5 or GbE6)

NOTE Before making an inband management connection on anOmniBAS-8W NE, verify that the inband management parameters ofthe NE have been set (as described in par. Configuring the InbandManagement, on page 22).


11

Discovering the OmniBAS-8W NEs

To discover the OmniBAS-8W NE through the uni|MS Node Manager,proceed as follows:

Step Action1 Connect to uni|MS Node Manager (Launch Client and Log-in).2 View managed NE (via Photorealistic View).

NOTE For full description of the actions, please refer to uni|MS NodeManager Common Actions for all NEs Reference Manual.

End of procedure.


12

2.2 User Interface

The scope of this section is to get you familiar with the User Interface of theuniMS Node Manager for OmniBAS.The section includes the following topics: OmniBAS NEs Photorealistic View OmniBAS State Indicators in Photorealistic View


13

OmniBAS NEs Photorealistic View

Introduction This paragraph shows the photorealistic view of the OmniBAS-8W NE andhelps you to identify the OmniBAS-8W equipment managed by uni|MS.

NOTE One OmniBAS-8W NE is managed per uni|MS Node Managerinstance.

Cards Slot Card / Module Available Card Types1 to 8 Modem PTP Modem

XPIC_PTP 9 Control Card(1) Control Card 4GbSFP - 2Gb Electrical 1

10 Control Card(1) Control Card 4GbSFP - 2Gb Electrical 211 Interface Card Interface Card 16E1 1

Interface Card 32E1 1 Interface Card 1+1xSTM-1-VC12 1 Interface Card 4xSTM-1-VC12 1

12 Interface Card Interface Card 16E1 2 Interface Card 32E1 2 Interface Card 1+1xSTM-1-VC12 2 Interface Card 4xSTM-1-VC12 2

Fan Tray


(1) Through Control Card 1 the corresponding Power Supply (PS1) sub-unit is managed. Also, PowerSupply (PS2) sub-unit of Control Card 2 is managed through Control Card 2.


14

OmniBAS NEs Photorealistic View, Continued

Ports Find below the ports / lines of OmniBAS-8W NE managed by uni|MS:

Card Ports / LinesControl Card 4GbSFP - 2Gb Electrical GbEthernet x.1 to GbEthernet x.4 (SFP)

GbEthernet x.5 and GbEthernet x.6 (Electrical)Interface Card 16E1 E1 x.1 to E1 x.16Interface Card 32E1 E1 x.1 to E1 x.16 and E1 x.17 to E1 x.32Interface Card 1+1xSTM-1-VC12 STM1_VC12 x.1 and STM1_VC12 x.2Interface Card 4xSTM-1-VC12 STM1_VC12 x.1 to STM1_VC12 x.4Modem Card ODU x

Where x = Card slot number

NOTE The selection of the E1 lines (for configuration and monitoringpurposes) is made through the E1 panel.To access E1 panel, select the 16/32 E1 Interface Card and clickthe Forward ( ) button on the System View toolbar (or double-click on the Interface Card). To return back to NE, click theBackward ( ) button.


15

OmniBAS State Indicators in Photorealistic View

Introduction This paragraph describes the state indicators used by uni|MS in photorealisticview to depict the current status of the OmniBAS-8W NE.The state indicators used by uni|MS are listed and described in the GraphicalView Legend window (see schematic below) that appears when you selectthe Show legend ( ) button in the System/ Graphical View toolbar.In the schematic below, the state indicators that are specific for OmniBAS-8WNE are shown with orange marking. The remaining (no marked) indicators areused by uni|MS for any type of NE.

Common stateindicators forany type of NE

For the description of the state indicators that are common for all NEsmanaged by uni|MS, please refer to uni|MS Node Manager Common Actionsfor all NEs Reference Manual (Chapter 3, par. Graphical Indications Used inSystem (Photorealistic) View).

Specific stateindicators forOmniBAS-8WNE

The following table describes the state indicators provided by uni|MS for theOmniBAS-8W NE:

Indicator Color Position Description

Green Control Card / NE Locked operational status for thesynchronization of the OmniBAS-8W NE.

Grey Control Card / NE Freerun or Unlocked operation status forthe synchronization of the OmniBAS-8WNE.

Orange Control Card / NE HoldOver operation status for thesynchronization of the OmniBAS-8W NE.



16

OmniBAS State Indicators in Photorealistic View, Continued

Specific state indicators for OmniBAS-8W NE (continued)

Indicator Color Position Description

White Modem Modem works in protected mode and it isthe standby one.

Black Modem Modem works in protected mode and it isthe working one.

Green Modem (left(1)) Modem (local) is locked.

Modem (right(1)) Associated remote Modem is locked.ODU ODU is connected.Fast Ethernet orelectrical GbE port

Ethernet link is up (there is no EthernetLink Down alarm).

Optical GbE port Ethernet link is Ok (there is no SFP RxLOS and/ or Ethernet Link Down alarm).

STM-1 port STM-1 link is Ok (there is no active alarm).Red Modem (left(1)) Modem (local) is not locked.

Modem (right(1)) Associated remote Modem is not locked.Black Modem (right(1)) Associated remote Modem is unknown (i.e.

its status cannot be retrieved). Not Used (2)

(1) Example: Left / right indicators on a Modem Card:

(2) Feature available in a next S/W version.


17

2.3 Modelling

Summary Information of an OmniBAS-8W NE

AboutSummary view

uni|MS provides the Summary view of the OmniBAS-8W NE to get an overviewabout its current status.More specifically, the Summary view of the OmniBAS-8W NE summarizes in asingle screen general information about OmniBAS-8W NE and also informationabout the current link status of each connected Modem. (When no Modem isinstalled in an OmniBAS-8W slot, the corresponding fields are displayedblank).To open the Summary view of an OmniBAS-8W NE, right-click on theOmniBAS-8W NE and select Summary. Alternatively (in case of uni|MS Node Manager or Node Managerperspective), select the OmniBAS-8W NE and in the NM Tabbed Pane clickthe Summary tab.

NE status In the upper part of the Summary view, the following general informationabout OmniBAS NE is provided: Software version System uptime Operational status of modem pairs (standalone or protected)



18

Summary Information of an OmniBAS-8W NE, Continued

Modem / ODUstatus

Summary view provides the following information for monitoring the status ofeach connected Modem (and its associated ODU): Modem protection state. (1) Link status of selected local Modem and associated remote Modem. Inband IP address of the remote NE and slot position of the remote

Modem. ACM / ATPC mode used. Current Modulation Mode, Bandwidth Channel and Configuration Profile

on Tx (local to remote path) and Rx (remote to local path) directions. Data throughput on Tx (modem to network ports) and Rx (network ports to

modem) directions. Communication status between ODU and Modem equipment. Mute status of the ODU in relation with operational status of Modem. LDPC Decoders Stress. Number of uncorrected FEC blocks. ODU transmission power. SNR and RSSI values. XPIC XPD value. (2)

NOTE For detailed information about the Summary view, see par. LinkSummary Status, on page 134.

(2) Applicable only for Modems of XPIC type.


19

3 Configuration

This chapter provides all procedures required to configure an OmniBAS-8WNE. The chapter groups configuration procedures into the following sections: Management OmniBAS-8W NE (Basic) Bridge Ethernet QoS

3.1 Management

Introduction This section describes how to configure the management parameters of theOmniBAS-8W NE. The section includes the following topics: Changing the Outband IP Address Configuring the Inband Management Setting the Real Time Clock (RTC) Configuring Trap Destinations Configuring Trap Profiles Adding/ Removing Static Routes Modifying Communication Credentials


Chapter 3. Configuration

20

Management, Continued

OpeningManagementview

Right-click on the OmniBAS-8W NE and select Configuration. Alternatively (in case of uni|MS Node Manager or Node Managerperspective), select the OmniBAS-8W NE and in the NM Tabbed Pane click theConfiguration tab.In the Configuration view of the OmniBAS-8W NE, select the Management tab.In the Management view, select: The Inband/ Outband/ RTC tab(1) to configure the inband and outband

management parameters and Real Time Clock (RTC).

The Trap Destinations tab to manually add or remove Trap Destinations. The Trap Profiles tab to add or remove Trap Profiles(2). The Static Routes tab to add or remove Static Routes.

(1) System Bridge feature (Bridge Connection between Inband &Outband Interfaces) will be available in anext S/W version.(2) Experimental feature in current S/W version.


21

Changing the Outband IP Address

Introduction This paragraph describes how to change the outband IP address of anOmniBAS-8W NE.

NOTE 192.168.1.100 is the default IP address of the OmniBAS-8W NEfor outband connection.

Procedure To change the outband IP address of an OmniBAS-8W NE, open theManagement view of the OmniBAS-8W NE and select the Inband/Outband/RTC tab. Then, proceed as follows:

Step Action1 In the Outband Management Parameters group box:

Enter the new outband IPaddress in the IPAddress text box.

Enter the new outbandnetmask (if required) inthe NetMask text box.

NOTE The Mac Address text box displays the MAC address ofthe OmniBAS-8W NE physical interface through which theoutband connection with uni|MS is made.

2 Click to apply the settings.3 If you manage the OmniBAS-8W NE through outband connection,

the contact with the specific NE will be lost. To recover the contactwith the NE log-in again by giving the new outband IP address.

End of procedure.


22

Configuring the Inband Management

Introduction This paragraph describes how to configure the inband management ofan OmniBAS-8W NE.

Prerequisites In the initial configuration of an OmniBAS-8W NE use an outbandconnection to set their inband parameters. Thereafter, the OmniBAS-8WNE is ready to be managed via inband connection.

The VLAN with ID=1 is the default management VLAN of theOmniBAS-8W NE. It is recommended to change the default managementVLAN associating to a new one.

The VLAN ID to be assigned to management should be created inadvanced and it should be also associated with the appropriate L2 ports(through VLAN / VLAN Port view).

The management VLAN should be associated to the L2 modemports of the OmniBAS-8W NE taking into account the remoteconnectivity and loop avoidance. Otherwise, management losswith the remote NE will take place and a visit to the site maybe required.

Procedure To configure the inband management of the OmniBAS-8W NE, open theManagement view of the OmniBAS-8W NE and select the Inband/Outband/RTC tab. Then, proceed as follows:

Step Action1 Enter the Gateway IP Address in the Default Gateway IP Address

text box.



23

Configuring the Inband Management, Continued

Procedure (continued)

Step Action2 In the Inband Management Parameters group box:

Enter the inband IP address in the IP Address text box. Enter the inband netmask in the NetMask text box.

NOTE The Mac Address text box displays the MAC address ofthe OmniBAS-8W NE physical interface through whichthe inband connection with uni|MS is made.

3 From the VLAN ID drop-down list select the VLAN to be used for theinband management.

4 Select the priority to be applied to the management VLAN from thePriority drop-down list.You can select a value from 0 (lowest priority) to 7 (highest priority).It is recommended to select the highest priority (7). (1)

5 From the Inner VLAN ID drop-down list, select Not Used unless youwant to enable the Q-in-Q VLAN termination feature.In this case select the VLAN ID you want to assign (values range: 1to 4094). Q-in-Q VLAN termination feature is used when: The operator network is working with double-tagged packets

(802.1ad) and thus management IP is a double-taggedtermination.

The access to the OmniBAS-8W NE is on a transparent VLANport. (2)

6 Click the settings.

End of procedure

(1) Its operators responsibility to define the appropriate priority for the various traffic types. In case ofIEEE 1588v2 synchronization method, the packets carrying the timestamps are usually assigned thehighest priority.(2) In this second case, the transparent VLAN port always adds a VLAN tag to inbound packetsaccording to its default VLAN id. Inbound packets cannot be terminated to the management host, unlessan inner VLAN id is enabled. Inner VLAN id is set to the desired inband management VLAN and VLAN idis set with the same VLAN as the default VLAN of the transparent port. Thus, packets with themanagement VLAN coming from the network are inserted into the transparent port, get the default VLANas the outer VLAN and terminate correctly as double-tagged at the management host. Outbound double-tagged packets become single-tagged on egress of the transparent port with the management VLAN id.


24

Setting the Real Time Clock (RTC)

Introduction This paragraph describes: How to manually set the Real Time Clock (RTC) of an OmniBAS-8W NE. How to synchronize the clocks between the PC in which the uni|MS Node

Manager application is running and the Control Card of the OmniBAS-8W NE.

Procedure To set the Real Time Clock (RTC) of an OmniBAS-8W NE, open theManagement view of the OmniBAS-8W NE and select the Inband/Outband/RTC tab. Then, proceed as follows:

Step Action1 Click in the Real Time Clock field. The Date Picker window appears

to enter the RTC settings.

2 To get the your PC time in case of uni|MS Node Manager, select theGet current date/time check box. Then, proceed to step 4.

3 To manually set the RTC of the OmniBAS-8W NE, you can enter theRTC settings either directly in the Real Time Clock field(1) or viaDate Picker window, as follows: Set the year (e.g. 2012), by using the buttons or the

corresponding drop-down list. Set the month, by using the corresponding drop-down list. Set the day, by using the calendar area. Set the current time, by clicking on the corresponding text boxes

and using the left-right arrows.4 Close the Date Picker window. The new RTC is displayed in the Real

Time Clock field.5 Click the setting.

End of procedure.

(1) In this case, be careful to keep the uni|MS RTC formatting.


25

Configuring Trap Destinations

Introduction This paragraph describes how to manually add (or remove) PC/ Laptopports(1) to which the OmniBAS-8W NE will send its traps.OmniBAS-8W NE supports the addition of up to nine ports as trap destinations(8089 to 8098). For uni|MS Node Manager, 8089 is the default port. If this portis reserved, the next available port up to port 8098 will automatically be addedas trap destination port. Be careful that if a 10th trap destination entry is added,the first of the nine already existing entries will be overridden.

NOTE Particularly, there is no need to manually add trap destinations.Trap destinations is automatically added (or removed) in the TrapDestinations view after NE connection (or disconnection) withuni|MS or after NE synchronization. This automatic procedureenables / disables fault management without requiring any userinteraction.

NOTE After NE connection with uni|MS or after NE synchronization, anyerroneously removed trap destinations will be re-added.

NOTE When uni|MS has failed to add a trap destination, the Add TrapDestination event is generated indicating Result = Fail.

Opening TrapDestinationsview

In the Management view of the OmniBAS-8W NE, select the TrapDestinations tab.

Adding a trapdestination port

To add PC/ Laptop ports to which the OmniBAS-8W NE will send its traps,open the Trap Destinations view and proceed as follows:

Step Action1 Right-click on the list

and select Add(2).


(1) PC/ Laptop ports concern the management of OmniBAS-8W NE through uni|MS Node Manager.(2) If you select an existing entry and then you right-click, the drop-down menu will also include theRemove option.


26

Configuring Trap Destinations, Continued

Adding a trap destination port (continued)

Step Action2 A new row is created at the end of the list.

Double click on the Trap Destination IP Address box, type the IPaddress of PC/ Laptop and press ENTER.

3 Double click on the TrapDestination Port box, typethe new UDP port of thePC/ Laptop and pressENTER.

4 Click .

5 The new trap destination isadded in the TrapDestinations view.

End of procedure.

Removing trapdestinationports

To remove PC/ Laptop ports to which the OmniBAS-8W will send its traps,open the Trap Destinations view and proceed as follows:

Step Action1 Select the trap destination entries, right-click and select Remove.2 Click . The selected trap destinations should be removed from

the Trap Destinations view.

End of procedure.


27

Configuring Trap Profiles

Introduction uni|MS provides you the ability to disable certain types of SNMP traps frombeing sent to a specific trap destination port. This is achieved through thecreation of a trap profile and its registration to a specific trap destination port.This paragraph describes you how to configure a trap profile and register itto a specific trap destination port(1).

Opening TrapProfiles view

In the Management view of the OmniBAS-8W NE, select the Trap Profilestab.

Configuring atrap profile

To configure a trap profile, open the Trap Profiles view and proceed asfollows:

Step Action1 Right-click and

select Add(2).


(1) Experimental feature in current S/W version.(2) If you select an existing entry and then you right-click, the drop-down menu will also include theRemove option.


28

Configuring Trap Profiles, Continued

Configuring a trap profile (continued)

Step Action2 In the Add Trap Profile window, double-click on the Disable box of

the trap you want to disable and select Yes. Repeat for as manytraps you want.

NOTE In each trap row, the Oid is the trap identification number inthe SNMP MIB and is different from the Event ID and theAlarm ID appearing in the reports. Furthermore, each Oidcorresponds to more than one Alarm IDs.

3 In the Profile Name text box, type the profile name.To register the profile, select the Register check box.Then, click OK.



29

Configuring Trap Profiles, Continued

Configuring a trap profile (continued)

Step Action4 The trap profile is added in the Trap Profiles view.

Also, in uni|MS Node Manager, the registered trap profile isautomatically assigned to your PC/Laptop port (i.e. the trap profile isautomatically added in Trap Destination view).

From now and then, the selected traps will not be sent to the uni|MSNode Manager PC.

End of procedure.


30

Adding/ Removing Static Routes

Introduction This paragraph describes how to add (or remove) a static route to anOmniBAS-8W NE. In this case, the OmniBAS-8W NE can be accessed fromoutside of the Management Stations Subnet via the specified router.

NOTE You can add up to 128 different static route entries on anOmniBAS-8W NE.

OpeningStatic Routesview

In the Management view of the OmniBAS-8W NE, select the Static Routestab.

Adding astatic route

To add a static route to an OmniBAS-8W NE, open the Static Routes view andproceed as follows:

Step Action1 Right-click on the list and select Add(1).


(1) If you select an existing entry and then you right-click, the drop-down menu will also include theRemove option.


31

Adding/ Removing Static Routes, Continued

Adding a static route (continued)

Step Action2 A new row is created at the end of the list.

Consult the following table to enter the static route values you want.To enter a value (e.g. RouteID), double-click on the corresponding box,type the value and press ENTER.

Attribute DescriptionRoute ID This value is an index that is assigned to each route entry. Value

Range: 1 to 32768IP Address IP address of the static route.Mask Subnet Mask address assigned to the static route.Gateway IP address of Gateway assigned to the static route.

3 Click . The new trap static route entry should be added in the StaticRoutes view.

End of procedure.

Removingstaticroutes

To remove static routes from an OmniBAS-8W NE, open the Static Routes viewand proceed as follows:

Step Action1 Select the static route entries, right-click and select Remove.2 Click . The selected static route entries should be removed from

the Static Routes view.

End of procedure.


32

Modifying Communication Credentials

Introduction This paragraph describes how to change or restore the CLI communicationcredentials of OmniBAS-8W NEs.

NOTE OmniBAS-8W NE support CLI communication credentials only.

Be very careful when modifying the default communicationcredentials as they are case-sensitive for all NEs. A NE is impossibleto be managed by uniMS Node Manager when communicationcredentials do not match with those used by the NE.

NOTE Regarding uni|MS Node Manager, the new communicationcredentials will be applied as long as the uni|MS Node Managersession is open. Upon re-login the new communicationcredentials should be re-entered.

Opening ModifyCommunicationCredentialswindow

To open the Modify Communication Credentials window of an OmniBAS-8WNE, proceed as follows:Right-click on the OmniBAS-8W NE and select Administration > Security >Modify Communication Credentials.The Modify Communication Credentials window appears through which youcan change or restore the CLI communication credentials of the selected NE.



33

Modifying Communication Credentials, Continued

Restoring thedefaultcommunicationcredentials

To restore the default CLI communication credentials of the selectedOmniBAS-8W NE, proceed as follows:

Step Action1 In the Modify Communication Credentials window, select the Set to

Default check box.2 Click OK to apply.

End of procedure.

Changingcommunicationcredentials

To change the CLI communication credentials of the selected OmniBAS-8WNE, proceed as follows:

Step Action1 In the Modify Communication Credentials window, enter the new CLI

communication credentials:

Attribute Description DefaultValue

CLI User To enter the username required for CLI access tothe NE from uni|MS Node Manager.

admin

CLIPassword

To enter the password required for CLI access tothe OmniBAS-8W NE from uni|MS Node Manager.

admin

Confirm To re-enter the corresponding password forconfirmation.

admin

CLIProtocol

To select the CLI protocol to be used, telnet or SSH. ssh

2 Select the Apply to Element check box.

If you change the communication credentials withoutselecting the Apply to Element check box, communicationloss with OmniBAS-8W NE will be caused.

3 When you complete, click OK to apply the communication credentialschange.

End of procedure.


34

3.2 OmniBAS-8W NE (Basic)

This section includes the following topics to provide the procedures requiredfor configuring the basic parameters of an OmniBAS-8W NE: Configuring Synchronization Source Configuring GbE (electrical) / GbE (SFP) Ports Configuring Modem Parameters Configuring Radio Parameters Configuring Hot Standby (HSB) Protection Enabling / Disabling APS Operation of SDH Interface Card Configuring 16/32 E1 Interface Card Setting OmniBAS-8W NE Thresholds Activating/ Deactivating External Devices & Monitoring External Alarms Recording Site Information


35

Configuring Synchronization Source

Introduction This paragraph describes how to configure (and monitor) the OmniBAS-8Wsynchronization source. The available operation modes includes: Manual, when user selects the clock source to which the system will be

synchronized. Freerun, when system is synchronized to the internal clock. Auto QL Disabled, when system is self-synchronized to an available clock

source based on user-defined priorities. Auto QL Enabled, when system is self-synchronized to an available clock

source based on its Quality Level (QL), as specified in the ITU-T G.781standard. (1)

The paragraph also describes how to enable or disable the Sync-Out port.

OmniBAS-8Wavailable clocksources

The available clock sources of OmniBAS-8W synchronization include: External synchronization port (Synch In) GbE interfaces (GbEthernet 1 to GbEthernet 6) Modem ports (Modem 1 to Modem 8) E1 interfaces(2) (E1 1.1 to E1 1.16 (or E1 1.32) and

E1 2.1 to E1 2.16 (or E1 2.32)) STM1 interfaces (STM1 1.1 to STM1 1.2 (or STM1 1.4) and

STM1 2.1 to STM1 2.2 (or STM1 2.4))

Prerequisites Before proceeding to any change on the synchronization source of theOmniBAS-8W NE, take into consideration the following prerequisites: Configuration of the OmniBAS-8W NE synchronization source must be

made in accordance with the relevant Network planning. It is recommended to configure the synchronization source, the first time

you setup the OmniBAS-8W NE (prior to starting NEs configuration). Be very careful when you make changes on the synchronization of an NE

because disruption in normal operation of the system may be caused.For this reason, select a convenient time for making the changes.


(1) If multiple clock sources have the same highest QL, the clock source with the highest priority isselected. For the case that multiple clock sources have the same highest Priority and QL, the currentexisting selected clock source is maintained (if it belongs to this group), otherwise an arbitrary clock sourcefrom this group is selected. Clock sources that are not capable of receiving SSM (as Sync-In, E1 andSTM-1 ports) are assigned to a Default QL by the user.(2) E1 and STM-1 ports with loopback is excluded from the synchronization candidates list in Auto QL mode.


36

Configuring Synchronization Source, Continued

OpeningSynchronizationview

Right-click on the OmniBAS-8W NE and select Configuration. Alternatively (in case of uni|MS Node Manager or Node Managerperspective), select the OmniBAS-8W NE and in the NM Tabbed Pane clickthe Configuration tab.In the Configuration view of the OmniBAS-8W NE, select the Synchronizationtab and then: Clock Configuration tab to configure and monitor the OmniBAS-8W NE

synchronization source.

Clock Sources tab to configure and monitor the clock sources of theOmniBAS-8W NE, in case of Auto QL mode.

Setting Freerunoperation mode

To configure the OmniBAS-8W NE for Freerun operation mode, proceed asfollows:

Step Action1 In the Clock Configuration tab, select Freerun from the Operation

Mode drop-down list.2 Click to apply the operation mode setting.3 Ensure that OmniBAS-8W NE is locked to the internal clock:

DPLL Status = Freerun Active Clock Source = N/A

End of procedure.



37


Setting Manualoperation mode

To configure the OmniBAS-8W NE for Manual operation mode, proceed asfollows:

Step Action1 In the Clock Configuration tab, select Manual from the Operation

Mode drop-down list.2 From the Configured Clock Source drop-down list, select one of

the available synchronization sources.3 Click to apply the operation mode settings.4 Ensure that OmniBAS-8W NE is locked to the selected clock:

DPLL Status = Locked Active Clock Source = selected synchronization source (e.g.

Modem 1)

End of procedure.

Setting Auto QLDisabledoperation mode

To configure the OmniBAS-8W NE for Auto QL Disabled operation mode,proceed as follows:

Step Action1 For each one of the OmniBAS-8W synchronization sources listed in

the Clock Sources tab: Click the corresponding row. Editable attributes turn into orange

color. Double-click the Priority box and enter the priority value you want

to assign to the specific clock source (1 = highest priority,255 = lowest priority and 0 = port excluded from selection).

Double-click the Holdoff Timeout box and type the duration (inmsec) after which source is considered unavailable (FAILED)during the systems automated synchronization process. (1)

If you want to temporarily exclude this specific source, double-clickthe Lockout Flag box and select Set.By selecting Clear makes this specific source available again.

2 Click to apply the settings in the Clock Sources tab.3 In the Clock Configuration tab, select Auto QL Disabled from the

Operation Mode drop-down list.


(1) Ranges for Holdoff Timeout are as follows: 6000 (default value) to 10000, for GbE interfaces. 300 (default value) to 1800, for all other interfaces.


38


Setting Auto QL Disabled operation mode (continued)

Step Action4 Click to apply the operation mode settings.5 Ensure that OmniBAS-8W NE is locked to a specific

synchronization source: DPLL Status = Locked Active Clock Source = one of the sources configured in step 1

End of procedure.

Setting Auto QLEnabledoperation mode

To configure the OmniBAS-8W NE for Auto QL Enabled operation mode,proceed as follows:

Step Action1 For each one of the OmniBAS-8W synchronization sources listed in

the Clock Sources tab: Click the corresponding row. Editable attributes turn into orange

color. Double-click the Priority box and enter the priority value you want

to assign to the specific clock source (1 = highest priority,255 = lowest priority and 0 = port excluded from selection).

Double-click the Holdoff Timeout box and type the duration (inmsec) after which source is considered unavailable (FAILED)during the systems automated synchronization process. (1)

If you want to temporarily exclude this specific source,double-click the Lockout Flag box and select Set.By selecting Clear makes this specific source available again.

2 Click to apply the settings in the Clock Sources tab.3 In the Clock Configuration tab, select Auto QL Enabled from the

Operation Mode drop-down list.


(1) Ranges for Holdoff Timeout are as follows: 6000 (default value) to 10000, for GbE interfaces. 300 (default value) to 1800, for all other interfaces.


39


Setting Auto QL Enabled operation mode (continued)

Step Action4 Execute this step only if external sync is connected. (1)

From the Default QL for Sync In drop-down list, select the defaultQuality Level (QL) to be assigned to the external synchronization input(Sync-In).

Def. QualityLevel (QL)

Description Order

PRC Source transports a timing quality generated by aPrimary Reference Clock (PRC) (as defined in ITU-T.G.811)

Highest

SSU-A Source transports a timing quality generated byTypes I or V slave clock (as defined in ITU-T.G.812).

SSU-B Source transports a timing quality generated by aType VI slave clock (as defined in ITU-T. G.812).

SEC Source transports a timing quality generated by aSynchronous Equipment Clock (SEC) (as defined inITU-T. G.813 or ITU-T G.8262, option I).

Lowest

5 Execute this step only if timing signals retrieved from E1 lines are tobe used. (1)

From the Default QL for E1 drop-down list, select the default QualityLevel (QL) to be assigned to E1 clock sources.Select one of the following values: PRC, SSU-A, SSU-B or SEC.

6 Execute this step only if timing signals retrieved from STM-1 (VC-12)ports are to be used. (1)

From the Default QL for STM1 drop-down list, select the defaultQuality Level (QL) to be assigned to STM-1 clock sources.Select one of the following values: PRC, SSU-A, SSU-B or SEC.

7 In the Wait to restore Timer text box, enter the timeout value (inminutes) for the wait-to-restore timer. This time ensures that aprevious failed clock source is considered as available by theselection auto QL process if it is fault free for that time.Available value range: 0 to 12 minDefault value: 5 min

8 Click to apply the operation mode settings.


(1) This, because Sync-In, E1 and STM-1 clock sources cannot provide messages for determiningquality. Thus, a fixed QL has to be assigned to these sources manually.


40


Setting Auto QL Enabled operation mode (continued)

Step Action9 Ensure that OmniBAS-8W NE is locked to a specific synchronization

source: DPLL Status = Locked Active Clock Source = any appropriate source

10 In the Clock Sources tab, you can check the Quality Level (QL) foreach one of the candidate sources.

End of procedure.

Enabling /disablingSync-Out

To enable / disable the Sync-Out port, proceed as follows.

Step Action1 Select the Clock Configuration tab and from the Sync-Out

drop-down list, select Enabled to enable the port or Disabled todisable it.

2 Click to apply the change.

End of procedure.



41


Monitoring syncinfo (Clock Con-figuration tab)

The following table describes the information displayed in the ClockConfiguration tab for monitoring the current synchronization status of theOmniBAS-8W NE.

Attribute PossibleValues

Description Applicable for(Operation

Mode):

LockedState Icon(1):

(Green)

OmniBAS-8W NE succeeds to find theselected clock source (shown in theActive Clock Source attribute) and lockto it.

Manual /Auto QL

HoldoverState Icon(1):

(Orange)

OmniBAS-8W NE loses the clock towhich it is locked and fails to find anyother clock provided by OmniBAS-8WNE. Being in Holdover state tries tosimulate the previous clock source bymaking use of an internal memory.

Manual /Auto QL

FreerunState Icon(1):

(Grey)

The internal clock of OmniBAS-8W NEis used for the synchronization.

Freerun

DPLLStatus

UnlockedState Icon(1):

(Grey)

OmniBAS-8W NE cannot synchronizeas the PLL synthesizer of the ControlCard is unlocked.

Manual /Auto QL

See page Current synchronization clock source inwhich OmniBAS-8W NE is locked.

Manual /Auto QL

ActiveClockSource N/A Not Available (N/A) when OmniBAS-8W

NE is Freerun synchronized.Freerun


(1) On the photorealistic equipment view, the current operation status of the OmniBAS-8W NEsynchronization is displayed on the Sync port of Control Card through the corresponding state indicator.The exact position is shown below:


42


Monitoringsync info(ClockSources tab)

The following table describes the information displayed in the ClockSources tab for monitoring the current synchronization status of theOmniBAS-8W NE operating in Auto QL (Disabled or Enabled) mode.

Attribute Description

Source Clock source provided by OmniBAS-8W NE for synchronization.QualityLevel

Indicates the clock source Quality Level (QL) and it is applicable forAuto QL Enabled operation mode only.

Possible values:

Quality Level(QL)

Description Order

PRC Source transports a timing quality generatedby a PrimaryReference Clock (PRC) (as defined in ITU-T.G.811)

Highest

SSU-A Source transports a timing quality generatedby Types I or V slave clock (as defined inITU-T.G.812).

SSU-B Source transports a timing quality generatedby a Type VI slave clock (as defined inITU-T. G.812).

SEC Source transports a timing quality generatedby a Synchronous Equipment Clock (SEC)(as defined in ITU-T. G.813 or ITU-T G.8262,option I).

DNU Source should not be used forsynchronization (DNU - Do Not Use).

INV / FAILED /NSUPP

These QLs (as defined in ITU-T G.781) areinternal QLs inside the NE and are nevergenerated at an output port. INV: The received SSM code is invalid. FAILED: The input signal has failed. NSUPP (Not SUPPorted): SSM processing

is not supported (concerns only Auto QLDisabled mode).

Lowest



43


Monitoring sync info (Clock Sources tab) (continued)

Attribute Description

Priority To specify priority value for the specific clock source.Priorities are used to define the preferred clock source within NetworkElement (NE) when an Auto QL operation mode is selected.Different priorities among clock sources reflect a preference of onesynchronization source over the other.Equal priorities reflect that no preference exists between thesynchronization sources.Possible values: 1 (highest) to 255 (lowest). 0 (indicating that this clock source is not used as a synchronization

source).Default value: 0

LockoutFlag

To temporarily remove (Set) the clock source as availablesynchronization source in the selection auto QL process.To recover the synchronization availability of the clock source, theClear option should be selected.Default value: Clear

QuarantineFlag

Indicates whether the clock source is available in the selection autoQL process (Clear) or not (Set). The Set value is caused byerroneous clock signals.

HoldoffTimeout

The hold-off timer ensures that short time failures on the specificclock source do not impact to the selection auto QL process.Possible values: For a GbE clock source:

0 (a zero value will cause immediate timeout) 6000 to 10000 msec

For Modem, Sync-In and E1s clock sources: 0 (a zero value will cause immediate timeout) 300 to 1800 msec

Default value: 6000 msec (for GbE clock sources) and 300 msec (forModem, Sync-In, E1 and STM-1 clock sources).

Status Operational status of the specific clock source when OmniBAS-8WNE operating in an Auto QL mode. The Active value indicates that theclock source is currently used for OmniBAS-8W NE synchronization.Otherwise, the value Not Active is displayed.


44

Configuring GbE (electrical) / GbE (SFP) Ports

Introduction This paragraph describes:

How to: GbE(electrical)

GbE(SFP)

Enable the auto negotiation mode of a GbE port. Set the Forced mode of a GbE port (auto-negotiationmode disabling). In this case, the Speed and DuplexMode parameters of the port should be specified.

Enable or disable a GbE port. Enable or disable the Link Loss Forwarding (LLF)mechanism of a GbE port.

NOTE GbE (SFP) ports support operation in Auto Negotiate mode only.

OpeningConfigurationview of GbEport

Right-click on the GbE port, and select Configuration. Alternatively (in case of uni|MS Node Manager or Node Managerperspective), select the GbE port and in the NM Tabbed Pane click theConfiguration tab.The following example screen shows the Configuration view of an electricalGbE port:

Configuration view of electrical GbE port Configuration view of GbE (SFP) port



45

Configuring GbE (electrical) / GbE (SFP) Ports, Continued

Setting auto-negotiationmode

When the auto-negotiation mode of an electrical GbE port is enabled, the portwill negotiate the highest mutually possible line speed and duplex modewith the other connected device port. Note that the other connected deviceport should have the same configuration.To enable the auto-negotiation mode of an electrical GbE port, proceed asfollows:

Step Action1 From the Negotiation Mode drop-down list, select Auto Negotiate.2 Click to apply the change.

Note that:When the Link Status of the GbE port is: Up, the Speed and Duplex Mode fields display the current speed

and duplex mode status of the port. Down, the N/A indication is displayed in the Speed and Duplex

Mode fields.

End of procedure.

Setting Forcedmode

When the forced mode of an electrical GbE port is enabled, the port is forcedto operate at the specified Speed and Duplex Mode, regardless of whetherthe link partner is capable of working at that speed. This setting allows the portto support equipment that cannot support auto negotiation.To set the electrical GbE port to operate in forced mode, proceed as follows:

Step Action1 From the Negotiation Mode drop-down list, select, Forced.2 From the Speed drop-down list, specify the speed of the port to be

used: 100 Mbps or 10 Mbps.3 From the Duplex Mode drop-down list, specify the duplex mode of

the port to be used: Full Duplex to allow data to be transmitted and received in both

directions at the same time. Half Duplex to allow data to be transmitted and received in both

directions, but only in one direction at a time (not simultaneously).4 Click to apply the changes.

End of procedure.



46


Enabling ordisabling aGbE port

To enable/ disable a GbE port, proceed as follows:

5

Be very careful when you disable a GbE port. If you disable theGbE port used for the inband connection, the management withthe OmniBAS-8W NE will be lost and a visit to the site may berequired.

Step Action1 From the Admin State drop-down list, select:

Up to enable the port. Down to disable the port.

2 Click to apply the change on the GbE port.

End of procedure.

Enabling/Disabling LLF

When enabling the LLF mechanism of a GbE port, the port will be deactivatedautomatically, as soon as a link down condition occurs: either on all specified Modems (AND condition) of the OmniBAS-8W NE or on any of the specified Modems (OR condition) of the OmniBAS-8W NE.This is useful for routers or switches, which will become capable to quicklydetect the failed Ethernet connection and consequently activate the existingprotection mechanisms (such as RSTP).To enable or disable the LLF mechanism of a GbE port, proceed as follows:

Step Action1 To enable the LLF mechanism of the GbE port:

Select Enabled from the LLF Operation drop-down list (of the LinkLoss Forwarding group box).

Select the Modem Slot group boxes corresponding to the Modemsto be used in the LLF mechanism (e.g. Modem Slot 1 and ModemSlot 2).Also, From the Modem Usage Logic drop-down list, select:- OR: In case you want the link down condition to be determined

by any of the selected Modems. For example, the GbE port willbe automatically deactivated when a link down condition occurson one of the selected Modems.

- AND: In case you want the link down condition to be determinedby all of the selected Modems. For example, the GbE port will beautomatically deactivated when a link down condition occurssimultaneously on all selected Modems.



47


Enabling/ Disabling LLF (continued)

Step Action2 To disable the LLF mechanism of the GbE port, select Disabled from the

LLF Operation drop-down list.3 When you complete, click to apply the settings.

End of procedure.


48

Configuring Modem Parameters

Introduction This paragraph describes: How to configure the basic parameters of a Modem (Bandwidth, Profile,

Adaptive Mode and Min / Max Auto PHY Mode). Hot to enable / disable the traps generation by PHY Mode changes.

Prerequisites The configuration settings must be the same for all modems localand remote that participate in the same link.

Be very careful when you change the configuration of a Modem because,link downtime may be caused. For this reason, select a convenient timefor making the modem changes and also start with the configurationchange of the most remote modem. Otherwise, management loss withthe remote modems will take place and a visit to the remote sites may berequired.

Modem configuration must be made in accordance with the relevant RFplanning.

OpeningConfigurationview of Modem

To open the Configuration view of a Modem, proceed as follows:Right-click on the Modem and select Configuration. Alternatively (in case of uni|MS Node Manager or Node Managerperspective), select the Modem and in the NM Tabbed Pane click theConfiguration tab.

NOTE XPIC Mode field is displayed only in the Configuration view of aModem card of XPIC type (PTP_XPIC Modem card).



49

Configuring Modem Parameters, Continued

ConfiguringModem

To configure an OmniBAS-8W Modem, open the Configuration view of theModem and proceed as follows:

Step Action1 Execute this step only for a Modem of XPIC type (PTP XPIC).

For XPIC link operation, select Enabled from the XPIC Modedrop-down list.

For non-XPIC link operation, select Disabled from the XPIC Modedrop-down list.

Click to apply setting.

NOTE When you enable the XPIC functionality of a Modem, theModem Protection Mode of both relevant modem pairs willbe automatically set to Standalone (in NEs Configuration >Modem > Hot Standby view).

2 From the Bandwidth drop-down list, select the channel bandwidth ofthe Modem (in MHz): 7, 14, 20, 28, 40 or 56.

3 From the Profile drop-down list, select link performance target duringlink operation: Optimum Sys Gain, to enable optimum robustness for the link. Normal, to enable normal gain and capacity performance for the link. Optimum Capacity, to enable higher capacity performance (and

hence, lower gain) for the link.

NOTE Normal profile is not available when XPIC Mode is Enabled.

NOTE For 20 MHz bandwidth, only the Optimum Capacity profile isavailable. Also, for 40 MHz bandwidth, only the Optimum SysGain and Optimum Capacity profiles are available.

4 From Adaptive Mode drop-down list, select the mode of operationregarding the physical modulation and transmit (Tx) power adjustment: Manual: Both the physical mode and Tx power are set manually. Auto-Manual Power: Physical mode is changed automatically while

Tx power is set manually. Auto-Optimum: Physical mode is changed automatically while Tx

power is changed optimally per modulation. Auto-Max Power: Physical mode is changed automatically while Tx

power is the maximum possible per modulation.



50


Configuring Modem (continued)

Step Action5 If you selected Adaptive Mode = Manual, then select also the physical

mode of the link from the PHY Mode drop-down list.

6 If you select Adaptive Mode = Auto-Manual Power, Auto-Optimum orAuto-Max Power, then: From the Max Auto PHY Mode drop-down list, select the modulation

profile that provides the upper modulation limit you want to assign tothe modem.

From the Min Auto PHY Mode drop-down list, select the modulationprofile that provides the lower modulation limit you want to assign tothe modem.

7 Click to apply the settings.8 For Adaptive Mode = Manual or Auto-Manual Power, you should also

set the transmission (Tx) power of the ODU (in the Tx Power (dBm) textbox in the corresponding Configuration view of ODU.

End of procedure.



51


Enabling/disabling PHYMode ChangeTraps

In case you want to enable (or disable) the Modulation Change eventcreation each time a physical modulation change occurs, proceed asfollows:

Step Action1 From the Enable Tx PHY Mode Change Traps drop-down list,

select Enable Tx Trap to enable traps generation for the local toremote path (i.e. in the transmit direction of the Modem).Otherwise, select Disable Tx Trap.

2 From the Enable Rx PHY Mode Change Traps drop-down list,select Enable Rx Trap to enable traps generation for the remote tolocal path (i.e. in the receive direction of the Modem).Otherwise, select Disable Rx Trap.

3 Click to apply the settings.

End of procedure.


52

Configuring Radio Parameters

Introduction This paragraph describes how to configure the following parameters of anODU: Tx frequency, Tx Power, DC power, Muting and Update mode.

Prerequisites The configuration settings must be the same for all radios local andremote that participate in the same link.

Be very careful when you change the radio parameters of an ODU,because link downtime may be caused. Also, start with the configurationchange of the most remote OmniBAS-8W NE; otherwise, managementloss with the remote NEs will take place and a visit to remote sites maybe required.

The configuration on the radio parameters of an OmniBAS-8W NE must bemade in accordance with the relevant RF planning.

Opening ODUConfigurationview

Right-click on the ODU and select Configuration. Alternatively (in case of uni|MS Node Manager or Node Managerperspective), select the ODU and in the NM Tabbed Pane click theConfiguration tab.

Procedure To configure an ODU, open the Configuration view of the ODU and proceedas follows:

Step Action1 To change the transmission power, enter the new value (in dBm) in

the Tx Power (dBm) text box.Note that you can see the upper and lower limits of the transmissionpower (related to the modulation that is currently used by theModem) in the Status view of the ODU (Max/ Min Tx Power fields ofthe Capabilities group box).



53

Configuring Radio Parameters, Continued


Step Action2 To change the transmission frequency, click the button in the Set

Tx Frequency (KHz) field.The Suggested Frequency Valueswindow appears listing the available Txfrequency values (1). The currenttransmission frequency is displayedred-colored.Click the new Tx frequency value youwant and click OK.

The Suggested Frequency Values window closes and the new Txfrequency value is displayed in the Set Tx Frequency (KHz) field.

3 From the Mute drop-down list, select: Off to unmute the ODU; the ODU will be capable of transmitting. On (default value) to mute the ODU; the ODU will stop transmitting.

4 From the DC Power drop-down list, select: On, to enable the power up of the ODU. Off (default value), to enable the power down of the ODU

5 From the Update Mode drop-down list, select: Auto, to enable the automatic software upgrading of the ODU.

When uni|MS detects that an ODU software upgrading is required(e.g. after an ODU replacement), the Needs Update message willappear in the ODUs Status view (Software Update field). The ODUupgrading process will take place, upon next ODUs power up.

Manual (default value), to enable the manual software upgrading ofthe ODU (i.e. the software upgrade of the ODU will be performed bythe user at a convenient time).

6 Click to apply the changes on the ODU.

NOTE To perform a DC Power off test, see par. Performing DCPower Off Test on ODU, on page 174.

End of procedure.

(1) The available Tx frequencies are determined by the bandwidth selected on the corresponding Modemand also result from the First / Last Frequency and Frequency Step values displayed in the Status viewof the ODU (Capabilities group box).


54

Configuring Hot Standby (HSB) Protection

Introduction This paragraph describes how to configure the modems operational mode ofan OmniBAS-8W NE. The modem pairs can be configured either as HotStandby (HSB) (Protected) or Standalone (Unprotected).The schematic below shows the OmniBAS-8W modem pairs supportingprotection functionality:

OpeningModem - HotStandby view

To open the Modem - Hot Standby view of the OmniBAS-8W NE, proceed asfollows:Right-click on the OmniBAS-8W NE and select Configuration. Alternatively (in case of uni|MS Node Manager or Node Managerperspective), select the OmniBAS-8W NE and in the NM Tabbed Pane clickthe Configuration tab.In the Configuration view select the Modem > Hot Standby tab.



55

Configuring Hot Standby (HSB) Protection, Continued

Prerequisites(for XPICconfigurations)

Prior to performing XPIC configurations on OmniBAS-8W NE, take intoconsideration the following:

XPIC Configurations ImplementationXPIC 2+0 (unprotected) Two Modem Cards / ODUs are required per site to

implement one complete XPIC link 2+0.XPIC 4+0 (unprotected)XPIC 8+0 (unprotected)

Four (or eight) Modem Cards / ODUs are required persite to implement two (or four) complete XPIC links(East-East or East-West).

XPIC 2+2 (protected)XPIC 4+4 (protected)

Four (or eight) Modem Cards / ODUs are required persite to implement one (or two) complete XPIC link 2+2.

Procedure To configure the modems operation mode of an OmniBAS-8W NE, proceedas follows:

Step Action1 In the Modem Protection group box, execute the following actions

for each modem pair (Pair 1-3, Pair 2-4, Pair 5-7 and Pair 6-8) youwant to configure:

Attribute From the drop-down list:ModemProtection Mode

Select the operational mode of the modems pair,Protected or Standalone: When selecting Protected mode, the one modem

enters working mode and the other enters standbymode(1).

When selecting Standalone mode, the modem(s)works in standalone (i.e. unprotected) mode.

In case you select Standalone, proceed to step 2.PreferredWorking Modem

Select the modem you want to enter working mode.

Revert toPreferredModem

Select Yes, in case you want the protection mechanismto revert to the preferred working modem when itrecovers from a failure. Otherwise, select No.


(1) In photorealistic view, the state icon appears on the Modem Card when the card is in workingmode and the state icon appears when it is in stand-by mode.


56

Configuring Hot Standby (HSB) Protection, Continued


Step Action2 Execute this step only if you want to enable RAI feature(2) for the

modem pairs configured in Protected mode.In the Remote Alarm Indication (RAI) Configuration group box,select the RAI Enabled check box.To change the default RAI timer value (60 sec), type the new one inRAI Timer text box.

3 Click .

End of procedure.

(2) About RAI mechanism: Normally, in a protected 1+1 HSB link, each working ODU (ODULOCAL and ODUREMOTE) transmits to

both ODUs at the other side of the link. The standby local (L) and remote (R) ODUs just receiveand do not transmit.

In case one of the ODUs (e.g. working ODULOCAL) stops transmitting, the two ODUs at the otherside of the link stop listening and the working ODUREMOTE) dispatches a RAI alarm. Switchover tostandby local modem is about to occur after the RAI timeout.

If the link is re-established within the predefined RAI timer value, the RAI alarm ceases. Otherwise,the local (working) modem issues a RAI Blocked alarm to notify the management that a switchoverto the standby modem could not be executed.


57

Enabling / Disabling APS Operation of SDH Interface Card

Introduction This paragraph describes: How to enable the APS (Automatic Protection Switching) operation of the

SDH Interface Card (Linear MSP, 1+1 unidirectional, non-revertive). How to disable the APS operation of the SDH Interface Card.APS feature provides automatic protection switching on STM-1 ports. APS(also referred to as SDH multiplex section protection (MSP)) refers tomechanism of providing fault tolerance through fiber cable redundancy inSDH networks.A supplementary STM-1 port (called Protecting) is dedicated to protect theprimary STM-1 port (referred to as Working). In case of problems detectedon the Working STM-1 port, the traffic is redirected to the Protecting STM-1port and vice versa.Manual switch commands are available to provide a manual intervention inthe APS switching process.

APS operation Next table describes the position of the selector and the contents of thetransmitted K1 byte when the Local Switch Actions (internal states andmanual switch commands (rows in grey)) are changing.A higher priority Local Switch Action preempts the lower priority one(i.e. lower priority command is denied when a higher priority command / stateis active).The table below lists the Local Switch Actions from highest to lowest orderpriority.

Priority Local Switch Action Preconditions Tx K1(1) Switchingto:

1 Lockout ofProtection (2)

None 1111 - 0000 Workingport

2 Forced SwitchProtect to Working

No Local SwitchAction with higherswitching priority.

1110 - 0000 Workingport


(1) Bytes K1 and K2 in the MS Overhead of the STM-1 signal carry a Multiplex Section Protection (MSP)protocol used to coordinate protection switching between the Near End and the Far End.In 1 + 1 unidirectional switching, the signal selection is based on the local conditions and requests.Therefore each end operates independently of the other end, and bytes K1 and K2 are not needed tocoordinate switch action. However, byte K1 is still used to inform the other end of the local action, and bit5 of byte K2 is set to zero.(2) Switching from Working to Protecting STM-1 port is denied. If the Protecting STM-1 port is currentlyactive, this command switches the traffic to the Working STM-1 port.


58

Enabling / Disabling APS Operation of SDH Interface Card,Continued

APS operation (continued)

Priority Local Switch Action Precondition Tx K1 Switchingto:

3 Forced SwitchWorking to Protect

No equal or higherswitching priorityexists.

No SF onProtecting port.

1110 - 0001 Protectingport

4 Signal Fail (SF) onProtection



5 Signal Fail (SF) onWorking



6 Manual SwitchProtect to Working



7 Manual SwitchWorking to Protect



8 Do not revert No equal or higherswitching priorityexists.

Traffic was onProtecting port butnow Working portis repaired.


9 No Request No equal or higherswitching priorityexists.

No failures whileWorking port is inuse.


The Clear external switch command (not shown in the above table) can beused to clear the Lockout of Protection, Forced Switch or Manual Switchexternal switch commands.



59


Available SDHCard types /operatingmodes

The available SDH Interface Card types are shown in the table below:

SDH Card Type Available Operating ModesInterface Card 1+1xSTM1-VC12 1+0 / 1+1 (protected operation)Interface Card 4xSTM1-VC12 1+0 / 2+0 / 3+0 / 4+0 (unprotected operation)

2+2 (protected operation)

The following schematic shows the protected and unprotected operationmodes supported for each SDH Interface Card.To configure an SDH Interface Card in protected mode, the APS (AutomaticProtection State) functionality should be enabled (and the correspondingAPS Groups will be created). By default, STM-1 Working Ports are theactive ones (used for traffic). In case of failure in a Working STM-1 Port, theprotection is activated and all the traffic is sent through the Protecting port(that now becomes the active).



60


OpeningConfigurationview of SDHInterfaceCard

Right-click on the SDH Interface Card and select Configuration. Alternatively (in case of uni|MS Node Manager or Node Managerperspective), select the SDH Interface Card and in the NM Tabbed Pane clickthe Configuration tab.The following example screen shows the configuration view of an SDH(4xSTM-1) Interface Card(1) for:

UnprotectedMode (APS isdisabled)

ProtectedMode (APS isenabled)


(1) Note that in case of SDH (1+1xSTM-1) Interface Card only APS Group 1 group box is displayed.


61


Enabling APS To enable APS on an SDH Interface Card, proceed as follows:

SDH Interface Card should be reset after the operation modechange. During cards rebooting, traffic loss will occur.

Step Action1 In the APS Protection group box, select the Protection Mode check

box.2 Click .3 The following message appears to inform you that SDH Interface

Card will be restarted. To proceed, click Yes.

4 Wait for the card to reboot and stabilize. After that, APS should havebeen activated.

5 In case you want the APS Switchover event to appear in Real TimeAlarms & Events list each time a port switchover occurs select theProtection Switchover Notification Events check box and click

.6 In APS Group box(es) you can monitor:

The STM-1 port(s) that is currently active (Active Channel field(s)). The Rx/Tx K1-K2 bytes (received / transmitted APS signaling bytes

providing information about the local switch state).

End of procedure.



62


PerformingManual SwitchCommand

To perform a manual (external) switch command on an SDH Interface Cardoperating in protected mode (APS enabled), proceed as follows:

Step Action1 From Switch Command drop-down list of APS Group 1, select one

of the following commands to be applied to STM-1 Port 1 and STM-1Port-2. Lockout of Protection - Switching from working to protecting STM-1

port is denied. If the protecting STM-1 port is currently active, thiscommand switches the traffic to the working STM-1 port.

Forced Switch Protect to Working Forced Switch Working to Protect Manual Switch Protect to Working Manual Switch Working to Protect No Command Clear

NOTE You cannot select a command of a lower switching priority ifa higher switching priority exists. In case you try a messageas the following appears:

2 Execute this step only in case of SDH (4xSTM-1) Interface Card.From Switch Command drop-down list of APS Group 2, select theswitch command to be applied to STM-1 Port 3 and STM-1 Port-4.

4 Click .5 In each APS Group box you can monitor:

Attribute To monitorRx K1-K2 bytes Received APS signaling bytes providing information

about the local switch state.Tx K1-K2 bytes Transmitted APS signaling bytes providing

information about the local switch state.Local Switch Action Local Switch Action that is currently active.Active Channel The STM-1 port that is currently active.

End of procedure.



63


Disabling APS To change the operating mode of an SDH Interface Card from Protected toUnprotected (i.e. to disable APS), proceed as follows:

SDH Interface Card should be reset after the operation modechange. During cards rebooting, traffic loss will occur.

Step Action1 In APS Group box, deselect the Protection Mode check box and

click .2 In the following confirmation that message appears click Yes to

proceed.

3 Wait for the card to reboot and stabilize. After that, APS shouldhave been activated.

End of procedure.


64

Configuring 16/32 E1 Interface Card

Introduction This paragraph describes how to enable or disable(1) the E1 lines of a 16E1(or 32E1) Interface Card: Through the Configuration view of a specific E1 line. Through the Configuration view of the 16/32 E1 Interface Card

(individually or massively).

OpeningConfigurationview of 16/32 E1Interface Card

Right-click on the Interface Card and select Configuration. Alternatively (in case of uni|MS Node Manager or Node Managerperspective), select the Interface Card and in the NM Tabbed Pane click theConfiguration tab.

OpeningConfigurationview of an E1line

Right-click on the E1 line and select Configuration. Alternatively (in case of uni|MS Node Manager or Node Managerperspective), select the E1 line and in the NM Tabbed Pane click theConfiguration tab.


(1) When the E1 port is disabled, an E1 Line Admin Down alarm will be generated by the port. The alarmwill be ceased, when the E1 port is enabled again.


65

Configuring 16/32 E1 Interface Card, Continued

Enabling ordisabling E1lines

To enable or disable an E1 line, proceed as follows:

A. Through Configuration view of E1 line

Step Action1 Open the Configuration view of the E1 line.2 From the Admin State drop-down list, select Up to enable the line or

Down to disable it.3 Click to apply the setting.

End of procedure.

B. Through Configuration view of 16/32 Interface Card (Individually)

Step Action1 Open the Configuration view of the 16/32 Interface Card.2 For each E1 line you want to configure:

Click the corresponding row. Editable attributes turn into orangecolor.

Double-click the Admin State box and select Up to enable the lineor Down to disable it.

3 When you complete, click to apply the settings.

End of procedure.

C. Through Configuration view of 16/32 Interface Card (Massively)

Step Action1 Open the Configuration view of the 16/32 Interface Card.2 Hold down the Shift key to make consecutive selections or the Ctrl

key for non-consecutive selections. Right-click and selectConfiguration. (Note that in case of photorealistic view, the multipleselection of the E1 lines are made only by using the Shift key).The Massive Configuration window for the selected E1 lines appears.



66

Configuring 16/32 E1 Interface Card, Continued

Enabling or disabling E1 lines (continued)

Step Action3 From the Admin State drop-down list, select Up to enable the

selected lines or Down to disable them.

NOTE You cannot make any change on the selected E1 lines,when timeslots of at least one E1 line are associated withservices/ service fragments. In case you try, an errormessage appears.

4 When you complete, click to apply the settings.

End of procedure.


67

Setting OmniBAS-8W NE Thresholds

Introduction This paragraph describes how to change the thresholds on an OmniBAS-8W NE: Low / High Temperature of OmniBAS-8W equipment (NE group box). SNR and LDPC Deco

unims r4.2 technology driver omnibas8w r5.1 rm ed2.1 en

Documents