12.7.2  
Automatic Logging of Administration Procedures 
 

Definition  
All accesses to customer-related data in the HiPath 3000 are automatically logged in an area of the MMC (LOG area) reserved for this purpose. The information recorded includes who the user is, the data manipulated by the user, and the time. An authorized user (member of the "Revision" user group) can transfer the system data to a PC and assess it.

12.7.2.1  
Logging 
A log entry contains the following information:
 •   Date and time
 •   User name and user group
 •   Type of activity (format identification) and activity (command entry)

12.7.2.1.1  
Format Identification and Command Entry 
The following format information is logged:
 •   Assistant T (1)
All activities are logged, regardless of system access. The respective code with the most important parameters is recorded as the command entry (station/number, for example).
 •   Manager TC (2)
Same as Assistant T (1)
 •   Session Information (3)
The system access is logged, regardless of whether it is logged using Assistant T, HiPath 3000/5000 Manager E, or other systems. Possible command entries are:
A0-1 = Login procedure
A0-2 = Logout procedure
A0-3 = Unauthorized login attempt
 •   HiPath 3000/5000 Manager E Database (4)
Access to the database is logged using HiPath 3000/5000 Manager E. Possible command entries are:
A1-1 = Database read
A1-2 = Regeneration of CDB (Load CDB into the system)
A1-3 = Write database
 •   Program Systems (5)
APS transfers and system boots (first bootup, for example) are recorded. Possible command entries are:
- A2-1 = APSXF started
- A2-2 = APSXF ended
- A2-3 = APS boot (APS stamp also included)
 •   HiPath 3000/5000 Manager E Maintenance (6)
Maintenance activities which can be assigned with the following command entries are logged:
- B1-1 = Read error memory
- B1-2 = Delete error memory
- B2-1 = Out of service
- B3-1 = Read Direct Memory Access
- B3-2 = Write Direct Memory Access
- B4-1 = Delete base station status overload
- B4-2 = Delete base station restart
- B5-1 = Digital loopback change
- B6-1 = Trunk rolling change
- B7-1 = Read trunk status
- B8-1 = Delete trunk error counter
 •   Simulated or pseudo Assistant T format (7)
The HiPath 3000/5000 Manager E records the offline changes of a CDB as a "simulated" Assistant T command. For data areas subject to change by HiPath 3000/5000 Manager E, pseudo areas are generated. When loading an offline CDB into the system, the following simulated commands are logged as command entries:
C1 = Pseudo area "System parameter"
- C1-1 System fags/CMI
- C1-2 System intercept/AC
- C1-3 Tones and calls
- C1-4 Direction flag special (Variable direction#)
- C1-5 System settings
- C1-6 Host Link Interface
- C1-7 Relocate activation
C2 = Pseudo area "System timer"
- C2-1 System timer
C3 = Pseudo area "S0 configuration"
- C3-1 Station bus
- C3-2 Line supervision
- C3-3 Mode
C4 = Pseudo area "Lines"
- C4-1 Loop start parameter (Variable Slot/Line#)
C5 = Pseudo area "Digit analysis"
- C5-1 Internal number (Variable Stn#, Grp#)
- C5-2 Service codes
C6 = Pseudo area "Daylight saving time"
- C6-1 Daylight saving time
C7 = Pseudo area "Routes"
- C7-1 Routing flags (Variable Trk Grp#)
C8 = Pseudo area "Door setup"
- C8-1 Door setup (Variable door#)
C9 = Pseudo area "UCD flags"
- C9-1 UCD flags
C10 = Pseudo area "Delete system counter"
- C10-1 Delete system counter
 •   HiPath 3000/5000 Manager E online (8)
Archives from the log file and the user administration are logged. Possible command entries are:
- D1-1 = Archive
- D2-1 = New user
- D2-2 = Delete user
- D3-1 = Change password
Logging External Accesses (Solutions, Applications)  
Plus products used with "AMHOST" can only make limited changes. Because these changes "automatically" run simultaneously (Check In and Check Out for hotel solutions, for example), these are not logged. Only the session information (user name is "amhost") with the command entries "Login procedure" and "Logout procedure" are logged.  

12.7.2.2  
Issuing and Saving Log Data 
Data is automatically logged in an area (LOG area) on the MMC reserved for this purpose (HiPath 3000) or in a special directory (HiPath 5000). It cannot be switched off.
If approximately 80 % of the MMC log area capacity is exceeded, a Class A error is issued. This error is dealt with like all Class A errors and is displayed on the optiPoint Attendant as "Revisor Alarm."
The log should now be read out and archived, meaning it should be saved in an archive file (file extension = arc). If an archive is not created, the oldest data block is overwritten if there is a danger of overflow.
You can only issue log entries using HiPath 3000/5000 Manager E. You cannot retrieve the log entries from the system until you have logged on as a user with "Revisor" rights.

Archive  
If you request an archive (storage), the system checks whether or not there is already an archive file (file extension = arc). If it is a file with log data from a previous archive, the file must match the current customer. In case of a positive result, the system log entries are retrieved and attached to the existing data in the archive file. At the same time, the data in the system is deleted.
If malfunctions occur during this procedure (for example, line interruption), the entire procedure ends and the archive has to be restarted.
If no archive is requested, the revisor can retrieve, view, and print the log entries. However, log entries remain in the system.
You do not have to log on to the system to use the HiPath 3000/5000 Manager E to check archive files on the PC monitor. In this case, a password is not required.

Multimedia card  
When replacing the multimedia card, the following applies:
 •   If the memory area for logging data is empty, logging restarts.
 •   If the memory area for logging data is not empty, logging continues.

Example of a log printout  
The following assumption applies as an example: The first system boot up has taken place. Customer-specific programming was completed.
1050  
00-11-25 15:57:10  
rev(R)  
(6)D1-1  
Archive  
1051  
00-11-25 15:58:22  
rev(R)  
(3)A0-2  
Logout procedure  
1052  
00-11-26 09:20:15  
serv(S)  
(3)A0-1  
Login procedure  
1053  
00-11-26 09:21:35  
serv(S)  
(4)A1-1  
Database read  
1054  
00-11-26 09:21:52  
serv(S)  
(7)14-12-*(20)  
Station names  
1055  
00-11-26 09:22:45  
serv(S)  
(4)A1-3  
Write database  
1056  
00-11-26 09:23:25  
serv(S)  
(3)A0-2  
Logout procedure  
1057  
00-11-26 10:10:15  
pnkm(A)  
(3)A0-1  
Login procedure  
1058  
00-11-26 10:11:15  
pnkm(A)  
(2)14-12-"30"  
Station names  
1059  
00-11-26 10:11:35  
pnkm(A)  
(2)14-12-"31"  
Station names  
1060  
00-11-26 10:12:15  
pnkm(A)  
(3)A0-2  
Logout procedure  
1061  
00-11-27 11:20:30  
rev(R)  
(3)A0-1  
Login procedure  
The sample printout (without consideration of headers and footers) refers to the following information concerning administration procedures:
 •   The Revisor ("rev" user in "R" (Revision) user group) has generated an initial archive.
 •   The Service ("serv" user in "S" (system maintenance) user group) has read out the system database, changed 20 station names, and rewritten them to the system.
 •   The Customer ("pnkm" user in "A" (Administration) user group) has changed two additional station names.
 •   The Revisor has retrieved the most recent log entries and printed them out.

HiPath 3000/5000 V9, Service Documentation, Issue 7   up Top
Disclaimer & Copyright   ID: P31003H3590S100017620   2012-06-25