Strange messages in syslog.log

[Robert Ngo]

Hi

I have receive some ticket from HP-UX server that i am monitoring with the following messages


server1 vmunix: 0/2/1/0/4/0.21 fcd_fcp

server022 vmunix: 0/4/0/0.22.0.0.0 fcparray

so i when on to check the syslog on both server and found the following entry in the log

Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0 fcparray
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.0 tgt
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.0.0 sdisk
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.1 tgt
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.1.0 sdisk
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.2 tgt
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.2.0 sdisk
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.3 tgt
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.3.0 sdisk
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.4 tgt
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.4.0 sdisk
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.5 tgt
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.5.0 sdisk
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.6 tgt
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.6.0 sdisk
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.7 tgt
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.7.0 sdisk
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.8 tgt
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.8.0 sdisk
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.9 tgt
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.9.0 sdisk
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.10 tgt
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.10.0 sdisk
Aug 18 11:47:35 server022 vmunix: 0/4/0/0.22.0.0.0.11 tgt
Aug 18 11:47:36 server022 vmunix: 0/4/0/0.22.0.0.0.11.0 sdisk
Aug 18 11:47:36 server022 vmunix: 0/4/0/0.22.0.0.0.12 tgt
Aug 18 11:47:36 server022 vmunix: 0/4/0/0.22.0.0.0.12.0 sdisk
Aug 18 11:47:36 server022 vmunix: 0/4/0/0.22.0.0.0.13 tgt
Aug 18 11:47:36 server022 vmunix: 0/4/0/0.22.0.0.0.13.0 sdisk
Aug 18 11:47:36 server022 vmunix: 0/4/0/0.22.0.0.0.14 tgt
Aug 18 11:47:36 server022 vmunix: 0/4/0/0.22.0.0.0.14.0 sdisk
Aug 18 11:47:36 server022 vmunix: 0/4/0/0.22.0.0.0.15 tgt
Aug 18 11:47:36 server022 vmunix: 0/4/0/0.22.0.0.0.15.0 sdisk
Aug 18 11:47:36 server022 vmunix: 0/4/0/0.22.0.255.0 fcpdev
Aug 18 11:47:36 server022 vmunix: 0/4/0/0.22.0.255.0.0 tgt
Aug 18 11:47:36 server022 vmunix: 0/4/0/0.22.0.255.0.0.0 sctl


Aug 18 11:46:51 server1 vmunix: 0/2/1/0/4/0.21 fcd_fcp
Aug 18 11:46:51 server1 vmunix: 0/2/1/0/4/0.21.128.0.0 fcd_vbus
Aug 18 11:46:51 server1 vmunix: 0/2/1/0/4/0.21.128.255.0 fcd_vbus
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22 fcd_fcp
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0 fcd_vbus
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.255.0 fcd_vbus
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.0 tgt
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.255.0.0 tgt
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.0.0 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.255.0.0.0 sctl
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.0.1 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.0.2 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.0.3 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.1 tgt
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.1.0 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.1.2 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.1.3 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.2 tgt
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.2.0 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.2.4 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.3 tgt
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.3.0 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.4 tgt
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.4.0 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.5 tgt
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.5.0 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.6 tgt
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.6.0 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.7 tgt
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.7.0 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.8 tgt
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.8.0 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.9 tgt
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.9.0 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.10 tgt
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.10.0 sdisk
Aug 18 11:46:55 server1 vmunix: 0/5/1/0/4/0.22.16.0.0.11 tgt

does these entry indicate some problem with the SAN enviroment or is it something else


Thanks

Robert Ngo

[Patrick Wallek]

Has the machine been rebooted recently?

Those appear to me to be normal boot messages.

[Robert Ngo]

the servers have not been rebooted since last month

[Michael Steele_2]

They do look pretty normal. No error has been recorded. But you can check you HBAs.

ioscan -funC fc

tdutil /dev/td#

STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > RAW SUMMARY

paste or attach results.

[Sean Dale]

There aren't any error messages there, no problems. Do you have the SAN directly attached or do you use a network switch? The reason I am asking is because we have a server that is connected via 2 switches and both HBAs are connected to the switches. You may be seeing the messages in the log due to the alternate paths to the SAN. I don't think an ioscan would log those, but, I think insf may have. Have you run insf recently? It installs special files for the new devices in the system. That is one possible reason why you see those messages in the log.

[Dave Hutton]

Those look like the usual for our servers connected to our SAN disks.
But it usually only says that after its booted.

uptime does show a month?

[IT_2007]

if you run ioscan, insf -e commands then syslog shows those commands for SAN devices. Somebody might have ran ioscan command. check root .sh_history for it. Those are not harmful anyway. Talk to SAN team if they assigned any new LUNs to the server.

[Sandman!]

These messages appear in the syslog file after executing ioscan in an attempt to discover new hardware...insf does not log messages to syslog.

cheers!