CS 2000 Compact Performance Monitoring-CVM12-SEB-08!00!018.v.12.0.3

SEB 08-00-018 CS 2000 Compact Performance Monitoring Carrier Voice over IP Engineering Document Date: Feb 26,2009 Document Version: 12.0.3 Document Owner: RDA13

The information contained in this release relates to certain Nortel products that have been designed by or on behalf of Nortel to conform to applicable Nortel and third party specifications and requirements, including, for example, NEBS compliance. In addition, such Nortel products are designed to be used for its intended purpose as specified in this documentation. In the event, and to the extent, that such Nortel products are used by the user for a purpose other that its intended purpose, or used with third party products that do not conform to any such applicable Nortel and third party specifications and requirements, including, for example, NEBS compliance, Nortel shall have no liability of any kind to the user for any problems which may arise, including, without limitation, any related failure of the Nortel product to perform in accordance with its specification.

3

CS2000 Compact Performance Monitoring

NORTEL CONFIDENTIAL

Abstract The Carrier Voice over IP solutions offer great flexibility. The subscribers could be either residential or enterprise customers. For residential customers, the data network access could be an end-to-end managed network provided by the carrier space, or through a managed core network connecting the residential access network (DSL, HFC, Internet) via an Access Network. For enterprise customers, the data network access would typically be for either IP Virtual Private Network service, connecting multiple enterprise sites, access to an ISP, or both.

Figure 1 Carrier Voice over IP Network

The focus of this document is to provide the engineering rules monitor the CPU capacity and memory usage of the CS 2000 Compact.

LineGWC

TrunkGWC

H.323GWC

CICMGWC

Succession Core Managed Network

CS-LAN

UASAMSUSP

MediaProxy

CS 2000EMServersOAM&P

Clients

CPE NAT/FW

MCS 5200

PSTN

Internet

ResidentialNetwork

CPENAT/FW(Optional)

Ctx IP Clients

MCS Clients

Access Network

IAD

Ctx IP Clients

MCS Clients

CPE GW(e.g. H.323,

Ethernet Line)

EnterpriseNetwork

DPTGWC

PVG

ResidentialNetwork

DSL

IAD

LineGWC

TrunkGWC

H.323GWC

CICMGWC

Succession Core Managed Network

CS-LAN

UASAMSUSP

MediaProxy

CS 2000EMServersOAM&P

Clients

CPE NAT/FW

MCS 5200

PSTNPSTN

InternetInternet

ResidentialNetwork

CPENAT/FW(Optional)

Ctx IP Clients

MCS Clients

ResidentialNetwork

CPENAT/FW(Optional)

Ctx IP Clients

MCS Clients

Access Network

IAD

Ctx IP Clients

MCS Clients

CPE GW(e.g. H.323,

Ethernet Line)

EnterpriseNetwork

IAD

Ctx IP Clients

MCS Clients

CPE GW(e.g. H.323,

Ethernet Line)

IAD

Ctx IP Clients

MCS Clients

CPE GW(e.g. H.323,

Ethernet Line)

EnterpriseNetwork

EnterpriseNetwork

DPTGWC

PVG

ResidentialNetwork

DSL

IAD

4


NORTEL CONFIDENTIAL

Revision Control

Date Version Revised by Remarks

2004-10-25 8.0.0 Hady Abi-Aad Initial draft

2004-10-29 8.0.1 Hady Abi-Aad Added Alarms information

2004-11-16 8.0.2 Hady Abi-Aad Added internal review changes

2005-02-15 8.0.3 Hady Abi-Aad Changes to new template

2006-07-12 9.1.1 R. Graman SN09FF update

2007-06-04 10.0.1 R. Graman SN10 update

2007-11-01 10.0.2 R. Graman CPCI 6115 memory update

2009-02-26 10.0.3 D. Kaya Ilhan Updated section 2.2 and 3.2

2008-04-01 11.0.1 I. Marangoz CVM11 update

2008-04-20 11.0.2 I. Marangoz Added internal review changes

2008-05-25 11.0.3 I. Marangoz Updated review changes

2008-06-09 11.0.4 I. Marangoz Table in section 2.3.2 corrected


2008-06-18 12.0.1 T. Cerit CVM12 drop1 update

2008-09-25 12.0.2 I. Marangoz Updated section 3.2.2


5


NORTEL CONFIDENTIAL

Table of Contents

1. INTRODUCTION ..................................................................................................................... 6

2. CORE CALLP UTILIZATION.................................................................................................. 7

2.1 Background........................................................................................................................ 7

2.2 Capacity Engineering........................................................................................................ 9 2.2.1 Engineered Capacity (ENGCAP) BHCA.................................................................... 10 2.2.2 Supported BHCA level based on sparing bandwidth limit ......................................... 10 2.2.3 Feature Real Time Impact ......................................................................................... 11

2.2.3.1 TCAP/LNP ............................................................................................................. 11

2.3 Monitoring Capacity ........................................................................................................ 11 2.3.1 Engineered Capacity Projection ................................................................................ 11 2.3.2 CS 2000c Software Upgrade..................................................................................... 12

2.4 Monitoring Tools.............................................................................................................. 12 2.4.1 BRSTAT OM.............................................................................................................. 13 2.4.2 CAPCI ........................................................................................................................ 14 2.4.3 DMSMON; HIGHCAP................................................................................................ 15 2.4.4 TPCSPOM OM .......................................................................................................... 15

3. MEMORY USAGE................................................................................................................. 18

3.1 Background / Terminology ............................................................................................. 18

3.2 Memory Engineering ....................................................................................................... 19 3.2.1 Monitoring Memory Usage......................................................................................... 19 3.2.2 CS 2000c Software Upgrade..................................................................................... 19

3.3 Monitoring Tools.............................................................................................................. 21 3.3.1 STORE OM................................................................................................................ 21 3.3.2 STORE ALL USAGE ................................................................................................. 22 3.3.3 Memory Alarms.......................................................................................................... 24

LIST OF ACRONYMS................................................................................................................... 25

6


NORTEL CONFIDENTIAL

1. Introduction This document addresses the monitoring of the CS 2000 Compact Core Utilization and Memory usage.

7


NORTEL CONFIDENTIAL

2. Core CallP Utilization 2.1 Background The Core has a fair share scheduler. 72% of the processor real time is guaranteed for call processing (CallP). The remaining time is guaranteed for other classes, such as maintenance, background, guaranteed terminal access, etc (as depicted in the figure below).

CallP Utilization (CPUTIL or UTIL) is the indicator of Core processor utilization. UTIL is 100% when CallP uses all of its guaranteed 72% CPU occupancy.

If needed, CallP can tap into the other classes’ un-use share of CPU occupancy. In that case UTIL will be > 100%.

8


NORTEL CONFIDENTIAL

CALLP 72%

GTERM 1%

FORE 1%

SNIP 1%

BKG 3%

OM 3%

DNC 3%

MAINT 8%

SCHED 8%

100%

CPU

occ

upan

cy

100%

CP

Util

izat

ion

9


NORTEL CONFIDENTIAL

2.2 Capacity Engineering As of CVM12 drop1 there are three available processor options. The table below shows the processor option and the BHCA capacity at the ENGCAP or 100% Call Processing utilization level. Also shown is the Sparing bandwidth capacity of each. Sparing bandwidth is described later in this section.

MCPN 765 NTRX51GZ

MCPN 905 NTRX51HZ

CPCI6115 NTR651HZ

Call Model NA Intl NA Intl NA Intl Tandem

No LNP/IN, 1.3M 700K 2.0M 1.1M 2.0M 1.1M

Tandem, 30% LNP/TCAP/IN,

90% AMA

900K 525K 1.40M 800K 1.40M 800K

EO, No LNP/IN Multiple features

assigned

800K 575K 1.25M 875K 1.25M 875K

EO, 30% LNP/TCAP/IN Multiple features

assigned, 100% AMA

525K 400K 800K 625K 800K 625K

ACD/ICM/OCS/Converged Desktop 5 msgs/call

350K 250K 550K 400K 550K 400K

Sparing Bandwidth NTRX51GZ NTRX51HZ NTR651HZ Fibre Channel

(see Note 1) Non-Geo 8000 Geo 8000

6000 Non-Geo 16,000 Geo 12,000

GE Channel (CS2100 Only)

6000 6000 6000

Memory Allocation NTRX51GZ NTRX51HZ NTR651HZ SOS available

Memory allocation in MegaBytes(MB)

1216MB 1152MB 1152MB

Note 1: Sparing Bandwidth (dirty pages) may limit the Compact BHCA capacity. To stay within the sparing bandwidth capacity noted in the Table, BHCA should not go above the ranges given below;

6000= 500K-600K 8000= 700K-850K 10000= 900K-1.1M 16000= 2.0M

10


NORTEL CONFIDENTIAL

These figures are planning figures, and not limits. The customer should use the OM to determine where the switch is running against the hard limit of max # dirty pages.

2.2.1 Engineered Capacity (ENGCAP) BHCA

The ENGCAP BHCA figures shown in the Table above are stated for a Tandem or End office call model that has 60% of the call attempts producing an AMA record, with no LNP or other feature activation.

As features and services are added to the call mix the ENGCAP BHCA supported figures are reduced. Feature/service activations, in particular TCAP queries associated with LNP or 800 database queries add to the processor real time used per call attempt. With 100% LNP in an End office model, which is approximately 30% of the call attempts doing an LNP TCAP query, the ENGCAP is reduced from 1.35M BHCA to 950K BHCA on the MCPN765, or approximately 30%. This percentage decrease would apply to the ENGCAP values of the other processor options as well. This must be considered as part of the Compact capacity planning. ENGCAP is defined in Section 2.2.2.

2.2.2 Supported BHCA level based on sparing bandwidth limit

Capacity engineering of the MCPNxxx must also consider the sparing bandwidth capacity of the Compact. Sparing bandwidth refers to the inter core Fiber channel capacity. For the Compact Call Agents to remain in sync the number of “dirty pages” that can be transferred every 500 msecs is approximately 8000. Call processing, Maintenance, Audits, Office Size, and parameter settings , all contribute to the use of dirty pages. When these tasks run a peak in the number of dirty pages required can exceed 8000 at capacity, which can cause the CS2000-Compact to drop to WARM SYNC and potentially drop sync.

Actual field performance will vary based on parameter datafill, line/trunk data fill, and associated features. Parameters NCCBS and NUMCALLPROCESSES in Table OFCENG can have a significant impact on the amount of sparing bandwidth required every 500 msec. Operational Measurements (OM) CP and CP2 report the High Water Mark (HWM) use of these resources. The EXT OM group should be used to monitor HWM use of various parameter settings such as NO_OF_DMS250_REC_UNITS. If sparing bandwidth capacity is nearing the Dirty Page use limit identified above, reducing oversized parameters can reduce dirty page use.

Nortel recommends monitoring the dirty page use upon initial deployment, before and after line/trunk additions, Software upgrades or parameter changes to an office. Also, it is highly recommended to monitor the dirty page use in an office that is nearing the Engineered Call Attempt Capacity.

The average and highest number of dirty pages used in a five minute period can be retrieved from file /var/log/3pc.statlog which is located on the inactive CCA. At this time there is not an operational measurement or log that records the number of dirty pages in use.

11


NORTEL CONFIDENTIAL

2.2.3 Feature Real Time Impact

2.2.3.1 TCAP/LNP

%LNP 765CCA Erosion

905/6115CCA Erosion

0% 0% 0%

16% 16% 16%

30% 24% 23%

60% 34% 34%

2.3 Monitoring Capacity The Core should be engineered to a UTIL < 100% at the High Day Busy Hour (HDBH).

It is recommended to start planning for a core upgrade when the Average Busy Season Busy Hour (ABSBH) UTIL reaches 80% as reported by the BRSTAT_BRSCAP Operational Measurement. Sparing Bandwidth use or dirty pages as described in Section 2.2 must also be monitored.

2.3.1 Engineered Capacity Projection The Engineered Capacity (EngCap) is the Core’s traffic throughput at 100% UTIL. EngCap can be measured using the CAPCI command during the Busy Hour. CAPCI is a manual CI level command.

NOTE: Alternatively, EngCap can be derived using hourly OMs (OFZ and BRSTAT) during the Busy Hour:

EngCap = CATMP / UTIL

Where CATMP and UTIL are

CATMP = (NIN2 + NORIG2) x 65536 + NIN + NORIG

UTIL = BRSCAP

12


NORTEL CONFIDENTIAL

2.3.2 CS 2000c Software Upgrade Always make sure there is sufficient capacity before upgrading the CS 2000c to a new software release.

If an office planning to upgrade to a new release is not adding new ports, the following table gives an estimate of capacity erosion for a given upgrade.

New_UTIL = Old_UTIL / (1 – Erosion)

Where, Erosion is the per release capacity erosion given in the table below.

Assume 5% erosion per release for SN08 and higher. The following information is based on data obtained from Nortel’s lab facilities. As a result, Nortel does not guarantee the same results in a customer’s production environment as each scenario is unique and different from a call model and call mix perspective. Maximum 4% erosion is assumed from CVM11 to CVM12.

FROM \ TO SN08 SN09 SN09U SN10 CVM11 CVM12

SN07 5% 10% 15% 20% 25% 29% SN08 - 5% 10% 15% 20% 24% SN09 - - 5% 10% 15% 19%

SN09U - - - 5% 10% 14% SN10 - - - - 5% 9%

CVM11 - - - - - 4%

Example:

A SN08 office with an average busy hour of 60% UTIL is planning to upgrade to SN10. Once it upgrades to SN10 its new average busy hour UTIL will be

New_UTIL = 60 / (1 – 0.10) = 67%

2.4 Monitoring Tools There are Operational Measurement and CI command available to monitor capacity.

13


NORTEL CONFIDENTIAL

2.4.1 BRSTAT OM Register BRSCAP (= UTIL) of OM group BRSTAT should be used to monitor the CallP Utilization on the Core.

Sample BRSTAT OM BRSTAT CLASS: HOLDING START:2004/10/22 14:00:00 FRI; STOP: 2004/10/22 14:30:00 FRI; SLOWSAMPLES: 18 ; FASTSAMPLES: 180 ; BRSCAP BRSCMPLX BRSSCHED BRSFORE BRSMAINT BRSDNC BRSOM BRSGTERM BRSBKG BRSIDLE BRSAUXC BRSNETM BRSSNIP 0 82 0 168 54 7 0 12 3 150 0 1 0 8 NOTE: The values in the registers accumulate during accumulation periods. If there is multiple transfer periods during an accumulation period, the value of each register have to be divided by the number of transfer periods in the accumulation period.

Register Description

BRSCAP Measures Call Processing class utilization. CallP is allocated 72% (including AUXCP) of CPU. BRSCMPLX Not applicable to Compact BRSSCHED Measures Scheduler Overhead utilization. SCHED is allocated 8% of CPU. BRSFORE Measures Operating System Overhead (Foreground) utilization. Foreground is allocated 1% of CPU.BRSMAINT Measures Maintenance class utilization. MAINT is allocated 8% of CPU. BRSDNC Measures Network Operating System File Transfer class utilization. NOSFT is allocated 3% of CPU.BRSOM Measures Operational Measurement class utilization. OM is allocated 3% of CPU.

BRSGTERM Measures Guaranteed Terminal class utilization. GTERM is configured in OFCENG: GUARANTEED_TERMINAL_CPU_SHARE. Should be set to 1%.

BRSBKG Measures Background class utilization. BKG is allocated 3% of CPU. BRSIDLE Is pegged once for every minute that the Idle scheduler ran.

BRSAUXCP Measures the Auxiliary Call Processing class utilization. AUXCP CPU share is configured in OFCENG: AUXCP_CPU_SHARE. Should be set to 1%.

BRSNETM Measures Network Maintenance class utilization. NETM is allocated 0% (or 20% for STP offices only) of CPU.

BRSSNIP Measures Internet Protocol class utilization. SNIP is allocated 1% of CPU.

BRSTAT registers.

14


NORTEL CONFIDENTIAL

Operational Measurements CP and CP2 mainly monitor software resources but should also be monitored to detect any occurrences of Core Overload condition.

. OM Register Description

CP ORIGDENY Counts the denied originations by the Core Overload Controls CP CPLOOVFL Counts the dropped originations because of CP letter exhaustion. CP2 OVRLD Is pegged every minute the Core is in Overload condition. CP2 INEFDENY Counts the origination/abandon pairs ignored by the Core Overload Controls

CP and CP2 Core Overload Indicators

NOTE: An office could have indications of Core Overload conditions without BRSCAP ever go over 100%. This can happen when an office experiences high traffic peaks. BRSCAP is an average of UTIL over a transfer period. The DMSMON; HIGHCAP command keeps hourly UTIL high-water-marks for the last 30 days.

OM Register Description

OFZ NIN Counts number of incoming trunk calls OFZ NIN2 NIN extension register OFZ NORIG Counts number of originating line calls OFZ NORIG2 NORIG extension register

OFZ Traffic Throughput Registers.

2.4.2 CAPCI The CAPCI command provides a real time (one minute snapshots) view of:

Core utilization – UTIL

Indication if Core Overload Control was activated – CCOVRLD

EngCap: Projected Core capacity at 100% UTIL (same call mix) – ENGCATMP

Present hourly call rate – CATMP/HR

Indication if UTIL exceeded the value configured in OFCENG: cc_englevel_warning_threshold - ENGLEVEL

Indication if Core units are synchronized – SYNC

The other fields correspond to the different class utilizations as described for the BRSTAT OM.

15


NORTEL CONFIDENTIAL

Sample CAPCI output

CATMP/HR UTIL ENGCATMP ENGLEVEL SYNC CCOVRLD IDLE 328440 34% 939394 BELOW YES OFF YES SCHED FORE MAINT DNC AUXCP OM GTERM BKG NETM SNIP 161% 45% 10% 0% 1% 16% 0% 231 0% 9% NOTE: EngCap = ENGCATMP ~ CATMP HR / UTIL

2.4.3 DMSMON; HIGHCAP

The DMSMON; HIGHCAP command provides the hourly high-water-mark UTIL for the past 30 days. It can be used to determine the Busy Hour.

Sample DMSMON; HIGHCAP output ************************************** * HIGH WATER CAPACITY * ************************************** TIME DATE | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 00 ------------------------------------------------------------------------------- | 09/25 | 10 8 7 6 7 6 13 33 43 42 46 48 49 50 49 40 44 42 38 30 27 25 17 14 | 09/24 | 9 9 8 7 6 6 12 19 24 31 33 34 35 34 41 42 43 42 37 31 29 26 19 13 | 09/23 | 13 12 11 10 7 6 8 9 13 19 18 20 22 23 24 23 24 29 28 27 26 23 19 13 | 09/22 | 13 18 10 7 8 7 10 14 20 26 31 33 31 32 30 31 33 31 33 31 30 27 21 18

NOTE: This sample shows only a part of a complete output.

2.4.4 TPCSPOM OM The TPCSPOM OM group monitors traffic and utilization of CCA memory sparing rates. The calculations performed by the TPCSPOM OM group are: • CCA memory sparing bandwidth utilization over a configured collection period (5, 15 or 30 minutes).

16


NORTEL CONFIDENTIAL

• Peak (high water mark) CCA memory sparing bandwidth utilization, expressed as a percentage, over a configured collection period (5, 15 or 30min). • Specific percentage ranges of memory pages transferred per half second intervals

Sample TPCSPOM OM CLASS: ACTIVE START:2008/04/02 07:45:00 WED; STOP: 2008/04/2 07:57:39 WED; SLOWSAMPLES: 8 ; FASTSAMPLES: 76 ; INFO (TPC_SPARING_USAGE) SP_MAX SP_AVRG SP_0030 SP_3040 SP_4050 SP_5060 SP_6070 SP_7080 SP_8085 SP_8590 SP_9095 SP_95100 SP_100UP 0 Dirty Page Limit is: 8000 16 5 1509 0 0 0 0 0 0 0 0 0 0


SP_MAX Captures the peak (high water mark) CCA memory sparing bandwidth utilization

SP_AVRG Ratio of the number of pages transferred in a specific sampling interval ( eg. 500 sec ) to a Sampling interval page limit.

SP_0030 The number of pages transferred, in a half-second interval, that fall into the 0% - 30% Percentage range.






17


NORTEL CONFIDENTIAL






SP_100UP The number of pages transferred, in a half-second interval, that fall into the > 100% Percentage range.

18


NORTEL CONFIDENTIAL

3. Memory Usage 3.1 Background / Terminology Memory is divided in three different types:

Program Store (PS): Memory allocated for program (executable) code. PS is allocated from Spare memory in 32 MB chunks.

Data Store (DS): Memory allocated for data (tables, queues, s/w resources, etc). DS is allocated from Spare memory in 32 MB chunks.

Spare: Memory not yet allocated (neither PS nor DS).

Furthermore, DS memory is divided in different types. When DS is allocated it is assigned a type (DSTEMP_B, DSPROT_W, etc.)

Typed DS memory: DS is allocated in chunks of 64 KB from the un-typed DS memory. If there is not enough un-typed DS memory available, then 32 MB is allocated from Spare memory.

Un-typed DS memory: Memory allocated as DS but not yet assigned a type.

19


NORTEL CONFIDENTIAL

3.2 Memory Engineering There are two types of memory cards.

1 GB card: It has 704 MB of store available.

1.5 GB card: It is the largest memory card supported as of CVM12 and is baseline starting in SN06. It has 1216 MB of store available.

For additional information and details according to different card types, please refer to section 2.2 Capacity Engineering.

3.2.1 Monitoring Memory Usage

Offices equipped with the 1 GB card are recommended to upgrade to the 1.5 GB card when SPARE < 96 MB. Depending on customer order process cycle they may wish to start the upgrade process sooner.

Offices equipped with the 1.5 GB card should notify PLM when SPARE is < 128 MB. You must allow for 48 MB SPARE after the upgrade to avoid a low_mem alarm.

3.2.2 CS 2000c Software Upgrade Always make sure there is sufficient memory before upgrading the CS 2000c to a new software release.

The following formula gives an estimate of the Spare memory remaining after a CS 2000c upgrade.

SPARENEW = (TOTAL MEMORY) - DSTOTALNEW - PSTOTAL

TOTAL MEMORY = 1152 MB

PSTOTAL = 128 MB

DSTOTALNEW = RND_UP_by_32{DSUSEDOLDx(1.03)N+(Nodata Increase)}

Where:

N is the release difference (i.e. upgrade from 08 to 10, N = 10 – 8 = 2).

Nodata Increase is provided in MB by the following table: FROM \ TO SN08 SN09 SN10 CVM11 CVM12

SN07 6.0 10.9 14.4 16.2 16.7 SN08 - 4.9 7.9 9.7 10.2 SN09 - - 2.3 4.1 4.6

20


NORTEL CONFIDENTIAL

SN10 - - - 1.8 2.3 CVM11 - - - - 0.5

Example:

A CVM11 office equipped with a CPCI6115 card and has a DS TOTAL of 800 MB plans to upgrade to CVM12. Its SPARE memory after the upgrade will be:

DSTOTALCVM12 = rnd_up_by_32 {900 x 1.03 + 0.5} = 824

SPARECVM12 = 1152 – 824 – 128 = 200 MB

21


NORTEL CONFIDENTIAL

3.3 Monitoring Tools There are Operational Measurement, CI command and Alarms available to monitor Memory usage.

3.3.1 STORE OM Registers SPAREMB and SPAREKB of OM group STORE should be used to monitor the unallocated (spare) Core Memory.

Total Unallocated Memory (MB) = SPAREMB + SPAREKB/1024

Sample STORE OM STORE CLASS: HOLDING START:2004/10/26 13:00:00 TUE; STOP: 2004/10/26 13:30:00 TUE; SLOWSAMPLES: 18 ; FASTSAMPLES: 180 ; DSUSEDM DSUSEDK DSAVAILM DSAVAILK FREEMB FREEKB TOTALMB TOTALKB PSUSEDM PSUSEDK PSAVAILM PSAVAILK SPAREMB SPAREKB 0 794 846 36 996 46 531 955 753 114 400 9 559 256 0

NOTE: None of the STORE OM registers accumulate during Accumulation OM classes. (I.e. do not divide the registers by the number of transfer periods in an accumulation period).

. Register Description

DSUSEDM Data Store Used in MB. DSUSEDK Data Store Used in addition to DSUSEDMB in KB. DSAVAILM DS Available in MB. DSAVAILK DS Available in addition to DSAVAILM in KB. FREEMB FREEMB+FREEKB=DSAVAILM+DSAVAILK+PSAVAILM+PSAVAILK FREEKB FREEMB+FREEKB=DSAVAILM+DSAVAILK+PSAVAILM+PSAVAILK TOTALMB Total memory allocated in MB. DSUSEDM+PSUSEDM+FREEMB

22


NORTEL CONFIDENTIAL


TOTALKB Total memory allocated in KB. DSUSEDK+PSUSEDK+FREEKB PSUSEDM Program Store Used in MB. PSUSEDK Program Store Used in addition to PSUSEDM in KB. PSAVAILM PS Available in MB. PSAVAILK PS Available in addition to PSAVAILM in KB. SPAREMB Spare memory in MB. SPAREKB Spare memory in addition to SPAREMB in KB.

STORE Registers

3.3.2 STORE ALL USAGE

The STORE ALL USAGE command provides a real time view of memory usage.

The fields are comparable to the STORE OM registers:

TOTAL DS USED = DSUSEDM x 1024 + DSUSEDK

TOTAL DS AVAIL = DSAVAILM x 1024 + DSAVAILK

TOTAL PS USED = PSUSEDM x 1024 + PSUSEDK

TOTAL PS AVAIL = PSAVAILM x 1024 + PSAVAILK

TOTAL DS + TOTAL PS = TOTALMB x 1024 + TOTALKB

SPARE = SPAREMB x 1024 + SPAREKB

Sample STORE ALL USAGE output

Info based on inuse DS areas Storetype Used Free Total % Used DSTEMP_B 65010Kb 4237Kb 69247Kb 93% DSPROT_W 115743Kb 800Kb 116543Kb 99% DSPERM_B 569000Kb 1239Kb 570239Kb 99% DSSAVE_B 2031Kb 16Kb 2047Kb 99% DSFPROT_W 1503Kb 352Kb 1855Kb 81% DSFPERM_B 234Kb 21Kb 255Kb 91% DSPPERM_B 24Kb 39Kb 63Kb 38% DSSTACK_B 16920Kb 104Kb 17024Kb 99% DSSOS_B 4397Kb 402Kb 4799Kb 91% DSUNPROT_B 3650Kb 61Kb 3711Kb 98% DSSCRATCH 96Kb 31Kb 127Kb 75% DSSTOR_B 1961Kb 86Kb 2047Kb 95%

23


NORTEL CONFIDENTIAL

DSSTORPROT_W 22544Kb 47Kb 22591Kb 99% DSTEMP_W 744Kb 24Kb 768Kb 96% DSPROT_B 3234Kb 349Kb 3583Kb 90% DSPERM_W 1869Kb 50Kb 1919Kb 97% DSSOS_W 1598Kb 65Kb 1663Kb 96% DSUNPROT_W 2Kb 62Kb 64Kb 3% DSTEMP_M 13Kb 51Kb 64Kb 20% DSPERM_M 3419Kb 36Kb 3455Kb 98% DSSOS_M 84Kb 43Kb 127Kb 66% TOTAL DS 814107Kb 8115Kb 822222Kb 99% TOTAL BASED ON ALL DS AREAS TOTAL DS: USED = 814107Kb AVAIL = 37860Kb TOTAL = 851967Kb %USED = 96% Info based on inuse PS areas Storetype Used Free Total % Used PSPROT_W 117136Kb 1903Kb 119039 98% FIRMWARE_DLL 4160Kb 0Kb 4160Kb 100% TOTAL PS 121296Kb 1903Kb 123199Kb 95% TOTAL BASED ON ALL PS AREAS TOTAL PS: USED = 121296Kb AVAIL = 9775Kb TOTAL = 131071Kb %USED = 89% SPARE = 262144

24


NORTEL CONFIDENTIAL

3.3.3 Memory Alarms

There are two memory alarms that warn of memory exhaustion.

Alarms are raised when the sum of the SPARE and un-typed DS store is below a certain level. Un-typed DS store is equal to DS Available minus DS Free as displayed by the STORE ALL USAGE command.

Minor alarm is raised if

SPARE + un-typed DS < 48 MB Major alarm is raised if

SPARE + un-typed DS < 32 MB

Example:

Here is how the SPARE and un-type DS are derived from the previous section’s STORE ALL USAGE output:

SPARE = 262144 KB / 1024 = 256 MB

Un-typed DS = DS Available – DS Free = (37860 KB – 8115 KB) / 1024 = 29 MB

SPARE + un-typed DS = 256 + 61 = 317 MB (No memory alarm)

25


NORTEL CONFIDENTIAL

List of Acronyms

CallP Call Processing CPU Central Processing Unit CS 2000 Call Server 2000 CS 2000c Call Server 2000 Compact DS Data Store OM Operational Measurement PS Program Store STP Signaling Transfer Point

Documents

CS 2000 Compact Performance Monitoring-CVM12-SEB-08!00!018.v.12.0.3