Oracle Communications EAGLE (Software)
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec Eagle 5
 

This procedure explain how to copy a new UIM or UAM log file to a TDM.

In this Document

Goal

Solution

Created from <SR 3-9207888481>

Applies to:

Goal

How to copy a new UIM or UAM Log File to a TDM?

Solution

To ensure this procedure works properly, you must ensure to use an MO System Cartridge or removable drive that has an empty log. This can be accomplished by formatting a spare MO cartridge or removable drive, then use that cartridge/removable to copy the new log file from.


There are 2 methods described below: Legacy EOAM and OAMHC


Method 1 - For Legacy EOAM

Steps to Format an MO Cartridge

(1) Find a spare MO cartridge and insert into MDAL and wait for one minute.

(2) Issue the following command to format the cartridge

  format-disk:type=system:force=yes

  Note: this can take up to 15 minutes (30 minutes max).
(3) When completed, issue command rept-stat-db.

The database level for MDAL in slot 1117 should show a level of 1.


Steps to copy new UIM log to TDMs (table ID 148)

(1) Determine which GPSMII/TDM MASP is currently standby (use rept-stat-db) - 1113/1114 or 1115/1116.

(2) Insert a newly formatted MO cartridge into MDAL, slot 1117.

(3) Issue the following commands to copy a new UIM log to the standby TDM

  copy-tbl:stbl=148:sloc=1117:dtbl=148:dloc=
(4) After the copy-tbl command has displayed completed message, you need to initialize this standby MASP complex

  init-card:loc=
(5) After system recovers to duplex mode, we need to switch activity on the MASP complex

  init-card:loc=
(6) You will have to log back into the Eagle after the switch of activity.

(7) After system has recovered back to duplex, do steps 1-4 on the newly standby TDM




This will fix the problem with the UIM log. You can verify this with the command:

  rtrv-log:num=10:type=uim
Steps to copy new UAM (alarm) log to TDMs (table ID 173)

The steps are exactly the same as above, except table ID is 173


Method 2 - For OAMHC systems

Steps to Format a Removable Drive

(1) Find a spare Removable USB drive and insert into Active MASP and wait for one minute.

(2) Issue the following command to format the cartridge

  format-disk:type=system:force=yes

  Note: this can take up to 15 minutes (30 minutes max).
(3) When completed, issue command rept-stat-db.

The database level for Removable in Standby OAM-RMV (RD BKUP) should show a level of 1.


Steps to copy new UIM log to TDMs (table ID 148)

(1) Determine which MASP is currently standby (use rept-stat-db) - 1113/1114 or 1115/1116.

(2) Insert a newly formatted Removable into Standby TDM E5OAM.

(3) Issue the following commands to copy a new UIM log to the standby TDM

  copy-tbl:stbl=148:sloc=:dtbl=148:dloc=
(4) After the copy-tbl command has displayed completed message, remove the Removable USB from the Standby TDM E5OAM.

(5) Once the USB is removed, you need to initialize this standby MASP complex

  init-card:loc=
(6) After system recovers to duplex mode, we need to switch activity on the MASP complex

  init-card:loc=
(7) You will have to log back into the Eagle after the switch of activity.

(8) After system has recovered back to duplex, do steps 1-5 on the newly standby TDM




This will fix the problem with the UIM log. You can verify this with the command:

  rtrv-log:num=10:type=uim
Steps to copy new UAM (alarm) log to TDMs (table ID 173) for OAMHC systems

The steps are exactly the same as above, except table ID is 173


Spare TDM

Note: If the problem, which caused this procedure to be executed, involved the spare TDM, the spare TDM needs to be rolled into the standby MASP and the COPY-TBL commands executed on it.



Other Notes

Measurements must be turned off before formatting MO or USB.


The table id’s are the same for all Eagle STP releases.

This solution has no attachment