EMS problem

[Michał Wachowiak]

Hi all,

I've got a problem with EMS messages in my syslog. I've got a lot of below entries:

Dec 11 14:54:00 sac01 EMS [3328]: ------ EMS Event Notification ------ Value: "error" for Resource: "/net/interfaces/lan/status/lan9" (Threshold: = " 2") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 1434779831 -r /net/interfaces/lan/status/lan9 -a
Dec 11 14:54:20 sac01 EMS [3328]: ------ EMS Event Notification ------ Value: "error" for Resource: "/net/interfaces/lan/status/lan7" (Threshold: = " 2") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 1434779953 -r /net/interfaces/lan/status/lan7 -a
Dec 11 14:54:40 sac01 EMS [3328]: ------ EMS Event Notification ------ Value: "error" for Resource: "/net/interfaces/lan/status/lan0" (Threshold: = " 2") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 1434779709 -r /net/interfaces/lan/status/lan0 -a

There is no detailed information about it in event.log, and after executing command as requested:

/opt/resmon/bin/resdata -R 1434779709 -r /net/interfaces/lan/status/lan0 -a
resdata: /net/interfaces/lan/status/lan0 is an invalid resource name. Please specify a valid resource name.

And also:
resls /net/interfaces/lan/status/lan0
Contacting Registrar on sac01

NAME: /net/interfaces/lan/status/lan0
DESCRIPTION: None
TYPE: /net/interfaces/lan/status/lan0 is not a valid resource name

My network interfaces seems to work fine. Can anyone suggest how to deal with that problem?

Regards,
Michal

[Analyst]

Hi Michal,

Seems to be everything is working fine .but

Check the file for the configurations
/etc/rc.config.d/netconf, whether same parameters being set for lan0/7/9.

go for lanscan command and check the lan interface for any errors.

check for the H/W errors
ioscan -fnC lan.

Thanks,
Analyst.

[TTr]

> /net/interfaces/lan/status/lan0 is an invalid resource name

When did these errors start to appear? Do lan0, lan7, lan9 even exist? Check with ioscan as indicated above. Maybe they existed in the past nad are no longer there.

[Michał Wachowiak]

Those interfaces exist:

sac01:/root#lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/1/1/0/4/0 0x001A4BF532E4 2 UP lan2 snap2 1 ETHER Yes 119
0/1/1/0/4/1 0x001A4BF532E5 3 UP lan3 snap3 2 ETHER Yes 119
0/1/1/0/6/0 0x001A4BF532E6 4 UP lan4 snap4 3 ETHER Yes 119
0/1/1/0/6/1 0x001A4BF532E7 5 UP lan5 snap5 4 ETHER Yes 119
0/1/2/0/4/0 0x001A4BF531D0 6 UP lan6 snap6 5 ETHER Yes 119
0/1/2/0/4/1 0x001A4BF531D1 7 UP lan7 snap7 6 ETHER Yes 119
0/1/2/0/6/0 0x001A4BF531D2 8 UP lan8 snap8 7 ETHER Yes 119
0/1/2/0/6/1 0x001A4BF531D3 9 UP lan9 snap9 8 ETHER Yes 119
0/4/2/0 0x001A4B06E1A8 0 UP lan0 snap0 9 ETHER Yes 119
0/4/2/1 0x001A4B06E1A9 1 UP lan1 snap1 10 ETHER Yes 119
sac01:/root#ioscan -fnC lan
Class I H/W Path Driver S/W State H/W Type Description
========================================================================
lan 2 0/1/1/0/4/0 iether CLAIMED INTERFACE HP AB545-60001 PCI/PCI-X 1000Base-T 4-port 1000B-T Adapter
lan 3 0/1/1/0/4/1 iether CLAIMED INTERFACE HP AB545-60001 PCI/PCI-X 1000Base-T 4-port 1000B-T Adapter
lan 4 0/1/1/0/6/0 iether CLAIMED INTERFACE HP AB545-60001 PCI/PCI-X 1000Base-T 4-port 1000B-T Adapter
lan 5 0/1/1/0/6/1 iether CLAIMED INTERFACE HP AB545-60001 PCI/PCI-X 1000Base-T 4-port 1000B-T Adapter
lan 6 0/1/2/0/4/0 iether CLAIMED INTERFACE HP AB545-60001 PCI/PCI-X 1000Base-T 4-port 1000B-T Adapter
lan 7 0/1/2/0/4/1 iether CLAIMED INTERFACE HP AB545-60001 PCI/PCI-X 1000Base-T 4-port 1000B-T Adapter
lan 8 0/1/2/0/6/0 iether CLAIMED INTERFACE HP AB545-60001 PCI/PCI-X 1000Base-T 4-port 1000B-T Adapter
lan 9 0/1/2/0/6/1 iether CLAIMED INTERFACE HP AB545-60001 PCI/PCI-X 1000Base-T 4-port 1000B-T Adapter
lan 0 0/4/2/0 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
lan 1 0/4/2/1 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core

Entries started to appear few days ago after installing patch for HP software call OCSC 6.0. Server wasn't rebooted that day.

[TTr]

I don't know how deep OCSC goes into the lan hardware but probably reconfiguring EMS to re-inventory the lan interface is worth considering. The command is /etc/opt/resmon/lbin/monconfig, "man monconfig", and look into http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1003545

[Michał Wachowiak]

What's interesting, I disabled EMS using monconfig and those entries were still added...

[Michał Wachowiak]

I've discovered that following process writes to syslog those communicates: /etc/opt/resmon/lbin/lanmond

This monitor is not listed in EMS configuration. It's started by PID 1 but it's not listed in inittab. Can I restart it or kill it without impact on a system (I don't want to disable hardware notifications if my lan card dies)?

[Michał Wachowiak]

I resolved this by myself. Process p_client that is started from inittab is a watchdog for lanmond. I killed lanmond and it was started by p_client without creating problematic entries.

Thanks all for support.

[Michał Wachowiak]

I resolved problem by myself.