IBM 2109 Service Guide - Page 97

Message classification, Switch configuration

Get IBM 2109 - SAN Fibre Channel Switch Model S16 PDF manuals and user guides
UPC - 087944519355
View all IBM 2109 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 97 highlights

syslogd running on switch sw9 is sending log events to the UNIX machine called example. Figure 29 is an example of a No memory error generated by the shell. This is a severity 1 (LOG_CRITICAL) error. syslogd is configured to store the errors in the /var/adm/silkworm file. example% egrep sw9 /var/adm/silkworm Jul 11 16:48:25 sw9 1 0x103d8620 (tShell): Jul 11 16:48:19 Jul 11 16:48:25 sw9Error SYS-NOMEM, 1, No memory Jul 11 16:48:25 sw9 Traceback: Jul 11 16:48:25 sw9 _tl+0x40 (0x103a2030) Jul 11 16:48:25 sw9 _yystart+0x95c (0x1017128c) Jul 11 16:48:25 sw9 _yyparse+0x694 (0x10172dc4) Jul 11 16:48:25 sw9 _execute+0xdc (0x1014c06c) Jul 11 16:48:25 sw9 _shellTask+0x964 (0x1003aea4) Jul 11 16:48:25 sw9 _shellTask+0x198 (0x1003a6d8) Jul 11 16:48:25 sw9 _vxTaskEntry+0x10 (0x10114d14) Jul 11 16:48:25 sw9 Figure 29. Example of a no memory error generated by the shell Message classification | syslogd messages are classified according to facility and priority (severity code). | This allows a system administrator to take different actions depending on the error. | The action taken, based on the message facility and priority, is defined in the syslog | configuration file. See "Switch configuration" for examples of configurations. The switch uses the facility local7 for all error messages sent to the syslogd. | UNIX provides eight priorities, and the switch provides five severity codes (code | LOG_PANIC (0) causes a restart and is not sent to syslogd). The mapping between | the switch severity codes and the UNIX syslogd priorities is shown in Table 22, in | order of decreasing priorities. Table 22. syslogd message classifications Switch UNIX LOG_CRITICAL (1) alert LOG_ERROR (2) err LOG_WARNING (3) LOG_INFO (4) warning info LOG_DEBUG (5) debug Switch configuration Type the following command to start syslogd. syslogdIp | Entering the command with no parameter prints the IP address of the current target | syslogd machine. Entering an IP address of 0.0.0.0 disables the forwarding of error | messages to syslogd. Error messages are still logged internally to the switch, but | they are not forwarded to syslogd. Figure 30 on page 82 shows examples of | syslogd support. Chapter 7. Management tools 81

  • 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 running on switch sw9 is sending log events to the UNIX machine called
example
. Figure 29 is an example of a
No memory
error generated by the shell. This
is a severity 1 (
LOG_CRITICAL
) error. syslogd is configured to store the errors in the
/var/adm/silkworm
file.
Message classification
syslogd messages are classified according to facility and priority (severity code).
This allows a system administrator to take different actions depending on the error.
The action taken, based on the message facility and priority, is defined in the syslog
configuration file. See “Switch configuration” for examples of configurations.
The switch uses the facility local7 for all error messages sent to the syslogd.
UNIX provides eight priorities, and the switch provides five severity codes (code
LOG_PANIC (0)
causes a restart and is not sent to syslogd). The mapping between
the switch severity codes and the UNIX syslogd priorities is shown in Table 22, in
order of decreasing priorities.
Table 22. syslogd message classifications
Switch
UNIX
LOG_CRITICAL (1)
alert
LOG_ERROR (2)
err
LOG_WARNING (3)
warning
LOG_INFO (4)
info
LOG_DEBUG (5)
debug
Switch configuration
Type the following command to start syslogd.
syslogdIp <IP address of the syslogd machine>
Entering the command with no parameter prints the IP address of the current target
syslogd machine. Entering an IP address of
0.0.0.0
disables the forwarding of error
messages to syslogd. Error messages are still logged internally to the switch, but
they are not forwarded to syslogd. Figure 30 on page 82 shows examples of
syslogd support.
example% egrep sw9 /var/adm/silkworm
Jul 11 16:48:25 sw9 1 0x103d8620 (tShell): Jul 11 16:48:19
Jul 11 16:48:25 sw9Error SYS-NOMEM, 1, No memory
Jul 11 16:48:25 sw9 Traceback:
Jul 11 16:48:25 sw9 _tl+0x40 (0x103a2030)
Jul 11 16:48:25 sw9 _yystart+0x95c (0x1017128c)
Jul 11 16:48:25 sw9 _yyparse+0x694 (0x10172dc4)
Jul 11 16:48:25 sw9 _execute+0xdc (0x1014c06c)
Jul 11 16:48:25 sw9 _shellTask+0x964 (0x1003aea4)
Jul 11 16:48:25 sw9 _shellTask+0x198 (0x1003a6d8)
Jul 11 16:48:25 sw9 _vxTaskEntry+0x10 (0x10114d14)
Jul 11 16:48:25 sw9
Figure 29. Example of a no memory error generated by the shell
Chapter 7. Management tools
81
|
|
|
|
|
|
|
|
|
|
|
|
|