IBM SC30-3681-08 manual Sample Contents from Syslog News Info File, Msg

Using ELS

vA route from the source 2210 to the remote workstation was not in the routing table

vThe interface for the outbound UDP packet containing the ELS messages was not in the ªUpº state

Notice in that messages 311-313 did not get remote-logged. This is because an ARP request was outstanding and until the ARP response is received, all but the ®rst packet is dropped in the source 2210. Additionally, the ARP cache is cleared at a user-con®gured refresh rate, and a new ARP request is issued. To determine when this is occurring, you can remote log events ARP.002 and ARP.011 in addition to the primary ELS events of interest. Figure 11 on page 161 shows ARP events logged to the syslog_user_alert ®le that account for events 445 and 446, which were indicated as missing in Figure 9.

Nov 20 12:03:16 worksta01 root: THIS IS A TEST MESSAGE (news.info)

Nov 20 12:08:48 5.1.1.1 Msg [0310] from ** IBM / 2210 **: els: IP.022: add nt 192.9.200.0 int 192.9.200.20 nt 0 int Eth/0

(messages 311, 312, and 313 did not get remote-logged due to ARP request outstanding - see explanation in the text)

(messages 314 and 315 were logged to a separate file - see explanation in the text)

Nov 20		12:08:48 5.1.1.1	Msg [0316]	from ** IBM /	2210	**: els:	IP.068: routing cache cleared
Nov 20		12:08:48 5.1.1.1	Msg [0317]	from ** IBM /	2210	**: els:	IP.022: add nt 5.0.0.0 int 5.1.1.1 nt 5 int Eth/4
Nov	20	12:08:48 5.1.1.1	Msg [0318]	from ** IBM /	2210	**: els: SRT.017: Enabling SRT on port 5 nt 5 int Eth/4
(message 319 was logged			to a separate file)
Nov	20	12:08:48 5.1.1.1	Msg [0320]	from ** IBM /	2210	**: els:	IP.068: routing cache cleared

(120 messages not shown)

Nov 20 12:13:33 5.1.1.1 Msg [0441] from ** IBM / 2210 **: els: GW.022: Nt fld slf tst nt 3 int Eth/3

Nov 20 12:13:33 5.1.1.1 Msg [0442] from ** IBM / 2210 **: els: GW.022: Nt fld slf tst nt 6 int Eth/5

Nov 20 12:13:38 5.1.1.1 Msg [0443] from ** IBM / 2210 **: els: GW.022: Nt fld slf tst nt 11 int ISDN/0

(messages 444 and 447 were logged to a separate file)

(messages 445 and 446 did not get remote-logged due to ARP request outstanding)

Nov 20 12:13:50 5.1.1.1 Msg [0448] from ** IBM / 2210 **: els: GW.022: Nt fld slf tst nt 4 int PPP/0

Nov 20 12:13:50 5.1.1.1 Msg [0449] from ** IBM / 2210 **: els: IP.068: routing cache cleared

Nov 20 12:13:50 5.1.1.1 Msg [0450] from ** IBM / 2210 **: els: IP.058: del nt 4.0.0.0 rt via 0.0.0.4 nt 4 int PPP/0

Figure 9. Sample Contents from Syslog News Info File

If the initial ELS messages that are generated during and immediately after booting are of particular interest, then it is recommended that these messages also be displayed in the monitor queue, which is viewed with talk 2. Figure 10 on page 161 shows the talk 2 output including the initial messages that did not get remote-logged. Note that there is a message in the talk 2 output that indicates that the remote-logging facility is available. This does not indicate that a route exists to the remote workstation, nor that the associated interface is in the ªUpº state. It simply provides a reference point before which no messages can be successfully remote-logged.

Also notice that you can account for the messages that were missing (indicated in Figure 9 with ) in the talk 2 output.

160MRS V3.2 Software User's Guide