cc/td/doc/product/ong/15305/cecdocs
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

General Management

4.1  Management Modes and Configuration

4.1.1  Management Port Configuration

4.1.2  DCC Configuration

4.1.3  IP Default Gateway Configuration

4.2  ONS 15305 Scenarios

4.2.1  Notations Used

4.2.2  Scenario 1: Cisco Edge Craft and ONS 15305 on the Same Subnet

4.2.3  Scenario 2: Cisco Edge Craft and ONS 15305 on Different Subnets

4.2.4  Scenario 3: IP over DCC

4.2.5  Scenario 4: IP over PPP

4.3  Manage Common Parameters

4.3.1  View Common Parameters

4.3.2  Identify the Network Element

4.3.3  Time Settings

4.3.4  Users

4.3.5  Available Features (Licenses)

4.3.6  Physical Inventory - ONS 15305

4.3.7  Physical Inventory - ONS 15302

4.3.8  Restart the ONS 15305

4.3.9  Restart the ONS 15302

4.3.10  Logs (Alarm Logs, Performance Data Logs)

4.4  Synchronization Management

4.4.1  SDH Synchronization

4.4.2  ONS 15305

4.4.3  View the Synchronization Data (T0 or T4)

4.4.4  Add Synchronization Source Candidate (T0 or T4)

4.4.5  Modify Synchronization Source Candidate (T0 or T4)

4.4.6  Delete Synchronization Source Candidate (T0 or T4)

4.4.7  Operate Synchronization Switch (T0 or T4)

4.4.8  View Synchronization Switch (T0 or T4)

4.4.9  Activate Synchronization on the ONS 15302

4.5  Download Software to a Network Element

4.5.1  Network Release

4.5.2  Operational and Administrative Software Bank

4.5.3  Effect of Software Upgrades on Traffic

4.5.4  Download an ONS 15305 Network Release

4.5.5  Download Software to the ONS 15305

4.5.6  Download Software to the ONS 15302

4.6  Back Up and Restore Configuration Data

4.6.1  Back Up Configuration Data

4.6.2  Restore Configuration Data

4.7  Alarm and Event Configuration

4.7.1  Event Forwarding

4.7.2  Configure General Alarm Reporting

4.7.3  Suppress Specific Alarms

4.7.4  Modify Alarm Severity and Description

4.7.5  Set Signal Degrade Threshold

4.7.6  Modify Alarm Persistency

4.7.7  Modify ONS 15302 Alarm Configuration Attributes

4.8  Manage ONS 15305 Slots

4.8.1  View a Slot

4.8.2  Modify a Slot


General Management


This chapter describes the configuration operations supported by the Management Interface managed object (MO).

The attributes under the management interfaces MO are not unique in the information model. Each attribute mirrors a similar attribute located under another MO. The attributes under the management interfaces MO have been put together to allow the user to set up basic configuration of the management interfaces without having to browse through many MOs in the topology browser. For advanced configuration operations, additional MOs must still be used.

4.1  Management Modes and Configuration

The management traffic is IP based (SNMP and TFTP messages); therefore when configuring a management path IP datagrams must carry the management traffic over the network. For the management interfaces, two main encapsulation types are available:

IP directly carried over a layer 2 protocol (Ethernet, PPP, or proprietary).

IP encapsulated within CLNP carried over a layer 2 protocol (IEEE 802.x or LAP-D).

In addition, each management interface can be turned off. Actual encapsulation support varies depending on the management interface type (management port or DCC). Table 4-1 provides an overview of the different management modes versus the management interfaces.


Note This is an important feature for security purposes, especially for the management port, which is physically accessible on the network element (main card).


Table 4-1 Management Modes Versus Management Interface

Management Interface
Not Used
IP
IP/Ethernet
IP/proprietary encapsulation
IP/PPP

Management Port

X

X

   

DCC

X

 

X

X



Note The management port is able to run both IP over Ethernet and CLNP over IEEE 802.x at the same time. On the contrary, a DCC can run only one mode at a time. In addition, a maximum of eight DCCs can be used for management purposes, meaning only eight DCCs can have their management mode set to IP.


The following sections describe how to configure the management port and the DCCs by using the management interfaces MO present in the topology browser.

4.1.1  Management Port Configuration

The management port can run two types of encapsulation or mode. A particular mode is selected by setting the variable mode (management interfaces >management port > mode). Required configuration for possible modes is Not Used or IP.

4.1.1.1  Mode: Not Used

To configure the management port mode to Not Used complete the following steps.


Step 1 Click the ONS 15305 managed object, then click the management Interfaces managed object in the topology browser ( Figure 4-1).

Figure 4-1 Management Interfaces - Managed Object

.

Step 2 Click managementPort in the attributes window ( Figure 4-2).

Figure 4-2 ManagementPort - Attributes

Step 3 In the attributes window, the set mode to Not Used ( Figure 4-3).

Figure 4-3 ManagementPort - Mode Selector

.

Step 4 Click Save on the toolbar.


4.1.1.2  Mode: IP

To configure the management port with the mode set to IP, complete the following steps:


Step 1 Click the ONS 15305 managed object, then click the management Interfaces managed object in the topology browser.

Step 2 Click managementPort in the attributes window.

Step 3 In the attributes window, set mode to IP.

Step 4 Click Save on the toolbar.

Step 5 Click ipAddress in the attributes window ( Figure 4-4).

Figure 4-4 ManagementPort - IP Address Attribute

.

Step 6 Click Add on the toolbar. Set protocol to IP, and set ipAddress and subnetMask according to your IP addressing scheme or plan ( Figure 4-5).

Figure 4-5 ManagementPort - Add IP Address

.

Step 7 Click Save on the toolbar.

Depending on your topology, additional routing information might need to be configured. You can define static routes or control dynamic protocols (RIP, OSPF) by using the IP managed object in the topology browser. Defining a default gateway can be done directly from the management interface's managed object as explained in section "IP Default Gateway Configuration" section.


4.1.2  DCC Configuration

A DCC can run three types of encapsulation or mode. A particular mode is selected by setting the variable mode (management interfaces > DCC > mode). The required configuration for one of the two possible modes (Not Used or IP) is further detailed in the next sections.

4.1.2.1  Mode: Not Used

To configure a DCC with the mode set to Not Used, complete the following steps.


Step 1 Click the ONS 15305 managed object and then click the management Interfaces managed object in the topology browser.

Step 2 Click dcc in the attributes window.In the attributes window, each row represents a DCC interface.

Step 3 Set mode to Not Used.

Step 4 Click Save on the toolbar.


4.1.2.2  Mode: IP

To configure a DCC with the mode set to IP, complete the following steps.


Step 1 Click the ONS 15305 managed object and then click the management Interfaces managed object in the topology browser ( Figure 4-6).

Step 2 Click dcc in the attributes window.

Step 3 In the attributes window, each row represents a DCC interface. Set mode to IP over DCC for the desired DCC interface.

Figure 4-6 Management Interfaces - Dcc Attribute

.

Step 4 In addition, when the mode is set to IP, the layer 2 encapsulation for the IP datagrams must be configured. This done by setting the ipEncapsulation variable to the desired encapsulation (proprietary or PPP) ( Figure 4-7).

Figure 4-7 IPEcapsulation - Encapsulation Selector

.

Step 5 Click Save on the toolbar.

Step 6 Click ipAddress in the attributes window.

Step 7 Click Add on the toolbar. Set protocol to IP, and set ipAddress and subnetMask according to your IP addressing scheme or plan.

Step 8 Click Save on the toolbar.

If the mode is set to IP and ipEncapsulation is set to PPP, additional configuration for PPP can be performed via the pppConfiguration variable (management interfaces > DCC > pppConfiguration).

Depending on your topology, additional routing information might need to be configured. You can define static routes or control dynamic protocols (RIP, OSPF) by using the IP managed object in the topology browser. Defining a default gateway can be done directly from the management interfaces managed object as explained in "IP Default Gateway Configuration" section.


4.1.3  IP Default Gateway Configuration

To configure an IP default gateway on the network element complet ethe following steps.


Step 1 Click the ONS 15305 managed object, then click the management Interfaces managed object in the topology browser.

Step 2 Click ipDefaultGateway in the attributes window.

Step 3 Set the defaultGatewayIpAddress and defaultGatewayInterface according to your IP addressing plan.

Step 4 Click Save on the toolbar.


Note The default gateway must be directly reachable from the network element, meaning the default gateway must belong to a subnet defined on the interface identified by defaultGatewayInterface.
Modifying the default gateway results in removing the previous default gateway from the network element's routing table and adding the new (modified) gateway to the routing table.



Note Secure routing before removing the default gateway.



4.2  ONS 15305 Scenarios

This section presents four typical network topologies and describes how the management interfaces can be configured through the management interface's managed object to carry management traffic.

In the following scenarios, it is assumed that both RIP and OSPF are disabled. Although each IP network is unique, the topologies and configurations presented in this chapter can be considered basic building blocks that can be combined together to apply to a specific network.

In a real network, with a larger number of network elements, additional managed objects can be required to perform the configurations. In particular, configuration of IP and activation and configuration of dynamic routing protocols (RIP, OSPF, IS-IS) require the use of additional managed objects.

IP over DCC (with proprietary or PPP encapsulation) requires configuring a subnet per link (per DCC). Any network element configured with IP over DCC and located more than two DCC links away from Cisco Edge Craft must either have a static route to Cisco Edge Craft or must run a dynamic routing protocol. As the number of static routes increases with the number of interfaces configured to run IP over DCC, running a dynamic routing protocol can be advantageous. Depending on the network topology, care must be taken when enabling IP routing protocol over DCC to prevent the DCC network from being advertised as a path for the user traffic (as opposed to the management traffic only).

Each of the scenarios presents a figure from a typical IP topology with the parameters required in the management interface's managed object.

4.2.1  Notations Used

The following notations are used throughout the rest of this section:

The /<prefix-length> notation is used to denote the {IP address, subnet mask} pairs. As an example, the notation 192.168.0.1 / 24 refers to the following pair: {IP address 192. 168.0.1, subnet mask 255.255.255.0}.


Note The prefix-length is equal to the total number of contiguous 1-bits in the traditional subnet mask.


N/A (non-applicable) is used to denote that an attribute is not relevant for a particular configuration, meaning the value of the attribute will not influence the configuration.

The notation interface (XXX) defines the interface of the default gateway ( Figure 4-9 to Figure 4-11). Possible values for XXX are "MGMT Port" to the ifIndex of the management port and "DCC #n" to the ifIndex of the DCC channel. The values of the ifIndex can be found under the managed objects and DCCs.

4.2.2  Scenario 1: Cisco Edge Craft and ONS 15305 on the Same Subnet

Figure 4-8 Cisco Edge Craft and ONS 15305 on the Same Subnet

Table 4-2 Cisco Edge Craft and ONS 15305 on the Same Subnet - Settings 

 
ONS 15305 1
ONS 15305 2
ONS 15305 3

Mangement Port

     

mode

IP

IP

IP

iPAddess

IP, 10.10.10.10 / 24

IP, 10.10.10.20 / 24

IP, 10.10.10.30 / 24

DCC#1

     

mode

notUsed

notUsed

notUsed

ipEncapsulation

N/A

N/A

N/A

lapdRole

N/A

N/A

N/A

pppConfiguration

     

initialMRU

N/A

N/A

N/A

pppIpAdminStatus

N/A

N/A

N/A

compression

N/A

N/A

N/A

ipAddress

N/A

N/A

N/A

DCC#2

     

mode

not used

not used

not used

ipEncapsulation

N/A

N/A

N/A

lapdRole

N/A

N/A

N/A

pppConfiguration

     

initialMRU

N/A

N/A

N/A

pppIpAdminStatus

N/A

N/A

N/A

compression

N/A

N/A

N/A

ipAddress

N/A

N/A

N/A

IP Defaulty Gateway

     

ipAddress

N/A

N/A

N/A

interface

N/A

N/A

N/A


4.2.3  Scenario 2: Cisco Edge Craft and ONS 15305 on Different Subnets

Figure 4-9 Cisco Edge Craft and ONS 15305 on Different Subnets

Table 4-3 Cisco Edge Craft and ONS 15305 on Different Subnet - Settings 

 
ONS 15305 1
ONS 15305 2
ONS 15305 3

Mangement Port

     

mode

IP

IP

IP

iPAddess

IP, 10.10.10.10 / 24

IP, 10.10.10.20 / 24

IP, 10.10.10.30 / 24

DCC#1

     

mode

notUsed

notUsed

notUsed

ipEncapsulation

N/A

N/A

N/A

lapdRole

N/A

N/A

N/A

pppConfiguration

     

initialMRU

N/A

N/A

N/A

pppIpAdminStatus

N/A

N/A

N/A

compression

N/A

N/A

N/A

ipAddress

N/A

N/A

N/A

DCC#2

     

mode

not used

not used

not used

ipEncapsulation

N/A

N/A

N/A

lapdRole

N/A

N/A

N/A

pppConfiguration

     

initialMRU

N/A

N/A

N/A

pppIpAdminStatus

N/A

N/A

N/A

compression

N/A

N/A

N/A

ipAddress

N/A

N/A

N/A

IP Defaulty Gateway

     

ipAddress

10.10.10.1

10.10.10.1

10.10.10.1

interface

mgmt port

mgmt port

mgmt port


4.2.4  Scenario 3: IP over DCC

Figure 4-10 IP over DCC

Table 4-4 IP Over DCC - Settings 

 
ONS 15305 1
ONS 15305 2
ONS 15305 3

Mangement Port

     

mode

IP

IP

IP

iPAddess

N/A

IP, 10.10.10.10 / 24

N/A

DCC#1

     

mode

notUsed

notUsed

notUsed

ipEncapsulation

proprietary

proprietary

proprietary

lapdRole

N/A

N/A

N/A

pppConfiguration

     

initialMRU

N/A

N/A

N/A

pppIpAdminStatus

N/A

N/A

N/A

compression

N/A

N/A

N/A

ipAddress

IP, 192.168.10.1 / 24

IP, 192.168.20.1 / 24

IP, 192.168.30.1 / 24

DCC#2

     

mode

not used

not used

not used

ipEncapsulation

proprietary

proprietary

proprietary

lapdRole

N/A

N/A

N/A

pppConfiguration

     

initialMRU

N/A

N/A

N/A

pppIpAdminStatus

N/A

N/A

N/A

compression

N/A

N/A

N/A

ipAddress

IP, 192.168.30.2 / 24

IP, 192.168.10.2 / 24

IP, 192.168.20.2 / 24

IP Defaulty Gateway

     

ipAddress

192.168.10.2

N/A

192.168.20.1

interface

DCC #1

N/A

DCC #2


4.2.5  Scenario 4: IP over PPP

Figure 4-11 IP over PPP

Table 4-5 IP Over PPP- Settings 

 
ONS 15305 1
ONS 15305 2
ONS 15305 3

Mangement Port

   

mode

notUsed

IP

iPAddess

N/A

IP, 10.10.10.10 / 24

DCC#1

     

mode

IP

notUsed

ipEncapsulation

PPP

PPP

lapdRole

N/A

N/A

pppConfiguration

     

initialMRU

1500

1500

pppIpAdminStatus

open

open

compression

none

none

ipAddress

IP, 192.168.10.1

IP, 192.168.20.1

IP, 192.168.30.1 / 24

DCC#2

     

mode

IP

IP

ipEncapsulation

PPP

PPP

lapdRole

N/A

N/A

pppConfiguration

   

initialMRU

1500

1500

pppIpAdminStatus

open

open

compression

none

none

ipAddress

IP, 192.168.30.2

IP, 192.168.10.2

IP, 192.168.20.2 / 24

IP Defaulty Gateway

     

ipAddress

192.168.10.2

N/A

192.168.20.1

interface

DCC #1

N/A

DCC #2


Thethird-party equipment supports:

Standard IP over PPP over DCC according IF-DN-0101-R1

IP forwarding between its DCC interface

4.3  Manage Common Parameters

The purpose of this section is guide you through management of the attributes that are related to the network element sub-rack and the common hardware and software.

The section includes viewing and modifying NE parameters, time settings, users, available features, and the physical inventory, restart issues, LEDs and alarm output, and ping mechanism.

Synchronization, download of software, upload and download of configuration data, and management of NE's are described in separate sections.

4.3.1  View Common Parameters

Select device in the topology browser.

The common attributes (parameters) as defined in the information model are:

Identification of the network element

Time settings

Users

Available features (licenses)

Physical inventory

Network element restart

Logs (alarm logs, performance data logs)

LEDs and alarm output

Ping mechanism

4.3.2  Identify the Network Element


Step 1 Select the network element in the topology browser ( Figure 4-12).

Step 2 Modify the following attributes as needed:

Location

NativeName

Owner

Figure 4-12 Identification of Network Element

Step 3 Click Save to commit changes.


4.3.3  Time Settings

The following steps explain how to change time settings for an ONS 15305.


Step 1 Select ONS 15305 and then select the device managed object ( Figure 4-13).

Figure 4-13 Time Settings - Time Attribute

Step 2 Click Time ( Figure 4-14).

Figure 4-14 Time Attribute - Values

Step 3 Click SystemTime>Time to view or modify ( Figure 4-15).

Figure 4-15 Time Attributes - System Time

.

Step 4 Click TimeProtocol to view or modify the following objects:

TimeServerIpAddress

TimeSyncInterval

TimeZone


4.3.4  Users

This section explains how to add a new user ( Figure 4-16) and change the VT 100 password.

Figure 4-16 Add a New User - Overview

4.3.4.1  Add a New User


Step 1 Navigate as shown in Figure 4-16.

Step 2 Click Add.

Step 3 Enter the password or IpAddress .

Step 4 Select the AccessRight from the drop-down menu.

Step 5 Select the TrapsEnable state from pulldown menu.

Step 6 Click Save.


4.3.4.2  VT 100 Password (ONS 15302 only)


Step 1 In the topology browser select device > time > VT100.

Step 2 Edit the Vt100Password.

Step 3 Click Save.


4.3.5  Available Features (Licenses)

In the topology browser select device > Features > FeatureTable to view available licences ( Figure 4-17).

Figure 4-17 Available Features

4.3.6  Physical Inventory - ONS 15305


Step 1 In the topology browser select device > DevicePhysicalInventory ( Figure 4-18).

Figure 4-18 Physical Inventory - Overview

Step 2 Select Hardware to list a hardware inventory.

Step 3 Select Software to list a software inventory.


4.3.7  Physical Inventory - ONS 15302

In the topology browser select device > inventory.

4.3.8  Restart the ONS 15305


Step 1 In the topology browser select device > Restart ( Figure 4-19).

Figure 4-19 Restart of Network Element - Overview

Step 2 If selecting delayedRestart, set time and date.

Step 3 Select the RestartStatus.

Step 4 Click Save.


4.3.9  Restart the ONS 15302


Step 1 In the topology browser select device > Restart.

Step 2 Select Restart.

Step 3 Click Save.


4.3.10  Logs (Alarm Logs, Performance Data Logs)

4.3.10.1  Clear Alarm History


Step 1 In the topology browser select device > LogAdministration.

Step 2 Set ClearAlarmHistory to clear.

Step 3 Click Save.

Step 4 Refresh the Alarm History in the Alarm List.


4.3.10.2  Clear PM Data


Step 1 In the topology browser select device > LogAdministration

Step 2 Set ClearPMData to clear ( Figure 4-20).

Step 3 Click Save.

Figure 4-20 Clear Alarm- and Performance Data Log


4.3.10.3  LEDs and Alarm Output


Step 1 In the topology browser select device > LEDandOutput

Step 2 Select severity to light the NE LEDs ( Figure 4-21).

Figure 4-21 LEDs - Severity Selector


4.3.10.4  Ping Mechanism


Step 1 In the topology browser select device > Ping hyper link ( Figure 4-22).

Step 2 Edit any of the following attributes as needed:

Delay

PacketCount

TrapOnCompletion (true/false)

PacketSize

PacketTimeout

Figure 4-22 Ping Mechanism

4.3.10.5  Alarm Ports


Step 1 In the topology browser select device > alarmPort ( Figure 4-23).

Step 2 Edit the followig attributes as needed:

Description

Free text description.

Mode

enabled or disabled

TriggeredWhen

opens or closes (when an alarm is to be triggered)

Figure 4-23 Alarm Ports

.

Step 3 Click Save.


4.3.10.6  AUX Port - ONS 15305


Step 1 In the topology browser select device > auxPort ( Figure 4-24).

Figure 4-24 AUX Port

Step 2 Edit the following attributes as needed:

AdminStatus enabled or disabled

AuxPortTimeSlot ( Figure 4-25).

Figure 4-25 AUX port - Timeslots

Step 3 Edit the following attributes as needed for AuxPortTimeSlot:

OhByte: e1, e2, f1 or unmapped

Slot:

Description:

Port:

4.3.10.7  Power Module - ONS 15305


Step 1 In the topology browser select device > power ( Figure 4-26).

Figure 4-26 Power Module - Attributes

Step 2 Edit the following attributes as needed:

AlarmReporting

disabled or enabled

AlarmReportingInputA

disabled or enabled

AlarmReportingInputB

disabled or enabled

Description

free text description


4.4  Synchronization Management

The purpose of this section is to select the synchronization source for internal SDH timing (T0) and external synchronization output (T4).

The ONS 15305 T0 and T4 automatic selection processes can select the source from a short list of available inputs. This selection is based on quality and priority.

You can override the automatic selection process by manual commands.

The first part of this section gives a short introduction to SDH synchronization which is meant to help the reader in understanding the requirements specified in this document.The synchronization is G.781 compliant.


Note For further reading on SDH synchronization, see ETSI ETS 300 417-6-1, ITU-T Recommendation G.781, G.812 ("Timing requirements of slave clocks suitable for use as node clocks in synchronization networks") and G.813 ("Timing characteristics of SDH equipment slave clocks (SEC)")


4.4.1  SDH Synchronization

4.4.1.1  Synchronization Networks

A synchronization network is a set of clock nodes that are maintained in synchronization with one another. Synchronization networks require accurate transfer of synchronization reference information between nodes so that their relative synchronization can be monitored and maintained.

Since it is difficult to synchronize all international nodes from the same master clock, each network operator typically has a primary reference clock (PRC) as defined in ITU-T Recommendation G.811.

From the PRC the synchronization reference information is distributed to all nodes in the SDH network in a tree-type network topology ( Figure 4-27).

Figure 4-27 Synchronization Network Example

Intermediate slave clocks can enter holdover conditions if their connection to the master clock is lost. Slave clocks called Synchronization Supply Units (SSUs) will continue to serve their branch of the network until the connection with the PRC is reestablished. There may be several SSUs concatenated in a large network.

Intermediate SDH NEs will also contain slave clocks, the SDH equipment Clock (SEC). Their quality is not sufficient for providing synchronization reference information to other parts of the network, but they can serve the SDH NE itself in holdover mode if all high-quality incoming references are lost.

As shown in Figure 4-27, the SDH NEs have a dual role since they need a synchronization reference to operate properly in a network and they are important for distribution of synchronization reference information to other networks.

4.4.1.2  Selecting the Best Synchronization Reference

To reinforce the reliability of the synchronization network, alternative routes are often used between the clocks. The slave clock can then be switched to another synchronization reference manually, or automatically by monitoring the signal at the physical interface.

An improvement to simple signal monitoring is to send the synchronization status message (SSM) along with the synchronization signal to indicate the quality level (clock type) of the source clock. The next clock in the chain can now select the best clock based on this quality level.

Not all connections used for synchronization can send the SSM along with its synchronization reference. In this case it is possible to manually indicate the quality level for this interface in ONS 15305. This ensures that also references without SSM can be part of the automatic selection process that is based on quality level.

To avoid timing loops in the network it may be necessary to indicate in SSM that a synchronization reference should not be used. To do so, send the do not use (DNU) message.

4.4.1.3  Synchronizing the SDH Equipment

All SDH equipment contains a clock for the SDH pointer adjustments, cross-connection matrix operations, and the outgoing line signal (STM-N). It is normally operating as a slave clock and locked to a high quality incoming reference, but can run in holdover mode if the reference is lost.

This section describes how the internal timing (T0) is derived from the available synchronization references in ONS 15305.

Synchronization reference information can be extracted from any of the incoming STM-N SDH interfaces (T1), 2 Mbps PDH interfaces (T2), or the external 2 MHz synchronization input (T3) as indicated in Figure 4-28.

The figure shows that only one the available synchronization references will be used as a reference for the SEC. SEC is the clock used for internal timing (T0). When no reference is available it will run in Hold-over mode.

Figure 4-28 T0 Selection

4.4.2  ONS 15305

4.4.2.1  Signal Monitoring

All interfaces are monitored for signal level and framing errors. The failure will be reported to the candidate selection and QL-monitoring and switching processes.

4.4.2.2  Candidate Selection and Configuration

In the ONS 15305 up to five synchronization reference candidates can be selected to participate in the selection process.

For each synchronization source candidate the following parameters can be read or configured:

Type (T1, T2, or T3 where T2 must be a 2 Mbps PDH Port in PRA mode).

Identification of the synchronization source candidate (via its slot number, port number, etc.)

Whether SSM usage is enabled (T1 only).

Assigned quality level (QL). If SSM usage is disabled, the operator is free to assign a fixed QL.

Current quality level. If SSM usage is enabled (T1) the quality level of the incoming signal is seen here. If an alarm is detected on the synchronization source interface, the current quality level indicates failure (Independent on SSM usage).

The priority of the synchronization source candidate. This priority will apply only when there are multiple candidates all having the highest QL among all possible source candidates.

Hold-Off time and wait-to-restore time.

For each synchronization source candidate the following methods are available:

Set or Clear lockout. This is used to temporarily exclude a specified synchronization source.

Clear WTR.

4.4.2.3  QL-Monitoring and Switching

The QL-monitoring and selection process will continuously monitor the QL of the candidate synchronization references and select the reference with the best QL. Only error free references are included in the selection process. (Alarms are detected in the signal monitoring functional block). If there is more than one candidate with the highest available QL, the priority parameter will be used for selection.

The following parameters can be read or configured for the selection process:

Selected synchronization reference and its QL.

Switch mode. This indicates whether the selection process is running in the automatic, forced, or manual switch mode.

Manual switch command. A manual switch can be performed only to a source with the highest available QL. This means that manual switching can only be used to override the synchronization source priorities.

Forced switch command. This command overrides the currently selected synchronization source.

Clear command. Clears any of the manual or forced switch commands.

4.4.2.4  SEC

The ONS 15305 slave clock.

SEC will enter holdover mode for the specified Hold-Off time if an alarm is detected on the selected synchronization reference. After the Hold-Off time the selection process will switch to the error free reference with the highest QL.

When a candidate synchronization reference recovers from an alarm condition, the signal is free for faults for the wait-to-restore period before taken into consideration by the selection process.

The selected T0 reference is also used on all output STM-N signals.

4.4.2.5  Synchronizing External Equipment

ONS 15305 also provides an external synchronization output (T4). This is a separate 2 MHz signal that can be used directly as a synchronization reference for other equipment or as a synchronization reference to separate stand alone synchronization equipment (SASE).

Synchronization reference information can be extracted from any of the incoming STM-N SDH interfaces (T1) or the internal timing (T0) as indicated in Figure 4-29.

The figure shows that only one of the available synchronization references will be used for external timing (T4).

Figure 4-29 T4 Selection

4.4.2.6  Rules

When referring to a T1 or T2 synchronization reference, slot and port numbering is used.

When referring to the T0 or T3 synchronization reference, no further identification is required.

SSM is always disabled for T2 and T3 references

A 2 Mbps PDH port should be treated as a T2 source only when it is operating in PRA mode.

In principle a user can add the same source twice, but you should be advised not to do this.

More than one reference can have the same priority.

A warning message appears before an active synchronization source is deleted. No further restrictions apply.

The automatic selection process will find the best source based on the current QL. If more than one source has the highest QL, the source with the highest QL and priority will be selected. If the priority is also the same,the ONS 15305 will choose the first source in the list with the highest QL and priority.

A manual switch can be performed only to a source with the highest available QL.

A forced switch overrides the currently selected synchronization source.

The new source selected by the manual and forced switching cannot have a current quality level of failure or SEC.

WTR clear does not exist as a method in the MIB. The WTR must be set to 0 and then back to its original value if the method is implemented in the manager.

T0 is the default candidate for T4.

If no candidates are available for the T4 selection process, no synchronization source is selected and the external synchronization output is squelched.

When QL of the selected T4 reference falls below the QLM level, the T4 output signal is squelched (muted) to allow the slaved oscillator to go into holdover or to select another reference.

T4 is only used for external synchronization output (not for output STM-N signals).

4.4.2.7  Synchronization Alarms

Synchronization alarms are treated the same as other ONS 15305 alarms.

Figure 4-29 identifies the alarms related to SDH synchronization events.

Table 4-6 Alarms Related to SDH Synchronization Events 

Alarm ID
Description
Comment
Clearable
Default Severity

T0_HOLDOVER

SETG enters holdover

No sync. sources available (applies to T0 sync. only)

Yes

MAJOR

T0_SWITCH

Change of sync. source

Applies to automatic, manual or forced switchover (T0 only).

No

INFO

SYNCSRC_QL

QL_FAILED or QL_DNU for any sync. candidate

Applies to T1/T2/T3 sources member of the T0 sync. table

No

INFO

T4_SQUELCH

T4 output squelched (on permanent basis)

No T4 sync. candidate with QL equal to or above QLmin

Yes

MAJOR

T0_DEFECT

SETG failure

Caused by defective hardware impacting the internal T0 clock

Yes

CRITICAL



Note A synchronization candidate is a synchronization source contained in either of the T0 or T4 synchronization source tables (5 entries each).


4.4.3  View the Synchronization Data (T0 or T4)

T0 and T4 Synchronization are combined in the flow descriptions because of their common behavior. Users are assumed to be experienced SDH users because synchronization management is not directly related to the services offered by ONS 15305.

Access the synchronization attributes from the topology browser ( Figure 4-30).

Figure 4-30 Synchronization - Selecting Managed Object

.

The system presents a list of all Synchronization Source candidates ( Figure 4-31).

Figure 4-31 Synchronization - T0 SynchSources attribute

l.

If the source experiences a signal error the SSM attribute shows failure instead of the SSM value.

The system presents the synchronization attributes with the relevant data.

4.4.4  Add Synchronization Source Candidate (T0 or T4)


Step 1 Select T0 SynchSources or T4 SynchSources ( Figure 4-31).

Step 2 Click Add in the toolbar ( Figure 4-32).

Figure 4-32 Add Synchronization Source

Step 3 Enter the synchronization parameters in the topology browser for the new candidate. The list of existing synchronization source candidates must be less than five.

Type: STM-n, e1, external

Slot/ Port: number

SSM: enabled/disabled

Admin Quality/Assigned Quality Level (N/A when SSM is enabled): sec, ssuL, ssuT, prc

Priority: 1..5 (where 1 is highest priority)

Lockout:clear/set

Hold-Off Time: 300..1800 ms

Wait To Restore Time: 0..12 min

Step 4 Click Save.

If you attempts to add a new synchronization source candidate when the candidate list is fully populated (five entries), you will be informed that a candidate must be deleted before adding a new candidate.

The system verifies that the candidate is legal before performing the addition. If any errors are found, the candidate is not added and you are given the opportunity to correct the problem.

You can add more than one candidate before committing, and a failure on one candidate has no consequence for the addition of the other candidates.


4.4.5  Modify Synchronization Source Candidate (T0 or T4)


Step 1 Access the synchronization attributes from the topology browser ( Figure 4-31).

Step 2 Modify the synchronization source candidate attributes as needed. SSM Enabled can be True only for T1.

QL can only be modified if SSM enabled is False.

Step 3 Click Save to commit the changes.


4.4.6  Delete Synchronization Source Candidate (T0 or T4)

There are two methods for deleting a synchronization source candidate:


Step 1 Access the synchronization attributes from the topology browser.

Step 2 Select the synchronization source candidate(s) to delete and click Delete in the toolbar menu.

Step 3 Click Save.



Step 1 Select the Port (synchronization source) in the topology browser

Step 2 Select Do not use for T0 Synchronization from the drop-down menu.

Step 3 Select Delete. If synchronization source candidate is the active synchronization source, a warning message appears.

Step 4 Click Save.


4.4.7  Operate Synchronization Switch (T0 or T4)


Step 1 Select T0 or T4SwitchCommand and set to desired value, Figure 4-33.

Figure 4-33 Operate Synchronization Switch 1

Step 2 Click T0 or T4SwitchSource and select new synchronization source ( Figure 4-34).

Figure 4-34 Operate Synchronization Switch 2

.

Step 3 Click Save.

If the switch parameters are valid, the switch is performed. If a manual or forced switch is performed, the selected source will remain selected until a new forced, manual, or clear command is sent.


4.4.8  View Synchronization Switch (T0 or T4)


Step 1 Access the synchronization attributes from the topology browser ( Figure 4-35).

Figure 4-35 View Synchronization Switch

Step 2 Edit the synchronization switch attributes as needed:

QLM (T4 Only)

Manual, Forced, or Automatic selection mode

4.4.9  Activate Synchronization on the ONS 15302

Complete the following steps to activate synchronization for the ONS 15302.


Step 1 In the topology browser select device > Synchronization ( Figure 4-36).

Figure 4-36 Select Synchronization

Step 2 Select AdministrativeSynchSource from the pulldown menu ( Figure 4-37).

Figure 4-37 Select AdministravtiveSynchSource

Step 3 Click Save to activate the selected synchronization source.


4.5  Download Software to a Network Element

The purpose of this section is to describe the download of new software to the network element. The task of the management system is to give the network element the necessary information for it to begin downloading new software. The download process is controlled by the element itself.

The section involves presentation of an ongoing download process, starting a new software download process, restart of device after download, and switching between two banks in the element where the software is located.

4.5.1  Network Release

The network element contains device software, firmware, and license and module firmware. Software and firmware updates are delivered in network releases, which supports a given set of traffic modules. If a new module is introduced, the network element needs a new network release.

A network release is delivered as a zip-file together with a network release control file. The file must be unzipped and its contents must be copied to the TFTP server. You must initiate the download of the control file. The remaining part of the upgrade will be controlled by the embedded software on the network element; therefore, verify which files are included in the release and download those files that are missing or are too old in the network element.

4.5.2  Operational and Administrative Software Bank

ONS 15305 network elements store software or firmware in banks. There are two banks, one administrative and one operational. Bank 1 initially is both the administrative and the operational ( Figure 4-38). After a software download to bank 2, a switch (bank) command is performed and bank 2 becomes the administrative bank. When a restart is done, bank 2 also becomes the operational bank and the new software is active.

Figure 4-38 Example of Switching Software Banks

4.5.3  Effect of Software Upgrades on Traffic

A software update/upgrade including an FPGA fix will affect all traffic. Traffic affected depends on module configuration, therefore a network relase download will affect the modules that are a target for the FPGA fix in the downloaded network release.

It is possible to reset (reboot) the device with or without resetting the current configuration. Reboot have minimal impact on traffic processing. The following situations will affect Ethernet/IP traffic and require a device reset to become operative:

When the STP mode is changed, for example from per device to per VLAN (Ethernet/IP traffic affecting)

When decreasing/increasing entries in tunable tables, for example maxARP, maxVLANs, maxBridge, etc.

Whan a software upgrade without an FPGA fix occurs (Ethernet/IP traffic affecting)

When a software upgrade with FPGA fix occurs (All traffic affected)

The period of time from the moment you have triggered a restart to when the device is up and running depends on modules and the software configuration of the device. The down period depends on installed modules and configuration.

4.5.4  Download an ONS 15305 Network Release

A network release is delivered as a zip-file together with a network release control file ( Figure 4-39).


Note See the release notes for an example of a TFTP server that has been verified to work in cooperation with CiscoEdgeCraft.



Step 1 Unzip the Network Release File.

Step 2 Copy the contents to the TFTP - server.

Step 3 In the topology browser select device > SWdownload.

Step 4 Set destination to device.

Step 5 Set Filetype to networkRelease.

Figure 4-39 Download of Release Files

Step 6 Enter FromIPaddress (TFTP server Ip address).

Step 7 Set restartstatus to immediateRestart.

Step 8 Enter SwdlFileName attribute values (File path and name).


Note Click Save.The status of the SwitchBank attribute (switch/noSwitch) is overruled when Filetype is set to networkRelease; a switch will be performed.



4.5.5  Download Software to the ONS 15305


Step 1 In the topology browser select device and then SWDownload ( Figure 4-40).

Figure 4-40 Select Device

.

Modify the following attributes as needed:

Select a destination.

Set Filetype to software.

Enter the FromIPAdress (TFTP server Ip address).

Set the RestartDate.

Select RestartStatus.

Select Delayed Restart if the network element should restart at a specific date/time after the download process.

Enter the SwdlFileName attribute values (File path and name).

Set the SwitchBank attribute:

Switch

After the restart the operational bank will be switched and the new (downloaded) SW will be active.

noSwitch

The operational bank will not be switched after the restart, hence a manual switch must be performed in order to activate the new software. For further details see "Switch Banks Manually" section.

Step 2 Click Save.


4.5.5.1  Switch Banks Manually


Step 1 In the topology browser select device > DevicePhysicalInventory > Software.

Step 2 Select Administrativebank and switch to opposite bank number.

Step 3 Click Save.

Step 4 Perform a restart.


4.5.6  Download Software to the ONS 15302


Step 1 In the topology browser select device > SWdownload.

Step 2 Enter the FromIPaddress (TFTP server Ip address).

Step 3 Enter the SwdlFileName attribute values (File path and name).

Step 4 Click Save.

Step 5 Perform a restart.


4.6  Back Up and Restore Configuration Data

The purpose of this section is to guide you through management of the configuration data in the network element.

The configuration data is BER coded and cannot be edited on the host.

4.6.1  Back Up Configuration Data

Use the following steps to perform a back up of the configuration data and put it on the TFTP-server.


Step 1 In the topology browser select device.

Step 2 Click ConfigData. Select whether to upload or download the configuration from or to the network element ( Figure 4-41).

Figure 4-41 Select ConfigData

.

Step 3 Select BackupCDB.

Step 4 Edit the following attributes as needed:

TftpServerAddress

Destination IP address if configuration data should be uploaded on a remote host.

FileName

File name and path for the configuration data storage.

Trigger

If set to noop only parameters are saved.

If set to backup, the backup operation is started when clicking save.

Step 5 Set trigger to backup.

Step 6 Click Save.

Step 7 The TFTP upload process starts on the network element and the configuration data is stored on the selected host in the specified location (path and file name.)


Note Cisco recommends monitoringthe TFTP console during the upload process.



Note Some TFTP servers require that the file exist on the TFTP server before the upload can be performed.



4.6.2  Restore Configuration Data

If a scheduled restart is set before a new configuration data download process is started, the scheduling parameters will be overwritten.

For Cisco Edge Craft to restart the NE after the TFTP download session is terminated, the Cisco Edge Craft needs to be able to capture the endTftpSession trap sent from the NE. To enable trap-sending see the "1.3.2  Configure Community-Handler" section on page 1-5.


Step 1 In the topology browser select device.

Step 2 Click ConfigData. Select whether to upload or download the configuration from or to the network element ( Figure 4-42).

Figure 4-42 Select Device

Step 3 Select RestoreCDB.

Step 4 Edit the following attributes as needed:

TftpServerAddress

Source IP address if configuration data to be downloaded.

FileName

File name and path for the configuration data storage.

Trigger

If set to noop only parameters are saved.

If set to backup, the restore operation is started when clicking save.

Step 5 Set trigger to restore.

Step 6 Click Save.

The TFTP upload process begins and the configuration data is stored in the network element. Cisco Edge Craft will restart the network element after the restore is complete.


Note Cisco recommends the TFTP console during the download process.



4.7  Alarm and Event Configuration

This section explains how to configure alarm and event reporting and suppress and configure specific alarms.

The network element has a predefined set of combinations of managed objects and alarm types, that means alarm points. These combinations can not be changed by you but the severity level and a description can be defined.

Suppression of specific alarms is important to avoid alarm floods in the network and to focus on the root cause. The ONS 15305 allows you to suppress many alarm types, for example AIS.

You can suppress alarms that are oscillating between activity and inactivity. A time interval (a persistency filter) indicates the time period an alarm must have been on or off before being reported. The persistency filters are defined for a group of alarms of a specific type.

There are three possible persistency group categories:

High order level alarms

Low order level alarms

Unfiltered alarms

For some managed objects you can enable or disable the alarm reporting.

4.7.1  Event Forwarding

Alarms or events cannot be reported before the identity of the receiver of alarms and events has been configured. It is possible to forward alarms and events to more than one receiver.

Event forwarding is enabled when a new user is added with the TrapsEnable attribute set to TrapsEnable as described in the "5.3.2  Set a Loop in a ONS 15305 PDH Port" section on page 5-8.

4.7.2  Configure General Alarm Reporting

In ONS 15305 there are several levels where alarm reporting can be disabled or enabled. Alarms will be reported to a manager only when alarm reporting is enabled on all levels ( Figure 4-43). In addition the event forwarding must be configured for the IP address of the manager (described in the "Event Forwarding" section).

Figure 4-43 General Alarm Reporting Filters.

Note that all alarms from objects in the following sections must pass through the filter:

Device Alarm Enabling

Slot Alarm Enabling

Traffic Port Alarm Enabling

Alarm Port Alarm Enabling

Aux Port Alarm Enabling

In addition to general alarm reporting, it is possible to filter specific alarm types on specific object instances.

4.7.2.1  Device Alarm Enabling

It is possible to enable or disable alarm and event reporting from ONS 15305. In the disabled state, alarms or events are not reported (some generic events, like cold start, etc. are still reported).


Step 1 In the topology browser select device > AlarmConfig > AlarmReporting.

Step 2 Set AlarmReporting to enabled or disabled.


4.7.2.2  Slot Alarm Enabling


Step 1 Select the slot that should report alarms.

Step 2 Set AlarmReporting to enabled.


4.7.2.3  Traffic Port Alarm Enabling


Step 1 Select the SDH or PDH port that should report alarms.

Step 2 Set AdminStatus to enabled


4.7.2.4  Alarm Port Alarm Enabling


Step 1 Select the Alarm port that should report alarms.

Step 2 Set AdminStatus to enabled or disabled.


4.7.2.5  Aux Port Alarm Enabling


Step 1 Select the Aux port that should report alarms.

Step 2 Set AdminStatus to enabled.


Note Slot and port alarm reporting is disabled by default when the slot is configured for a new module.



4.7.3  Suppress Specific Alarms

In addition to configuration of the general alarm filters described above, it is possible to suppress specific alarm types to avoid alarm floods in the network. Other alarms from the same objects will be reported independently of these settings.

4.7.3.1  Suppress RDI, EXC, DEG, SSF Alarms

RDI, EXC, DEG, and SSF alarm reporting can be suppressed from the VC-12, VC-3 or VC-4 layers.


Step 1 In the topology browser select device > AlarmConfig > AlarmReportingVc.

Step 2 Set suppress for the attributes corresponding to the Alarms that should be suppressed:

RdiAlarms

ExcAlarms

DegAlarms

SsfAlarms


4.7.3.2  Suppress AIS Alarms from SDH Ports

AIS alarm reporting can be suppressed from the TU-12, TU-3, or AU-4 layers.


Step 1 In the topology browser select device > AlarmConfig > AlarmReportingVc.

Step 2 Set suppress for the AisAlarms attribute.


4.7.3.3  Suppress AIS Alarms from E1 Ports


Step 1 In the topology browser select device > AlarmConfig > AlarmReportingE1.

Step 2 Set AisAlarms to suppress.


4.7.3.4  Suppress AIS Alarms from AUX Port


Step 1 In the topology browser select device > AlarmConfig > AlarmReportingAux.

Step 2 Set AisAlarms to suppress.


4.7.4  Modify Alarm Severity and Description

It is possible to modify the severity of the reported alarms from ONS 15305.


Step 1 In the topology browser select device > AlarmConfig > AlarmPointConfig.

Step 2 Set the severity level and description for the combination of alarm type and object type. The next time the alarm is reported from this object type it will come up with the configured severity and description in the alarm list.


4.7.5  Set Signal Degrade Threshold

The threshold for a DEG alarm to be reported (and used for MSP switching) can be set for the VC-12, VC-3, VC-4, MS, and RS layers.


Step 1 In the topology browser select device > AlarmConfig > SdTreshold.

Step 2 Set SdThreshold to a value between -6 and -9 (BER= 10 exp -6 to 10 exp -9).


4.7.6  Modify Alarm Persistency

Alarm reporting on and off can be delayed by setting the alarm persistency filters in ONS 15305. The alarms are divided into groups according to their importance for fault management ( Table 4-7, Table 4-8, and Table 4-9).

4.7.6.1  Persistency Group 1 (HighOrderLevel)

Table 4-7 Persistency Group 1 (HighOrderLevel)

Associated Alarm Types
Object Classes Associated with Each Alarm Type

LOS

SdhPort, pdhPort

LOF

rs

AIS

ms

EXC

rs, ms

DEG

rs, ms

TIM

rs

RDI

ms

CDF

rs, ms

AUX

auxPort


4.7.6.2  Persistency Group 2 (Unfiltered)

Table 4-8 Persistency Group 2 (Unfiltered)

Associated Alarm Types
Object Classes Associated with Each Alarm Type

LOP

tu4, tu3, tu12

LOM

vc4

LOF-RX, LOF-TX

e1


4.7.6.3  Persistency Group 3 (LowOrderLevel)

Table 4-9 Persistency Group 3 (LowOrderLevel)

Associated Alarm Types
Object Classes Associated with Each Alarm Type

AIS

tu4, tu3, tu12, e1, e3

EXC

vc4, vc3, vc12

DEG

vc4, vc3, vc12

SSF

vc3, vc12

TIM

vc4, vc3, vc12

RDI

vc4, vc3, vc12

UNEQ

vc4, vc3, vc12

PLM

vc4, vc3, vc12



Step 1 In the topology browser select device > AlarmConfig > AlarmPersistency.

Step 2 Set onFilter or offFilter to a value between 0 and 30 seconds.


4.7.7  Modify ONS 15302 Alarm Configuration Attributes


Step 1 To locate alarm configuration attribues, select device > AlarmConfig ( Figure 4-43).

Figure 4-44 Select Device

Step 2 To modify the alarm severity and description, select device > AlarmConfig > AlarmConfig ( Figure 4-45).

Figure 4-45 Select Alarm Config

Step 3 Set the Severity level and Description for the combination of alarm type and object type of your choice.

Step 4 Click Save. The next time the alarm is reported from this object type it will come up with the configured severity and description in the alarm list.


4.7.7.1  View all Alarm Reporting Instances

To view all alarm reporting instances, select AlarmReportingAll ( Figure 4-46).

Figure 4-46 Select AlarmReportingAll

4.7.7.2  Enable Alarm Reporting


Step 1 To enable alarm reporting, set AlarmReporting to enable using the drop-down menu ( Figure 4-47).

Figure 4-47 Select AlarmReporting

Step 2 Click Save.


4.7.7.3  Modify Ais Rdi Alarm Reporting


Step 1 Select AlarmreportingAisRdi ( Figure 4-48).

Figure 4-48 Select AlarmreportingAisRdi

Step 2 Select the instance.

Step 3 Select allow or suppress for the Ais alarm ( Figure 4-49).

Figure 4-49 Select AIS Attributes

Step 4 Repeat for the Rdi alarm.

Step 5 Click Save.


4.7.7.4  Modify Alarm Persistency

Modifying the alarm prsistency filters in the ONS 15302 can prevent alarms that vascillate between activity and inactivity.


Step 1 In the topology browser select device > AlarmConfig > AlarmPersistency ( Figure 4-50).

Figure 4-50 Set Alarm Persistency Attributes

Step 2 Set onFilter or offFilter to a value between 0 and 255 seconds.

Step 3 Click Save.


4.7.7.5  Modify Signal Degraded (Sd) Threshold


Step 1 Select SdTreshold ( Figure 4-51).

Figure 4-51 Select SDTreshold

Step 2 Select desired MO class

Step 3 Set SdTreshold to a value between 6 and 9 ( Figure 4-52).

Figure 4-52 Set SDTreshold

.

Step 4 Click Save.


4.8  Manage ONS 15305 Slots

A slot represents a physical position on the network element where different hardware modules can be installed ( Figure 4-53). This section explains how to install and remove modules.

Figure 4-53 ONS 15305 Slots

4.8.1  View a Slot

The browser presents four slots numbered from 1 to 4. The slot attributes as defined in the information model are available in the attribute window. Each slot can be equipped with one HW module. By default the slot is unequipped ( Figure 4-54).

Figure 4-54 Select Slot

A slot can be empty or have a hardware module with a given number of ports and software version installed ( Figure 4-55).

Figure 4-55 Slot Module - Port Concept

The physical inventory data for an installed module also appears in the attribute window.

You can preconfigure a slot with an expected module before physically installing a module. The system populates the topology browser according to the specified expected module. The slot has an attribute that reflects the relation between the expected module and the installed module. Slot states include:

Empty

Installed and expected

Expected and not installed

Installed and not expected

Mismatch of installed and expected

Unavailable

Unknown

A state diagram for the possible transitions of a slot is shown in Figure 4-56. This is the suggested state machine from TMF 814 supporting documentation, equipmentStates.pdf.

Figure 4-56 Relation Between Installed and Expected Module in a Slot.

A state machine for the values of the attribute describing the relation between an installed and expected module is shown in Figure 4-56.

If a mismatch between the two modules occurs, an alarm will be generated. The alarm is cleared if the module is replaced or the expected module is changed, which means a match between expected and installed is present.

Before replacing a module and selecting a new expected module type, the expected module of the slot must be set to unequipped.

For management of different ports, see Chapter 5, "Traffic Port Management."

4.8.2  Modify a Slot

To modify the expected module attribute, the ports of the previous expected module must be unused and unstructured.


Step 1 Select a target slot ( Figure 4-57).

Figure 4-57 Select Target Slot

Step 2 Edit the following attributes as needed:

AlarmReporting

enable or disable

ExpectedModule

select module of current interest

ShutdownRestart

noop, restart or shutdown. (noop; No operation is applied)


Note The attribute Module Interface shows the physical interface on the selected module. This attribute value indicates LongHaul (for example, L-4.2-LC) or ShortHaul (for example, S-4.1-LC) for STM modules. The connector is also indicated.


Step 3 Click Save.

Some changes require a restart of the module. If this is the case you will be prompted to restart.

When a slot has been configured to contain a specific module, the ports of the module are automatically created in the network element. The type of ports created depends on the module type configured for the slot ( Figure 4-58).

Figure 4-58 Set View Mode to Children

.

The ports of an installed module were not created if the slot was configured to contain another module type or being empty.



hometocprevnextglossaryfeedbacksearchhelp

Posted: Fri Sep 14 11:44:20 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.