Lucent Technologies 5ESS-2000, Инструкции по эксплуатации и техническому обслуживанию

Страница: 303 / 1421

applicable.
To perform an UODD growth, perform Steps 4 through 8.
NOTE:
In the software releases of 5E9.2 and later, the UODD size is directly determined by the number of
peripherals and customers on the module. UODD growth is a normal part of growing a new module.
This was not the case for prior software releases.
2. To perform an NRODD growth, perform Steps 9 through 13.
3. To perform an RODD growth, perform Steps 14 through 19.
4. NOTE 1: The OP:ODD input message determines the current amount of used, available, and
unallocated ODD memory. This is accomplished at any operational recent change and verify (RC/V)
or master control center (MCC) terminal. Once the input message is accepted, observe the terminal
screen for the appropriate responses indicated. Note 2 evaluates the responses.
At the MCC, type and enter OP:ODD,SM=a;
Where:
a
= SM number
Response:
OP ODD
SM
RODD USED=ru AVAIL=ra PCT USED=rpu
NRODD PCT UODD PCT
USED AVAIL USED USED AVAIL USED UNALLOC SABM
SM s snu sna snpu suu sua supu suna sbm
Where:
ru
= Number of kilobytes (1024 bytes) used by the redundant ODD
ra
= Number of kilobytes (1024 bytes) available for use by the RODD
rpu = Percentage of RODD memory currently being used
s
= SM number
snu
= Number of kilobytes used by the NRODD in SM
sna = Number of kilobytes available for use by the NRODD
snpu
= Percentage of NRODD memory currently being used
suu
= Number of kilobytes used by the UODD in SM
sua
= Number of kilobytes available for use by the UODD
supu = Percentage of UODD memory currently being used
suna
= Number of kilobytes unallocated at the end of SM memory and available
for acquisition by ODD growths
sbm
= Number of kilobytes allocated to SAB memory
NOTE 2: The number of Kbytes available in the NRODD is used to determine how much memory can be
acquired by the UODD growth. The available Kbytes in the NRODD will be reduced by the
corresponding UODD growth size. The maximum UODD growth possible is such that the NRODD is
left with 80 percent of its memory being used FOLLOWING the UODD growth, or 512 Kbytes,
whichever is less.
UODD growth uses the global parameter DBmavsodd for this check. DBmavsodd is the minimum
percent available of protected ODD memory that must exist before a minor alarm is issued. This
value is ODBE updateable, but should be done with caution. When this limit is reached, a minor
235-105-210 October 1999
Copyright © 1999 Page 2