Confirm/Update the MIB

- Overview

A MIB confirmation should be performed during node creation or in any other situation where the MIB status is “Filled, not confirmed”.

- Before you begin

Before confirming or updating the MIB, determine the following:

  • Performing a MIB confirmation will cause the NE to reset. A new login, after waiting several minutes for the reset to take place, will have to be performed.

  • Confirming the MIB for an existing NE can result in traffic disruptions.

Procedure

Proceed as follows to confirm the MIB of a NE:

 
1

Select Management → Node Details.

Result: The Node Details window appears. This window allows confirmation or update of a NE MIB.

CAUTION: Confirming the MIB will result in an NE reset. The current login session will be terminated. Also, while overwriting the older MIB, traffic can be affected.


2

Click Confirm MIB.

Result: A confirmation window appears.


3

Click Yes.

Result: The operation will be started. Confirming the MIB should take several minutes. During this time, the connection between the ITM-CIT and the NE will be lost. To re-establish this connection, a login must once again be performed after waiting for the operation to complete.


4

Login again.


5

Select Management → Node Details.

Result: The Node Details window appears. In this window, the MIB state can be viewed. It should now be Filled.


6

Click Close.

Result: The Node Details window disappears.


End of steps

Parameters

NE type

The NE type is indicated.

NE name

The NE’s name is listed. The name must be unique across management domains. If the NE is not managed by the ITM-NM, then the name may be up to 20 characters in length. If the NE will be managed by the ITM-NM, then the name must be 3 to 10 characters long with the last three characters a slash and two digits. Only A-Z, 0-9, _, /, and - are permitted for NEs managed by the ITM-NM. An example of an ITM-NM compatible name is “LONDON/02”.

NE location

The location of the NE is given. The location may have up to 20 uppercase or lowercase characters, digits, and spaces.

MIB state

The status of the MIB is indicated. The possible values are described in the table below.

MIB state

Description

Empty

An empty System Controller (SC) has been inserted or the MIB was cleared after starting an MIB download automatically by the management system. If the MIB state is empty, the management system can proceed with the MIB download.

Filled

The NE possesses a valid MIB which has been confirmed.

Filled Unknown

The NE has a MIB, however, it is of unknown validity. This can occur, for instance, if one SC is replaced by another SC having a MIB.

Filled Not Confirmed

The NE has a MIB, however, it has not yet been confirmed by the ITM-CIT or OMS. The procedure Confirm/Update the MIB gives the steps necessary to confirm the MIB. Once confirmed, the state will become Filled.

Waiting for Upload

This state is only possible when the NE is managed by the OMS. After confirmation of the MIB, the NE performs a reset and loses its association with the OMS. When the NE restarts, the MIB state becomes Waiting for Upload. When the OMS reassociates with the NE and detects this MIB state, a MIB upload is performed, and the state will then become Filled.

Management state

The state of the association with the OMS is displayed. The possible states are described in the table below.

Management state

Description

Normal

Normal will be displayed whenever the automated management operations have been completed. In other words, the OMS has completed the MIB upload, MIB download, MIB resynchronization, or reevaluation of fault status. The state can also be Normal when the association between the ITM-CIT/OMS and the NE has been lost.

Uploading

The OMS is performing an MIB upload.

Resyncing

If the MIB of the NE and the MIB image on the OMS are out of synchronization, then the OMS invokes a resynchronization. The management state shows the progress of this operation. If executed properly, it should display, in order: Normal, Resyncing, Normal, ReEvaluatingFaultStatus, Normal.

ReEvaluating FaultStatus

After a resynchronization, the OMS initiates a reevaluate fault status operation.

Downloading

A MIB download has been started by the OMS. The management state is set to Normal during the downloading process. If the MIB download is in progress when a loss of association occurs, then the management state will remain Downloading.

EMS connection state

Indicates wether an active connection (CMISE association) exist to the element manager (OMS).