!**************************************************************!

!*
*!
!* EXAMPLE DT,APG43 MSC R13.2 DUAL Configuration file template*!
!*
*!
!* Document Number:
2/190 77-LXA 119 582/2
*!
!* Revision:
B
*!
!* Date:
2008-06-24
*!
!* Prepared by:
EAB/ZA/FBM Anders Hgberg
*!
!*
*!
!**************************************************************!
!*
*!
!* AS NAME
: MSC R13.2 APG
*!
!* AS IDENTITY
: 2/AXE 106 30/A46 R1A
*!
!*
*!
!**************************************************************!
!*
*!
!* References:
*!
!*
*!
!* 1) EXAMPLE DT APG40 MSC R13 DUAL, command file
*!
!*
3/153 72-LXA 119 582/5 Uen Rev A
*!
!*
*!
!* 2) CCR Form, APG43 Reference Project
*!
!*
1/152 43-LXA 119 582/2 Rev A
*!
!*
*!
!* 3) AGG43 Generic DT, manual steps
*!
!*
2/190 46- 5/LZY242060/43 Rev A
*!
!*
*!
!* 4) APG43 Configuration Guidelines
*!
!*
3/127 04-FDG 103 21/4 Rev A
*!
!*
*!
!* Test Loaded : Yes
*!
!*
*!
!**************************************************************!
!*
*!
!* In the event an end-user should find faulty
*!
!* information in this document, or should find
*!
!* that parts of this document needs improvement,
*!
!* please provide the feedback to our helpdesk mail
*!
!* address:
*!
!*
*!
!* ssi.services@ericsson.com
*!
!*
*!
!* or use the pre-defined e-mail for
*!
!* Question/Feedback for PCI manual found on the
*!
!* right side of BUGS Integration home page,
*!
!*
*!
!* http://internal.ericsson.com/page/
*!
!* hub_globalservices/products/delivery/
*!
!* integration/index.jsp
*!
!*
*!
!**************************************************************!
!*
*!
!* This file is intended to be loaded using Ericsson Element *!
!* manager tool, Winfiol.
*!
!*
*!
!**************************************************************!
!****************************************************!
!*
*!
!* Revision information:
*!
!*
*!
!* Rev A, 2008-01-23:
*!
!* Document based on Ref.1
*!
!*
*!
!* Rev B, 2008-06-25:
*!
!* Uppdated with R13.2 impacts and general updates. *!
!* 4.4.2 and 4.4.3 changed order
*!
!****************************************************!
!**********************************************************************!
!******************** INTRODUCTION TO THIS DOCUMENT *******************!
!**********************************************************************!
!*** MML-mode and AP Local Mode:
***!
!***
***!
!*** In the APG43 two different prompts are used:
***!
!***
***!
!*** <
for MML-mode
***!
!*** C:\>
for AP local mode
***!
!***
***!
!*** To switch between the modes use:
***!
!***
***!
!*** C:\>mml
Enter MML-mode
***!
!*** <exit;
Return to the local mode
***!
!*** <APLOC;
Enter AP local mode
***!
!*** C:\>exit
Return to MML-mode
***!
!***
***!
!**********************************************************************!
!**********************************************************************!
!*** For DT Input, this APG43 Example DT uses data specified
***!
!*** in "CCR-form APG43 Reference Project", Ref. 2
***!
!***
***!
!*** The commands in this file represent the configuration presented***!
!*** in the CCR-form Reference Project. In addition, for parameters ***!
!*** not covered by the CCR-form, the default values presented
***!
!*** in this file can be used as guiding values.
***!
!***
***!
!*** The correlation between the commands and parameters in this
***!
!*** file and the CCR-form APG43 Reference Project are outlined in ***!
!*** the APG43 Configuration Guidelines, Ref 4.
***!
!***
***!
!*** Parts of the configuration are required to be introduced
***!
!*** by means of "Manual Steps", i.e parameters set manually via
***!
!*** the GUI in APG43. The manual steps, outlined in
***!
!*** Ref 3, are included in this document and are denoted
***!
!*** as follows:
***!
!***
***!
!***
***!
!********************* MANUAL STEP ***********************************!
!*** (text)
***!
!*** (text)
***!
!*** (text)
***!
!********************* MANUAL STEP, END ******************************!
!**********************************************************************!
!*** Furthermore, alternative possibilities in realising specific ***!
!*** APG43 functionality exist. For information, such additional
***!
!*** commands (with relevant parameters) have been included in this ***!
!*** document, and are denoted as follows:
***!
!***
***!
!********************* ADDITIONAL COMMANDS ***************************!
!*** (text)
***!
!*** (text)
***!
!*** (text)
***!
!********************* ADDITIONAL COMMANDS, END **********************!
!**********************************************************************!
!**************** INTRODUCTION TO THIS DOCUMENT, END ******************!
!**********************************************************************!
!**********************************************************************!
!**************** START OF CONFIGURATION FILE *************************!
!**********************************************************************!
!*******************************************!
!*** 1. Configuration AP1, Manual Steps ****!
!*******************************************!
!**************************************************************************
*************************************!
!************************************ MANUAL STEP ************************
*************************************!
!**************************************************************************
*************************************!
!***
***!
!*** Execute the following procedure first on the A-node and then repeat pr
ocedure on the B-node
***!
!***
***!
!*** Logon using Terminal server/Remote desktop
***!
!*** Connect to node IP address
***!
!*** Log on to the node
***!
!*** Logon as:
***!
!***
User:
<Administrator>
***!
!***
Password: <password>
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 1.1 Keyboard layout
***!
!***
***!
!*** Ref: CCR form, Node Start-up Configuration AP1
***!
!***
***!
!*** From your local console, open the control panel by selecting:
***!
!*** Start -> Control Panel -> Regional and Language Options
***!
!*** Select tab LANGUAGES
***!
!*** Select DETAILS
***!
!*** Select ADD.
***!
!*** In the menu INPUT LANGUAGE, choose "English (United States)"
***!
!*** Mark tick box KEYBOARD LAYOUT/IME
***!
!*** Select "US"
***!
!*** Select OK
***!
!*** In the DEFAULT INPUT LANGUAGE select "English (United States) - US"
***!
!*** Select OK
***!
!*** In the pop-up window, select OK.
***!
!***
***!
!*** Change the value of the registry key that sets the default keyboard la
yout to the required
***!
!C! !*** language option (US in this case), using the following command by sele
cting
***!
!N! !** Start -> Run -> and then type:
***!
!***
***!
!*** reg add HKEY_USERS\.DEFAULT\Keyboard Layout\Preload /v "1" /t REG_SZ /
d 0409 /f
***!
!***
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 1.2 Time Zone Settings
***!
!***
***!
!*** Ref: CCR form, Node Start-up Configuration AP1
***!
!***
***!
!*** From your local console, open the Date/Time Properties by double-click
ing on the clock indicator
***!
!*** in the Windows 2003 taskbar.
***!
!*** Select taqb TIME ZONE.
***!
!*** Click on the drop down menu and select the right time zone:
***!
!***
***!
!C! !*** (GMT+01:00) .........
***!
!***
***!
!*** Select OK
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 1.3 Legal notice, telnet Greeting Message
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Display of Legal Notice
***!
!***
***!
!*** The Telnet server can be configured to display a message when logging
on to the system.
***!
!***
***!
!*** See
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen, 3.4.3.1.2
***!
!*** Follow the instructions in User guide using command sfcexec
***!
!***
***!
!N! !*** Answere question 1, "copy files" NO
***!
!N! !*** Answere question 2, "edit files" YES
***!
!***
***!
!N! !*** Select the package containing the AES_TELNET_LEGAL_NOTICE parameter is
CXC 137 1187, TELSRVBIN.
***!
!***
***!
!*** Use following message
***!
!*** WARNING
***!
!*** You are about to access a private computer network.
***!
!*** Unauthorized access will be punished to the fullest extent possible un
der the law.
***!
!***
***!
!*** Select OK
***!
!**************************************************************************
*************************************!
!***
***!
!*** 1.4 Legal notice, ssh Greeting Message
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Display of Legal Notice
***!
!***
***!
!*** See also:
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen, 3.4.3.2.5
***!
!***
***!
!*** The SSH server can be configured to display a message when a user conn
ects to the system.
***!
!***
***!
!*** Open Notepad:
***!
!*** Start -> All Programs -> Accessories -> Notepad
***!
!***
***!
!*** Type the desired message:
***!
!***
***!
!*** ***************
***!
!*** *** WARNING ***
***!
!*** ***************
***!
!***
***!
!*** ************************************************************
***!
!*** *** You are about to access a private computer network. ***
***!
!*** *** Unauthorized access will be punished to the fullest ***
***!
!*** *** extent possible under the law.
***
***!
!*** ************************************************************
***!
!***
***!
!*** Name and save the file under c:\winnt\system32\.
***!
!*** The name of the default message file acs_acsc_message.txt can be used
***!
!C! !*** if the SSH legal notice message and terminal login (1.8)
***!
!N! !** will be the same as the Warning message.
***!
!***
***!
!*** Start the SSH Configuration tool:
***!
!*** Start -> All Programs -> F-Secure SSH Server -> Configuration
***!
!*** Select GENERAL
***!
!*** In the input field BANNER MESSAGE FILE,
***!
!*** specify the filename of the text file above containing the message
***!
!*** (or press the browser button and select the file from there).
***!
!***
***!
!*** Note:
***!
!*** Do not delete or change the name of file acs_acsc_message.txt.
***!
!*** This file is needed for Warning message display.
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 1.5 Legal notice, ftp Welcome Message
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Display of Legal Notice
***!
!***
***!
!*** See also:
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen, 3.4.3.3.5
***!
!*** Application Information "Adjunct Computer Subsystem", 2/155 18-ANZ 222
43 Uen, 2.1.6
***!
!***
***!
!*** The FTP server can be configured to display a message to the user when
logging on to the system.
***!
!***
***!
!*** Start Internet Information Service (IIS) Manager:
***!
!*** Start -> Administrative Tools -> Internet Information Services (IIS) M
anager
***!
!***
***!
!*** Open the folder LOCAL COMPUTER
***!
!*** Open the folder FTP sites
***!
!*** Right click on DEFAULT FTP SITE
***!
!*** select PROPERTIES
***!
!*** Select tab MESSAGES
***!
!*** In the field WELCOME, specify the legal notice text:
***!
!***
***!
!*** WARNING
***!
!*** You are about to access a private computer network.
***!
!*** Unauthorized access will be punished to the fullest extent possible un
der the law.
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 1.6 Ftp Exit Message
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Display of Welcome messages
***!
!***
***!
!*** See also:
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen, 3.4.3.3.5
***!
!*** Application Information "Adjunct Computer Subsystem", 2/155 18-ANZ 222
43 Uen, 2.1.6
***!
!***
***!
!*** The FTP server can be configured to display a message to the user when
logging out
***!
!*** from the system.
***!
!***
***!
!*** Start Internet Information Service (IIS) Manager:
***!
!*** Start -> Administrative Tools -> Internet Information Services (IIS) M
anager
***!
!***
***!
!*** Open the folder LOCAL COMPUTER
***!
!*** Open the folder FTP sites
***!
!*** Right click on DEFAULT FTP SITE
***!
!*** select PROPERTIES
***!
!*** Select tab MESSAGES
***!
!***
***!
!*** When connected to AP Node A, specify the exit message in the field EXI
T:
***!
!***
***!
!*** Logged out from MSC1 AP Node A.
***!
!***
***!
!*** When connected to AP Node B, specify the exit message in the field EXI
T:

***!
!***

***!
!*** Logged out from MSC1 AP Node B.
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 1.7 Legal notice, terminal logon Greeting Message
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Display of Legal Notice
***!
!***
***!
!*** It is possible to define a legal notice to be displayed before logon a
ccording to the
***!
!*** instructions below.
***!
!***
***!
!*** Start the Registry Editor:
***!
!*** Start -> Run -> Type regedit and press OK.
***!
!***
***!
!*** Go to key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Ver
sion\Winlogon
***!
!***
***!
!*** Right click on LegalNoticeCaption, choose Modify and type the desired
caption in the Value
***!
!*** data field:
***!
!***
***!
!*** WARNING
***!
!***
***!
!*** Right click on LegalNoticeText, choose Modify and type the desired tex
t in the Value
***!
!*** data field:
***!
!***
***!
!*** Do Not Attempt to logon to this system unless you are an authorized us
er.
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 1.8 Warning message, terminal logon Greeting Message
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Display of Warning Message
***!
!***
***!
!*** See also:
***!
!*** OPI "AP, Authority, Administer", 4/154 31 CRZ 222 05 Uen
***!
!***
***!
!*** Go to directory c:\winnt\system32
***!
!*** Open file acs_acsc_message.txt
***!
!*** Insert text, as follows:
***!
!***
***!
!*** "This system is restricted solely to "Company_Name" authorized users f
or legitimate
***!
!*** business purposes only. The actual or attempted unauthorized access, u
se, or
***!
!*** modification of this system is strictly prohibited by "Company_Name".
***!
!*** Unauthorized users are subject to Company disciplinary proceedings and
/or criminal a
***!
!*** nd civil penalties under state, federal, or other applicable domestic
and foreign
***!
!*** laws. The use of this system may be monitored and recorded for adminis
trative and
***!
!*** security reasons. Anyone accessing this system expressly consents to s
uch monitoring
***!
!*** and is advised that if monitoring reveals possible evidence of crimina
l activity,
***!
!*** "Company_Name" may provide the evidence of such activity to law enforc
ement
***!
!*** officials."
***!
!***
***!
!*** Save and exit file acs_acsc_message.txt
***!
!***
***!
!***
***!
!*** Go to directory c:\winnt\system32
***!
!*** Open file acs_acsc_question.txt
***!
!*** Insert text, as follows:
***!
!***
***!
!*** "Are you an authorized user? (Yes/No)"
***!
!***
***!
!*** Save and exit file acs_acsc_question.txt
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 1.9 Setting up Master User Domain (MUD) trust (if to be used)
***!
!***
***!
!*** Prerequisites: A Windows Domain Server to be used as MUD server
***!
!***
***!
!*** References:
***!
!*** CCR form, Node Start-up Configuration AP1
***!
!*** CCR form, Initial user accounts, Master User Domain
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen
***!
!***
***!
!*** Follow the step-by-step instruction presented in the User Guide,
***!
!*** "Security Administration of the APG43", 2/198 17-ANZ 222 43 Uen chapte
r 3.4.2.
***!
!***
***!
!*** The relevant values to be entered are found in the following CCR forms
:
***!
!***
***!
!*** "Node Start-up Configuration AP1"
***!
!*** (Cluster Name, Domain Name, Node Names (node A & B), IP Addresses (clu
ster, node A, node B),
***!
!*** Master User Domain Server, etc)
***!
!***
***!
!*** "Initial user accounts, Master User Domain"
***!
!*** (Initial Password, Master User Domain usergroup, Local usergroups, etc
)
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 1.10 Setting up Convenience groups (if to be used)
***!
!***
***!
!*** Ref: CCR form, Initial user accounts, Convenience groups
***!
!***
***!
!*** See also:
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen, 3.2.9
***!
!***
***!
!*** If it's found that a certain category of users always belong to the sa
me groups it
***!
!*** possible to create a Global group that is given membership in the Loca
l groups and
***!
!*** give the users membership to the Global group instead, this also remov
es the
***!
!*** necessity for the Domain Users group.
***!
!***
***!
!*** Start:
***!
!*** Start -> Administrative Tools -> Active Directory Users and Computers.
***!
!N! !*** Open local computer
***!
!*** Select folder USERS
***!
!C! !*** From the actions menu (Right click), choose NEW -> GROUP
***!
!*** Enter GROUP NAME:
***!
!***
***!
!*** STS_Users_Group
***!
!***
***!
!*** In GROUP SCOPE, tick Global Group
***!
!*** In GROUP TYPE, tick Security
***!
!*** Press OK.
***!
!***
***!
!*** Global group is created.
***!
!***
***!
!*** Select the newly created group
***!
!C! !*** From the actions menu (right click), choose PROPERTIES
***!
!*** In the field DESCRIPTION, write:
***!
!***
***!
!*** Access for STS administration. APG access only.
***!
!***
***!
!*** To grant the group membership in the desired local groups, go to
***!
!*** tab MEMBER OF
***!
!*** Press ADD.
***!
!*** Type the names, separated with semicolons, of the
***!
!*** groups which the global group should be member of:
***!
!***
***!
!*** STSADMG;ACSUSRG
***!
!***
***!
!*** Press OK.
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 1.11 Automatic termination of inactive user sessions
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Session timeout settings
***!
!***
***!
!*** See also:
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen,
***!
!*** 3.4.3.1.1, 3.4.3.2.5, 3.4.3.3.4, 3.4.3.8.2
***!
!***
***!
!*** --------***!
!***
***!
!*** TELNET:
***!
!*** Start the Telnet configuration tool:
***!
!C! !*** Follow user guide 3.4.3.1.1 using command sfcexec
***!
!N! !*** Answere question 1, "copy files" NO
***!
!N! !*** Answere question 2, "edit files" YES
***!
!***
***!
!N! !*** Select the package containing the AES_TELNET_LOGOFF_TIMEOUT parameter
is CXC 137 1187, TELSRVBIN.
***!
!*** Use timeoutvalue 1200
***!
!***
***!
!*** --------***!
!***
***!
!*** SSH/SFTP:
***!
!*** Start the SSH Configuration tool:
***!
!*** Start ->Programs -> F-Secure SSH Server -> Configuration
***!
!***
***!
!*** Select GENERAL
***!
!*** In the field IDLE TIMEOUT (SECONDS), type:
***!
!***
***!
!*** 1200
***!
!***
***!
!N! !*** Press Apply
***!
!*** Press OK
***!
!***
***!
!*** --------***!
!***
***!
!*** FTP:
***!
!*** Start the Internet Information Services (IIS) Manager:
***!
!*** Start -> Administrative Tools -> Internet Information Services (IIS) M
anager.
***!
!*** Open the folder LOCAL COMPUTER
***!
!*** Open the folder FTP sites
***!
!*** Select DEFAULT FTP SITE
***!
!*** From the Action menu (, chose PROPERTIES
***!
!*** In the field CONNECTION TIMEOUT (IN SECONDS), type:
***!
!***
***!
!*** 600
***!
!***
***!
!*** Press OK
***!
!***
***!
!*** --------***!
!***
***!
!*** Terminal Services:
***!
!*** Start Terminal Services:
***!
!*** Start -> Administrative Tools
***!
!*** Select Group Policy Management
***!
!** Click on -> Forest:<domain name> -> Domains -> <domain name> -> Domain
controllers
***!
!***
***!
!*** Under the tab LINKED GROUP POLICY OBJECTS, right click on DEFAULT DOMA
IN POLICY
***!
!*** Select EDIT
***!
!*** This will open up the Group Policy Object Editor.
***!
!***
***!
!*** Under Default Domain Controllers Policy [<hostname>] Policy ->
***!
!*** Computer Configuration -> Administrative Templates -> Windows Componen
ts ->
***!
!*** Terminal Services -> Sessions,
***!
!*** Select SETS A TIME LIMIT FOR ACTIVE BUT IDLE TERMINAL SERVICES SESSION
S
***!
!***
***!
!*** From the Action menu, chose PROPRTIES
***!
!*** Tick box ENABLED
***!
!*** in the dropdown menu IDLE SESSION LIMIT, choose:
***!
!***
***!
!*** 30 minutes
***!
!***
***!
!*** (Since this is a group policy that affects all domain controllers, the
change
***!
!*** will automatically be applied to both nodes in the APG43 cluster)
***!
!***
***!
!N! !*** Press OK
***!
!***
***!
!N! !*** Close application.
***!
!**************************************************************************
*************************************!
!************************************ MANUAL STEP, END *******************
*************************************!
!**************************************************************************
*************************************!
!**********************************************************************!
!*** 2. Configuration AP1, Commands
***!
!**********************************************************************!
!**********************************************************************!
!*** 2.1 DEFINITION OF APG43 USERS ON AP1
***!
!**********************************************************************!
!**********************************************************************!
!*** 2.1.1 DEFINITION OF USERGROUPS (LOCAL GROUPS) FOR THE CP USERS ***!
!**********************************************************************!
!**********************************************************************!
!*** Ref: CCR form, Initial user accounts, Local accounts on AP1
***!
!**********************************************************************!
!**********************************************************************!
!*** Here three local groups will be created. One for full
***!
!*** access users, one for operators access (more rights than the ***!
!*** limited users, but less than the full access users) and one
***!
!*** for limited access (only printouts) users
***!
!*** Ref: CCR form, Initial user accounts, Local accounts on AP1
***!
!**********************************************************************!
net localgroup CP_FullAccGr /add
net localgroup CP_OperAccGr /add
net localgroup CP_PrintAccGr /add
!***********************************************************************!
!*** 2.1.2 DEFINITION OF CP USER PROFILES ON AP1
***!
!***********************************************************************!
!***********************************************************************!
!*** Ref: CCR form, Initial user accounts, Local accounts on AP1
***!
!***********************************************************************!
mml
!*** Print existing users, groups and authority option
IOUAP:USER=ALL;

***!

!***
!***
!***
!***
!***
!***

***!
***!
***!
***!
***!
***!

Here, three users will be created, corresponding to the

three local groups created above.
Important: In the IOUAL commands below, the PSW for the
CP_xxx user is not used for authentication when connecting
to the system via remote client (telnet). The PSW is used
only in case of direct CP connection.

!*** Full access user

IOUAL:USER=CP_Full,PSW=cpfull0,USERGR=0;
IOUAI:USER=CP_Full;

***!

!*** Command category auhorization for User group 0

!*** Category 0 - 255 inserted (all categories)
!*** Must not be loggon with user from group 0
IOUGC:USERGR=0, CATI=0&&255;

***!
***!
***!
!*** Limited access user ***!
IOUAL:USER=CP_Operator,PSW=cpoperator0,USERGR=2;
IOUAI:USER=CP_Operator;
!*** Command category auhorization for User group 2
!*** Category 0 - 63 inserted. Category 64 - 255 removed ***!
IOUGC:USERGR=2, CATI=0&&63, CATR=64&&255;

***!

!*** User with access only to printouts ***!

IOUAL:USER=CP_Print,PSW=cpprint0,USERGR=1;
IOUAI:USER=CP_Print;
!*** Command category auhorization for User group 1
!*** Category 0 inserted. Category 1 - 255 removed
IOUGC:USERGR=1, CATI=0, CATR=1&&255;

***!
***!

!*** Print all defined users, groups and authority option ***!
IOUAP:USER=ALL;
!*** List all defined associations between ***!
!*** the AP groups and the CP users
***!
!C! exit;
cuals
!*** Define association between the already defined ***!
!C! !*** local groups and the CP users, if not already exist ***!
cuadef -g CP_FullAccGr -u CP_Full
-c "CP Full access"
-p 1
cuadef -g CP_OperAccGr -u CP_Operator -c "CP Operator access" -p 2
cuadef -g CP_PrintAccGr -u CP_Print
-c "CP Printouts"
-p 3
!*****************************************!
!*** 2.2 DEFINITION OF OSS USER ON AP1 ***!
!*****************************************!
!************************************************************************!
!*** Ref: CCR form, Initial user accounts, Local accounts on AP1
***!
!************************************************************************!
net user ossadm Ossuserpsw1 /add
!*** Add the OSS user to the necessary local groups ***!
net localgroup CP_FullAccGr ossadm /add
net localgroup ACSUSRG ossadm /add
net localgroup APIOUSRG ossadm /add
net localgroup APLOCG ossadm /add
net localgroup CDHFTPUSRG ossadm /add
net localgroup FMSADMG ossadm /add
net localgroup FTPUSRG ossadm /add
net localgroup MASUSRG ossadm /add
net localgroup MCSADMG ossadm /add
net localgroup STSADMG ossadm /add
net localgroup STSUSRG ossadm /add
net localgroup AESADMG ossadm /add
!*** For APG43 remote FCH ***!
net localgroup Administrators ossadm /add
!**********************************************************************!
!********************* ADDITIONAL COMMANDS ***************************!
!**********************************************************************!
!***
***!
!*** Only for APZ 21240:
***!
!***
***!
!*** net localgroup APZADMG ossadm /add
***!
!***
***!
!**********************************************************************!
!********************* ADDITIONAL COMMANDS, END***********************!
!**********************************************************************!
!********************************************************!
!*** 2.3 DEFINITION OF USERS FOR GLOBAL GROUPS ON AP1 ***!
!********************************************************!
!************************************************************************!
!*** Ref: CCR form, Initial user accounts, Convenience groups
***!
!************************************************************************!
net user stsuser1 Stsupsw1 /add
net user stsuser2 Stsupsw2 /add
net user stsuser3 Stsupsw3 /add
!**********************************************************************!
!********************* ADDITIONAL COMMANDS ***************************!
!**********************************************************************!
!***
***!
!*** Print information about all users defined in the system:
***!
!***
***!
!*** UserDump
***!
!***
***!
!*** Delete all users PREDIFINED on the reference dump, not
***!
!*** related to the actual configuration:
***!
!***
***!
!*** mml
***!
!*** IOUAE:USER=user;
***!
!*** IOUAR:USER=user;
***!
!*** exit;
***!
!***
***!
!**********************************************************************!
!********************* ADDITIONAL COMMANDS, END***********************!
!**********************************************************************!
!***********************************!
!*** 2.4 FTP/SMO SETTINGS ON AP1 ***!
!***********************************!
!*** Check for common parameters/environment ***!
set
!*** Set path for access to vital commands if needed ***!
!N! path=%path%;C:\Program Files\AP\ACS\bin
path=%path%;C:\Program Files\AP\AES\bin
!N! path=%path%;C:\Program Files\AP\APIO\bin
!N! path=%path%;C:\Program Files\AP\CPHW\bin
!N! path=%path%;C:\Program Files\AP\CPS\bin
!N! path=%path%;C:\Program Files\AP\FMS\bin
!N! path=%path%;C:\Program Files\AP\MAS\bin
!N! path=%path%;C:\Program Files\AP\MCS\bin
!N! path=%path%;C:\Program Files\AP\OCS\bin
!N! path=%path%;C:\Program Files\AP\PES\bin
!N! path=%path%;C:\Program Files\AP\SGS\bin
!N! path=%path%;C:\Program Files\AP\STS\bin
!*** Get server name ***!
ftpls
!***
!***
!***
!***
!***
vdls

Server Name "Default FTP Site"

IP Address: Port: ":21:"
List virtual directories:
Usage: vdls -n ServerName
Check if virtual smo directory
-n "Default FTP Site"

***!
***!
***!
***!
exists ***!

!*** Check if phisycal smo directory exists ***!

dir K:\fms\data\tmp\smo
!*** If not there, create the physical smo directory ***!
mkdir K:\fms\data\tmp\smo
!*** If not already done, make the smo directory virtual ***!
!*** Usage:
***!
!*** vdcreate -n ServerName -a AliasName -d PhysicalPath ***!
vdcreate -n "Default FTP Site" -a smo -d K:\fms\data\tmp\smo
!**********************************************!
!*** 2.5 IO Devices in CP with APG43 ON AP1 ***!
!**********************************************!
!*** The supported alphanumeric I/O device types for APG are ***!
!*** AD, TW and AF devices only. No other alphanumeric
***!
!*** device types shall be used.
***!
!*** Print the IO Device data ***!
mml
IOIOP:IO1=ALL;
IOROP;
!*** In case AT/AMTP devices are in the IOROP table remove them ***!
!*** by using blank routing.
***!
IOROL:PRCA=0&&31;
IOROI:PRCA=0&&31;
IOROL:PRCA=32&&63;
IOROI:PRCA=32&&63;
IOROL:PRCA=64&&95;
IOROI:PRCA=64&&95;
IOROL:PRCA=96&&127;
IOROI:PRCA=96&&127;
IOROL:PRCA=128&&159;
IOROI:PRCA=128&&159;
IOROL:PRCA=160&&191;
IOROI:PRCA=160&&191;
IOROL:PRCA=192&&223;
IOROI:PRCA=192&&223;
IOROL:PRCA=224&&255;
IOROI:PRCA=224&&255;
!N! exit;
!***************************************!
!*** 2.6 ROUTING OF PRINTOUTS ON AP1 ***!
!***************************************!
!**********************************************************************!
!********************* ADDITIONAL COMMANDS ***************************!
!**********************************************************************!
!***
***!
!*** Define more AD devices, if necessary:
***!
!***
***!
!*** cpdinsert AD-4
***!
!*** cpdinsert AD-5
***!
!*** cpdinsert AD-6
***!
!*** cpdinsert AD-7
***!
!***
***!
!**********************************************************************!
!********************* ADDITIONAL COMMANDS, END***********************!
!**********************************************************************!
!******************************************************!
!*** Ref: CCR form, Definition of Alarm Routing
***!
!******************************************************!
!**********************************************************************!
!*** There are two ways of routing printouts in a system with APG43 ***!
!*** The first way is to define the routing in the CP. That makes ***!
!*** possible the usage of standby devices ( in case the original ***!
!*** device fail).
***!
!*** The second and the recommended way is to define routing in the ***!
!*** AP. It is used when there is no need for having a standby
***!
!*** destination (sending printouts to OSS server, or when using
***!
!*** file/subfile as destination).
***!
!**********************************************************************!
!**************************************************************************
********!
!*** 2.6.1 DEFINITION OF ALARM ROUTING IN AP (SUBSCRIPTION OF PRINTOUTS ON
AP1) ***!
!**************************************************************************
********!
!**********************************************************************!
!*** All printouts from the CP-EX side (except HB-signal, PRCA=35) ***!
!*** will be routed to the IP destination 164.44.55.66:50000. In ***!
!*** case of faulty destination, rerouting will take place
***!
!*** (option -r omitted, printouts will be re-routed immediately). ***!
!**********************************************************************!
cpdinsert -i 164.44.55.66:50000 -v 0-34,36-255 AD-10
!**********************************************************************!
!********************* ADDITIONAL COMMANDS ***************************!
!**********************************************************************!
!***
***!
!*** All printouts from the CP-SB will be routed to the IP
***!
!*** destination 164.44.55.66:50000:
***!
!***
***!
!*** cpdinsert -i 164.44.55.66:50000 -v 0-255 AD-11
***!
!*** cpdchange -s yes AD-11
***!
!***
***!
!**********************************************************************!
!********************* ADDITIONAL COMMANDS, END***********************!
!**********************************************************************!
!************************************************!
!*** 2.6.2 SENDING OF HEARTBEAT SIGNAL ON AP1 ***!
!************************************************!
!**********************************************************************!
!*** No rerouting will take place (option -r, value -1).
***!
!**********************************************************************!
cpdinsert -i 164.44.55.66:50000 -r -1 -v 35 AD-12
!**********************************************************************!
!********************* ADDITIONAL COMMANDS ***************************!
!**********************************************************************!
!***
***!
!*** In case that there is possibility of using remote client
***!
!*** on local port the following setup can be used:
***!
!***
***!
!*** Define printout destination for remote clients (Port 4000 is ***!
!*** a local port in the APG).
***!
!***
***!
!*** cpdinsert -q 4000 AD-11
***!
!***
***!
!**********************************************************************!
!********************* ADDITIONAL COMMANDS, END***********************!
!**********************************************************************!
!*****************************************!
!*** 2.6.3 IO DEVICE CP, INSERT ON AP1 ***!
!*****************************************!
!*******************************************************************!
!*** Please refer to OPI: 'Alphanumeric Device in AP, Define'
***!
!***
***!
!*** Insert devices if needed with command 'cpdinsert' or change ***!
!*** attributes for existing devices with command 'cpdchange'. ***!
!***
***!
!*** Below are given some examples for cpdinsert.
***!
!*******************************************************************!
!*** List alphanumeric device table ***!
cpdlist -l
cpdlist -p
!*** Definition of file based AD which later will be ***!
!*** used as SB device for AD-10
***!
cpdinsert -f K:\MCS\logs\PDS\AD_20SBDev.log AD-20
!*************************************!
!*** 2.7 STANDBY IO DEVICES ON AP1 ***!
!*************************************!
!******************************************************!
!*** Ref: CCR form, Definition of Alarm Routing
***!
!******************************************************!
!****************************************************************!
!*** 2.7.1 STANDBY IO DEVICES for primary alphanumeric device ***!
!****************************************************************!
!*** AD-20 will be specified as SB device for AD-10 ***!
mml
IOSBC:FUNCTION=ALPHA,IO=AD-10&AD-20;
exit;
!*************************************************!
!*** 2.7.2 Definition of system standby device ***!
!*************************************************!
!********************************************************************!
!*** Define the system standby device. A new subfile is created ***!
!*** at midnight for the first day in every month.
***!
!********************************************************************!
cpdinsert -x 01:00:00 AD-0
mml
IOSYC:IO=AD-0;
exit;
!**********************************************************************!
!********************* ADDITIONAL COMMANDS ***************************!
!**********************************************************************!
!***
***!
!*** Remove all AT and AMTP devices:
***!
!***
***!
!*** IOBLI:IO=AT-x;
***!
!*** IOIOR:IO=AT-x;
***!
!*** IOIOR:IO=AMTP-y;
***!
!***
***!
!**********************************************************************!
!********************* ADDITIONAL COMMANDS, END***********************!
!**********************************************************************!
!**************************************!
!*** 2.8 DEFINE FILES IN APG ON AP1 ***!
!**************************************!
!*************************************!
!*** 2.8.1 Start of CP file system ***!
!*************************************!
mml
IOCDP;
IOCDI:APPL=CPF,NUM=01;
exit;
!*************************************!
!*** 2.8.2 Creation of Volumes
***!
!*************************************!
!*******************************************************!
!*** The following Volumes need to be defined before ***!
!*** CP Files can be defined:
***!
!*** -EXCHVOLUME
***!
!*** -RELVOLUMSW
***!
!*** -TEMPVOLUME
***!
!*******************************************************!
!*** List volume table defined in APG ***!
cpfdf
!*** List the cluster name ***!
cluster /VER
!*** If any of the volumes
mkdir \\MSC1APG43_C\"Share
mkdir \\MSC1APG43_C\"Share
mkdir \\MSC1APG43_C\"Share

below is missing, define it. ***!

FMS"\FMS\data\CPF\EXCHVOLUME
FMS"\FMS\data\CPF\RELVOLUMSW
FMS"\FMS\data\CPF\TEMPVOLUME

!******************************************!
!*** 2.8.3 Creation of CP files ON AP1 ***!
!******************************************!
!***********************************************************************!
!*** Command cpfmkfile creates either a simple file, a composite
***!
!*** main file or a subfile in the CP file system.
***!
!*** The volume where the file is created must already exist.
***!
!***
***!
!*** A simple file is always regular.
***!
!*** A composite file is either regular or infinite, and consists of ***!
!*** a main file and zero (0) or more subfiles. The main file acts ***!
!*** as a template when creating subfiles.
***!
!*** A subfile may only be created for an existing composite file, ***!
!*** and it contains the actual data. A regular file is written or ***!
!*** read sequentially or randomly. An infinite file is always
***!
!*** composite and is written sequentially. In an infinite file, new ***!
!*** subfiles may be created automatically. The infinite file may
***!
!*** contain any combination of three 'change conditions': maxsize, ***!
!*** maxtime and release. When at least one of the conditions is
***!
!*** fulfilled the active subfile will change.
***!
!***********************************************************************!
!****************************!
!*** APZ FILE DEFINITIONS ***!
!****************************!
!***********!
!*** CPF ***!
!***********!
!*** Print CPF file table on AP ***!
cpfls -l -s
!*** Create regular files ***!
cpfmkfile -c -l 2048 RELFSW0 RELVOLUMSW
cpfmkfile -c -l 2048 RELFSW1 RELVOLUMSW
cpfmkfile -c -l 2048 RELFSW2 RELVOLUMSW
!***********************!
!*** APZ Command log ***!
!***********************!
cpfmkfile -c -l 512 RELCMDHDF
RELVOLUMSW

!************************************************!
!*** SW upgrade, remote function change files ***!
!************************************************!
cpfmkfile -c -l 512 AC
RELVOLUMSW
cpfmkfile -c -l 512 DCFILE RELVOLUMSW
cpfmkfile -c -l 512 DEV
RELVOLUMSW
cpfmkfile
cpfmkfile
cpfmkfile
cpfmkfile

-c
-c
-c
-c

-l
-l
-l
-l

512
512
512
512

EC
EMRP
FC
LO

RELVOLUMSW
RELVOLUMSW
RELVOLUMSW
RELVOLUMSW

!*********************************!
!*** Alpha numeric output file ***!
!*********************************!
cpfmkfile -c -l 160 AFFILE EXCHVOLUME
!**************************************************!
!*** IN Interface Operations Log Parameter File ***!
!**************************************************!
cpfmkfile -l 32 INMPAR EXCHVOLUME
!****************************************!
!*** IN Interface Operations Log File ***!
!****************************************!
cpfmkfile -c -l 512 INMLOG EXCHVOLUME
!********************************************!
!*** IN Interface Operations Buffer Files ***!
!********************************************!
cpfmkfile -l 512 INMFILE9
EXCHVOLUME
cpfmkfile -l 512 INMFILE10 EXCHVOLUME
cpfmkfile -l 512 INMFILE11 EXCHVOLUME
!****************************!
!*** APT FILE DEFINITIONS ***!
!****************************!
!********************************************!
!*** CCITT7 Traffic recording output file ***!
!********************************************!
!C! cpfmkfile -f inf -l 512 -s 100 -r C7TMFILE EXCHVOLUME
!**************************************************!
!*** CCITT7 Performance measurement output file ***!
!**************************************************!
!C! cpfmkfile -f inf -l 512 -s 100 -r C7PMFILE EXCHVOLUME
!******************************************************!
!*** Printout of part of defined accounting classes ***!
!******************************************************!
cpfmkfile -f inf -l 2048 SINGLEACC EXCHVOLUME
!*****************************************************!
!*** Printout of all of defined accounting classes ***!
!*****************************************************!
cpfmkfile -f inf -l 2048 SINGLEALLACC EXCHVOLUME
!******************************************!
!*** Periodic output of accounting data ***!
!******************************************!
cpfmkfile -f inf -l 2048 PERIODICACC EXCHVOLUME
!**********************************!
!*** Charging check output file ***!
!**********************************!
cpfmkfile -c -l 100 CHCNTRL EXCHVOLUME
!***************************************!
!*** Charging statistics output file ***!
!***************************************!
!C! cpfmkfile -c -l 2048 CHSTATFILE EXCHVOLUME
!***********!
!*** NMS ***!
!***********!
cpfmkfile -f inf -l 4072 CODARTEFILE EXCHVOLUME
cpfmkfile -f inf -l 3622 CODADESTFILE EXCHVOLUME
cpfmkfile -f inf -l 256 ACBORFILE
EXCHVOLUME
!***********!
!*** OMS ***!
!***********!
cpfmkfile -f inf -l 1984 TIMCOFILE
cpfmkfile -f inf -l 366 TRACAFILE

EXCHVOLUME
EXCHVOLUME

!********************************************!
!*** Traffic type measurement output file ***!
!********************************************!
cpfmkfile -f inf -l 2048 -r TRARTFILE EXCHVOLUME
!*************************************!
!*** Traffic recording output file ***!
!*************************************!
cpfmkfile -f inf -l 2048 -r TRARFILE EXCHVOLUME
!**************************************************!
!*** Traffic dispersion measurement output file ***!
!**************************************************!
cpfmkfile -f inf -l 2048 -r TRDIPFILE EXCHVOLUME
!**********************************************!
!*** Service quality statistics output file ***!
!**********************************************!
cpfmkfile -f inf -l 2048 SEQSFILE EXCHVOLUME
!*******************************!
!*** Data recording per call ***!
!*******************************!
cpfmkfile -f inf -l 2046 TRADOFILE EXCHVOLUME
!*******************************!
!*** License management file ***!
!*******************************!
!C! cpfmkfile -f inf -l 125 -r -s 120 LMAFILE EXCHVOLUME
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!

!**********************************************************************!
!********************* ADDITIONAL COMMANDS ***************************!
!**********************************************************************!
!***
***!
!*** Files for Licensing of Simultaneous Call Capacity, LSCTC.
***!
!*** cpfmkfile -f inf -l 153 -r LSCCFILE EXCHVOLUME
***!
!***
***!
!**********************************************************************!
!N! !********************* ADDITIONAL COMMANDS, END***********************!
!N! !**********************************************************************!
!N!
!N!
!N!
!N!

!**********************************!
!*** C7 accounting file, M7POI ***!
!**********************************!
cpfmkfile -f inf -l 512 -r -s 100 -t 1440 C7ACPOFILE EXCHVOLUME

!N!
!N!
!N!
!N!
!N!

!*****************************************!
!*** Charging Audit Measurement, CHAMI ***!
!*****************************************!
cpfmkfile -f inf -l 384 -r -s 500 MFCHAUFILE EXCHVOLUME !Simple output!
cpfmkfile -f inf -l 2529 -r -s 500 MFCHAUFILE EXCHVOLUME !Detail output!

!N!
!N!
!N!
!N!
!N!

!*********************************!
!*** Hardware invetory, EXHWP ***!
!*********************************!
cpfmkfile -l 256 HWIDFILE1 EXCHVOLUME
cpfmkfile -l 256 HWIDFILE2 EXCHVOLUME

!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!
!N!

!**********************************************************************!
!********************* ADDITIONAL COMMANDS ***************************!
!**********************************************************************!
!***
***!
!*** Files for monitoring
***!
!***
***!
!*** Files for monitoring BICC (BIMTI)
***!
!*** cpfmkfile -l 512 -c BIMONFILE01 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c BIMONFILE02 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c BIMONFILE03 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c BIMONFILE04 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c BIMONFILE05 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c BIMONFILE06 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c BIMONFILE07 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c BIMONFILE08 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c BIMONFILE09 EXCHVOLUME
***!
!***
***!
!*** Files for monitoring ISUP (UPMTI)
***!
!*** cpfmkfile -l 512 -c UPMONFILE01 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c UPMONFILE02 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c UPMONFILE03 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c UPMONFILE04 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c UPMONFILE05 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c UPMONFILE06 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c UPMONFILE07 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c UPMONFILE08 EXCHVOLUME
***!
!*** cpfmkfile -l 512 -c UPMONFILE09 EXCHVOLUME
***!
!***
***!
!**********************************************************************!
!********************* ADDITIONAL COMMANDS, END***********************!
!**********************************************************************!
!**********************************************************************!
!*** NOTE:
***!
!*** Charging files (e.g. TTFILExx, ICIFILExx) and Statistics
***!
!*** Measurement files (e.g. STSTART, STOBJTYPE) used on IOG are
***!
!*** not used on APG.
***!
!**********************************************************************!
!**********************************************************************!
!*** Verify that all needed destinations are defined for output of ***!
!*** files.
***!
!*** Follow OPI "Common Destination Handling, Destination, Define" ***!
!*** if more destinations have to be defined.
***!
!**********************************************************************!
!****************************************************!
!*** 2.9 COMMON DESTINATION HANDLING (CDH) ON AP1 ***!
!****************************************************!
!******************************************************!
!*** Ref: CCR form, Destination Configuration
***!
!******************************************************!
!************************************************************************!
!*** When processing MSC measurement files (TRDIP,TRAR,TRART) via FTP ***!
!*** two options are available for transferring them:
***!
!*** - to be transferred to the remote destination - Initiating FTP ***!
!*** - to be reported on a local FTP directory in the APG and fetched ***!
!*** from there on request (e.g. from OSS) - Responding FTP
***!
!************************************************************************!
!*************************************!
!*** 2.9.1 CDH with Initiating FTP ***!
!*************************************!
!*** Define Destinations ***!
!*** Initiating FTP to destination 164.44.55.66 is defined. The files ***!
!*** will be stored on the remote server under home/mscvlr1/trar*/
***!
!*** directories. APG FTP client will login as MSCVLR1 user.
***!
!*** Password prompt will be displayed after the cdhdef command to
***!
!*** enter the remote password for MSCVLR1 user.
***!
cdhdef -t ftpv2 -a 164.44.55.66 -r home/mscvlr1/trart/ -c i -u mscvlr1 -p T
RARTDEST
cdhdef -t ftpv2 -a 164.44.55.66 -r home/mscvlr1/trar/ -c i -u mscvlr1 -p T
RARDEST
cdhdef -t ftpv2 -a 164.44.55.66 -r home/mscvlr1/trdip/ -c i -u mscvlr1 -p T
RDIPDEST
!*** List destinations ***!
cdhls -l
!*** Verify the destinations ***!
cdhver TRARTDEST
cdhver TRARDEST
cdhver TRDIPDEST
!*** Define Destination set ***!
!*** Note: In case of Ericsson OSS the destination name and the ***!
!*** destination set name should be identical. Otherwise the
***!
!*** handling of OSS-SMIA tool will be affected
***!
cdhdsdef TRARTDEST TRARTDEST
cdhdsdef TRARDEST TRARDEST
cdhdsdef TRDIPDEST TRDIPDEST
!*** List destination sets ***!
cdhdsls -l
!*** AP File Processing definitions ***!
afpdef -d 1440 TRARFILE TRARTDEST
afpdef -d 1440 TRARTFILE TRARDEST
afpdef -d 1440 TRDIPFILE TRDIPDEST
!*************************************!
!*** 2.9.2 CDH with Responding FTP ***!
!*************************************!
!************************************************************************!
!*** Responding FTP at address 164.44.55.66 will be defined.
***!
!*** When the files are ready ,they will be stored in
***!
!*** K:\Ftpvol\xxx_Resp directories.File notifications on port
***!
!*** 50014 will be send and the remote server will fetch the
***!
!*** files using FTPV2.
***!
!************************************************************************!
mkdir K:\Ftpvol\CLOG_Resp
mkdir K:\Ftpvol\STATISTICS_Resp
mkdir K:\Ftpvol\NMS_Resp
!*** IMPORTANT: The following commands should be done on both of the ***!
!*** nodes.
***!
!*** APG43, Node A ***!
vdcreate -n "Default FTP Site" -a CLOG_Resp
-d K:\FTPvol\CLOG_Resp
vdcreate -n "Default FTP Site" -a STATISTICS_Resp -d K:\FTPvol\STATISTICS_R
esp
vdcreate -n "Default FTP Site" -a NMS_Resp

-d K:\FTPvol\NMS_Resp

!*** APG43, Node B ***!

vdcreate -n "Default FTP Site" -a CLOG_Resp
-d K:\FTPvol\CLOG_Resp
vdcreate -n "Default FTP Site" -a STATISTICS_Resp -d K:\FTPvol\STATISTICS_R
esp
vdcreate -n "Default FTP Site" -a NMS_Resp

-d K:\FTPvol\NMS_Resp

!***************************!
!*** Define Destinations ***!
!***************************!
!*** Command log ***!
cdhdef -t ftpv2 -c r -h CLOG_Resp -f 164.44.55.66 -x 50014 CLOGDEST
!*** MSC Statistics ***!
cdhdef -t ftpv2 -c r -h STATISTICS_Resp -f 164.44.55.66 -x 50014 STATDEST
!*** NMS ***!
cdhdef -t ftpv2 -c r -h NMS_Resp -f 164.44.55.66 -x 50014 NMSDEST
!*** List CDH destinations ***!
cdhls -l
!*** Verify the destinations ***!
cdhver CLOGDEST
cdhver STATDEST
cdhver NMSDEST
!******************************!
!*** Define Destination set ***!
!******************************!
cdhdsdef CLOGDEST CLOGDESTSET
cdhdsdef STATDEST STATDESTSET
cdhdsdef NMSDEST NMSDESTSET
!*** List destination sets ***!
cdhdsls -l
!**************************************!
!*** AP File Processing definitions ***!
!**************************************!
!***
!***
!***
!***
!***
!***
!***

After CNI 109 22-APZ21220/5-1013 Uen the handling of the transfer

queues and the infinite files have been changed. There is no need
to create a single transfer queue for each infinite file. This
improves the capacity, since more transfer queues will be
available.
NOTE: The one-to-one relationship for block (record) outputs
(DBO) between an infinite file and a transfer queue remains.

***!
***!
***!
***!
***!
***!
***!

!*** APZ Command log ***!

!*** Note: RELCMDHDF is a regular file. One-to-one rule should be used ***!
afpdef -d 240 RELCMDHDF CLOGDESTSET
!*** MSC Statistics ***!
!*** Note: CHSTAT is a regular file. One-to-one rule should be used ***!
afpdef -d 1440 STATTQ STATDESTSET
afpdef -d 1440 CHSTAT STATDESTSET
cpfchange
cpfchange
cpfchange
cpfchange
cpfchange
cpfchange
cpfchange
cpfchange

-d
-d
-d
-d
-d
-d
-d
-d

STATTQ
STATTQ
STATTQ
STATTQ
STATTQ
STATTQ
STATTQ
STATTQ

-m
-m
-m
-m
-m
-m
-m
-m

FILE
FILE
FILE
FILE
FILE
FILE
FILE
FILE

C7TMFILE
C7PMFILE
SINGLEACC
SINGLEALLACC
PERIODICACC
SEQSFILE
TIMCOFILE
TRACAFILE

!*** NMS ***!

afpdef -d 1440 NMSTQ NMSDESTSET
cpfchange -d NMSTQ -m FILE CODARTEFILE
cpfchange -d NMSTQ -m FILE CODADESTFILE
cpfchange -d NMSTQ -m FILE ACBORFILE
!*** Verify that File Processing is defined for all files ***!
!*** that should be processed.
***!
afpls -ls
!**************************************************************************
!
!*** Follow OPI "AP File Processing, Transfer Queue, Define" if more

***

!*** transfer queues have to be defined.

***

!
!
!**************************************************************************
!
!*** The removal time in minutes (parameter * d in c'afpdef) specifies ***
!
!*** how long time the subfile will remain on the APG43 hard disk after ***
!
!*** the subfile has been moved to the Delete directory. This option

***

!
!*** shall be discussed with the customer and included in the CCR form. ***
!
!**************************************************************************
!
!***************************************!
!*** 2.10 ALARM CATEGORY DATA ON AP1 ***!
!***************************************!
!*********************************************!
!*** 2.10.1 Definition of alarm categories ***!
!*********************************************!
mml
ALACP;
ALACC:ALCATNO=0,
ALACC:ALCATNO=1,
ALACC:ALCATNO=2,
ALACC:ALCATNO=3,
ALACC:ALCATNO=4,
ALACC:ALCATNO=5,
ALACC:ALCATNO=6,
ALACC:ALCATNO=7,
ALACC:ALCATNO=8,
ALACC:ALCATNO=9,
ALACC:ALCATNO=10,
ALACC:ALCATNO=11,
ALACC:ALCATNO=12,
ALACC:ALCATNO=13,
ALACC:ALCATNO=14,
ALACC:ALCATNO=15,
ALACP;

ALCAT="APZ",
ALCAT="APZ",
ALCAT="APZ",
ALCAT="APT",
ALCAT="APT",
ALCAT="APT",
ALCAT="APT",
ALCAT="APT",
ALCAT="POWER",
ALCAT="EXT",
ALCAT="EXT",
ALCAT="EXT",
ALCAT="EXT",
ALCAT="EXT",
ALCAT="EXT",
ALCAT="EXT",

DICAT=0;
DICAT=0;
DICAT=0;
DICAT=1;
DICAT=1;
DICAT=1;
DICAT=1;
DICAT=1;
DICAT=2;
DICAT=3;
DICAT=3;
DICAT=3;
DICAT=3;
DICAT=3;
DICAT=3;
DICAT=3;

!*********************************************!
!*** 2.10.2 Definition of alarm class data ***!
!*********************************************!
ALCLP;
ALCLC:ACLNO=0,ACL="A1";
ALCLC:ACLNO=1,ACL="A2";
ALCLC:ACLNO=2,ACL="A3";
ALCLC:ACLNO=3,ACL="O1";
ALCLC:ACLNO=4,ACL="O2";
ALCLP;
exit;
!*************************************************!
!*** 2.10.3 External Alarm Receiver Data ON AP1***!
!*************************************************!
!******************************************************!
!*** Ref: CCR form, External Alarm Receiver Data
***!
!******************************************************!
!*********************************************************************!
!*** OPI: 'External Alarm Receiver in AP, Connect'.
***!
!***
***!
!*** This is site dependent.
***!
!*** The site engineer must check the cable connection and discuss ***!
!*** with customer or refer to the CCR Form.
***!
!*********************************************************************!
!*** Note:
exaldef -s
exaldef -s
exaldef -s
exaldef -s

Check for the right exal positions in the CCR Form ***!
"POWER ALARM" -S "PDF FAILURE"
-C 8 -c 0 -o yes exal-1-4
"EXT. ALARM" -S "AIR CONDITION 1" -C 15 -c 0 -o no exal-1-6
"EXT. ALARM" -S "AIR CONDITION 2" -C 15 -c 0 -o no exal-1-7
"EXT. ALARM" -S "INTRUDER ALARM" -C 15 -c 0 -o yes exal-1-8

!*** List the defined alarm receivers ***!

exalls -l
!*** Deblock the defined alarm receivers ***!
exaldeblk exal-1-4
exaldeblk exal-1-6
exaldeblk exal-1-7
exaldeblk exal-1-8
!**************************************************!
!*** 2.11 Alarm-Display Data, Definition on AP1 ***!
!**************************************************!
!*******************************************************!
!*** OPIs: 'Alarm-Display in AP, Connect' and
***!
!*** 'Remote Alarm-Display in AP, Define'.
***!
!*******************************************************!
!*************************************************************!
!*** In APG43 the Alarm Display is defined to supervise
***!
!*** the local exchange. On top of that in
***!
!*** APG43 there is a possibility to either supervise
***!
!*** remote exchanges (as subordinates) or to send the
***!
!*** alarm status to superior exchange (OMC)
***!
!*** This new possibilities are defined as examples below. ***!
!*************************************************************!
!D!
!D!
!D!
!D!
!D!
!D!
!D!

!********************************************!
!*** 2.11.1 Removal of ALI 0 (if defined) ***!
!********************************************!
mml
ALALP;
ALBLI:ALI=0;
ALALE:ALI=0;
!****************************************!
!*** 2.11.2 Definition of Alarm host ***!
!****************************************!

!*** Check if Alarm host is defined:

***!
!*** APPL=ALARMHOST in the IOCDP printout. ***!
!N! mml
IOCDP;
!*** Define the Alarm host if necessary. ***!
IOCDI:APPL=ALARMHOST, NUM=1;
!******************************************!
!*** 2.11.3 Definition of Alarm Display ***!
!******************************************!
!**********************************************!
!*** Ref: CCR form, Alarm Display Settings ***!
!**********************************************!
!*** List the Alarm Display properties ***!
exit;
aldpls
!**********************************************************************!
!********************* ADDITIONAL COMMANDS ***************************!
!**********************************************************************!
!***
***!
!*** The default values presented in aldpls printout can be used. ***!
!*** If change is required, use command aldpdef:
***!
!***
***!
!*** aldpdef -l lampprop
***!
!*** [ -1 alcat] [ -2 alcat] [ -3 alcat] [ -4 alcat]
***!
!***
***!
!*** aldpdef -s soundprop
***!
!*** [ -a sd] [ -b sd] [ -c sd] [ -d sd] [ -e sd ]
***!
!***
***!
!**********************************************************************!
!********************* ADDITIONAL COMMANDS, END***********************!
!**********************************************************************!
!*** Definition of On-site Alarm display with default properties ***!
alddef ald-1
!*** Definition of Remote Alarm display - sends alarm status to ***!
!*** superior exchange.
***!
alddef -a 164.55.66.88 -p 7011 ALD-61
!*** Definition of Alarm display for subordinate exchange (shows ***!
!*** the status of remote subordinate exchange).
***!
alddef -p 7011 ALD-11
!*********************************************!
!*** 2.11.4 Alarm Display test and deblock ***!
!*********************************************!
!****************************!
!*** Alarm display, List ***!
!****************************!
aldls
!***************************!
!*** Alarm-Display, Test ***!
!***************************!
!*** Begin test ***!
aldblk ald-1
aldblk ald-61
aldtest -b ald-1
aldtest -b ald-61
!*** End test ***!
aldtest -e ald-1
aldtest -e ald-61
!******************************!
!*** Alarm-Display, Deblock ***!
!******************************!
alddeblk ald-1
alddeblk ald-61
!***************************************************!
!*** 2.12 Activate Command Log Function on APG43 ***!
!***************************************************!
!*** Check that the file RELCMDHDF is defined on APG43. ***!
cpfls -ls RELCMDHDF
!*** Activate command log function. ***!
mml
SYCLI;
exit;
!**********************************************************************!
!********************* ADDITIONAL COMMANDS ***************************!
!**********************************************************************!
!***
***!
!*** If the result printout COMMAND LOG ACTIVATION RESULT gives
***!
!*** FAULT CODE 93 "NO SUBFILE DEFINED", a subfile has to be
***!
!*** created with command SYCSI.
***!
!***
***!
!*** Define command log subfile:
***!
!***
***!
!*** SYCSI;
***!
!***
***!
!**********************************************************************!
!********************* ADDITIONAL COMMANDS, END***********************!
!**********************************************************************!
!*************************************************!
!*** 2.13 Activate Audit Log Function on APG43 ***!
!*************************************************!
!*****************************************************************!
!*** Ref: CCR form, Additional Parameters, Audit Log function ***!
!*****************************************************************!
alogact
!************************************************************!
!*** 2.14 Activate Heart Beat and Sending of Alarm Status ***!
!************************************************************!
!*** Initiate sending of the heartbeat signal. ***!
mml
ALHBI;
!*** Start sending of alarm status ***!
ALSTI;
!**************************!
!*** 2.15 Exchange Name ***!
!**************************!
!*** Change the exchange name. ***!
!IOEXC:EXCHANGE="xxxxxxx";
exit;
!******************************************!
!*** 2.16 APG Time zone settings ON AP1 ***!
!******************************************!
!*** Check the current time settings in the APG ***!
mtzln -p
!*** Check the current time settings in CP ***!
mml
CACLP:ALL;
exit;
!*** List the defined time zones on the APG43 ***!
tzls
!****************************************!
!*** Set the zone supervision(TMZ=0) ***!
!****************************************!
!*******************************************************!
!*** Ref: CCR form, Node Start-up Configuration AP1 ***!
!*******************************************************!
!C! mtzln -f "(GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna" 0
!**********************************************!
!*** 2.17 Configuring STS for APG 40 ON AP1 ***!
!**********************************************!
!*************************************************************!
!*** NOTE: The STS configuration below is just an example. ***!
!*** The number of the object types, the structure of the ***!
!*** measurement programs and reports may differ depending ***!
!*** on the available features and customer requirements ***!
!*************************************************************!
!***********************************!
!*** 2.17.1 APZ Settings for STS ***!
!***********************************!
!*** STS makes requests to Block LAVS on the CP for counter data. ***!
mml
SAAEP:SAE=ALL,BLOCK=LAVS;
SAAII:SAE=809,BLOCK=LAVS,NI=16384;
SAAII:SAE=810,BLOCK=LAVS,NI=1024;
exit;
!***********************************!
!*** 2.17.2 APG Settings for STS ***!
!***********************************!
!*******************************************************************!
!***Check the database configuration with command stmotls.
***!
!***
***!
!***Use the output to determine which objects are to be included ***!
!***in the STS database.
***!
!***Below is just an example for your reference:
***!
!*******************************************************************!
!*** List the STS database configuration ***!
stmotls
!*** Terminate any ongoing Data Collection (if any) ***!
stmcc -e
!*** INITIATE CORRECTION AREA ***!
stmotd -i
!*** ACTIVATE STS OBJECT TYPES ***!
stmotd -a APDISKS APPLATFORM
stmotd -a CP RP EM EMG EMGPRS EMGSTAT EMRP
stmotd -a BSCSTAT BSCSTAT2 CELLSTAT CHASSIGNT DTISTAT EQIDCON MAPSIGIWRK
stmotd -a ODBINV OPTFEAT PAGING REGSERVICE RNCSTAT SECHAND SGSNSTAT
stmotd -a SHMSGSERV SMSGMSC SMSIWMSC GPRSGS MTRAFTYPE
stmotd -a RESTART SAE DATA TRAFFDEST1 TRAFFMEAS TRAFFSAE TRAFFTYPE1 LOSSROU
TE VLR
stmotd -a M3DATA M3SSNM M3ASPSM M3ASPTM M3MGMT M3ASSOC M3DEST1 M3DEST2 M3PE
RF MTSFB
stmotd -a TRUNKSUP TRUNKROUTE DYNTRUNKV LOCAREAST HLRSTAT NBRCELLST NBRMSCL
ST
stmotd -a C7SCSIGP C7SL1 C7SL2 C7SLSET C7RTSET C7ADJSLP C7OPC C7DPC C7OPCSI
O C7DPCSIO C7ODS
stmotd -a C7SCSUBSYS C7MESS C7SCPERF CALLFSERV CSRROUTE DIGPATH DIP DIPPRM
DIPSEC DISCCALL
stmotd -a ECPOOL EOS EXCHFAULT LOADREG LOAS LOASINCO LOASMISC SDIPHP SDIPLP
SNT
!*** Set Basic Recording Period (BRP) ***!
!*** In minutes, numeral 5 or 15
***!
stmotd -b 5 APDISKS APPLATFORM
stmotd -b 5 CP RP EM EMG EMGPRS EMGSTAT EMRP
stmotd -b 15 BSCSTAT BSCSTAT2 CELLSTAT CHASSIGNT DTISTAT EQIDCON MAPSIGIWRK
stmotd -b 15 ODBINV OPTFEAT PAGING REGSERVICE RNCSTAT SECHAND SGSNSTAT
stmotd -b 15 SHMSGSERV SMSGMSC SMSIWMSC GPRSGS MTRAFTYPE
stmotd -b 15 RESTART SAE DATA TRAFFDEST1 TRAFFMEAS TRAFFSAE TRAFFTYPE1 LOSS
ROUTE VLR
stmotd -b 15 M3DATA M3SSNM M3ASPSM M3ASPTM M3MGMT M3ASSOC M3DEST1 M3DEST2 M
3PERF MTSFB
stmotd -b 15 TRUNKSUP TRUNKROUTE DYNTRUNKV LOCAREAST HLRSTAT NBRCELLST NBRM
SCLST
stmotd -b 15 C7SCSIGP C7SL1 C7SL2 C7SLSET C7RTSET C7ADJSLP C7OPC C7DPC C7OP
CSIO C7DPCSIO C7ODS
stmotd -b 15 C7SCSUBSYS C7MESS C7SCPERF CALLFSERV CSRROUTE DIGPATH DIP DIP
PRM DIPSEC DISCCALL
stmotd -b 15 ECPOOL EOS EXCHFAULT LOADREG LOAS LOASINCO LOASMISC SDIPHP SDI
PLP SNT
!*** Check the changes made in the correction area before activating ***!
!*** NOTE: If necessary use stmotd -q, to discard changes
***!
stmotls -c
!*** COMMIT THE CORRECTION AREA ***!
stmotd -e
!*** INITIATE STS COLLECTION ***!
stmcc -i
!*** UPDATE TRANSLATION TABLE ***!
stmttu
!********************************************************!
!*** 2.17.3 File transfer of STS files, AP Responding ***!
!********************************************************!
!******************************************************!
!*** Ref: CCR form, Destination Configuration
***!
!******************************************************!
!*** Create directory where STS will be stored for Responding FTP ***!
mkdir K:\ftpvol\STS_Resp
!*** On both nodes ***!
!*** Node A ***!
vdcreate -n "Default FTP Site" -a STS_Resp -d K:\FTPvol\STS_Resp
!*** Node B ***!
vdcreate -n "Default FTP Site" -a STS_Resp -d K:\FTPvol\STS_Resp
!*** Define STS destination with file notification and type responding ***!
cdhdef -t FTPV2 -c r -f 164.55.66.77 -x 50010 -h STS_Resp STSDEST
!*** Check if destination is defined correctly ***!
cdhls -l STSDEST
!*** Verify the destination ***!
cdhver STSDEST
!*** Define destination set ***!
cdhdsdef STSDEST STSDEST
!*** List destination sets ***!
cdhdsls -l
!**************************************************************************
***************!
!********************* ADDITIONAL COMMANDS *******************************
***************!
!**************************************************************************
***************!
!***
***!
!*** ADDITIONAL OPTIONS FOR STS File transfer
***!
!*** File transfer of STS files, AP Initiating:
***!
!***
***!
!*** Define Destinations.
***!
!*** Initiating FTP to destination 164.44.55.66 is defined.
***!
!*** The files will be stored on the remote server under directories home/m
sc_vlr1/sts/***!
!*** APG FTP client will login as msc_vlr1 user.
***!
!*** Password prompt will be desplayed after the cdhdef command
***!
!*** to enter the remote password for msc_vlr1 user:
***!
!***
***!
!*** cdhdef -t ftpv2 -a 164.44.55.66 -r home/msc_vlr1/sts/ -c i -u msc_vlr1
-p STSDEST ***!
!***
***!
!*** List destination:
***!
!***
***!
!*** cdhls -l
***!
!***
***!
!*** Verify destination:
***!
!***
***!
!*** cdhver STSDEST
***!
!***
***!
!*** Define Destination set
***!
!*** Note: The destination name and the destination set name should
***!
!*** be identical. Otherwise the handling of OSS-SMIA tool is affected:
***!
!***
***!
!*** cdhdsdef STSDEST STSDEST
***!
!***
***!
!*** List destination sets:
***!
!***
***!
!*** cdhdsls -l
***!
!***
***!
!**************************************************************************
***************!
!********************* ADDITIONAL COMMANDS, END***************************
***************!
!**************************************************************************
***************!
!********************************************!
!*** 2.17.4 STS REPORT DEFINITIONS ON AP1 ***!
!********************************************!
!*************************************************************************!
!*** IMPORTANT: After Destinations and Destination sets are defined
***!
!*** there are two ways to continue with the STS measurement report
***!
!*** configuration.
***!
!*** If Ericsson OSS SMIA tool is going to be used, then there is no ***!
!*** need for Transfer Queue (c'afpdef), measurement report (c'stmrp) ***!
!*** and measurement program (c'stmmp)t definitions. They are going to ***!
!*** be created by the SMIA tool. In fact SMIA will ask for transfer ***!
!*** queue name and the specified one will be used. If already defined ***!
!*** transfer queue is specified in the SMIA tool, the STS job will
***!
!*** fail (Setup error).
***!
!*************************************************************************!
!*************************************************************************!
!*** The commands below are to be loaded in case that SMIA tool is not ***!
!*** used for configuring the STS measurements
***!
!*************************************************************************!
!****************************************!
!*** 2.17.4.1 Creation of directories ***!
!****************************************!
! Create the directories where the reports will be stored locally on !
! the APG43. Reports should be stored in a subdirectory under
!
! K:\STS\data\Deliverydir.
!
mkdir
mkdir
mkdir
mkdir
mkdir
mkdir
mkdir
mkdir
mkdir
mkdir
mkdir

K:\STS\data\DeliveryDir\APGmp
K:\STS\data\DeliveryDir\APZmp
K:\STS\data\DeliveryDir\APTmp1
K:\STS\data\DeliveryDir\APTmp2
K:\STS\data\DeliveryDir\APTmp3
K:\STS\data\DeliveryDir\APTmp4
K:\STS\data\DeliveryDir\APTmp5
K:\STS\data\DeliveryDir\APTmp6
K:\STS\data\DeliveryDir\APTmp7
K:\STS\data\DeliveryDir\APTmp8
K:\STS\data\DeliveryDir\APTmp9

!*********************************************!
!*** 2.17.4.2 Definition of transfer queue ***!
!*********************************************!
!******************************************************!
!*** Ref: CCR form, Destination Configuration
***!
!******************************************************!
!*** Define a transfer queue to the AFP function for the statistics files.
***!
afpdef
PQ STSDEST
afpdef
PQ STSDEST
afpdef
P1Q STSDEST
afpdef
P2Q STSDEST
afpdef
P3Q STSDEST
afpdef
P4Q STSDEST
afpdef
P5Q STSDEST

-s DELETE -d 60 -r 5 -t 10 -w K:\STS\data\DeliveryDir\APGmp STSAPGM

-s DELETE -d 60 -r 5 -t 10 -w K:\STS\data\DeliveryDir\APZmp STSAPZM
-s DELETE -d 60 -r 5 -t 10 -w K:\STS\data\DeliveryDir\APTmp1 STSAPTM
-s DELETE -d 60 -r 5 -t 10 -w K:\STS\data\DeliveryDir\APTmp2 STSAPTM
-s DELETE -d 60 -r 5 -t 10 -w K:\STS\data\DeliveryDir\APTmp3 STSAPTM
-s DELETE -d 60 -r 5 -t 10 -w K:\STS\data\DeliveryDir\APTmp4 STSAPTM
-s DELETE -d 60 -r 5 -t 10 -w K:\STS\data\DeliveryDir\APTmp5 STSAPTM
afpdef
P6Q STSDEST
afpdef
P7Q STSDEST
afpdef
P8Q STSDEST
afpdef
P9Q STSDEST

-s DELETE -d 60 -r 5 -t 10 -w K:\STS\data\DeliveryDir\APTmp6 STSAPTM

-s DELETE -d 60 -r 5 -t 10 -w K:\STS\data\DeliveryDir\APTmp7 STSAPTM
-s DELETE -d 60 -r 5 -t 10 -w K:\STS\data\DeliveryDir\APTmp8 STSAPTM
-s DELETE -d 60 -r 5 -t 10 -w K:\STS\data\DeliveryDir\APTmp9 STSAPTM

!***********************************************************!
!*** 2.17.4.3 Statistics and Traffic Measurement, Report ***!
!***********************************************************!
!*** The system will automatically create a reportID for each report. ***!
stmrp APGmp APDISKS APPLATFORM
stmrp APZmp CP RP EM EMG EMGPRS EMGSTAT EMRP
stmrp APTmp1 BSCSTAT BSCSTAT2 CELLSTAT CHASSIGNT DTISTAT EQIDCON MAPSIGIWRK
stmrp APTmp2 ODBINV OPTFEAT PAGING REGSERVICE RNCSTAT SECHAND SGSNSTAT
stmrp APTmp3 SHMSGSERV SMSGMSC SMSIWMSC GPRSGS MTRAFTYPE
stmrp APTmp4 RESTART SAE DATA TRAFFDEST1 TRAFFMEAS TRAFFSAE TRAFFTYPE1 LOSS
ROUTE VLR
stmrp APTmp5 M3DATA M3SSNM M3ASPSM M3ASPTM M3MGMT M3ASSOC M3DEST1 M3DEST2 M
3PERF MTSFB
stmrp APTmp6 TRUNKSUP TRUNKROUTE DYNTRUNKV LOCAREAST HLRSTAT NBRCELLST NBRM
SCLST
stmrp APTmp7 C7SCSIGP C7SL1 C7SL2 C7SLSET C7RTSET C7ADJSLP C7OPC C7DPC C7OP
CSIO C7DPCSIO C7ODS
stmrp APTmp8 C7SCSUBSYS C7MESS C7SCPERF CALLFSERV CSRROUTE DIGPATH DIP DIP
PRM DIPSEC DISCCALL
stmrp APTmp9 ECPOOL EOS EXCHFAULT LOADREG LOAS LOASINCO LOASMISC SDIPHP SDI
PLP SNT
!************************************************************************!
!*** 2.17.5 MP DEFINITIONS, Statistics & traffic measurement program ***!
!************************************************************************!

!*** Check the reportID for the report, defined by command stmrp, above: *
**!
stmrp -L -l
!*** Complete the stmmp-commands below with <reportID> fetched from stmrp-p
rintout above. ***!
!*** MP with Load File format (regular data files)
***!
!*** n=MPname, t=transfer queue, b=start time, 30=interval of MP: ***!
!stmmp
!stmmp
!stmmp
!stmmp
!stmmp
!stmmp
!stmmp
!stmmp
!stmmp

-a
-a
-a
-a
-a
-a
-a
-a
-a

-n
-n
-n
-n
-n
-n
-n
-n
-n

APGmp
APZmp
APTmp1
APTmp2
APTmp3
APTmp4
APTmp5
APTmp6
APTmp7

-r
-r
-r
-r
-r
-r
-r
-r
-r

-t
-t
-t
-t
-t
-t
-t
-t
-t

STSAPGMPQ
STSAPZMPQ
STSAPTMP1Q
STSAPTMP2Q
STSAPTMP3Q
STSAPTMP4Q
STSAPTMP5Q
STSAPTMP6Q
STSAPTMP7Q

-b
-b
-b
-b
-b
-b
-b
-b
-b

1600
1600
1600
1600
1600
1600
1600
1600
1600

30
30
30
30
30
30
30
30
30

<reportID>
<reportID>
<reportID>
<reportID>
<reportID>
<reportID>
<reportID>
<reportID>
<reportID>

!
!
!
!
!
!
!
!
!
!stmmp -a -n APTmp8 -r -t STSAPTMP8Q -b 1600 30 <reportID> !
!stmmp -a -n APTmp9 -r -t STSAPTMP9Q -b 1600 30 <reportID> !
!**************************************************************************
***************!
!********************* ADDITIONAL COMMANDS *******************************
***************!
!**************************************************************************
***************!
!***
***!
!*** MP with ASN.1 format
***!
!*** n=MPname, t=transfer queue, b=start time, 30=interval of MP:
***!
!***
***!
!*** stmmp -a -n APGmp -t STSAPGMPQ -z ASN.1 -b 0000 30 <reportID>
***!
!*** stmmp -a -n APZmp -t STSAPZMPQ -z ASN.1 -b 0000 30 <reportID>
***!
!*** stmmp -a -n APTmp1 -t STSAPTMP1Q -z ASN.1 -b 0000 30 <reportID>
***!
!*** stmmp -a -n APTmp2 -t STSAPTMP2Q -z ASN.1 -b 0000 30 <reportID>
***!
!*** stmmp -a -n APTmp3 -t STSAPTMP3Q -z ASN.1 -b 0000 30 <reportID>
***!
!*** stmmp -a -n APTmp4 -t STSAPTMP4Q -z ASN.1 -b 0000 30 <reportID>
***!
!*** stmmp -a -n APTmp5 -t STSAPTMP5Q -z ASN.1 -b 0000 30 <reportID>
***!
!*** stmmp -a -n APTmp6 -t STSAPTMP6Q -z ASN.1 -b 0000 30 <reportID>
***!
!***
***!
!*** List MP(s) in long format (MP is same as reportID):
***!
!***
***!
!*** stmmp -l -L <reportID>
***!
!***
***!
!**************************************************************************
***************!
!********************* ADDITIONAL COMMANDS, END***************************
***************!
!**************************************************************************
***************!
!************************************************!
!*** 2.18 Network Surveillance Function (NSF) ***!
!************************************************!
!**************************************************************************
*!
!*** Ref: CCR form, Additional parameters, Network Surveillance Function **
*!
!**************************************************************************
*!
!*** NSF is not applicable for Reference Project (Ref. 2). ***!
!*** Example of NSF configuration is presented below
***!
!**************************************************************************
*******************!
!********************* ADDITIONAL COMMANDS *******************************
*******************!
!**************************************************************************
*******************!
!***
***!
!*** (Ref: Application Information 2/155 18-CXC 137 1091/5)
***!
!***
***!
!*** NSF Activation:
***!
!***
***!
!*** If NSF is to be used, activate NSF by setting ACS_NSF_activeFlag to 1:
***!
!***
***!
!*** C:\>copy C:\Program Files\AP\ACS\conf\cxc1371091.par C:\temp\cxc13710
91.par
***!
!*** Start WordPad.
***!
!*** Start->Programs->Accessories->WordPad.
***!
!*** In the File menu, click Open.
***!
!*** Change Files of Type to:All Documents (*.*) Click to (AP)C:\temp Open
CXC1371091.par ***!
!*** Scroll down to ACS_NSF_activeFlag : 0;
***!
!*** Replace 0 with 1.
***!
!***
***!
!*** NSF Supervision data:
***!
!***
***!
!*** If necessary, edit all other parameters:
***!
!***
***!
!*** C:\>copy C:\Program Files\AP\ACS\conf\cxc1371091.par C:\temp\cxc13710
91.par
***!
!*** Start WordPad.
***!
!*** Start->Programs->Accessories->WordPad.
***!
!*** In the File menu, click Open.
***!
!*** Change Files of Type to:All Documents (*.*) Click to (AP)C:\temp. Open
CXC1371091.par ***!
!*** Scroll down to the parameters and set them according to the CCR form.
***!
!*** Replace 'x' with the right values:
***!
!*** ACS_NSF_pingPeriod : x;
***!
!*** ACS_NSF_routerResponse : x;
***!
!*** ACS_NSF_failovers : x;
***!
!*** ACS_NSF_resetTime : x;
***!
!***
***!
!***
***!
!*** In the File menu, click Save.
***!
!*** In the File menu, click New, Text Document, (Add the following line in
the new doc.) ***!
!*** C:\temp\cxc1371091.par
***!
!*** In the File menu, click Save As .. par.txt in C:\temp
***!
!*** Exit WordPad.
***!
!*** Start->Programs->Command Prompt
***!
!***
***!
!*** fchstart -p c:\temp\par.txt
***!
!***
***!
!**************************************************************************
*******************!
!********************* ADDITIONAL COMMANDS, END **************************
*******************!
!**************************************************************************
*******************!
!*****************************!
!*** 2.19 Public key Logon ***!
!*****************************!
!**************************************************************!
!*** Ref: CCR form, Additional parameters, Public key Logon ***!
!**************************************************************!
!*** In the Reference Project (Ref. 2), the location of public key is ***!
!*** the default directory. If other directory is desired, the below ***!
!*** example can be used
***!
!**************************************************************************
*!
!********************* ADDITIONAL COMMANDS *******************************
*!
!**************************************************************************
*!
!***

**

!*** For connections to port 52nnn, the PHA parameter

**

!*** MSS_User_Config_Directory in the parameter file

**

*!
*!
*!
!C! !*** C:\Program Files\AP\MCS\conf\cxc1371127.par is used.
**
*!
!***
**
*!
!*** Parameter: MSS_User_Config_Directory
**
*!
!*** Format:
**
*!
!*** string Specifies the dir where the user public keys and
**
*!
!***
authorization-file are located for pubkey auth. %D id user **
*!
!***
home dir, %U is user login name.
**
*!
!***
**
*!
!*** Follow OPI: APG40, Soft Function Change, Parameter, Change
**
*!
!***
**
*!
!*** Select edit parameter file
**
*!
!*** Choose MLSMSSBIN package to upgrade parameters
**
*!
!*** edit parameter MSS_User_Config_Directory by specifiyng the location **
*!
!*** of the public key
**
*!
!***
**
*!
!**************************************************************************
*!
!********************* ADDITIONAL COMMANDS, END **************************
*!
!**************************************************************************
*!
!********************************************!
!*** AP1 CONFIGURATION, END******************!
!********************************************!
!*******************************************!
!*** 3. Configuration AP2, Manual Steps ****!
!*******************************************!
!**************************************************************************
*************************************!
!************************************ MANUAL STEP ************************
*************************************!
!**************************************************************************
*************************************!
!***
***!
!*** Execute the following procedure first on the A-node and then repeat pr
ocedure on the B-node
***!
!***
***!
!*** Logon using Terminal server
***!
!*** Connect to node IP address
***!
!*** Log on to the node
***!
!*** Logon as:
!***
!***

***!
<Administrator>
***!
Password: <password>
***!
User:

!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 3.1 Keyboard layout
***!
!***
***!
!*** Ref: CCR form, Node Start-up Configuration AP2
***!
!***
***!
!*** From your local console, open the control panel by selecting:
***!
!*** Start -> Control Panel -> Regional and Language Options
***!
!*** Select tab LANGUAGES
***!
!*** Select DETAILS
***!
!*** Select ADD.
***!
!*** In the menu INPUT LANGUAGE, choose "English (United States)"
***!
!*** Mark tick box KEYBOARD LAYOUT/IME
***!
!*** Select "US"
***!
!*** Select OK
***!
!*** In the DEFAULT INPUT LANGUAGE select "English (United States) - US"
***!
!*** Select OK
***!
!*** In the pop-up window, select OK.
***!
!***
***!
!*** Change the value of the registry key that sets the default keyboard la
yout to the required
***!
!C! !*** language option (US in this case), using the following command by sele
cting
***!
!N! !** Start -> Run -> and then type:
***!
!***
***!
!*** reg add HKEY_USERS\.DEFAULT\Keyboard Layout\Preload /v "1" /t REG_SZ /
d 0409 /f
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 3.2 Time Zone Settings
***!
!***
***!
!*** Ref: CCR form, Node Start-up Configuration AP2
***!
!***
***!
!*** From your local console, open the Date/Time Properties by double-click
ing on the clock indicator
***!
!*** in the Windows 2003 taskbar.
***!
!*** Select taqb TIME ZONE.
***!
!*** Click on the drop down menu and select the right time zone:
***!
!***
***!
!C! !*** (GMT+01:00) .........
***!
!***
***!
!*** Select OK
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 3.3 Legal notice, telnet Greeting Message
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Display of Legal Notice
***!
!***
***!
!*** See
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen, 3.4.3.1.2
***!
!***
***!
!*** The Telnet server can be configured to display a message when logging
on to the system.
***!
!***
***!
!*** Follow the instructions in User guide using command sfcexec
***!
!***
***!
!N! !*** Answere question 1, "copy files" NO
***!
!N! !*** Answere question 2, "edit files" YES
***!
!***
***!
!N! !*** Select the package containing the AES_TELNET_LEGAL_NOTICE parameter is
CXC 137 1187, TELSRVBIN.
***!
!***
***!
!*** Use following message
***!
!*** WARNING
***!
!*** You are about to access a private computer network.
***!
!*** Unauthorized access will be punished to the fullest extent possible un
der the law.
***!
!***
***!
!*** Select OK
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 3.4 Legal notice, ssh Greeting Message
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Display of Legal Notice
***!
!***
***!
!*** See also:
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen, 3.4.3.2.5
***!
!***
***!
!*** The SSH server can be configured to display a message when a user conn
ects to the system.
***!
!***
***!
!*** Open Notepad:
***!
!*** Start -> All Programs -> Accessories -> Notepad
***!
!***
***!
!*** Type the desired message:
***!
!***
***!
!*** ***************
***!
!*** *** WARNING ***
***!
!*** ***************
***!
!***
***!
!*** ************************************************************
***!
!*** *** You are about to access a private computer network. ***
***!
!*** *** Unauthorized access will be punished to the fullest ***
***!
!*** *** extent possible under the law.
***
***!
!*** ************************************************************
***!
!***
***!
!*** Name and save the file under c:\winnt\system32\.
***!
!*** The name of the default message file acs_acsc_message.txt can be used
***!
!C! !*** if the SSH legal notice message and terminal login (3.7)
***!
!N! !** will be the same as the Warning message.
***!
!***
***!
!*** Start the SSH Configuration tool:
***!
!*** Start -> All Programs -> F-Secure SSH Server -> Configuration
***!
!*** Select GENERAL
***!
!*** In the input field BANNER MESSAGE FILE,
***!
!*** specify the filename of the text file containing the message
***!
!*** (or press the browser button and select the file from there).
***!
!***
***!
!*** Note:
***!
!*** Do not delete or change the name of file acs_acsc_message.txt.
***!
!*** This file is needed for Warning message display.
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 3.5 Legal notice, ftp Welcome Message
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Display of Legal Notice
***!
!***
***!
!*** See also:
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen, 3.4.3.3.5
***!
!*** Application Information "Adjunct Computer Subsystem", 2/155 18-ANZ 222
43 Uen, 2.1.6
***!
!***
***!
!*** The FTP server can be configured to display a message to the user when
logging on to the system.
***!
!***
***!
!*** Start Internet Information Service (IIS) Manager:
***!
!*** Start -> Administrative Tools -> Internet Information Services (IIS) M
anager
***!
!***
***!
!*** Open the folder LOCAL COMPUTER
***!
!*** Open the folder FTP sites
***!
!*** Right click on DEFAULT FTP SITE
***!
!*** select PROPERTIES
***!
!*** Select tab MESSAGES
***!
!*** In the field WELCOME, specify the legal notice text:
***!
!***
***!
!*** WARNING
***!
!*** You are about to access a private computer network.
***!
!*** Unauthorized access will be punished to the fullest extent possible un
der the law.
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 3.6 Ftp Exit Message
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Display of Welcome messages
***!
!***
***!
!*** See also:
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen, 3.4.3.3.5
***!
!*** Application Information "Adjunct Computer Subsystem", 2/155 18-ANZ 222
43 Uen, 2.1.6
***!
!***
***!
!*** The FTP server can be configured to display a message to the user when
logging out
***!
!*** from the system.
***!
!***
***!
!*** Start Internet Information Service (IIS) Manager:
***!
!*** Start -> Administrative Tools -> Internet Information Services (IIS) M
anager
***!
!***
***!
!*** Open the folder LOCAL COMPUTER
***!
!*** Open the folder FTP sites
***!
!*** Right click on DEFAULT FTP SITE
***!
!*** select PROPERTIES
***!
!*** Select tab MESSAGES
***!
!***
***!
!*** When connected to AP Node A, specify the exit message in the field EXI
T:
***!
!***
***!
!*** Logged out from MSC1 AP Node A.
***!
!***
***!
!*** When connected to AP Node B, specify the exit message in the field EXI
T:
***!
!***
***!
!*** Logged out from MSC1 AP Node B.
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 3.7 Legal notice, terminal logon Greeting Message
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Display of Legal Notice
***!
!***
***!
!*** It is possible to define a legal notice to be displayed before logon a
ccording to the
***!
!*** instructions below.
***!
!***
***!
!*** Start the Registry Editor:
***!
!*** Start -> Run -> Type regedit and press OK.
***!
!***
***!
!*** Go to key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Ver
sion\Winlogon
***!
!***
***!
!*** Right click on LegalNoticeCaption, choose Modify and type the desired
caption in the Value
***!
!*** data field:
***!
!***
***!
!*** WARNING
***!
!***
***!
!*** Right click on LegalNoticeText, choose Modify and type the desired tex
t in the Value
***!
!*** data field:
***!
!***
***!
!*** Do Not Attempt to logon to this system unless you are an authorized us
er.
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 3.8 Warning message, terminal logon Greeting Message
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Display of Warning Message
***!
!***
***!
!*** See also:
***!
!*** OPI "AP, Authority, Administer", 4/154 31 CRZ 222 05 Uen
***!
!***
***!
!*** Go to directory c:\winnt\system32
***!
!*** Open file acs_acsc_message.txt
***!
!*** Insert text, as follows:
***!
!***
***!
!*** "This system is restricted solely to "Company_Name" authorized users f
or legitimate
***!
!*** business purposes only. The actual or attempted unauthorized access, u
se, or
***!
!*** modification of this system is strictly prohibited by "Company_Name".
***!
!*** Unauthorized users are subject to Company disciplinary proceedings and
/or criminal a
***!
!*** nd civil penalties under state, federal, or other applicable domestic
and foreign
***!
!*** laws. The use of this system may be monitored and recorded for adminis
trative and
***!
!*** security reasons. Anyone accessing this system expressly consents to s
uch monitoring
***!
!*** and is advised that if monitoring reveals possible evidence of crimina
l activity,
***!
!*** "Company_Name" may provide the evidence of such activity to law enforc
ement
***!
!*** officials."
***!
!***
***!
!*** Save and exit file acs_acsc_message.txt
***!
!***
***!
!***
***!
!*** Go to directory c:\winnt\system32
***!
!*** Open file acs_acsc_question.txt
***!
!*** Insert text, as follows:
***!
!***
***!
!*** "Are you an authorized user? (Yes/No)"
***!
!***
***!
!*** Save and exit file acs_acsc_question.txt
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 3.9 Setting up Master User Domain (MUD) trust (if to be used)
***!
!***
***!
!*** Prerequisites: A Windows Domain Server to be used as MUD server
***!
!***
***!
!*** References:
***!
!*** CCR form, Node Start-up Configuration AP2
***!
!*** CCR form, Initial user accounts, Master User Domain
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen
***!
!***
***!
!*** Follow the step-by-step instruction presented in the User Guide,
***!
!*** "Security Administration of the APG43", 2/198 17-ANZ 222 43 Uen chapte
r 3.4.2.
!***

***!

***!
!*** The relevant values to be entered are found in the following CCR forms
:
***!
!***
***!
!*** "Node Start-up Configuration AP2"
***!
!*** (Cluster Name, Domain Name, Node Names (node A & B), IP Addresses (clu
ster, node A, node B),
***!
!*** Master User Domain Server, etc)
***!
!***
***!
!*** "Initial user accounts, Master User Domain"
***!
!*** (Initial Password, Master User Domain usergroup, Local usergroups, etc
)
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 3.10 Setting up Convenience groups (if to be used)
***!
!***
***!
!*** Ref: CCR form, Initial user accounts, Convenience groups
***!
!***
***!
!*** See also:
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen, 3.2.9
***!
!***
***!
!*** If it's found that a certain category of users always belong to the sa
me groups it
***!
!*** possible to create a Global group that is given membership in the Loca
l groups and
***!
!*** give the users membership to the Global group instead, this also remov
es the
***!
!*** necessity for the Domain Users group.
***!
!***
***!
!*** Start:
***!
!*** Start -> Administrative Tools -> Active Directory Users and Computers.
***!
!N! !*** Open local computer
***!
!*** Select folder USERS
***!
!C! !*** From the actions menu (Right click), choose NEW -> GROUP
***!
!*** Enter GROUP NAME:
***!
!***
***!
!*** Billing_Usr_Group
***!
!***
***!
!*** In GROUP SCOPE, tick Global Group
***!
!*** In GROUP TYPE, tick Security
***!
!*** Press OK.
***!
!***
***!
!*** Global group is created.
***!
!***
***!
!*** Select the newly created group
***!
!C! !*** From the actions menu (right click), choose PROPERTIES
***!
!*** In the field DESCRIPTION, write:
***!
!***
***!
!*** Access for Billing/RTR administration. APG access only
***!
!***
***!
!*** To grant the group membership in the desired local groups, go to
***!
!*** tab MEMBER OF
***!
!*** Press ADD.
***!
!*** Type the names, separated with semicolons, of the
***!
!*** groups which the global group should be member of:
***!
!***
***!
!*** ACSADMG;AESADMG
***!
!***
***!
!*** Press OK.
***!
!***
***!
!**************************************************************************
*************************************!
!***
***!
!*** 3.11 Automatic termination of inactive user sessions
***!
!***
***!
!*** Ref: CCR form, APG GUI Settings, Session settings
***!
!***
***!
!*** See also:
***!
!*** User Guide "Security Administration of the APG43", 2/198 17-ANZ 222 43
Uen,
***!
!*** 3.4.3.1.1, 3.4.3.2.5, 3.4.3.3.4, 3.4.3.8.2
***!
!***
***!
!*** --------***!
!***
***!
!*** TELNET:
***!
!*** Start the Telnet configuration tool:
***!
!C! !*** Follow user guide 3.4.3.1.1 using command sfcexec
***!
!N! !*** Answere question 1, "copy files" NO
***!
!N! !*** Answere question 2, "edit files" YES
***!
!***
***!
!N! !*** Select the package containing the AES_TELNET_LOGOFF_TIMEOUT parameter
is CXC 137 1187, TELSRVBIN.
***!
!***
***!
!*** --------***!
!***
***!
!*** SSH/SFTP:
***!
!*** Start the SSH Configuration tool:
***!
!*** Start ->Programs -> F-Secure SSH Server -> Configuration
***!
!***
***!
!*** Select GENERAL
***!
!*** In the field IDLE TIMEOUT (SECONDS), type:
***!
!***
***!
!*** 1200
***!
!***
***!
!N! !*** Press Apply
***!
!*** Press OK
***!
!***
***!
!*** ---------
***!
!***
***!
!*** FTP:
***!
!*** Start the Internet Information Services (IIS) Manager:
***!
!*** Start -> Administrative Tools -> Internet Information Services (IIS) M
anager.
***!
!*** Open the folder LOCAL COMPUTER
***!
!*** Open the folder FTP sites
***!
!*** Select DEFAULT FTP SITE
***!
!*** From the Action menu, chose PROPERTIES
***!
!*** In the field CONNECTION TIMEOUT (IN SECONDS), type:
***!
!***
***!
!*** 600
***!
!***
***!
!*** Press OK
***!
!***
***!
!*** --------***!
!***
***!
!*** Terminal Services:
***!
!*** Start Terminal Services:
***!
!*** Start -> Administrative Tools
***!
!*** Select Domain Controllers under Group Policy Management -> Forest:<dom
ain name>
***!
!*** -> Domains -> <domain name>
***!
!***
***!
!*** Under the tab LINKED GROUP POLICY OBJECTS, right click on DEFAULT DOMA
IN POLICY
***!
!*** Select EDIT
***!
!*** This will open up the Group Policy Object Editor.
***!
!***
***!
!*** Under Default Domain Controllers Policy [<hostname>] Policy ->
***!
!*** Computer Configuration -> Administrative Templates -> Windows Componen
ts ->
***!
!*** Terminal Services -> Sessions,
***!
!*** Select SETS A TIME LIMIT FOR ACTIVE BUT IDLE TERMINAL SERVICES SESSION
S

***!
!***

***!
!*** From the Action menu, chose PROPRTIES
***!
!*** Tick box ENABLED
***!
!*** in the dropdown menu IDLE SESSION LIMIT, choose:
***!
!***
***!
!*** 30 minutes
***!
!***
***!
!*** (Since this is a group policy that affects all domain controllers, the
change
***!
!*** will automatically be applied to both nodes in the APG43 cluster)
***!
!***
***!
!N! !*** Press OK
***!
!***
***!
!N! !*** Close application.
***!
!***
***!
!**************************************************************************
*************************************!
!************************************ MANUAL STEP, END *******************
*************************************!
!**************************************************************************
*************************************!
!*****************************************!
!*** 4. Configuration AP2, Commands ******!
!*****************************************!
!****************************************!
!*** 4.1 DEFINITION OF OSS USER ON AP2***!
!****************************************!
!************************************************************************!
!*** Ref: CCR form, Initial user accounts, Local accounts on AP2
***!
!************************************************************************!
net user ossadm Ossuserpsw1 /add
!*** Add the OSS user to the necessary local groups ***!
net localgroup ACSUSRG ossadm /add
net localgroup CDHFTPUSRG ossadm /add
net localgroup AESADMG ossadm /add
net localgroup FTPUSRG ossadm /add
net localgroup CPUSRG ossadm /add
!*** For APG43 remote FCH ***!
net localgroup Administrators ossadm /add
!*******************************************************!
!*** 4.2 DEFINITION OF USERS FOR GLOBAL GROUPS ON AP2***!
!*******************************************************!
!******************************************************************!
!*** Ref: CCR form, Initial user accounts, Convenience groups ***!
!******************************************************************!
net user billinguser1 Billingpsw1 /add
net user billinguser2 Billingpsw2 /add
!**********************************************************************!
!********************* ADDITIONAL COMMANDS ***************************!
!**********************************************************************!
!***
***!
!*** Print information about all users defined in the system:
***!
!***
***!
!*** UserDump
***!
!***
***!
!**********************************************************************!
!********************* ADDITIONAL COMMANDS, END***********************!
!**********************************************************************!
!***********************************!
!*** 4.3 FTP/SMO SETTINGS ON AP2 ***!
!***********************************!
!*** Check for common parameters/environment ***!
set
!*** Set path for access to vital commands if needed ***!
!N! path=%path%;C:\Program Files\AP\ACS\bin
path=%path%;C:\Program Files\AP\AES\bin
!N! path=%path%;C:\Program Files\AP\APIO\bin
!N! path=%path%;C:\Program Files\AP\CPHW\bin
!N! path=%path%;C:\Program Files\AP\CPS\bin
!N! path=%path%;C:\Program Files\AP\FMS\bin
!N! path=%path%;C:\Program Files\AP\MAS\bin
!N! path=%path%;C:\Program Files\AP\MCS\bin
!N! path=%path%;C:\Program Files\AP\OCS\bin
!N! path=%path%;C:\Program Files\AP\PES\bin
!N! path=%path%;C:\Program Files\AP\SGS\bin
!N! path=%path%;C:\Program Files\AP\STS\bin
!*** Get server name ***!
ftpls
!***
!***
!***
!***
!***
vdls

Server Name "Default FTP Site"

IP Address: Port: ":21:"
List virtual directories:
Usage: vdls -n ServerName
Check if virtual smo directory
-n "Default FTP Site"

***!
***!
***!
***!
exists ***!

!*** Check if phisycal smo directory exists ***!

dir K:\fms\data\tmp\smo
!*** If not there, create the physical smo directory ***!
mkdir K:\fms\data\tmp\smo
!*** If not already done, make the smo directory virtual ***!
!*** Usage:
***!
!*** vdcreate -n ServerName -a AliasName -d PhysicalPath ***!
vdcreate -n "Default FTP Site" -a smo -d K:\fms\data\tmp\smo
!*****************************************!
!*** 4.4 Charging Data Handling ON AP2 ***!
!*****************************************!
!*******************************************************!
!*** 4.4.1 Default Configuration of Record transfer ***!
!*******************************************************!
!*** Create the RTR directory if not already done ***!
mkdir K:\Acs\data\Rtr
!C! !*** IMPORTANT: Parameter ACS_RTRBIN_Home in CXC1371137.par ***!
!*** should be changed to "K:\ACS\data\RTR"
***!
!N! !*** File is found under C:\program files\ap\acs\conf
***!
!*** List the default RTR settings ***!
rtrls -d
!*** Check the message store for name, site and size ***!
phaprint -t ACS_ACABIN_MessageStores
!*********************************************!
!*** 4.4.2 FILE BASED TRANSFER, RESPONDING ***!
!*********************************************!
!***********************************************!
!*** Ref: CCR form, Charging configuration ***!
!***********************************************!
!***
!***
!***
!***
!***
!***
!***

Create a virtual directory. For a responding destination

a Virtual Directory (VD) shall be defined. The VD is the
entry point when a mediator connects to APG43 with FTPv2
Responding.
Important: The virtual directory should be specified
after K:\Acs\Data\ and should not have name RTR.
This command shall be executed on an active node.

***!
***!
***!
***!
***!
***!
***!

mkdir K:\Acs\Data\Billing
!*** Create a virtual directory on the FTP site. The commands ***!
!*** must be executed on both nodes.
***!
!*** Noda A ***!
vdcreate -n "Default FTP Site" -a BILLING -d K:\ACS\Data\Billing
!*** Noda B ***!
vdcreate -n "Default FTP Site" -a BILLING -d K:\ACS\Data\Billing
!**************************!
!*** Define Destination ***!
!**************************!
cdhdef -t ftpv2 -c r -k yes -h BILLING -f 164.44.55.66 -x 50010 RTRDEST
!N! !*** List destinations ***!
!N! cdhls -l
!*** Verify the destination setup ***!
cdhver RTRDEST
!******************************!
!*** Define Destination Set ***!
!******************************!
cdhdsdef RTRDEST RTRDEST
!N! !*** List destination sets ***!
!N! cdhdsls -l
!*************************************************!
!*** Define AP File Processing Transfer Queue. ***!
!*************************************************!
afpdef -r -1 -t 1800 -d 1440 -n MSCVLR1_billing_ -g FyymmddHHMMSSpppp -j Lo
cal RTRTQ RTRDEST
!********************************************!
!*** 4.4.3 Definition of Record transfer ***!
!********************************************!
!***********************************************!
!*** Ref: CCR form, Charging configuration ***!
!***********************************************!
!*** Check the CP settings
***!
!*** NOTE: mml-session can only be done on AP1 ***!
mml
CHOPP;
!*** initiate the AP interface for charging output ***!
CHOPI:BSIZE=4;
exit;
!*** Create RTR Transfer Queue ***!
!*** CHS is the message store, cp0ex is the CP site ***!
rtrdef -a RTRTQ CHS cp0ex
!*** Change features of a transfer queue output definition.
!*** The size of the file will be 2 kbytes. New file will
!*** be created every 15min. Statistics will be generated
!*** every day at midnight and the statistic counters will
!*** not be reset.
rtrch -h 2048 -j 900 -k 00:00 -l NO CHS cp0ex

***!
***!
***!
***!
***!

!*** Print cdh and rtr configuration. ***!

cdhls
cdhdsls
afpls
rtrls
!*************************************************************************!
!********************* ADDITIONAL COMMANDS ******************************!
!*************************************************************************!
!***
***!
!*** ADDITIONAL OPTIONS FOR CHARGING SETUP
***!
!***
***!
!*************************************************************************!
!*** FILE BASED TRANSFER, INITIATING
***!
!*************************************************************************!
!*** Define BGW Destination. AP initiating the transfer:
***!
!cdhdef -a 164.23.34.45 -t FTPV2 -r home/billing/mscvlr1/ -c i -u MSCVLR1_A
P -s 2 -d 10 -p -g YES -o YES RTRDEST !
!*** Verify if Definition is setup correctly
!cdhver RTRDEST !

***!

!*** Define Destination Set

!cdhdsdef RTRDEST RTRDEST !

***!

!*** Define AP File Processing Transfer Queue.

***!
!afpdef -r 1 -t 1800 -d 1440 -n MSCVLR1_TTFile_ -g Fpppp -j Local RTRTQ RTR
DEST !
!*************************************************************************!
!*** BLOCK BASED TRANSFER
***!
!*************************************************************************!
!*** Example of realising the charging output using FTPV2 Initiating
!*** Define BGW Destination. Transfer type BGWRPC.
!cdhdef -a 164.44.55.66 -t BGWRPC -s 2 -m 2000 RTRDBODEST !

***!
***!

!*** Define Destination set

!cdhdsdef RTRDBODEST RTRDBODEST !

***!

!dbodef -m yes RTRDBOTQ RTRDBODEST !

!rtrdef -b RTRDBOTQ CHS Cp0ex !
!rtrch -a 4096 -e 60 -k 00:00 -l NO CHS cp0ex !
!*** Print cdh configuration.
!cdhls -l RTRDBODEST !
!cdhdsls -l RTRDBODEST !
!rtrls !
!dbols -l RTRDBOTQ !

***!

!*************************************************************************!
!********************* ADDITIONAL COMMANDS, END *************************!
!*************************************************************************!
!*****************************************!
!*** 4.5 APG Time zone settings ON AP2 ***!
!*****************************************!
!*** Check the current time settings in the APG ***!
mtzln -p
!*** Check the current time settings in CP
***!
!*** NOTE: mml-session can only be done on AP1 ***!
mml
CACLP:ALL;
!N! exit;
!*** If needed, set the APG clock according to the CP time settings ***!
!*** First list the time zones and choose the one corresponding to ***!
!*** the CP time
***!
tzls
!*****************************************!
!*** Set the zone supervision (TMZ=0) ***!
!*****************************************!
!*******************************************************!
!*** Ref: CCR form, Nose Start-up Configuration AP2 ***!
!*******************************************************!
mtzln -f "(GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna" 0
!********************************************!
!*** AP2 CONFIGURATION, END******************!
!********************************************!
!**********************************************************************!
!**************** CONFIGURATION FILE, END *****************************!
!**********************************************************************!