HP XP P9500 Hitachi Dynamic Link Manager Software User Guide for VMWare (HIT52 - Page 61

Setting Up Integrated Traces, Table 3-6 Default and Recommended Values for the Integrated Trace File

Page 61 highlights

After you have set up the collection of audit log data, use the following command to make sure that the setting has been specified correctly: >dlnkmgr -l view -sys -audlog Audit Log : on(6) Audit Log Category : all KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss > Setting Up Integrated Traces When you use HDLM, the activity logs of the HDLM command are output to the integrated trace information file(installation-drive:\Program Files# \HITACHI\HNTRLib2\spool\hntr2n.log(where n indicates a file number)) of the Hitachi Network Objectplaza Trace Library (HNTRLib2) installed on the remote management client. # For Windows 7 (x64) , Windows Server 2008, and Windows Vista (x64), Program Files is Program Files (x86). If a lot of integrated trace information is output, the older information might end up getting deleted in a very short amount of time. Also, if a large amount of integrated trace information is suddenly all output at the same time, any integrated trace information that is overflowing the buffer might not be saved into the integrated trace files. To save as much information as possible, change the settings for Hitachi Network Objectplaza Trace Library, increasing the integrated trace file size and buffer size. Note that if the values are too large, it will place a heavy load on the system. When determining these values, be sure to consider these operational tradeoffs. Table 3-6 Default and Recommended Values for the Integrated Trace File Settings on page 3-13 shows the default and recommended values for the integrated trace file settings. Table 3-6 Default and Recommended Values for the Integrated Trace File Settings Setting Default value Integrated trace file size Number of integrated trace files Buffer size per monitoring interval Monitoring cycle Buffer size per monitoring interval Number of messages to be output per Monitoring cycle 256 (KB) 4 10 (seconds) 64 (KB) 0 (seconds) Recommended value 4096 (KB) 8 5 (seconds) 256 (KB) 0 (seconds) Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for VMware(R)) 3-13

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188

After you have set up the collection of audit log data, use the following
command to make sure that the setting has been specified correctly:
>dlnkmgr -l view -sys -audlog
Audit Log
: on(6)
Audit Log Category
: all
KAPL01001-I The HDLM command completed normally. Operation name =
view, completion time =
yyyy
/
mm
/
dd
hh
:
mm
:
ss
>
Setting Up Integrated Traces
When you use HDLM, the activity logs of the HDLM command are output to
the integrated trace information file(
installation-drive
:\Program
Files
#
\HITACHI\HNTRLib2\spool\hntr2
n
.log
(where
n
indicates a file number)) of
the Hitachi Network Objectplaza Trace Library (HNTRLib2) installed on the
remote management client.
#
For Windows 7 (x64) , Windows Server 2008, and Windows Vista (x64),
Program Files
is
Program Files (x86)
.
If a lot of integrated trace information is output, the older information might
end up getting deleted in a very short amount of time. Also, if a large amount
of integrated trace information is suddenly all output at the same time, any
integrated trace information that is overflowing the buffer might not be saved
into the integrated trace files. To save as much information as possible,
change the settings for Hitachi Network Objectplaza Trace Library, increasing
the integrated trace file size and buffer size. Note that if the values are too
large, it will place a heavy load on the system. When determining these
values, be sure to consider these operational tradeoffs.
Table 3-6 Default and Recommended Values for the Integrated Trace File
Settings on page
3-
13
shows the default and recommended values for the
integrated trace file settings.
Table 3-6 Default and Recommended Values for the Integrated Trace File
Settings
Setting
Default value
Recommended
value
Integrated trace file size
256 (KB)
4096 (KB)
Number of integrated trace files
4
8
Buffer size per
monitoring
interval
Monitoring cycle
10 (seconds)
5 (seconds)
Buffer size per
monitoring interval
64 (KB)
256 (KB)
Number of
messages to be
output per
Monitoring cycle
0 (seconds)
0 (seconds)
Creating an HDLM Environment
3-13
Hitachi Dynamic Link Manager User Guide (for VMware(R))