IBM 2109 Service Guide - Page 98

syslogd configuration, Power-on self-test (POST)

Page 98 highlights

Enable and verify syslogd support: | Sr99:admin> syslogdIpAdd "10.0.0.10" | Committing configuration....done. | Sr99:admin> syslogdIpShow | syslog.IP.address.1: 10.0.0.10 | Sr99:admin> syslogdIpRemove "10.0.0.10' | Committing configuration....done. | Sr99:admin> syslogIpShow | No addresses configured Disable syslogd support: | Sr99:admin> syslogdIpRemove "10.0.0.10" | Committing configuration....done | Sr99:admin> syslogdIpShow | No addresses configured Figure 30. syslogd support syslogd configuration | The syslog configuration provides the syslogd with instructions on how to handle | different messages. Figure 31 and Figure 32 are example entries in a syslog | configuration file (/etc/syslog.conf), of how to store switch error messages stored | in different files. Refer to the syslog manual pages on your UNIX system for the full | documentation of the syslog configuration file. | Figure 31 shows the entry in /etc/syslog.conf that causes all messages from the | silkworm of UNIX priority warning or higher (switch severity LOG_WARNING or higher) | to be stored in the file/var/adm/silkworm file. local7.warning /var/adm/silkworm Figure 31. Example syslog configuration file entry | Figure 32 shows the entries in /etc/syslog.conf that cause the messages from the | silkworm of UNIX priority alert (switch severity LOG_CRITICAL) to be stored in the | file/var/adm/alert file, and all other messages from the switch to be stored in the | /var/adm/silkworm file. local7.alert local7.debug /var/adm/alert /var/adm/silkworm Figure 32. Example syslog configuration file entry The local7 prefix identifies the message from a switch. Note that usually a file must exist and have the proper permission in order for the syslogd to write to it. Power-on self-test (POST) When the switch is started, a series of commands are executed to test the switch. This procedure is called the POST. The fabric OS POST includes the following tests: ramTest - Bit write and read test of SDRAMS in the switch. 82 IBM SAN Fibre Channel Switch: 2109 Model S16 Installation and Service Guide

  • 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

syslogd configuration
The syslog configuration provides the syslogd with instructions on how to handle
different messages. Figure 31 and Figure 32 are example entries in a syslog
configuration file (
/etc/syslog.conf
), of how to store switch error messages stored
in different files. Refer to the syslog manual pages on your UNIX system for the full
documentation of the syslog configuration file.
Figure 31 shows the entry in
/etc/syslog.conf
that causes all messages from the
silkworm
of UNIX priority warning or higher (switch severity
LOG_WARNING
or higher)
to be stored in the
file/var/adm/silkworm
file.
Figure 32 shows the entries in
/etc/syslog.conf
that cause the messages from the
silkworm
of UNIX priority alert (switch severity
LOG_CRITICAL
) to be stored in the
file/var/adm/alert
file, and all other messages from the switch to be stored in the
/var/adm/silkworm
file.
The
local7
prefix identifies the message from a switch. Note that usually a file must
exist and have the proper permission in order for the syslogd to write to it.
Power-on self-test (POST)
When the switch is started, a series of commands are executed to test the switch.
This procedure is called the POST.
The fabric OS POST includes the following tests:
ramTest
- Bit write and read test of SDRAMS in the switch.
Enable and verify syslogd support:
Sr99:admin> syslogdIpAdd
10.0.0.10
Committing configuration
....
done.
Sr99:admin> syslogdIpShow
syslog.IP.address.1:
10.0.0.10
Sr99:admin> syslogdIpRemove
10.0.0.10
Committing configuration
....
done.
Sr99:admin> syslogIpShow
No addresses configured
Disable syslogd support:
Sr99:admin> syslogdIpRemove
10.0.0.10
Committing configuration
....
done
Sr99:admin> syslogdIpShow
No addresses configured
Figure 30. syslogd support
local7.warning
/var/adm/silkworm
Figure 31. Example syslog configuration file entry
local7.alert
/var/adm/alert
local7.debug
/var/adm/silkworm
Figure 32. Example syslog configuration file entry
82
IBM SAN Fibre Channel Switch: 2109 Model S16 Installation and Service Guide
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|