Lazy Guide For Emergency Handling of APG40: Ericsson

ERICSSON LAZY GUIDE FOR EMERGENCY HANDLING OF APG40 1 / 75
Prepared Subject Resp. No

Daniel Figueiredo (SEPDAFI) SEP\SD\CSS
Doc Resp/Approved Checked Date Rev File/Referenced
2004-12-14 A Lazy_APG40.doc
Lazy Guide For Emergency Handling of APG40
APG40?
Now what!!
I. Introduction.........................................................................................2
II. Scope 2
III. First Actions and data collection.............................................3

Basic Node Status...............................................................................3
IV Recovery Actions............................................................................4
Collect data.........................................................................................4
FCH handling......................................................................................5
Hard Function Change........................................................................5
Soft Function Change.......................................................................11
V How to Put/Get a CP backup copy into/from APG40....12
Put a CP backup (SYBUP) into APG40 (RELFSW).........................12
Get a CP backup (SYBUP) from APG40 (RELFSW)........................13
Loading CP with IPN configuration, using FCCPL.............................14
Loading CP using CPT command PTCPL.........................................15
If we have contact with CP for separating IPN :................................15
If we don't have CP contact for separating an IPN............................16
VII How to work with Charging in APG40...............................18
Important concepts for charging with APG40....................................18
How the CDR’s travel from CP to AP................................................18
See an example of charging definition in the test plant.....................22
VIII How to work with STS in APG40.........................................28
Commands for statistics....................................................................28
STS not working ?............................................................................29
Example,how to configure a STS report for Object Type AAL2PATH30
IX How to do a backup / restore of APG40 software.........35

Backup of APG40..............................................................................35
Restore an APG40 in case of malfunction.........................................41
X APG40 Healthcheck: Primus Solution SCS123402:......42
XI How to SET time in APG40.......................................................45
XII K-disk full problem.....................................................................45
XIII C-disk full problem....................................................................46
The mml Command in APIO Appendix.....................................................47
Cluster Appendix................................................................................48
FHC Appendix......................................................................................52
APG40 commands vs. IOG20.....................................................................66
Useful Commands Appendix........................................................................69
I. Introduction
We have the lazy moose, the lazy dog, and lazy guides for almost everything,
why not a Lazy APG?
Special because this is a new product to all of us, and some of us did not have
yet the chance to work with it enough or at all, although we all have to eventually
start to handle emergency situations.
II. Scope
The purpose with this document is to have one document as a base of the
APG40 handling. This document is to be used as an help to our local engineers
when handling emergency situations. Although you must be careful when
fowling some of the suggested recovery actions, and if you are not sure if it is
applicable, or how to proceed, please contact the next level of support (I always
love this sentence, specially in OPI?s)
Note that you are supposed to know a little bit of APG40 when following this
document.
Keep this document as internal use only, do not send it to the customer at any
circumstances, since it is an non official document.
This document is based in Alex Library as well some other useful APG docs and
Primus Cases. Please let me know if you find out something that is not clear
enough, or that might need an update.
III. First Actions and data collection
The very first thing we should do when receiving an Emergency APG40 call is to
check the AP status and find out if they’re where any works in progress:
Take note of the APG status, this may be performed by phone, later on a cmd file
or a list of commands may be asked to the customer together with the log files.
Basic Node Status
Enter commands in both nodes:

hostname ( to be sure to which node are you connected A or B )
date /t
time /t
prcstate ( Active, passive or undefined , ideal one active other passive )
Cluster Group (Cluster group: Status shall be Online)
Cluster Res
Alist (AP alarm list )
If SW is R9.1
fchstart –V
If SW R10
fchstate
From the active node only:

Check cp connection available:
Mml
If so , check :
ALLIP;
APAMP; Reason: To check status of the LAN's towards the AP directory service.
Expected result: The STATUS shall be: one ACTIVE and one PASSIVE! Link
towards each node.
OCINP:IPN=ALL; This command orders a printout of data and state for an Inter-
Platform Network (IPN). Both IPN should be WO.
Exit (back to AP mode)
If not, exit back to AP
"C:\Program Files\Dptmgr\Raidutil" -L all

Reason: Check the RAID disk and firmware status.
Expected result: On an active node all disks should be Optimal and
FW version FT06 or newer. Ignore status 'Drive Failed' on RAID volumes on the
passive or undefined nodes.
Now at this stage, together with the customer explanation you should be able to
identify the severity of the case as well an idea of might be need to recover the
problem.
So before you start to do anything you should always request the customer to
make an mktr log on both nodes .
Just enter the command : mktr YYMMDD-HHMM
IV Recovery Actions
Collect data
If you will escalate this problem the best will be if you collect data before.
Send the following CMD file to the customer and ask him to open a new log file
and run it on both nodes.
collectdata.cmd
!APG_collectdata_CMD
hostname
date /t
time /t
set
prcstate
swrprint
swrsid -h
pstat
alist
ipconfig /all
type d:\burinfo.txt
netdom query
netdom bdc
net start
cluster node
cluster group
cluster res
!if R9.1
fchstart –V
! if R10
fchstate
! only in the active node
mml allip:alcat=apz
mml apamp
dsdls -a
mml octdp
cpdlist -l
cpfls
afpls
cdhls
cdhdsls
"C:\Program Files\Dptmgr\Raidutil" -L all
dir /s k:\images
net share
!CLose the logfile
FCH handling
Hard Function Change
As a first action in these situations, you must figure out which kind of fallback you
need, one node restore or both node restore? or just a fallback with command
fchfb.
Note : The command fchstart -V (or fchstate if R10) will print the current status
of the FCH session and information on what steps must be performed.
The printout will guide the user how to proceed. The printout has several
sections. The first line is the status of the node and the FCH session.
After the first line may follow one or two lines describing for how long time this
state has been in effect and how long time it may take before the operation is
completed.
After these lines follows several lines describing what actions are going on.
Finally, one or several lines describing the status of the cluster server, the
ACS_FCH_Server and the connection to the other node.
1)
-The alarm AP FUNCTION CHANGE FAILED is issued if the function change

failed. Before enter the command fchcommit ?,go to step 3 ).
Note 1 if this is an MEC which as two FCH, maybe a first one to remove a
module and no backup was performed meanwhile; go to the next option also.
Since even if you fallback you will end up with different SW between the two
nodes.
- The alarm AP FUNCTION CHANGE FAILED is issued if the function change

failed. After enter the command fchcommit ? go to step 8)
Two nodes restore is needed.
3) Was LBB upgraded?

This is true if the options -L, -c or -x were used. However, if the actions
performed during the LBB upgrade or the commands executed in the -c or -x
options, did not harm the system, you can force a fallback using option -u in the
command fchfb.
Yes –step 4 (LBB so we go to one node restore)

No –step 7 (no LBB, proceed with fchfb command)
4) One node restore.

Verify which node to restore.
The node to be restored is the node on which the fchstart command was
executed. You must be logged on to the other node, that is the node that is not to
be restored.
Perform FCH restore.
Use command : fchrst
You are about to do a single node restore
of the system disk on node AP1A.
Is the other node backed up and ready??
Are you sure?
Enter y or n [default= y]<dialoguePrompt> y
The system is now prepared for restore.

Please follow the BUR OPI to restore the other node.
On the other Node :
burrestore
Data about the image file from the backup partition will be shown (image name,
date, node and status). Confirm this as a valid backup. y
As the system restore forces a swap of the disk partitions C and D the
system running on C will be stored as an image on D.
Enter an image name at dialog:
Enter a description for the currently running system.

Image name: <nodename>_corrupt
The node will reboot, wait 5 minutes then logon to the restored node.
After executing the burrestore command, the cluster configuration may still be
corrupt. But that will be corrected when executing fchend. If the cluster
configuration is not properly restored by fchend, see FCH Appendix Information
Section 3.2.
Was the FCH restore successful ?
The restored node comes back online and joins the cluster. Use command
cluster node /stat to verify the node comes back online and joins the cluster.
Note: The restore operation will take 5-10 minutes to finish.
Yes Go to step 6 .
No, an error message was received from the command fchrst.

One node restore not possible. Go to “A complete two node restore of the
system must be performed” step 8.
No, the node did not come back after the reboot. No contact.
Note in this case, try to reboot the restored node.
Send the command fcc_reset other from the active node.
No, the node did come back but did not join the cluster. Undefined state.
Go to step 5 then to the next one step 6.
5) From passive node
enter net start clussvc / to see whether it succeeds or fails
if fails go with the solution SCS346435, otherwise , if o.k. go to step 6)

1.- passive node --> C:\>net start netlogon
2a.- If Net Logon service starts, then go to step 1 of this particular instruction.
2b.- If Net Logon service does not start, then continue with step 3
3.- passive Node --> C:\>netdom BDC /RESET
4.- passive Node --> C:\net accounts /sync
4.1 passive Node (added) --> setupservices

5.- active node --> C:\nbtstat -RR
6.- passive node --> C:\>prcboot
> From SCS346435: Chek group permissions as well.

> In case of the situation challenges, we may implement the SCS262728.
6) End a Failed Function Change
End failed function change session.

Use command : fchend
fchend must be executed on the passive node. Use fchstate to determine which
node is passive.
Then check node status, back to normal operation.
7) fchfb
No Lbb SW was loaded, initiate a Function Change (FCH) Fallback.
It can be executed in all FCH states up to and including Supervision state (that is,
after a successful execution of the fchstart command and the following reboot,
but before executing the fchcommit command).
On the upgraded node, send command:
fchfb
Note: This command will return the system to the configuration that existed
before the function change was initiated.
Note: At the end of this command the system will be rebooted. The operator
must wait for the node to come back on-line and connect to it again before
continuing.
Was the command successful?
Note: Use the command fchstart -V. Possible format of printouts from fchstart -V
is described in FCH apendix. The state End indicates a successful fallback.
Note: Please note that it may take some minutes for the fchfb to complete after
the system has come back on-line after the reboot.
Yes
Go to Step 6). End FCH
No
Go to Step 4). One Node Restore
8) Two nodes restore is needed

1. Logon to the B-node.
Note: It doesn't matter if the B-node is active or passive.
The system restore has to be initiated from the B-node.
2 Restore the system from the C:\>burrestore -stay

backup partition.
3 Data about the image file from the

backup partition will be shown
(image name, date, node and status).
Confirm this as a valid backup. y
4 As the system restore forces a swap

of the disk partitions C and D the
system running on C will be stored
as an image on D.
Enter an image name at dialog: Enter a description for the currently
running system.
5 Stop one cluster ressource.
C:\>cluster res ACS_PRC_ClusterControl_1 /offline /wait
6 Shutdown the B-node. C:\>prcboot -s

Note: The telnet session will time out.
Either wait or open another shell.
7 Logon to the A node.
8 Restore the system from the C:\>burrestore

backup partition.
9 Data about the image file from the

ERICSSON LAZY GUIDE FOR EMERGENCY HANDLING OF APG40 10 /
75
backup partition will be shown

(image name, date, node and status).
Confirm this as a valid backup. y
10 As the system restore forces a swap

of the disk partitions C and D the
system running on C will be stored
as an image on D.
Enter an image name at dialog: Enter a description for the currently
running system.
Note:
The AP will reboot and start up again.
During the reboot time, the APG will
be unavailable and will be unable
to offer any service.
11 Logon to the restored node.
12 Check that the cluster service C:\>net start

is started.
Note: If the cluster service has not

started automatically start it
by command. C:\>net start clussvc
13 Check that all cluster resources C:\>cluster res

owned by the node are online.
14 Check that the FC is in state C:\>fchstart -V

noFCH.
15 Restart the other node. C:\>fcc_reset other
16 Check that the cluster service C:\>net start

is started.
Note:
If the cluster service has not
started automatically start it
75
by command. C:\>net start clussvc
17 Check that all cluster resources C:\>cluster res

are online.
18 Go to chapter
"Backup of the AP system"
to backup the running system
to the D partition.
Note:
The currently running system
should be on CM124_R1A level. So
do not use exact the system names
from chapter
"Backup of the AP system".
19 Go to "Return to normal operation"
Soft Function Change
The fallback should be performed by command, or automatically, but if

something goes wrong, it may be the case bellow:
The soft function change has failed due to an error and sfcexec has
initiated fallback. Due to a second error the sfcexec has failed to restore the old
parameters (failed fallback).
As a result the active node has got the new CXC parameters (sfcexec
has failed to restore the old values), while the passive node has got the old
parameters.
The fault is that the OPIs indicate that 'The job is completed', and the system is
left in an inconsistent state (different CXC parameters in the two nodes).
So as first measure this OPI's will be updated.
What you should do in this situation is restore the node which got the new
CXC parameters, for this go to one node restore step 4) of FCH handling.
Note if this node is active one, you should reboot it, and force a fail over.
75
V How to Put/Get a CP backup copy into/from APG40
Put a CP backup (SYBUP) into APG40 (RELFSW)
LCT --> APG Directory of L:\FMS\data\tmp --> CP File System (RELFSW)
Note 1. LCT is your computer, called Local Craft Terminal

in the Alex documentation.
You must have the backup subfiles R0...R5 stored
in your LCT.
1.- Check the size of the subfiles (R0...R5) you want to

transfer from your computer.
2.- Open a channel with WIOL 6.0 towards the cluster IP-addr
of the APG, using administrator rights.
3.- Check you have enough free space in the L: partition

of your APG for storing temporarily the subfiles R0..R5:
C:\>L:
L:>\cd FMS
L:\cd data
L:\ cd tmp
L:\>dir
4.- Create a directory on L:\fms\data\tmp\ in the APG for storing

the backup:
Directory of L:\FMS\data\tmp
L:\FMS\data\tmp mkdir \CPbackup
75
5.- Send the CP backup subfiles from LCT to APG40 system partition
L:\FMS\data\tmp\CPbackup, using ftp.
For the ftp transfer, you can use WS_ftp or Microsoft Internet
Explorer . Use binary transfer option. Close ftp session after the transfer.
6.- Create a RELFSW file for storing the backup in the CP

File System (CPF). You don't need to do this step if you
are going to use an already created RELFSW file.
C:\>cpfmkfile -l 2048 -c RELFSW15 RELVOLUMSW
7.- Check the file has been created

C:\>cpfls -ls RELFSW15
8.- Import the subfiles from APG system partition to

CP file system inside APG.
(APG L:\FMS\data\tmp:\CPbackup --> CPF )
C:\>cpfport -i -m over L:\FMS\data\tmp\CPbackup RELFSW15
9.- Check from CP that the RELFSW15 has the backup:

C:\>mml
<SYBFP:FILE=RELFSW15;
<exit;
10.- DON'T FORGET TO CLEAR L:\FMS\data\tmp\CPbackup in the APG!

the CP backup was stored there only temporarily.
L:\FMS\data\tmp\CPbackup>del *.*
L:\FMS\data\tmp>rmdir CPBackup
L:\FMS\data\tmp> exit
Get a CP backup (SYBUP) from APG40 (RELFSW)
CP File System (RELFSW) --> APG L:\FMS\data\tmp\CPbackup --> LCT
1.- Check from CP, what RELFSW file you want.

C:\>mml
<SYBFP:FILE;
<exit;
75
2.- Check you have enough free space in the L:\ partition
of your APG for exporting temporarily the subfiles R0..R5:
C:\>L:
L:\FMS\data\tmp >dir
3.- Create a directory on L:\ in the APG for storing

the backup:
L:\FMS\data\tmp> mkdir k:\public\CPbackup
4.- Export the requiered RELFSW file from

CPF --> APG L:\FMS\data\tmp\CPbackup
C:\>cpfport -e -m over RELFSW15 L:\FMS\data\tmp\CPbackup
5.- Open a FTP session with APG40.

Tranfer the backup from APG L:\FMS\data\tmp\CPbackup to your LCT,
using binary transfer option. Close ftp session after the transfer.
6.- DON'T FORGET TO CLEAR L:\FMS\data\tmp\CPbackup in the APG!

The CP backup was stored there only temporarily.
L:\FMS\data\tmp\CPbackup>del *.*
L:\FMS\data\tmp >rmdir CPBackup
L:\FMS\data\tmp >exit
VI How to reload CP with APG40/IPN
Loading CP with IPN configuration, using FCCPL
Connect to CP EX-side:
C:\>mml
Separate IPN-1:
<OCISI:IPN=1;
Separate CP SB-side:
<FCSEI;
Load new dump in SB-side:

<FCCPL:FILE=RELFSWx;
75
Connect to CP SB-side:
<exit;
C:\>mml -s
Set clock and start application block:

<CACLS:DATE=YYMMDD,TIME=HHMM,DAY=day;
<SYATI;
<exit;
C:\>mml
Switch in the new system:

<FCSWI:CTYPE=NOTR;
Bring the CP in parallel:

<DPPAI;
Loading CP using CPT command PTCPL
If we have contact with CP for separating IPN :
C:\>mml
Separate IPN-1:
<OCISI:IPN=1;
<DPSES;
Connect to CPT:
<PTCOI;

cpt< PTCPL:FILE=RELFSWx,CS=B,IPN=1;
Release terminal pressing Ctrl-D in TTY mode

to see the loading progress
cpt< Ctlr-D
75
CPT MESSAGE INITIAL LOADING (ABSOLUTE) STARTED

END
CPT MESSAGE INITIAL LOADING (ABSOLUTE) IN PROGRESS
END
….
CPT MESSAGE INITIAL LOADING (ABSOLUTE) FINISHED
END
End CPT:
cpt< PTCOE;
<exit;
C:\>mml -s

<SYATI;
Connect to CPT:
<PTCOI;

cpt< PTSWI;
End CPT:
cpt< PTCOE;
<exit;
C:\>mml

<DPPAI;
If we don't have CP contact for separating an IPN
C:\>mml -s
75
Connect to CPT:
<PTCOI;
Check that CP-B is SB:

cpt< PTWSP;
cpt< PTSES;
End CPT:
cpt< PTCOE;
<exit;
Separate IPN-1:
C:\>ipnaadm -state sep -ipnano 1
C:\>mml -s
Connect to CPT:
<PTCOI;

cpt< PTCPL:FILE=RELFSWx,CS=B,IPN=1;
End CPT:
cpt< PTCOE;
<exit;
C:\>mml -s

<SYATI;
Connect to CPT:
<PTCOI;

cpt< PTSWI;
75
End CPT:
cpt< PTCOE;
<exit;
C:\>mml

<DPPAI;
VII How to work with Charging in APG40
Important concepts for charging with APG40
Firstable, two important concepts in charging with APG40:
File-Based Protocol: is a communication protocol that uses files as logical unit of

transfer. Call Records are buffered in files before being transferred
to the Operation System (OS=BGW).
File-Based can be "initiating" if the APG starts the FTP session to the BGW to
send the charging,or "responding" if the BGW starts FTP to get the files.
(TTFILE on IOG20 is like a file-based method).
Block-Based Protocol:is a communication protocol that allows the earliest

possible transfer of Call Records to the BGW after the end of a call. (Hot Billing).
Block-Based is always "initiating", APG uses the Remote Procedure Call (RPC)
to invoke the remote BGW.
How the CDR’s travel from CP to AP
!charging scheme!
!---------------!
CP(FOAM) APG OS
/----!----\ /---\ /--\
CDR's-->CHOP-->MTAP ----> RDT ------>BGW
75
The CDR's follow these steps before arriving to BGW:
Note. this example is valid for File-Based Protocol "initiating" or "responding",

For Block-Based is valid until the CRB is released, after that the CRB is sent
from APG to BGW inmediately without storing in a file.
1) A call is finished and some CDR's are generated according to the charging
case data (i.e. CHASP:CC=7).
2) The CDR's of the call arrives to CHOP

SAAEP:SAE=500,BLOCK=CHOP; !NIU reflects how many CDR's!
3) The CDR's are not sent to APG until the buffer is full or the time limit for
releasing the buffer has expired.
In the example below, if you make a single call that generates 2 CDR's,for sure
these CDR's don't fill the 4Kb buffer, so they will have to wait OUTP=00100 = 1
minute until these 2 CDR's are sent to the APG(RDT).
<CHOPP;
COMMON CHARGING OUTPUT ADJUNCT PROCESSOR INTERFACE DATA
STATUS BSIZE OUTP

OPEN 4 00100--->format mmmss (m=minutes s=seconds)
END !-->Buffer size, from 1Kb to 32Kb, normally 4Kb.
If the buffer becomes full before 1 minute, the system sends the contents of the
buffer to the APG40 inmediately.
4) When the CDR's arrives to APG, they are stored in a Call Record Block,
(CRB, is like a group of CDR's). This CRB has a size and a time limit, and the
same behaviour as the buffer in CHOP.
The size and time limit can be found printing the charging parameters in APG:
C:\rdtview -f
In the example below CRB length is 16384 bytes (see BlockingLength) and the
time limit is 300sg (see BlockingHoldTime). If the CRB is full before 300sg, the
75
CRB will be released, if the CRB is incomplete, the CDR's will have to wait in the
CRB 300sg (5minutes) before the block will be released.
========================================
RDT Output Stream Table
========================================
RDT_OutputStream BlockingLength: 16384 (range 512--32768 bytes)
RDT_OutputStream BlockingMaxCallRecordsPerBlock: 0 (max. num of CDR's
per CRB)
RDT_OutputStream BlockingLengthType: VARIABLE
RDT_OutputStream BlockingHoldTime: 300 (range 1--7200 seconds)
RDT_OutputStream BlockingPaddingCharacter: 32
RDT_OutputStream FilingFileSize: 16384 (range 10-16384 Kilobytes)
RDT_OutputStream FilingFileHoldTime: 300 (range 1--86400 seconds)
RDT_OutputStream FilingFileGroupID: OHSLOCALUSRG
In case of Block-Based protocol, as soon as the CRB is released, it is sent to the

BGW, in case of File-Based continue with the next step.
5) The CRB's released are put together in a file, once more, this file will have a
size and a time limit, in the above parameters we can see a file size of 16384
Kb, (see FilingFileSize) and a time limit of 300sg (see FilingFileHoldTime). This
time, is going to be complicated to fill a file with this size limit, so, after 5 minutes
(time limit) a file will appear with the CDR's received until that moment.
6) When the charging files are released, they are stored in the disk partition
Y:\RDT\data\FileBasedDest1\Ready, for File Based initiating method, and in
Y:\RDT\data\RespFile1\Ready, for File Based responding method.
7) In case you are in a test plant, and there's no BGW, if you need to get the
charging files for decoding, you can do the following:
a) Connect to active node in order to copy the charging files to the ftp area
Open a telnet session with the active node, with administrator rights.
C:\>rem check we are connected to active node
C:\>prcstate
active
75
C:\>rem check charging files for 2002-10-16

note. the charging files are released to the initiating and responding ready
directories, with their respective name according to parameter tables.
C:\>dir y:\rdt\data\filebaseddest1\ready\initfile.20021016*
Volume in drive Y is Disk Y:
Volume Serial Number is 9884-7F2B
Directory of y:\rdt\data\filebaseddest1\ready
10/16/02 12:21p 583 Initfile.200210161222044

10/16/02 12:33p 296 Initfile.200210161238045
10/16/02 12:40p 296 Initfile.200210161245046
10/16/02 12:56p 296 Initfile.200210161301047
10/16/02 04:40p 574 Initfile.200210161641330
10/16/02 06:04p 861 Initfile.200210161806300
6 File(s) 2,906 bytes
18,233,614,336 bytes free
C:\>dir y:\rdt\data\respfile1\ready\respfile.20021016*
Volume in drive Y is Disk Y:
Volume Serial Number is 9884-7F2B
Directory of y:\rdt\data\respfile1\ready
10/16/02 12:21p 583 Respfile.200210161222044

10/16/02 12:33p 296 Respfile.200210161238045
10/16/02 12:40p 296 Respfile.200210161245046
10/16/02 12:56p 296 Respfile.200210161301047
10/16/02 04:40p 574 Respfile.200210161641330
10/16/02 06:04p 861 Respfile.200210161806300
18,233,614,336 bytes free
C:\>rem copy them into ftproot directory
C:\>copy y:\rdt\data\respfile1\ready\respfile.20021016* C:\inetsrv\ftproot

y:\rdt\data\respfile1\ready\Respfile.200210161222044
75
6 file(s) copied.
b) Now, open a ftp session, as we saw in chapter 2, from your computer in order
to get the files.
8)How the CDR's travel from AP to BGW is another story, out of the scope of
this document.
See an example of charging definition in the test plant
!charging commands in GSM R9.1/UMTS CN2.0!

!-----------------------------------------
!CHOC 6PAB/CAAZ 107 7430/MLEAA R1A02
COMMANDS:
!IOG INTERFACE COMMANDS

CHOFI FILE OPEN, INITIATE
CHOFE FILE OPEN, END
CHOBI FILE BLOCK, INITIATE
CHOBE FILE BLOCK, END
CHOFP FILE STATUS, PRINT
CHOTC FILE ATTRIBUTES, CHANGE
CHOTP FILE ATTRIBUTES, PRINT
CHOUC USER FUNCTION PARAMETERS, CHANGE
CHOUP USER FUNCTION PARAMETERS, PRINT
!AP INTERFACE COMMANDS

CHOPI ADJUNCT PROCESSOR INTERFACE, INITIATE
CHOPE ADJUNCT PROCESSOR INTERFACE, END
CHOPP ADJUNCT PROCESSOR INTERFACE, PRINT
CHOEC ADJUNCT PROCESSOR INTERFACE PARAMETERS, CHANGE
!COMMON COMMANDS FOR AP AND IOG INTERFACES

CHOIC INTERFACE, CHANGE
CHOIP INTERFACE, PRINT
75
CHOLC LIMIT, CHANGE

CHOLP LIMIT, PRINT
CHODP CHARGEABLE DURATION DATA, PRINT
--------------------------------------------------------------------------
!CHOP 6PDA/CAAZ 107 6645/MLEBM R3A04
THE BLOCK CHARGING OUTPUT TO ADJUNCT PROCESSOR (CHOP)

IS PART OF THE FORMATTING AND OUTPUT AM IN APT.
CHOP RECEIVES OUTPUT REQUEST FROM BLOCK RMP, COLLECTS

THE CHARGING DATA, BUILDS UP CALL DATA RECORDS AND SENDS
THEM TO ADJUNCT PROCESSOR (AP) VIA BLOCK MTAP IN ASN.1
FORMAT.
-------------------------------------------------------------------------
CHOLP;
COMMON CHARGING OUTPUT LIMIT DATA
LIMIT
BANS
END
CHOIP;
COMMON CHARGING OUTPUT INTERFACE DATA
INTERF
IOG
END
CHODP;
COMMON CHARGING OUTPUT CHARGEABLE DURATION DATA
FN CDN RSN
AP 0000000000 00000000
TT 0000000322 00000057
ICI 0000000000 00000000
END
!Following actions are according to OPI

!Common Charging Output, Charging Data Interface from IOG
!to Adjunct Processor, Change 2/154 31-CNT 215 1663 Uen A
!Activation of charging output to APG;

-------------------------------------
!check interface to AP is closed

75
CHOPP;
STATUS BSIZE OUTP

CLOSED 4 OUTPOFF
END
!OUTP=OUTPOFF means that The sending of buffer is initiated only

!when the buffer is full (4 Kb buffer)
!if not close

CHOPE;
!in case Data Message Handler output, is not required,

!change with DBTSC the parameter;
SYPAC:ACCESS=ENABLED,PSW=PSW2PAR;
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=AMCFOAMC,NAME=DMHSUPPORTED,
VALUE=0;
DBTRE:COM;
SYPAC:ACCESS=DISABLED;
<DBTSP:TAB=AXEPARBLOCKRELS,NAME=DMHSUPPORTED;
DATABASE TABLE
BLOCK TAB TABLE WRAPPED

PARTAB2 AXEPARBLOCKRELS YES
BN PARID RELID REL NAME SETNAME

28 567 614 OWNS DMHSUPPORTED AMCFOAMC
LPARPTR
0
END
<LASLP:BN=28;
STORAGE LAYOUT
BLOCK BN BS TYPEEXT TYPE PSA PSV PCV

CHOP H'01C ACTIVE H'2800 H'8000 H'01A3E0A0 19928 19414
SAAEP:SAE=500,BLOCK=CHOP;
SAAII:SAE=500,BLOCK=CHOP,NI=2000;
75
!Change the The maximum duration of time for charging data

!to reside in a buffer expressed as mmmss.
CHOEC:OUTP=00100;
EXECUTED
CHOPP;
STATUS BSIZE OUTP

CLOSED 4 00100
END
!Open the interface, with current buffer size BSIZE=4 Kb
CHOPI:BSIZE=4;
EXECUTED
CHOPP;
STATUS BSIZE OUTP

OPEN 4 00100
END
!Change Active Call Data Output Interface to AP

CHOIP;
CHOIC:INTERF=AP;
CHOIP;
COMMON CHARGING OUTPUT INTERFACE DATA
INTERF
AP
END
!Verify output format is ASN1
<CHOUP:fn=tt;
COMMON CHARGING OUTPUT USER FUNCTION DATA
FN PRIORITY NUMIND PBC CONV

75
TT HIGH 0-30 ASN1

END
!Check SAE 500 for CHOP are working;

SAAEP:SAE=500,BLOCK=CHOP;
!Check charging parameters in APG;
Y:\RDT\data\FileBasedDest1\Ready>rdtview -f
========================================
OHS Initiating Rpc Output Handler Table
========================================
OHS_InitiatingRpcOutputHandler BlockBasedDest1 DestinationID: BlockBasedDest1
OHS_InitiatingRpcOutputHandler BlockBasedDest1 DestinationHostName: 159.107.9.120
OHS_InitiatingRpcOutputHandler BlockBasedDest1 RPCProgramNumber: 300625
OHS_InitiatingRpcOutputHandler BlockBasedDest1 DataVersion: 2
OHS_InitiatingRpcOutputHandler BlockBasedDest1 RetryInterval: 1
OHS_InitiatingRpcOutputHandler BlockBasedDest1 LinkDownTimeOut: 300
OHS_InitiatingRpcOutputHandler BlockBasedDest1 RPCBackupEnabled: NO
OHS_InitiatingRpcOutputHandler BlockBasedDest1 RPCBackupDestinationHostName: -
OHS_InitiatingRpcOutputHandler BlockBasedDest1 RPCBackupRPCProgramNumber:
591751040
OHS_InitiatingRpcOutputHandler BlockBasedDest1 RPCBackupDataVersion: 2
OHS_InitiatingRpcOutputHandler BlockBasedDest1 RPCBackupRetryInterval: 10
OHS_InitiatingRpcOutputHandler BlockBasedDest1 RPCBackupLinkDownTimeOut: 300
OHS_InitiatingRpcOutputHandler BlockBasedDest1 FileBackupEnabled: NO
OHS_InitiatingRpcOutputHandler BlockBasedDest1 FileBackupDirectoryName:
Y:\RDT\BlockBasedDest1
OHS_InitiatingRpcOutputHandler BlockBasedDest1 FileBackupFillingSize: 1024
OHS_InitiatingRpcOutputHandler BlockBasedDest1 FileBackupFillingFileHoldTime: 300
OHS_InitiatingRpcOutputHandler BlockBasedDest1 FileBackupFillingFileGroupID:
OHSLOCALUSRG
OHS_InitiatingRpcOutputHandler BlockBasedDest1 FileBackupAllocationLimit: 2097152
OHS_InitiatingRpcOutputHandler BlockBasedDest1 FileBackupWarningLimit: 80
OHS_InitiatingRpcOutputHandler BlockBasedDest1 FileBackupNameTemplate:
BackupRespFile.<yyyy><mm><dd><HH><MM><SS><n>
OHS_InitiatingRpcOutputHandler BlockBasedDest1 FileBackupKeepTime: 24
OHS_InitiatingRpcOutputHandler BlockBasedDest1 FileBackupStartupSequenceNumber: 0
========================================
OHS Initiating Ftp Output Handler Table
========================================
OHS_InitiatingFtpOutputHandler FileBasedDest1 DestinationID: FileBasedDest1
OHS_InitiatingFtpOutputHandler FileBasedDest1 DestinationHostName: 159.107.9.120
OHS_InitiatingFtpOutputHandler FileBasedDest1 UserName: reeguest
OHS_InitiatingFtpOutputHandler FileBasedDest1 Password: reeguest
OHS_InitiatingFtpOutputHandler FileBasedDest1 RetryInterval: 5
OHS_InitiatingFtpOutputHandler FileBasedDest1 DestinationHostPort: 21
75
OHS_InitiatingFtpOutputHandler FileBasedDest1 SecureDestinationHost: NO

OHS_InitiatingFtpOutputHandler FileBasedDest1 BackupEnabled: NO
OHS_InitiatingFtpOutputHandler FileBasedDest1 BackupDestinationHostName: -
OHS_InitiatingFtpOutputHandler FileBasedDest1 BackupUserName: -
OHS_InitiatingFtpOutputHandler FileBasedDest1 BackupPassword: -
OHS_InitiatingFtpOutputHandler FileBasedDest1 BackupRetryInterval: 1
OHS_InitiatingFtpOutputHandler FileBasedDest1 BackupDestinationHostPort: 1
OHS_InitiatingFtpOutputHandler FileBasedDest1 BackupSecureDestinationHost: NO
========================================
RDT File Based Destination Table
========================================
RDT_FileBasedDestination RespFile1 DestinationID: RespFile1
RDT_FileBasedDestination RespFile1 AllocationLimit: 2097152
RDT_FileBasedDestination RespFile1 WarningLimit: 80
RDT_FileBasedDestination RespFile1 NameTemplate:
Respfile.<yyyy><mm><dd><HH><MM><SS><n>
RDT_FileBasedDestination RespFile1 KeepTime: 24
RDT_FileBasedDestination RespFile1 StartupSequenceNumber: 0
RDT_FileBasedDestination FileBasedDest1 DestinationID: FileBasedDest1

RDT_FileBasedDestination FileBasedDest1 AllocationLimit: 2097152
RDT_FileBasedDestination FileBasedDest1 WarningLimit: 80
RDT_FileBasedDestination FileBasedDest1 NameTemplate:
Initfile.<yyyy><mm><dd><HH><MM><SS><n>
RDT_FileBasedDestination FileBasedDest1 KeepTime: 24
RDT_FileBasedDestination FileBasedDest1 StartupSequenceNumber: 0
========================================
OHS File Based Output Handler Table
========================================
OHS_FileBasedOutputHandler RespFile1 DestinationID: RespFile1
OHS_FileBasedOutputHandler RespFile1 DirectoryName:
OHS_FileBasedOutputHandler FileBasedDest1 DestinationID: FileBasedDest1

OHS_FileBasedOutputHandler FileBasedDest1 DirectoryName:
========================================
RDT Block Based Destination Table
========================================
RDT_BlockBasedDestination BlockBasedDest1 DestinationID: BlockBasedDest1
RDT_BlockBasedDestination BlockBasedDest1 AllocationLimit: 2097152
RDT_BlockBasedDestination BlockBasedDest1 WarningLimit: 80
========================================
RDT General Table
========================================
RDT_General DataLoggerWarningLimit: 80
RDT_General DataLoggerAllocationLimit: 2048
RDT_General VolumeManagerWarningLimit: 80
75
========================================
RDT Output Stream Table
========================================
RDT_OutputStream BlockingLength: 16384
RDT_OutputStream BlockingMaxCallRecordsPerBlock: 0
RDT_OutputStream BlockingLengthType: VARIABLE
RDT_OutputStream BlockingHoldTime: 300
RDT_OutputStream BlockingPaddingCharacter: 32
RDT_OutputStream FilingFileSize: 16384
RDT_OutputStream FilingFileHoldTime: 300
RDT_OutputStream FilingFileGroupID: OHSLOCALUSRG
========================================
RDT Statistics Table
========================================
RDT_Statistics GenerationTime: 00:00
RDT_Statistics ResetFlag: NO
Useful info
-----------
The RDT application, when is started, creates authomatically the following
directories:
TmpReady: The RDT application uses this directory internally.

When all destinations have a link in their TmpReady directory to the
same CRB file, the link is moved to the Ready directory.
Ready: This directory contains CRB files that are ready to be sent to the OHS.
When such a file will be sent, the file is moved to the Send directory.
When such a file will be archived, the file is moved to the Archive directory.
Send: This directory contains the CRB file that is being sent to the destination.
When this file is successfully transferred, the file is moved to the Delete directory.
When this file is going to be archived, the file is moved to the Archive directory.
Delete: This directory contains CRB files that were sent or archived and can
therefore be removed from the AP (as far as this destination is concerned).
For each file, the file will be removed after a certain amount of minutes.
This value is configurable using the parameter KeepTime in the
RDT_FileBasedDestinationTable (Check the Application Information of RDT).
Archive: This directory contains CRB files that are being archived.
When such a file is archived, the file is moved to the Delete directory,
unless it was stated that the file must be archived twice.
75
Keep: This directory contains CRB files coming from the Delete directory.
Each file will be physically removed after a configurable amount of hours using
the parameter KeepTime in the RDT_FileBasedDestinationTable (Check the
Application Information of RDT).
VIII How to work with STS in APG40
Commands for statistics
!List configuration for given Object Types in long format

!stmotls -l AAL2PATH!
!List configuration for all Object Types

!stmotls -l
!List configuration changes for given Object Types in the

!correction area
!stmotls -c AAL2PATH
!List configuration changes for all Object Types

!stmotls -c
!Print a list of the Object Types only.

!stmotls
C:\>stmotls
RECORDING AREA
ON OPER
OBJTYPE INCL BRP NCNT AVAILABLE PRIORITY

AAL2PATH NO 15 9 LOW
ACCESSROUT NO 15 14 LOW
ALLSERV NO 15 27 LOW
.
.
END
!Retaining time
stmdbrt -p
75
STS not working ?
One know fault : If the stmotls list is full and state is cancelled!
The sts process needs to be restarted.In some cases when the STSCBIN is in a
faulty revision.
stmotls
stmfols
stmmp -L -l
stmrp -L -l
cdhls –l dest………
afpls –a transq… destset…. ! –1 on retries is equal to infintive!
cdhdsls -l
afpls –ls dest………
vdls -n "Default FTP Site"

Directory Structure of STS collection and transferto Virtual directory.
The STS is collected in the S drive and transferred using AES to the virtual
directory in the K drive.

cd /d S:\STS\data\DeliveryDir && DIR
cd /d S:\STS\data\DeliveryBuffDir && DIR
Check if something is written in S drive

cd /d K:\aes\data\cdh\ftp && for /d %I in (*) do dir %I\Ready /b/s/ad
To check the K drive
Restart STS prcoess
!#stop STS collection !

stmcc -e
!#stop STS processes (all three will stop)!

cluster res sts_main /off /wait
!#check all three STS processes are offline!

cluster res
75
!#start STS processes (all three will start)!

cluster res sts_prov /on /wait

!REM Initiate/End STS collection!
stmcc -i
stmcc -e
Example,how to configure a STS report for Object Type AAL2PATH
1.- Print the present data for AAL2PATH
C:\>stmotls -c
Error: No correction area
C:\>stmotls -l AAL2PATH
RECORDING AREA
ON OPER

AAL2PATH NO 15 9 LOW
CNTNAME CNTTYPE CNTDES

NCONN PC NO CONN ATTEMPTS ON PATH
NSUCC PC NO EST BEARER CONN ON AAL2PATH
NFAILCGCID PC NO LOST CONN DUE TO CIDS CONG
NFAILCGBW PC NO LOST CONN DUE TO BDWDTH CONG
NFAILCGGS PC NO LOST CONN DUE TO GS CONG
NFAILCGCH PC NO LOST CONN DUE TO AAL2 CONG
TRAL ST NO ACTIVE CONN ON PATH
NTRALACC PC ACCUMULATED ACTIVE CONN ON PATH
NSCAN PC NUMBER OF ACCUMULATIONS
END
2.- Initiate a correction area for configurating STS data.

No result printout means that command was OK:
C:\>stmotd -i
3.- Activate counter collection for Object Type AAL2PATH

C:\>stmotd -a AAL2PATH
C:\>stmotd -a ALLSERV
75
4.- Check that correction area shows that AAL2PATH is included

in the collection of statistical counters (parameter INCL=YES)
C:\>stmotls -c
RECORDING AREA
ON CORR

AAL2PATH YES 15 9 LOW
END
5.- End job in the correction area.

C:\>stmotd -e
6.- Update Operating area with the changes introduced in the

correction area.
C:\>stmttu
7.- Initiate the collection of statistical counters:

C:\>stmcc -i
8.- Check STS data for AAL2PATH in long format
C:\>stmotls -l AAL2PATH
RECORDING AREA
ON OPER

AAL2PATH YES 15 9 NO LOW
CNTNAME CNTTYPE CNTDES

NCONN PC NO CONN ATTEMPTS ON PATH
NSUCC PC NO EST BEARER CONN ON AAL2PATH
NFAILCGCID PC NO LOST CONN DUE TO CIDS CONG
NFAILCGBW PC NO LOST CONN DUE TO BDWDTH CONG
NFAILCGGS PC NO LOST CONN DUE TO GS CONG
NFAILCGCH PC NO LOST CONN DUE TO AAL2 CONG
TRAL ST NO ACTIVE CONN ON PATH
NTRALACC PC ACCUMULATED ACTIVE CONN ON PATH
NSCAN PC NUMBER OF ACCUMULATIONS
END
75
9.- Define a report for the Object Type AAL2PATH, the result printout
of this command is the Report Identity assigned:
C:\>stmrp AAL2REP AAL2PATH

ReportId: 2002
10.- Print all defined statistics reports

C:\>stmrp -L
REPORTID IN-USE NAME
2000 yes DTIREP
2001 yes MULTIMEDIAREP
2002 no AAL2REP
11.- Define a measurement program for the previous report id. 2002,
the result printout of this command is the MP Identity assigned.
!with this definition, we received output reports every 60 minutes

C:\>stmmp -z ASN.1 -n AAL2MP 60 2002
MPId: 1002
!with this definition, we receive a single report, with data collection

!from 9:30 until 9:45
C:\>stmmp -n OTROAAL2MP -z LF 15 2002 -b 200206110930 -s
200206110945
MPId: 1003
12.- Print all the MP defined in the system, check that our reports
identities 1002 and 1003 are present:
S:\Sts\data\Deliverydir>stmmp -L
MPID STATUS MP-NAME
1000 running DTIMP
1001 running MULTIMEDIAMP
1002 running AAL2MP
1003 running OTROAAL2MP
13.- Print MP id.1002 and 1003 with long format:
C:\>stmmp -L -l 1003
MPID UTC BEGINTIME ENDTIME REPEATS INTERVAL REPORTID
1003 no 06/11/2002 09:30:00 06/11/2002 09:45:00 15 2002
OUTPUTFORMAT STATUS MP-NAME
LF running OTROAAL2MP
75
C:\>stmmp -L -l 1002
1002 no 06/11/2002 08:45:00 infinite 60 2002
ASN.1 running AAL2MP
14.- Wait until output reports are created, check

the following directory to see the reports:
S:\Sts\data\Deliverydir>dir
Volume in drive S is Disk S
Volume Serial Number is 444A-8936
Directory of S:\Sts\data\Deliverydir
06/11/02 11:46 <DIR> .
06/11/02 11:46 <DIR> ..
06/11/02 09:46 <DIR> AAL2MP_200206110645_1
06/11/02 10:46 <DIR> AAL2MP_200206110745_2
06/11/02 11:46 <DIR> AAL2MP_200206110845_3
06/11/02 09:46 <DIR> OTROAAL2MP_200206110745_1
76 File(s) 0 bytes
4,605,517,824 bytes free
Note. The time in the reports name is always referred to GMT (UTC Universal
Time Coordinated).
In Spain the local time is GMT + 1hour, and due to daylight savings
changes:
-From end of March to end of October (spring-summer):

GMT + 1hour + 1hour daylight savings = GMT + 2hours
-From end of October to end of March (autumn-winter):

GMT + 1hour.
15.- The statistics information is stored in each report directory,

this info can be taken with FTP.
16.- Check how long statistics reports are kept in the system,
this is the retaining time, giving in days :
C:\>stmdbrt -p
Database retainment time: 1 (one day)
75
17.- Delete MP's and reports defined previously:
!check status!
S:\Sts\data\Deliverydir>stmmp -L -l 1003
1003 no 06/11/2002 09:30:00 06/11/2002 09:45:00 15 2002
LF expired OTROAAL2MP
S:\Sts\data\Deliverydir>stmmp -L -l 1002
1002 no 06/11/2002 08:45:00 infinite 60 2002
ASN.1 running AAL2MP
!delete MP's
S:\Sts\data\Deliverydir>stmmp -D 1002
Program deleted
S:\Sts\data\Deliverydir>stmmp -D 1003
Program deleted
S:\Sts\data\Deliverydir>stmmp -L
MPID STATUS MP-NAME
1000 running DTIMP
1001 running MULTIMEDIAMP
!delete reports
C:\>stmrp -L
2000 yes DTIREP
2002 no AAL2REP
C:\>stmrp -D 2002
Report deleted
C:\>stmrp -L
2000 yes DTIREP
75
IX How to do a backup / restore of APG40 software
Backup of APG40
According to OPI 6/15431-ANZ 222 03 AP,SYSTEM BACKUP AND VERIFY

INITIATE;
1.- login to active node (in our case node B), check this node is the "active" one!
C:\>prcstate
active
C:\>hostname
APG40-1B -->this is the B-node, and is active.
2.-check that C:\bur exits in this node!
C:\>cd bur
3.-Store partition info in C:\bur, this action must be done from active node!
C:\bur>burbackup -savedatadiskinfo c:\bur\020116_backup.ddi

Execute burBackup with these parameters:
-SaveDataDiskInfo c:\bur\020116_backup.ddi
[y=yes, n=no]?y
Partition information of disks 2-4 successfully saved in c:\bur\020116_backup.ddi
C:\bur>dir
Volume in drive C is ntserv
Volume Serial Number is 18D2-B76A
Directory of C:\bur
01/16/02 11:16a <DIR> .

01/16/02 11:16a <DIR> ..
01/16/02 11:16a 22,090 020116_backup.ddi
11/07/01 07:52a 19,654 apmcm13_apiocm12_ohsrdt.ddi
11/13/01 09:19a 26,914 clone_test_all_appl_cm13.ddi
656,430,080 bytes free
75
4.-logout from active node!
C:\bur>exit
5.-login to the passive node (in our case node A)

and check the node is passive!
C:\>prcstate
passive
C:\>hostname
APG40-1A -->this is the A node.
6.-Verify c:\bur directory exists on passive node

you can use dir c:\bur, but the following is also available
C:\>dir \\APG40-1A\c$\bur
Volume in drive \\APG40-1A\c$ is ntserv
Volume Serial Number is 9893-1A66
Directory of \\APG40-1A\c$\bur
11/13/01 02:16p <DIR> .

11/13/01 02:16p <DIR> ..
11/13/01 02:17p 21,582 clone_test_all_appl_cm13.ddi
7.-Check if our .ddi file is on active node
C:\>dir \\APG40-1B\c$\bur
Volume in drive \\APG40-1B\c$ is ntserv
Volume Serial Number is 18D2-B76A
Directory of \\APG40-1B\c$\bur
01/16/02 11:16a <DIR> .

01/16/02 11:16a <DIR> ..
01/16/02 11:16a 22,090 020116_backup.ddi
11/07/01 07:52a 19,654 apmcm13_apiocm12_ohsrdt.ddi
11/13/01 09:19a 26,914 clone_test_all_appl_cm13.ddi
75
8.- Copy the .ddi info from active node (node-B) to passive node A,
in the following way:
C:\>copy \\APG40-1B\c$\bur\020116_backup.ddi c:\bur

1 file(s) copied.
C:\>cd bur
C:\bur>dir
Volume in drive C is ntserv
Volume Serial Number is 9893-1A66
Directory of C:\bur
01/16/02 11:31a <DIR> .

01/16/02 11:31a <DIR> ..
01/16/02 11:16a 22,090 020116_backup.ddi
9.-copy C: to D: with burbackup, first in node A which is passive
C:\bur>burbackup
Image name:apawqofg079r_A_ingo2_msc10
-src C:\
-dest D:\
-ImageName "apawqofg079r_A_ingo2_msc10"
[y=yes, n=no]?y
burBackup execution completed
687 directories and 11304 files copied or equal and 0 files locked
C:\bur>d:
D:\>cd bur
D:\bur>dir
Volume in drive D is ntbackup
Volume Serial Number is D4A5-52E3
Directory of D:\bur
01/16/02 11:37a <DIR> .
01/16/02 11:37a <DIR> ..
01/16/02 11:16a 22,090 020116_backup.ddi
75

1,201,598,464 bytes free
C:\>prcstate
passive
10.-check that directory K:\images exists
!APG40-1C is the name of the cluster (see with cluster /VER command).
C:\>dir \\APG40-1C\k$\images
Volume in drive \\APG40-1C\k$ is Disk K
Volume Serial Number is 906C-7BC2
Directory of \\APG40-1C\k$\images
01/18/02 10:17a <DIR> .

01/18/02 10:17a <DIR> ..
01/18/02 10:34a <DIR> nodeA
01/17/02 04:19p <DIR> nodeB
11.-do a copy of D: to K:\images\nodeA as zip file
C:\>burbackup -src D:\ -imgdest \\APG40-1C\images\nodeA\node_A_020116.zip

-src D:\
-imgdest \\APG40-1C\images\nodeA\node_A_020116.zip
[y=yes, n=no]?y
12.- Logout from the current passive node A.

C:\>exit
13.-login to the active node B
C:\>prcstate
active
C:\>hostname
APG40-1B
14.-Change the node state from active to passive with prcboot!

75
C:\>prcboot
REBOOT INITIATED!
C:\>exit
!Open again connection to the node
C:\>prcstate
Error: failed to find pipe. Error: 2
!take it easy, wait a minute!
C:\>prcstate
passive
C:\>hostname
APG40-1B -->now, node-B is passive
15.-do a copy of C: into D: for node B
C:\>burbackup
Image name:apawqofg079_B_ingo2_msc10
-src C:\
-dest D:\
-ImageName "apawqofg079_B_ingo2_msc10"
[y=yes, n=no]?y
680 directories and 11283 files copied or equal and 0 files locked
C:\>d:
D:\>dir
Volume in drive D is ntbackup
Volume Serial Number is 5084-EB2B
Directory of D:\
01/16/02 12:11p <DIR> acs

01/16/02 12:11p 0 AM_DISK_CHECK.DAT
06/27/01 12:18p 17,415 AM_DOS.EXE
75
10/15/01 11:06a 5,241 AM_DOS.LOG

01/16/02 12:11p <DIR> APIO
05/09/01 10:55a 434 AUTOEXEC.BAT
01/16/02 12:11p <DIR> BIOS730
01/16/02 12:11p <DIR> bur
05/31/94 07:22a 54,645 COMMAND.COM
10/30/00 04:24p 173 CONFIG.SYS
01/16/02 12:11p <DIR> ExecSoft
01/16/02 12:11p <DIR> inetpub
01/16/02 12:11p <DIR> Inetsrv
10/15/01 11:11a 25 install.log
10/15/01 11:10a 0 IPN100.0
02/01/01 02:43p 154 MANUAL.BAT
01/16/02 12:11p <DIR> MSCS
01/16/02 12:11p <DIR> Multimedia Files
01/10/02 04:02p 814 nxnetdom.log
10/15/01 11:06a 9,870 PCIDIAG.LOG
01/16/02 12:14p <DIR> Program Files
01/16/02 12:16p <DIR> scriptit
10/16/01 11:35a 1,024 SVTYP.1
01/16/02 12:16p <DIR> TEMP
01/16/02 12:16p <DIR> TFTPBOOT
05/31/94 07:22a 9,349 WINA20.386
01/16/02 12:21p <DIR> winnt
1,199,652,864 bytes free
C:\>prcstate
passive
16.-Copy D: into K:\images\nodeB as zip file!
C:\>burbackup -src d:\ -imgdest \\APG40-1C\images\nodeB\node_B_020116.zip

-src d:\
-imgdest \\APG40-1C\images\nodeB\node_B_020116.zip
[y=yes, n=no]?y
C:\>exit
Restore an APG40 in case of malfunction
According to OPI , AP System Restore Initiate, 7/15431-ANZ 222 03 rev.H
Note. In this document we only consider the case of restoring one node
at a time. Recover two nodes simultaneously is out of the scope of
75
this document.
One node restore (see step 22 "Select appropiate action" in the OPI)
----------------
In this example, we want to restore A node, that is working badly:
1.- Connect to the faulty node A with administrator rights.
2.- If the restore is going to be done from backup partition D:

continue in step 3. But if we need to restore from an older
backup (.zip file) stored in K: , first you need to pass this
backup from K: to D: doing the following:
C:\>burbackup -imgsrc \\APG40-1C\images\nodeA\AP02090222A_CM110.zip -dest D:\
Note. APG40-1C is our cluster name, check yours with command cluster /ver.
3.- Restore system from backup partition D:, sending the command:
C:\>burrestore
4.- The system ask you something like “Restore from this backup [y=yes, n=no]”,
confirm with yes (y) the question:
Imagename: AP02090222A_CM110_LBB_updated
Date: 9/23/02 4:26:11 PM
Node: APG40-1A
Status: OK (7150 files and 719 directories copied, 0 locked files)
Restore from this backup [y=yes, n=no]:y
5.- The system will ask you a name for the faulty SW running in node A,
in our case we chose "corrupt_system_node_A"
The currently running system will be stored on the backup partition.

Enter a description for the currently running system.
Image name: corrupt_system_node_A
7.- After typing the name, press Enter and the system will answer:
Partition 2 & 3 successfully swapped
Note.Partitions C: and D: were swapped, and the A node was rebooted,

after the reboot, the A node will start with the correct system
75
from C:, and the corrupt system will be left in D:.
8.- Check that all cluster resources are on-line after reboot:
C:\>cluster res
Note: it could take several minutes for the resources to be on-line, repeat the
command and take it easy.
Note. After restoring the node is recommended to do a burbackup in order to

update the backup partition D:\ with a valid backup.
X APG40 Healthcheck: Primus Solution SCS123402:
CONDITIONS:
All commands should be entered from the ACTIVE node.

Use the command prcstate to check the status of the current node.
PROCEDURE:
1. Verify that no major alarms are present.

C:\>alist
2. Verify that all resource are online.

C:\>cluster res|findstr -ive online
3. Verify the status of the RAID disks. All entries must be reported as Optimal.
If the command is issued on the PASSIVE node, Disk Drive entries will be
reported as "Optimal" and RAID 1 entries as "Drive Failed".
C:\>"C:\Program Files\Dptmgr\dptutil" -L raid
Steps 4-6 are only applicable on an APG with charging.
4. Verify that charging data is being received from the CP.
The lastMessNo should be increasing to indicate charging data is being received

from the CP.
The lastAckMess should be increasing to indicate charging data is being fetched
by the billing subsystem (RDT/FOS).
75
The lastMessNo should be greater than or equal to the lastAckMess.
The msdls command should be repeated several times to confirm the

lastMessNo is increasing.
MessageStore Name can be:

CHS usually for wireline systems
CHSMOB usually for mobile systems
C:\>msdls -m CHS -s cp0ex

or
C:\>msdls -m CHSMOB -s cp0ex
5. Verify charging data is being processed by the billing subsystem.

RDT:
C:\>rdtview -s
FOS:
C:\>fosview -s
6. Verify charging is being transferred to the billing centre.

RDT:
C:\>rdtview -b
FOS:
C:\>fosview -b
Steps 7-9 are only applicable on an APG with APIO.

7. Verify mml and CPT are working.
C:\>mml
<PTCOI;
cpt< PTWSP;
cpt< PTCOE;
<EXIT;
8. Verify IO devices are being routed OK.

No Faulty pds processes should be found.
C:\>cpdlist -l
9. Verify FMS is working.

C:\>cpfls
75
Make sure CP file system can communicate with FMS in the APG.
C:\>mml SYBFP:FILE
Step 10 needs to be performed from a CP connected terminal.

Depending on the site configuration this can be performed via the mml prompt of
an APG, an IOG terminal or a TW.
10. Verify status of CP-AP communication and the state of IPNs.

Only ACTIVE/PASSIVE and WO should be seen.
>DPWSP;
<APAMP;
<OCINP:IPN=ALL;
11. Verify there have been no recent process restarts.

C:\>ispprint
12. Verify there have been no recent errors or warning messages in the event
logs.
C:\>dumplog system
C:\>type c:\temp\log.txt
C:\>dumplog application
C:\>dumplog security
C:\>del c:\temp\log.txt
13. Verify that no major alarms are present.

C:\>alist
XI How to SET time in APG40

75
This instruction may be follow when the alarm CP AP time diference exceed
600ms.
Active Node
1. Check time
time /t
2. Check CP time
mml CACLP;
3. Set time
time
4. Check time
time /t
5. Passive Node
Check time
time /t
5. set time
net time / domain / set

or
net time \\active_ap_node_name / set
6. Check time
time /t
XII K-disk full problem.

The primus SCS326816 usually is good reference.

for /d %I in (K:\aes\data\cdh\ftp\*) do dir %I\Ready /b/s/ad
75
cd /d K:\aes\data\cdh\ftp && for /d %I in (*) do dir %I\Ready /b/s/ad

cd /d K:\aes\data\afp && DIR

cd /d K:\aes\data\cdh\ftp

! Then go to the dir where the the files are stored ie cd SGWDEST !

Check if the there are any current job in the AFP table that are in ready or
delete status.

afpls -ls

!!!These are examples please modify after the necessitate !!!!!!!

for /d %I in (*-MP1*_200305*) do move %I ..\Delete

APG40 Backup Images

cd /d K:\images && DIR /s

Should be maximum 2 backups files(400mb each)

Alarm output

cd /d K:\MCS\logs\PDS && dir

If the AD-0&4 log are big the best way is to flush the file.

Type con > AD-0.log

IPN Dumps

cd /d K:\OCS\logs && DIR

XIII C-disk full problem

75
Check in C:\temp. Application, system, and security .log can be deleted

check date stamp first. It happens that CP dumps are found on the C drive
as well(100Mb).Primus SCS298170 as your reference.

FCH files.

cd /d C:\acs\logs\fch && DIR

Application core files
- don't remove Dr. Watson file (i.e. drwtsn32.log)
- Do not remove the system.dmp file
- user.dmp files are core files that haven't been renamed to core.xxx
- user.dmp files can be safely removed or moved

cd /d C:\WINNT && dir user.dmp
cd /d C:\ACS\logs\core && DIR /s
(cd /d F:\ACS\logs\core || cd /d F:\ACS\logs) && DIR /s

Application core files on C: can be moved to the F: drive
if you wish to recover some disk space on C: drive

move C:\ACS\logs\core\core* F:\ACS\logs\core
move C:\WINNT\user.dmp F:\ACS\logs\core

Temporary CP dump files, Can be deleted

dir c:\R? /s
The mml Command in APIO Appendix
This is a partial list of the parameters for the mml command. Check the man
page to find all the parameters and their functions.
-a Used to indicate that this terminal will be an alarm receiver during this mml
session. This means that when the operator releases the terminal using “ctrl
d” or the equivalent, all spontaneous printouts, including alarms, will be sent
to the terminal.
75
-c Used to cause all commands sent from this terminal to be confirmed

automatically (no check print). THIS OPTION MAY BE DANGEROUS.
-d Must include the device ID. This parameter specifies the device ID to be
seized for this session. If the device is already in use, a fault message
“Device is occupied” will be returned.
-i Must include the device ID. Sends all spontaneous printouts to the specified
device ID. When used in conjunction with the –a parameter, alarms are
received at both devices.
-I Must include the device ID. Redirects spontaneous printouts to the specified
device ID.
-Q Invokes a dialog that asks which CP side you want to connect to: EX or SB.
-s Connects the terminal to the CP Standby. This is the same as a “separated

terminal” in an IOG-based system.
-r Time period for continuous retries when Function Busy is returned by the
system.
-w Specifies the waiting time for result printouts before sending the next
command. A value of zero means no wait time.
-W Specifies the delay between displayed lines.
The most convenient method for system access is to log on to the AP, then
immediately enter the mml command with appropriate parameters (-a being the
most common for maintenance personnel). The AP system is then reachable via
the APLOC command without releasing the AD device that was originally seized
at CP logon.
**********************************CAUTION*******************************
If you use APLOC; to access the AP, then you should always return to the CP
using exit. If you return to the CP with mml, you now have two CP sessions
running and you run the risk of "losing" a session.
Cluster Appendix
cluster group
75
(expected printout, ! Cluster group: Status shall be Online )

Listing status for all available resource groups:
Group Node Status

-------------------- --------------- ------
Disk Group AP_BOA1HE_A Online
PMC860 Group AP_BOA1HE_A Online
Cluster Group AP_BOA1HE_A Online
RGAPM_1 AP_BOA1HE_A Online
RGAPM_0 AP_BOA1HE_A Online
Cluster res ---- R9.1

(expected printout, ! Cluster res : Status shall be all Online )
Listing status for all available resources:

Resource Group Node Status
-------------------- -------------------- --------------- ------
Disks J: K: L: M: Disk Group AP_MAT1HE_A Online
Diskeeper Disk Group AP_MAT1HE_A Online
Share J Disk Group AP_MAT1HE_A Online
Share K Disk Group AP_MAT1HE_A Online
Images Disk Group AP_MAT1HE_A Online
Share LOGS Disk Group AP_MAT1HE_A Online
Disks X: R: S: Disk Group AP_MAT1HE_A Online
Disk L: Disk Group AP_MAT1HE_A Online
Share L Disk Group AP_MAT1HE_A Online
Share M Disk Group AP_MAT1HE_A Online
Share X Disk Group AP_MAT1HE_A Online
Share R Disk Group AP_MAT1HE_A Online
Share S Disk Group AP_MAT1HE_A Online
Share Y Disk Group AP_MAT1HE_A Online
Share MCS Disk Group AP_MAT1HE_A Online
ACS_ALOG_Main Disk Group AP_MAT1HE_A Online
ACS_PRC_IspLogger Disk Group AP_MAT1HE_A Online
AES_CDH_server Disk Group AP_MAT1HE_A Online
AES_AFP_server Disk Group AP_MAT1HE_A Online
AES_DFO_server Disk Group AP_MAT1HE_A Online
APIO_TFTP_Server Disk Group AP_MAT1HE_A Online
APM_DHCP_Server Disk Group AP_MAT1HE_A Online
FMS_CPF_server Disk Group AP_MAT1HE_A Online
CPS_BUAP_parmgr Disk Group AP_MAT1HE_A Online
CPS_BUAP_filemgr Disk Group AP_MAT1HE_A Online
CPS_BUAP_loader Disk Group AP_MAT1HE_A Online
CPS_BUFTPD Disk Group AP_MAT1HE_A Online
MAS_CPTASP_cptcentral Disk Group AP_MAT1HE_A Online
MAS_CPTASP_cptheartbeat Disk Group AP_MAT1HE_A Online
75
MCS_ADH_ADM Disk Group AP_MAT1HE_A Online

MCS_AIAP_ADM Disk Group AP_MAT1HE_A Online
MCS_ALDA_ADM Disk Group AP_MAT1HE_A Online
MCS_ALEC_ADM Disk Group AP_MAT1HE_A Online
MCS_ALIS_ADM Disk Group AP_MAT1HE_A Online
MCS_MTS_ADM Disk Group AP_MAT1HE_A Online
MPS_ROS_RosService Disk Group AP_MAT1HE_A Online
OCS_IPNAADM Disk Group AP_MAT1HE_A Online
OHS_FTP Disk Group AP_MAT1HE_A Online
OHS_FTP_FileBasedDst1 Disk Group AP_MAT1HE_A Online
OHS_RPC Disk Group AP_MAT1HE_A Online
OHS_RPC_BlockBased Dst1 Disk Group AP_MAT1HE_A Online
RDT_Messagestore Disk Group AP_MAT1HE_A Online
RDT_service Disk Group AP_MAT1HE_A Online
stsmain Disk Group AP_MAT1HE_A Online
stsopcf Disk Group AP_MAT1HE_A Online
stsprov Disk Group AP_MAT1HE_A Online
PMCrHW_1 PMC860 Group AP_MAT1HE_A Online
PMCrSDLC_1 PMC860 Group AP_MAT1HE_A Online
ACS_ALOG_BufMan_1 RGAPM_1 AP_MAT1HE_B Online
ACS_ALOG_SecLog_1 RGAPM_1 AP_MAT1HE_B Online
ACS_ALOG_SysMon_1 RGAPM_1 AP_MAT1HE_B Online
ACS_DSD_service_1 RGAPM_1 AP_MAT1HE_B Online
ACS_CHB_ClockSyncService_1 RGAPM_1 AP_MAT1HE_B Online
ACS_CHB_HeartBeatService_1 RGAPM_1 AP_MAT1HE_B Online
ACS_ALH_Exec_1 RGAPM_1 AP_MAT1HE_B Online
ACS_NSF_Server_1 RGAPM_1 AP_MAT1HE_B Online
ACS_PRC_ClusterControl_1 RGAPM_1 AP_MAT1HE_B Online
ACS_PRC_CountReboot_1 RGAPM_1 AP_MAT1HE_B Online
ACS_PRC_EventAnalyser_1 RGAPM_1 AP_MAT1HE_B Online
ACS_SFC_Recovery_1 RGAPM_1 AP_MAT1HE_B Online
ACS_SSU_Monitor_1 RGAPM_1 AP_MAT1HE_B Online
ACS_USA_SyslogAnalyser_1 RGAPM_1 AP_MAT1HE_B Online
OCS_OCP_echo_1 RGAPM_1 AP_MAT1HE_B Online
Time Service Cluster Group AP_MAT1HE_A Online
Cluster IP Address Cluster Group AP_MAT1HE_A Online
Cluster Name Cluster Group AP_MAT1HE_A Online
Internal IP Address for SPOE Cluster Group AP_MAT1HE_A Online
AP_1 Cluster Group AP_MAT1HE_A Online
ACS_ALOG_BufMan_0 RGAPM_0 AP_MAT1HE_A Online
ACS_ALOG_SecLog_0 RGAPM_0 AP_MAT1HE_A Online
ACS_ALOG_SysMon_0 RGAPM_0 AP_MAT1HE_A Online
ACS_DSD_service_0 RGAPM_0 AP_MAT1HE_A Online
ACS_CHB_ClockSyncService_0 RGAPM_0 AP_MAT1HE_A Online
ACS_CHB_HeartBeatService_0 RGAPM_0 AP_MAT1HE_A Online
ACS_ALH_Exec_0 RGAPM_0 AP_MAT1HE_A Online
ACS_NSF_Server_0 RGAPM_0 AP_MAT1HE_A Online
ACS_PRC_ClusterControl_0 RGAPM_0 AP_MAT1HE_A Online
ACS_PRC_CountReboot_0 RGAPM_0 AP_MAT1HE_A Online
ACS_PRC_EventAnalyser_0 RGAPM_0 AP_MAT1HE_A Online
75
ACS_SFC_Recovery_0 RGAPM_0 AP_MAT1HE_A Online

ACS_SSU_Monitor_0 RGAPM_0 AP_MAT1HE_A Online
ACS_USA_SyslogAnalyser_0 RGAPM_0 AP_MAT1HE_A Online
OCS_OCP_echo_0 RGAPM_0 AP_MAT1HE_A Online
Cluster Res -- R10

Listing status for all available resources: R10
Resource Group Node Status

-------------------- -------------------- --------------- ------
Disks J: K: M: Disk Group AP_LIS1HE_A Online
Diskeeper Disk Group AP_LIS1HE_A Online
Share J Disk Group AP_LIS1HE_A Online
Share K Disk Group AP_LIS1HE_A Online
Images Disk Group AP_LIS1HE_A Online
Share LOGS Disk Group AP_LIS1HE_A Online
Disks V: R: S: G: Disk Group AP_LIS1HE_A Online
Disks L: Q: Y: Disk Group AP_LIS1HE_A Online
Share M Disk Group AP_LIS1HE_A Online
Share R Disk Group AP_LIS1HE_A Online
Share S Disk Group AP_LIS1HE_A Online
Share Y Disk Group AP_LIS1HE_A Online
Share FMS Disk Group AP_LIS1HE_A Online
Share MCS Disk Group AP_LIS1HE_A Online
Share Q Disk Group AP_LIS1HE_A Online
Share L Disk Group AP_LIS1HE_A Online
PMCrHW_1 PMC860 Group AP_LIS1HE_A Online
PMCrSDLC_1 PMC860 Group AP_LIS1HE_A Online
Time Service Cluster Group AP_LIS1HE_A Online
Cluster IP Address Cluster Group AP_LIS1HE_A Online
Cluster Name Cluster Group AP_LIS1HE_A Online
Internal IP Address for SPOE Cluster Group AP_LIS1HE_A Online
AP_1 Cluster Group AP_LIS1HE_A Online
ACS_ALOG_Main Disk Group AP_LIS1HE_A Online
ACS_MSD_service Disk Group AP_LIS1HE_A Online
ACS_PRC_IspLogger Disk Group AP_LIS1HE_A Online
AES_CDH_server Disk Group AP_LIS1HE_A Online
AES_AFP_server Disk Group AP_LIS1HE_A Online
AES_DBO_server Disk Group AP_LIS1HE_A Online
ACS_RTR_service Disk Group AP_LIS1HE_A Online
APIO_TFTP_Server Disk Group AP_LIS1HE_A Online
APM_DHCP_Server Disk Group AP_LIS1HE_A Online
FMS_CPF_server Disk Group AP_LIS1HE_A Online
CPS_BUAP_parmgr Disk Group AP_LIS1HE_A Online
CPS_BUAP_filemgr Disk Group AP_LIS1HE_A Online
CPS_BUAP_loader Disk Group AP_LIS1HE_A Online
CPS_BUFTPD Disk Group AP_LIS1HE_A Online
gatherer Disk Group AP_LIS1HE_A Online
75
MAS_CPTASP_cptcentral Disk Group AP_LIS1HE_A Online

MAS_CPTASP_cptheartbeat Disk Group AP_LIS1HE_A Online
MCS_ADH_ADM Disk Group AP_LIS1HE_A Online
MCS_AIAP_ADM Disk Group AP_LIS1HE_A Online
MCS_ALDA_ADM Disk Group AP_LIS1HE_A Online
MCS_ALEC_ADM Disk Group AP_LIS1HE_A Online
MCS_ALIS_ADM Disk Group AP_LIS1HE_A Online
MCS_MTS_ADM Disk Group AP_LIS1HE_A Online
OCS_IPNAADM Disk Group AP_LIS1HE_A Online
stsmain Disk Group AP_LIS1HE_A Online
stsopcf Disk Group AP_LIS1HE_A Online
stsprov Disk Group AP_LIS1HE_A Online
ACS_ALOG_BufMan_0 RGAPM_0 AP_LIS1HE_A Online
ACS_ALOG_SecLog_0 RGAPM_0 AP_LIS1HE_A Online
ACS_ALOG_SysMon_0 RGAPM_0 AP_LIS1HE_A Online
ACS_DSD_service_0 RGAPM_0 AP_LIS1HE_A Online
ACS_CHB_ClockSyncService_0 RGAPM_0 AP_LIS1HE_A Online
ACS_CHB_HeartBeatService_0 RGAPM_0 AP_LIS1HE_A Online
ACS_ALH_Exec_0 RGAPM_0 AP_LIS1HE_A Online
ACS_NSF_Server_0 RGAPM_0 AP_LIS1HE_A Online
ACS_PRC_ClusterControl_0 RGAPM_0 AP_LIS1HE_A Online
ACS_PRC_CountReboot_0 RGAPM_0 AP_LIS1HE_A Online
ACS_PRC_EventAnalyser_0 RGAPM_0 AP_LIS1HE_A Online
ACS_SFC_Recovery_0 RGAPM_0 AP_LIS1HE_A Online
ACS_SSU_Monitor_0 RGAPM_0 AP_LIS1HE_A Online
ACS_USA_SyslogAnalyser_0 RGAPM_0 AP_LIS1HE_A Online
OCS_OCP_echo_0 RGAPM_0 AP_LIS1HE_A Online
ACS_ALOG_BufMan_1 RGAPM_1 AP_LIS1HE_B Online
ACS_ALOG_SecLog_1 RGAPM_1 AP_LIS1HE_B Online
ACS_ALOG_SysMon_1 RGAPM_1 AP_LIS1HE_B Online
ACS_DSD_service_1 RGAPM_1 AP_LIS1HE_B Online
ACS_CHB_ClockSyncService_1 RGAPM_1 AP_LIS1HE_B Online
ACS_CHB_HeartBeatService_1 RGAPM_1 AP_LIS1HE_B Online
ACS_ALH_Exec_1 RGAPM_1 AP_LIS1HE_B Online
ACS_NSF_Server_1 RGAPM_1 AP_LIS1HE_B Online
ACS_PRC_ClusterControl_1 RGAPM_1 AP_LIS1HE_B Online
ACS_PRC_CountReboot_1 RGAPM_1 AP_LIS1HE_B Online
ACS_PRC_EventAnalyser_1 RGAPM_1 AP_LIS1HE_B Online
ACS_SFC_Recovery_1 RGAPM_1 AP_LIS1HE_B Online
ACS_SSU_Monitor_1 RGAPM_1 AP_LIS1HE_B Online
ACS_USA_SyslogAnalyser_1 RGAPM_1 AP_LIS1HE_B Online
OCS_OCP_echo_1 RGAPM_1 AP_LIS1HE_B Online
FHC Appendix
from Alex : OPI APG40, Hard Function Change, Software, Change

1. The command:
If SW is R9.1
fchstart –V
75
If SW R10
fchstate
This command is used to report the Function Change status. It may be used at
any time during a Function Change session to report the current status of the
session. It may also be used after a Function Change session to report the status
of the latest sessions.
Node status reported by fchstate -s
The command fchstate -s prints one line:
<status> <state>
The <status> indicates the node status:
active
The node is active.
passive
The node is passive.
ClusterDown
The Cluster is down.
Limbo
The Cluster Group is not online.
<state> indicates the FCH state.
2 Description of FCH state reported by fchstate
The command fchstate reports the FCH state.

The states are sorted in alphabetical order in this section.
In this section, the fchstate printouts are displayed in this style of text while the
description and possible actions to be taken are displayed in this type of text.
Note:
In most cases, FCH is able to perform the FCH session without manual
intervention (except for entering the commands 'fchstart', 'fchcommit' and
'fchend'). But in case of failures, it may sometimes be necessary to help FCH to
complete the FCH session.
CommitDone
THE SYSTEM IS COMMITTED.
Run the command 'fchend' to end the session.
If you cannot run the command 'fchend',
then run the command 'fchrst' to restore the non-upgraded node.
75
FCH has successfully prepared the non-upgraded node for upgrade.

Go to finish the FCH session. If the fchend command has failed, go to restore the
non-upgraded node and re-commit it.
Committing
The command 'fchcommit' commits the system after supervision.
Wait for the 'CommitDone' state.
FCH is in the middle of preparing the non-upgraded node for upgrade.
Wait for the 'CommitDone' state.
Config1
ACS_FCH_Server is executing deletion of resources
in the cluster database.
If the 'Config1' state persists for several minutes,
try executing the command 'fchfb' to initiate a fallback.
If 'fchfb' fails, then try to reboot the upgraded node
using the command 'prcboot'.
Else, if you are sure that restore is needed,
run the command 'fchrst' to restore the upgraded node.
FCH is updating the cluster database.
Wait for the 'Supervision' state before continuing. If the state 'Config1' persists for
several minutes, go to fallback the FCH session.
Config1B
ACS_FCH_Server is executing update of resources
in the cluster database.
If the 'Config1B' state persists for several minutes,
FCH is updating the cluster database.
Wait for the 'Supervision' state before continuing. If 'Config1B' state persists for
several minutes, go to fallback the FCH session.
Config2
The command 'fchend' is executing deletion of old resources
in the cluster database non-upgraded node.
75

then try to reboot the non-upgraded node
run the command 'fchrst' to restore the non-upgraded node.
The command fchend is updating the cluster database. The node will reboot
when the update is finished.
Wait for the rebooting node to come back online before continuing. If the
'Config2' state persists for several minutes, try rebooting the node you are
executing fchend on using the command prcboot. If this does not work, or if you
are certain the command has been interrupted, go to fallback, two node restore.
Config2B
The command 'fchend' is executing update to new resources
in the cluster database, non-upgraded node.
If the 'Config2B' state persists for several minutes,
The command fchend is updating the cluster database. The node will reboot
when the update is finished.
Wait for the rebooting node to come back online before continuing. If the
'Config2B' state persists for several minutes, try rebooting the node you are
executing fchend(1m) on using the command prcboot(1m). If this does not work,
or if you are certain the command has been interrupted, go to fallback two node
restore.
Config3
ACS_FCH_Server or the command 'fchfb' is executing deletion
of resources in the cluster database.
FCH is falling back to the system existing prior to the start of the FCH session.
Wait for the upgraded node to reboot and come back online before continuing. If
the fallback has failed, (that is if you receive an error message from the
command fchfb(1m) or the 'Config3' state persists for several minutes), reboot
75
the upgraded node to force a fallback. If this too fails, or you are sure that the
fallback has been interrupted, please go to restore the upgraded node.
Config4
ACS_FCH_Server or the command 'fchfb' is executing addition
of old resources in the cluster database.
command fchfb(1m) or the 'Config4' state persists for several minutes), reboot
the upgraded node to force a fallback. If this too should fail, or you are sure that
the fallback has been interrupted, please go to restore the upgraded node.
Config5
ACS_FCH_Server or the command 'fchfb' is executing update
to old resources in the cluster database, upgraded node.
FCH is in the middle of falling back to the configuration existing prior to the FCH
session.
Wait for the 'End' state . If options -L,-c or -x were used in the command fchstart,
fchfb cannot complete the fallback since LBB software upgrade. To complete the
fallback you must use the command fchrst.
If the fchfb fails or if the 'Config5' state persists for several minutes, try rebooting
the upgraded node using the command prcboot. If this also fails to fallback the
node, go to restore the upgraded node.
Config6
ACS_FCH_Server is executing deletion of old resources in
75
the cluster database, non-upgraded node.

Due to unavailability of the upgraded node,
the non-upgraded node is being made active.
Wait for the upgraded node to come back online.
If the 'Config6' state persists for several minutes after the
upgraded node is back online and the ACS_FCH_Server is started,
During execution of fchend , the active node failed or rebooted. The non-
upgraded node has temporarily taken over as active node.
When the upgraded node comes back online, go to complete fchend. If fchend
cannot be executed go to fallback, node restore needed.
Config6B
ACS_FCH_Server is executing update to old resources
in the cluster database, non-upgraded node.
If the 'Config6B' state persists for several minutes after the
upgrade node is back online and the ACS_FCH_Server is started,
cannot be executed go to fallback, restore needed.
End
A fallback has occurred. Please run the command 'fchend'
on the passive node to end the session.
FCH has finished a fallback of the session.
Go to end the FCH session.
EndInstallDone
The command 'fchend' has finished installation in the non-upgraded node.
75
The command fchend has finished installation of the non-upgraded node. The
node will reboot to activate the new software.
Wait for the rebooting node to come back online.
EndInstalling
The command 'fchend' is installing the non-upgraded node after commit.
The command fchend is installing software on the second node. If the command
fchend detects any problems during the installation process, error messages are
printed and the command initiates a local fallback.
If you are sure the command has failed, go to restore the non-upgraded node.
EndOrigNode
FCH is about to, or executing end of a failed FCH session.
Run the command 'fchend' if not already done so.
During fchend the other (active) node has failed or rebooted. The fchend
command has been aborted. The non-upgraded node has returned to the state
before fchend was started, and is now operating as the active node until the
upgraded node comes back online.
Wait for the other node to come back online and become active. Then go to
execute fchend once more. If the active node does not come back online you
may need to restore it.
EndReboot
The FCH session is in a boot state (prior to end of the FCH session).
FCH is about to finish the session after final reboot during command fchend.
Execute the command fchstate with regular intervals until it reports that "No
function change session is ongoing". If this has not happened within 20 minutes,
the fchend may has failed. Go to restore the non-upgraded node and re-commit
the system.
EndRebootDone
ACS_FCH_Server or the command 'fchend' has initiated a reboot successfully
and the FCH-session is about to end.
FCH is in the process of finishing the FCH session.
If you are sure that the session has failed, (that is, the 'EndRebootDone' state
persists for several minutes) go to restore the non-upgraded node and re-
commit the system.
75
EndWrongNode
Due to unavailability of the upgraded node, the non-upgraded node is active.
Wait for the upgraded node to come back online,
then run the command 'fchend' again.
If the upgraded node is still down after 20 minutes, try to start it
using the command 'fcc_reset other'.
cannot be executed go to fallback.
Failed Supervision
Failure during Supervision detected. FCH is about to fallback.
[Waiting for {A|B}-node removal of resources from the Cluster DB.]
[Waiting for {A|B}-node addition of resources to the Cluster DB.]
[If the 'Failed Supervision' state persists for more than 20 minutes after reboot,
then try to reboot the {A|B}-node using the command 'prcboot'.]
A failure is detected during the Supervision period and FCH has started a
fallback. If the other node is down, FCH will wait until the other node is back
online and then continue the fallback.
Wait for the FCH session to complete the fallback.
Failover1
ACS_FCH_Server is about to failover.
If the failover has failed (the 'Failover1' state persists for several minutes),
The switchover to the new configuration is in progress.
Wait for the 'Supervision' state before continuing. This may take a few minutes. If
the 'Supervision' state has not appeared within 10 minutes, or you are certain
that the FCH session has failed, go to initiate a fallback. If this should fail, you
need to restore the upgraded node.
Failover2
ACS_FCH_Server is about to start-up the nodes.
First, the new active node, then the other.
If the failover has failed (the 'Failover2' state persists for several minutes),
75

FCH is about to take the new system configuration online.
Wait for the 'Supervision' state before continuing. If the 'Failover2' state persists
for several minutes, go to initiate a fallback.
FbEndReboot
A fallback has occurred and the FCH session is in a boot state
(prior to reactivation of old software on the passive node).
Wait for the 'CommitDone' state after the rebooting node is back online.
FCH is in the process of falling back the passive node after a failed or interrupted
fchend command.
If the 'FbEndReboot' state persists for more than 20 minutes, or you are sure that
FCH has failed, go to restore the non-upgraded node and re-commit the system.
FbEndRebootDone
ACS_FCH_Server or the command 'fchend' has initiated a reboot successfully
after a local fallback and the node is about to become committed again.
FCH is finishing up a fallback of the passive node after a failed or interrupted
fchend command.
If the 'FbEndRebootDone' state persists for several minutes, or if you are sure
that the FCH has failed, go to restore the non-upgraded node and re-commit the
system.
FbFailover1
ACS_FCH_Server or the command 'fchfb' is about to initiate a fallback of
the upgraded node and bringing all resources offline.
If the fallback has failed (the 'FbFailover1' state persists for several minutes),
using the comamnd 'prcboot'.
command fchfb or the 'FbFailover1' state persists for several minutes), reboot the
75
upgraded node to force a fallback. If this too should fail, or you are sure that the
fallback has been interrupted, please go to restore the upgraded node.
FbFailover2
ACS_FCH_Server or the command 'fchfb' is about to, or has executed start-up of
the old non-upgraded node.
If the printout from the command 'fchstate' indicates that an LBB upgrade
is going on, the command 'fchfb' cannot continue the fallback.
If the fallback fails (the 'FbFailover2' state persists for several minutes),
session.
Wait for the 'End' state. If the options -L, -c or -x were used in the command
fchstart, fchfb cannot complete the fallback since LBB software upgrade was
used. To complete the fallback you must use the fchrst command.
If the fchfb should fail or if the 'FbFailover2' state persists for several minutes, try
rebooting the upgraded node using the prcboot command. If this also fails to fall
back the node, go to restore the upgraded node.
FbFailover3
(before boot to activate old software).
If the fallback fails (the 'FbFailover3' state persists for several minutes),
then try to reboot the upgraded node
session.
Wait for the 'End' state. If the options -L,-c or -x were used in the fchstart
command, fchfb cannot complete the fallback since LBB software upgrade was
used. To complete the fallback you must use the fchrst command.
If the fchfb should fail or if the 'FbFailover3' state persists for several minutes, try
rebooting the upgraded node using the prcboot command. If this also fails to
fallback the node, go to restore the upgraded node.
FbReboot
75
(before boot to activate old software).

If the fallback fails, then try to reboot the upgraded node
session.
Wait for the 'End' state.
If the options -L, -c or -x were used in the fchstart command, fchfb cannot
complete the fallback since LBB software upgrade was used. To complete the
fallback you must use the fchrst command.
If the fchfb should fail or if the 'FbReboot' state persists for more than 20 minutes,
try rebooting the upgraded node using the prcboot command. If this also fails to
FbReboot2
(prior to activation of old software).
If the fallback fails, then try to reboot the upgraded node
session.
Wait for the 'End' state.
If the option -L, -c or -x were used in the fchstart command, fchfb cannot
complete the fallback since LBB software upgrade was used. To complete the
fallback you must use the fchrst command.
If the fchfb should fail or if the 'FbReboot2' state persists for several minutes, try
rebooting the upgraded node using the prcboot command. If this also fails to
InitWrongNode
FCH is initiating activation of the non-upgraded node.
When the upgraded node is back online,
run the command 'fchend' again.
75
When the upgraded node comes back online, go to complete fchend.
If fchend cannot be executed go to fallback, restore is needed.
InitWrongNodeDone
FCH is about to start-up the non-upgraded node.
When the upgraded node is back online,
run the command 'fchend' again.
When the upgraded node comes back online, go to complete fchend.
If fchend cannot be executed go to fallback restore is needed
Installing
The command 'fchstart' is installing software.
The command fchstart is installing software on the passive node.
If the command fchstart detects any problems during the installation process,
error messages are printed and the command initiates a fallback.
If this was an LBB software upgrade session (that is , fchstart -L, -c or -x were
used), go to node restore.
LbbReboot1
The FCH session is in a boot state.
When the node is back online, you should run the command
'fchstart -L [other args]...' again.
The FCH session is in a boot state during LBB upgrade.
Wait for the node to come back on line, then see how to continue. If you are sure
that the session has failed, and a restore is needed, go to fallback.
LbbReboot2
The FCH session is in a boot state.
When the node is back online, you should run the command 'fchend' again.
The FCH session is in a boot state during LBB upgrade.
Wait for the node to come back on line, and then see how to continue. If you are
sure that the session has failed, and a restore is needed, go to fallback.
75
Move1
The FCH session is in a state of failover.
If the failover has failed (the 'Move1' state persists for several minutes), try
executing the command 'fchfb' to initiate a fallback.
If 'fchfb' fails, then try to reboot the upgraded node using the command 'prcboot'.
Else, if you are sure that restore is needed, run the command 'fchrst' to restore
the upgraded node.
FCH is in the middle of switching to the new configuration.
Wait for the 'Supervision' state before continuing. This may take a few minutes. If
this event has not appeared within 10 minutes, or you are certain that the FCH
session has failed, initiate a fallback. If this should fail, you need to restore the
upgraded node.
Move2
The FCH session is in a state of fallback.
If the fallback has failed (the 'Move2' state persists for several minutes),
the upgraded node.
the fallback has failed, (that is if you receive an error message from fchfb
command or the 'Move2' state persists for several minutes), reboot the upgraded
node to force a fallback. If this too should fail, or you are sure that the fallback
has been interrupted, please go to restore the upgraded node.
noFCH
No Function Change session is ongoing.
FCH-session started at <date-time> <result>
Last FCH-session started at <date-time> <result>
No function change is currently in progress.
The second and third lines are optional. <date-time> is the date and time when
the FCH-session started. <result> is "was successful", "failed" or nothing.
Reboot
The FCH session is in a boot state (prior to failover).
If the rebooting node is back online and the 'Reboot' state persists for more than
30 minutes, try executing the command 'fchfb' to initiate a fallback.
75
the upgraded node.
FCH is about to start switching to the new configuration.
Wait for the 'Supervision' state before continuing. This may take several minutes.
If this event has not appeared within 30 minutes, or you are certain that the FCH
session has failed, go to initiate a fallback. If this should fail, you need to restore
the upgraded node.
Reboot2
(prior to or after activation of old software).
If the fallback fails, try executing the command 'fchfb' to initiate a fallback.
the upgraded node.
session.
Wait for 'End' state and then go to fallback. If the options -L, -c or -x were used in
the fchstart command, fchfb cannot complete the fallback since LBB software
upgrade was used. To complete the fallback you must use the fchrst command.
If the fchfb should fail or if the 'Reboot2' state persists for more than 20 minutes,
try rebooting the upgraded node using the prcboot command. If this also fails to
Restore
Please follow the OPI: AP System Restore, Initiate.
When finished, run the command 'fchend' to end the session.
An FCH restore operation is in progress.
Wait for the command burrestore to complete before continuing.
Restore2
Please follow the OPI: AP System Restore, Initiate.
When finished, run the command 'fchcommit' again.
An FCH restore operation to restore the non-upgraded node after a failed fchend
is in progress.
Wait for the command burrestore to complete before continuing.
StartOrigNode
The FCH session is falling back the original node and making it active.
75

When the upgraded node is back online, run the command 'fchend' again.
the upgraded node.
During fchend the other (active) node has failed or rebooted. The fchend
command has been aborted and the non-upgrade node returned to the state
before fchend was started, and is now operating as the active node until the
upgraded node comes back online.
Wait for the other node to come back online and become active. Then go to
execute fchend once more. If the active node does not come back online you
may need to restore it.
Supervision
SUPERVISION HAS BEGUN.
Be sure that all resources are online, then observe the system for a while.
Then run the command 'fchcommit' or 'fchfb' to continue the session.
FCH has successfully switched to the new system configuration.
Unknown state
Unknown state <state>. If this state persists for a long time you might have to
restore both nodes.
A serious error has occurred and FCH is in an unknown state! The system must
be restored.
Make a Trouble Report, see Operational Instruction AP, Trouble Report, Initiate.
Then restore the system, please see Operational Instruction AP, System
Restore, Initiate.
APG40 commands vs. IOG20
This table is intend to give a brief overview of the relation between the IOG and
APG40, with IPN, commands. For some commands the nearest alternative has
been chosen. The syntax for all AP commands can be found in the ALEX
documentation.

AP command IOG Command
Common CP commands
OCINP:IPN=ALL; EXSLP:SPG=0;
APAMP;
OCISI:IPN=1; FCSLI:SPG=0;
OCIBE:IPN=1; BLSLE:SPG=0,LINK=1;
75
APLOC; MCLOC, IMLCT, IMMCT, INMCT

Adjunct Computer Subsystem, ACS
acease Ceasing of AP internal alarms (No mapping)
alist IMALP
alogact MCTBE
alogdeact MCTBI
alogexcl MCTXI
alogexls MCTXP
alogfind MCSAP, MCSTP
aloglist MCTLP
alogset MCTLS
dsdls EXJAP, EXTDP
fchstart FCSPI, FCSSL, FCSDL, FCSSI
fchcommit FCSSI, FCSPE
fchend FCSPE
fchfb FCSPE
fchrst FCSPE, FCSSS
ispprint IMRLP
mktr Make Trouble Report (No mapping)
msdls Message Store Listning (No mapping)
prcboot SYRSI
prcstate IMCSP
sfcexec FCSPI, FCSDL
sfcend FCSPE
sfcend FCSPE
swrprint LASSP
swrsid LASSP, FCDLS
swrprod LASSP, FCSDL
trautil DEBUG
Force/Nexus Commands
burbackup SYSBP
burrestore FCSPI, FCSSS, FCSSI, FCSPE
fcc_getbib IMHWP
fcc_reset SYRSI / Reset Button
fcc_save_to_remove Allows replacement (No mapping)
fcc_integrate Regenerate Cluster (No mapping)
fcc_watchdog Enable/Disable watchdog (No mapping)
75
fcc_am_download Update alarm module SW (No mapping)

Central Processor File system, CPF
cpfmkfile INFII, IOIFI
cpfchange INFIC, IOIFC
cpfrename INFIC
Moves a file to another volume in CPF (No
cpfmv
mapping)
cpfcp INFIT, INFET
cpfls INFIP, IOFIP
Exports/Imports files from CPF to/from physical
cpfport
files (No mapping)
cpfdf INVOP
cpfife IOIFE
cpfrm INFIR, IOIFR
AP File Processing, AFP
afpdef INFDI
afprep INFSI
afprm INFDR
afpls INFDP, INFSP
afpchd INFDC
afpfti INFTI
afpfte INFTE
Common Destination Handling, CDH
cdhdef ILDNI
cdhch Change destination (No mapping)
cdhls ILDNP
cdhrm ILDNR
Direct File Output, DFO
dfodef ILDFI
dform ILDFR
dfoch Change DFO file (No mapping)
dfols ILDFP
Man Machine Commuication, MCS
MCDSC:IO=AT-x,SEP=YES;
mml -s
telnet IOGx 5100
mml -a telnet IOGx 5001
mml -d AD-x telnet IOGx 5010
75
alddef ALALI
alddeblk ALBLE
aldls ALALP
aldrm ALALE
aldpdef ALDIC
aldprm Alarm Display Property, Delete (No mapping)
aldpls ALDIP
aldquiet Bell Switch
aldtest ALLTI
Cpdinsert ILSLI, MCDVI
Cpdremove ILSLR, MCDVR
Cpdchange MCDSC, MCDVC, ILSLC
Cpdlist ILNPP, MCDVP
Cpdtest ILLTI
Exaldef ALRDL, ALEXL
Exalrm ALEXE
Exaldeblk BLEAE
Exalblk BLEAI
exalch External Alarm Receiver, Change (No mapping)
exalclear ALEXR
exalls ALEXP
Central Processor, CPS
bupprint SYGPP
bupset SYGPS
Maintenance, MAS
PTCOI, PTCOE, PTCPL etc. Processor test commands remains the same.
Useful Commands Appendix
ACS
acease (Alarms Cease) Manually ceases an alarm. Caution: The alarm can
be manually ceased without being repaired.
alist (Alarms List) Displays information about alarms in an AP.
alogact (Audit Log Activate) Activates the Audit Log function of an Adjunct
Processor (AP).
alogdeact (Audit Log Deactivate) Deactivates the Audit Log function of an
Adjunct Processor (AP).
75
alogexcl (Audit Log Exclude) Inserts or ends the exclusion status of Man-
Machine Language (MML) commands, MML command parameters,
MML printouts or UNIX commands in the Audit Log function of the
Adjunct Processor (AP).
alogexls (Audit Log Exclude List) Lists the excluded items that are contained
in the Audit Log of an Adjunct Processor (AP).
alogfind (Audit Log Find) Searches the logged data for items that
correspond to the specified search parameters.
aloglist (Audit Log Attributes List) Lists the attributes of the Audit Log
function of an Adjunct Processor (AP).
alogset (Audit Log Set) Specifies the attributes of the Audit Log function of
an Adjunct Processor (AP).
burbup (Backup) Initiates a backup to DAT tape.
burres (Backup Restore) Reads a backup tape and restores its contents to
the system.
burver (Backup Verify) Reads the archives on a backup tape and checks
that the tape is still readable.
dsdls (Directory Service List) Lists and displays the contents of the
registration file that is a part of the Directory Service function.
dslist (Directory Service List) Lists and displays the contents of the
registration file that is part of the Directory Service function;
information common for the directory service is printed.
fchend (Function Change End) Terminates a Function Change
session.
fchfb (Function Change Fallback) Reverts the system to its state before a
Function Change.
fchstart (Function Change Start) Initiates a Function Change session
fchsudo (Function Change Set User) Enables execution of commands as
another user in the restricted Function Change environment.
ispprint (In Service Performance Print) Prints the process control In Service
Performance (ISP) log to standard output or makes some simple
statistics and prints the result to standard output.
mktr (Make Trouble Report) Reports and collects additional information
to be used when trouble reports are received.
msdls (Message Store List) Lists and displays the contents of a
message store.
phacreate (Parameter Create) Creates the parameter tables for a CXC
specified in a parameter file (used at installation).
phaprint (Parameter Print) Reads and prints one parameter, a group of
parameters, or all parameters to standard output.
75
pharm (Parameter Removal) Cleans up the directory structure from the

CXCs private parameter tables (used at PKG removal).
phatrans (Parameter Transfer) transfers parameter values from one revision
of a CXCs parameters to a later revision.
prcavail (Process Control Available) Ensures that a needed service is
available before starting the application (used mainly during boot).
prcutil (Process Control Utility) Starts the user interface to Process Control
(PRC).
sadfsconf (System Analysis Daemon File System Configure) Sets and
displays the alarm limits for file system supervision.
sfcend (Soft Function Change End) Terminates a Soft Function Change
(SFC) session.
sfcfb (Soft Function Change Fallback) Makes a fallback of a Soft
Function Change (SFC) session.
sfcgstate (Soft Function Change Get State) Gets the state of Soft Function
Change (SFC).
sfcnew (Soft Function Change New) Updates a system and switches over
to the updated new system.
sfcpkg (Soft Function Change Package) Performs special handling of CXC
symbolic zero-links during installation.
sfcreboot (Soft Function Change Reboot) Executes an embedded SFC in a
Function Change (FCH) fallback (invoked during a Soft Function
Change (SFC) session when an SFC Restore is needed).
sfcstart (Soft Function Change Start) Prepares and initiates a Soft Function
Change (SFC) session by updating a system and switching over to
the updated new system.
sfcsudo (Soft Function Change Set User) Enables execution of commands
as another user in the restricted Function Change environment.
sll (System Log List) Displays the contents of the Event Log that is a
part of the AP Event Handler.
swrbup (Software Record Backup) Creates a backup of the SWR
database.
swrprint (Software Record Print) Prints software records.
swrprod (Software Record Product) Implements support for third party
product identification.
swrrec (Software Record Retrieve) Performs as the CLI for retrieval of
parameters from PKG.
swrrst (Software Record Restore) Restores the SWR database from a
backup file created by swrbup.
swrsid (Software Record System Identification) Implements support for AP
system identification.
75
trainit (Trace Function Initiate) Initializes shared memory.

trautil (Trace Utility) Provides an operator with commands for creating or
deleting trace tasks, and displaying the trace log generated by a
trace task.
CPS
bupprint (Backup Parameter Print) Initiates a printout of parameters that are
used for backup generation handling and command log handling
(effective in connection with reload).
bupset (Backup Parameter Set) Sets up parameters for system backup
generation handling and command log handling.
FMS
afpchd (AP File Processing Change Definition) Changes the definition of a
file; inserts or removes a destination, and/or changes the remove
delay of a file in the Adjunct Processor File Processing (AFP).
afpdef (AP File Processing Define) Defines composite main files, simple
files and UNIX files to AFP.
afpls (AP File Processing List) Lists all files that are defined or reported
to AFP.
afprep (AP File Processing Report) File reports a subfile to Adjunct
Processor File Processing (AFP).
afprm (AP File Processing Remove) Removes UNIX files, composite main
files, subfiles, or simple files from Adjunct Processor File
Processing (AFP).
cpfchange (Central Processor File Change) Changes attributes of an infinite
file.
cpfcp (Central Processor File Copy) Copies a CP file to another CP file. A
simple file or a subfile may be copied to a simple file or a subfile.
cpfdf (Central Processor File Display File) Lists all volumes used by the
Central Processor (CP) file system.
cpfife (Central Processor File Infinite File End) Changes the active subfile
of an infinite file.
cpfls (Central Processor File List) Prints the names and attributes of one
or all files.
cpfmkfile (Central Processor File Make File) Creates a main file or subfile in
the CP file system.
cpfmv (Central Processor File Move File) Moves a CP file to another
volume. The file can be simple or composite.
cpfport (Central Processor File Port) Copies a CP file to a physical file path
(export), or copies a physical file or directory to a CP file (import).
75
cpfrename (Central Processor File Rename) Renames a file or a subfile. A

new subfile name must include the main file part of the old subfile
name.
cpfrm (Central Processor File Remove) Deletes a simple file, a composite
file, or a subfile from the CP file system.
FOS
foscopy (Format Output Subsystem Copy) Copies messages currently
being read by the Flexible Formatter from the Adjunct Computer
Subsystem Message Store to a file.
foslview (Format Output Subsystem Log View) Retrieves and decodes the
contents of an unprocessed data log-file.
fosview (Format Output Subsystem View) Shows information about the
Format and Output Subsystem (FOS) application on a user's
terminal.
MCS
cpdchange (Central Processor Device Change) Changes the attributes for the
specified parameters of a defined I/O device.
cpdinsert (Central Processor Device Insert) Initiates a PDS program
associated with the I/O (used when an operator inserts a new I/O
device into the CP).
cpdlist (Central Processor Device List) Lists the attributes of defined or
active I/O devices.
cpdremove (Central Processor Device Remove) Removes an I/O device from
the Central Processor (CP) and ends the Printout Destination
Services (PDS) program.
mml (Man-Machine Language) Executes MML commands.
pds (Printout Destination Services) Initiates the Printout Destination
Services (PDS) when used with command cpdinsert(1m).
PKG
pkgadd (Package Add) Adds operating system packages to a
specified directory.
pkgchk (Package Check) Checks the accuracy of installed files or, by use
of the –1 option, displays information about package files.
pkginfo (Package Information) Determines the version of the specified
package in the host operating system.
pkgrm (Package Remove) Removes operating system packages from a
specified directory.
STS
75
stmcc (Statistics and Traffic Management Counter Collection) Initiates or

ends the regular collection of statistics counter data.
stmdbrt (Statistics and Traffic Measurement Database Retainment Time)
Sets or prints the database retainment time to the given number of
calendar days.
stmdestls (Statistics and Traffic Measurement Destination List) Prints the
destination names for FTP and/or FTAM communications.
stmfo (Statistics and Traffic Measurement File Output) Generates load
files containing statistics data.
stmotd (Statistics and Traffic Measurement Object Type Data) Manages
the Correction Area and changes the configuration of Object Types.
stmotls (Statistics and Traffic Measurement Object Type List) Lists the
configuration of specified or all Object Types.
stmttu (Statistics and Traffic Measurement Translation Tables Update)
Updates Translation Tables (TTs). The command will execute only
once within a 5 minute period.

Lazy Guide For Emergency Handling of APG40: Ericsson

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lazy Guide For Emergency Handling of APG40: Ericsson

Uploaded by

Copyright:

Available Formats

ERICSSON LAZY GUIDE FOR EMERGENCY HANDLING OF APG40 1 / 75

Prepared Subject Resp. No

Lazy Guide For Emergency Handling of APG40

III. First Actions and data collection.............................................3

IX How to do a backup / restore of APG40 software.........35

III. First Actions and data collection

Basic Node Status

Enter commands in both nodes:

From the active node only:

"C:\Program Files\Dptmgr\Raidutil" -L all

Hard Function Change

-The alarm AP FUNCTION CHANGE FAILED is issued if the function change

- The alarm AP FUNCTION CHANGE FAILED is issued if the function change

3) Was LBB upgraded?

Yes –step 4 (LBB so we go to one node restore)

4) One node restore.

The system is now prepared for restore.

On the other Node :

Enter a description for the currently running system.

Was the FCH restore successful ?

Note: The restore operation will take 5-10 minutes to finish.

No, an error message was received from the command fchrst.

5) From passive node

enter net start clussvc / to see whether it succeeds or fails

if fails go with the solution SCS346435, otherwise , if o.k. go to step 6)

4.1 passive Node (added) --> setupservices

> From SCS346435: Chek group permissions as well.

6) End a Failed Function Change

End failed function change session.

On the upgraded node, send command:

Was the command successful?

Go to Step 4). One Node Restore

8) Two nodes restore is needed

2 Restore the system from the C:\>burrestore -stay

3 Data about the image file from the

4 As the system restore forces a swap

5 Stop one cluster ressource.

C:\>cluster res ACS_PRC_ClusterControl_1 /offline /wait

6 Shutdown the B-node. C:\>prcboot -s

7 Logon to the A node.

8 Restore the system from the C:\>burrestore

9 Data about the image file from the

backup partition will be shown

10 As the system restore forces a swap

11 Logon to the restored node.

12 Check that the cluster service C:\>net start

Note: If the cluster service has not

13 Check that all cluster resources C:\>cluster res

14 Check that the FC is in state C:\>fchstart -V

15 Restart the other node. C:\>fcc_reset other

16 Check that the cluster service C:\>net start

by command. C:\>net start clussvc

17 Check that all cluster resources C:\>cluster res

19 Go to "Return to normal operation"

Soft Function Change

The fallback should be performed by command, or automatically, but if

V How to Put/Get a CP backup copy into/from APG40

Put a CP backup (SYBUP) into APG40 (RELFSW)

LCT --> APG Directory of L:\FMS\data\tmp --> CP File System (RELFSW)

Note 1. LCT is your computer, called Local Craft Terminal

1.- Check the size of the subfiles (R0...R5) you want to

3.- Check you have enough free space in the L: partition

4.- Create a directory on L:\fms\data\tmp\ in the APG for storing