Missing netdiag1 driver, /dev/netlog, /dev/nettrace files

[Jack C. Mahaffey]

Did some patching today. Cannot see the netdiag1 driver in sam or the /dev/netlog or /dev/nettrace files.

Using 11.0 HP-UX.

Any suggestions?


Got following error in rc.log.

10715 NOTE: Executing insf to create new telnet ptys in /dev/pts.
10716 nettl : Warning: The device file /dev/nettrace and/or /dev/netlog is
10717 not present or cannot be opened. Continuing with the
10718 initialization of Trace/Log facility. Kernel tracing/logging
10719 cannot be done. Ensure that the kernel configuration includes
10720 the Trace/Log device driver netdiag1 and that the Trace/Log
10721 device files exist and are readable.
10722

[Jack C. Mahaffey]

Here's contents of swlist -l product | grep EMS

[5485]root:/var/adm/sw # swlist -l product | grep EMS
EMS-Config A.03.20 EMS Config
EMS-Core A.03.10 EMS Core Product
EMS-Core A.03.20 EMS Core Product
EMS-KRMonitor A.11.00.04 EMS Kernel Resource Monitor
EMS-MIBMonitor A.03.10 EMS MIB Resource Monitor Product
Isee_EmsListener A.11.07.13 ISEE TCP listener for EMS events
PHSS_26871 1.0 EMS (A.03.20) & HA Monitors (A.03.20) patch
[5490]root:/var/adm/sw #

I see there are two versions of EMS-Core, do I swremove the A.03.10 version?

Here's contents of swagent on swinstall.

It looks like I need to find and reload the following:

"EMS-DiskMonitor.DISKMON-RUN, fr=A.03.20,v=HP".
"EMS-MIBMonitor.MIBMON-RUN, fr=A.03.20,v=HP".
"EMS-RdbmsMon.RDBMSMON-RUN,fr=A.03.20,v=HP".

7270 NOTE: The fileset "PHSS_26871.EMS-GUI,r=1.0" is already installed.
7271 If you wish to reinstall this fileset, change the "reinstall"
7272 option to "true".
7273 * Reading source for file information.
7274 NOTE: The patch fileset "PHSS_26871.DISKMON-RUN,r=1.0" may only be
7275 installed upon a previously installed base fileset. The
7276 specification for this base fileset is
7277 "EMS-DiskMonitor.DISKMON-RUN,fr=A.03.20,v=HP". Since there is
7278 no fileset on the target or selected from the source which
7279 matches this specification, fileset
7280 "PHSS_26871.DISKMON-RUN,r=1.0" will be excluded.
7281 NOTE: The patch fileset "PHSS_26871.MIBMON-RUN,r=1.0" may only be
7282 installed upon a previously installed base fileset. The
7283 specification for this base fileset is
7284 "EMS-MIBMonitor.MIBMON-RUN,fr=A.03.20,v=HP". Since there is
7285 no fileset on the target or selected from the source which
7286 matches this specification, fileset

7288 NOTE: The patch fileset "PHSS_26871.RDBMSMON-RUN,r=1.0" may only be
7289 installed upon a previously installed base fileset. The
7290 specification for this base fileset is
7291 "EMS-RdbmsMon.RDBMSMON-RUN,fr=A.03.20,v=HP". Since there is
7292 no fileset on the target or selected from the source which
7293 matches this specification, fileset
7294 "PHSS_26871.RDBMSMON-RUN,r=1.0" will be excluded.


jack...

[Jack C. Mahaffey]

I compared the B7609BA product to another system and it looks like I need to replace the A.03.10 version with A.03.20.

Gonna search hp for B7609BA for download.
jack

[Jack C. Mahaffey]

Installed the missing components for A.20. Driver and device files still do not exist.

Some questions:

1 Should I swremove the A.10 version. I'm asumming everything will still be ok.
2 How do I add the netdiag1 driver?
3 How do I recreate the nettrace and netlog device files?

jack...

[Dave Olker · Accepted solution]

Hi Jack,

I've never heard of this problem before, but here are the steps I'd take:

1. Install PHNE_29231

This is the latest patch for the network tracing and logging facility. Hopefully this patch will ensure that the netdiag1 driver is installed.

2. Recreate the missing device files

# mknod /dev/netlog c 46 1
# mknod /dev/nettrace c 46 0

Hopefully these steps will restore your network tracing and logging capabilities.

Good luck,

Dave

[Jack C. Mahaffey]

Dave, thanks a whole bunch for the speedy reply. I'll try it in the next 10 minutes. I got about an hour before I got to release the server.

jack...

[Jack C. Mahaffey]

swinstall indicated software is configured... Ran mknod and now rebooting. I suspect it will still fail because the driver netdiag1 is not showing up in sam. How do I add it to sam?

jack...

[Jack C. Mahaffey]

Is it safe to remove the A.10 version of EMS?

[Dave Olker]

Hi Jack,

Make sure "netdiag1" is listed in the /stand/system file in the "Drivers and Subsystems" section. Looking at my 11.0 system:

# more /stand/system
* Drivers and Subsystems

DlkmDrv
GSCtoPCI
PCItoPCI
arp
asio0
asp
autofsc
btlan3
btlan6
c720
cb
cdfs
clone
core
diag0
diag1
diag2
dlkm
dlpi
dmem
echo
fc
fc_arp
fcgsc
fcgsc_lan
ffs
hpstreams
inet
ip
klog
lasi
lba
ldterm
lv
lvm
maclan
netdiag1 <<<<<<<<<<<<<<
netqa
nfs_client
...

If you don't have netdiag1 in your /stand/system file then I'd try manually adding it with vi. Then rebuild your kernel with:

# mk_kernel -o /stand/vmunix

Then reboot the new kernel and see if it works.

Regards,

Dave

[Dave Olker]

Hi Jack,

Sorry, I'm not sure why you're wanting to mess with EMS in the first place. Are you having an EMS-related problem that you believe is caused by a conflict of EMS code?

Dave

[Jack C. Mahaffey]

I'll give it a shot by updating the /stand/system file...

[Jack C. Mahaffey]

Dave, just wanted to clear up the remaining error message on bootup. I get to do patch maintenance on the server only one to two times a year.

jack..

[Jack C. Mahaffey]

/stand/system already has the netdiag1 entry.
I'm runing the mk_kernel now and rebooting.

Here's the current output from rc.log from the last reboot. I just changed owner and permissions to match another server.

376 Start network tracing and logging daemon
377 Output from "/sbin/rc2.d/S300nettl start":
378 ----------------------------
379 Initializing Network Tracing and Logging...
380 nettl : Warning: The device file /dev/nettrace and/or /dev/netlog is
381 not present or cannot be opened. Continuing with the
382 initialization of Trace/Log facility. Kernel tracing/logging
383 cannot be done. Ensure that the kernel configuration includes
384 the Trace/Log device driver netdiag1 and that the Trace/Log
385 device files exist and are readable.
386
387 Done.

[Jack C. Mahaffey]

Checked sam on another server that isn't having the problem and it doesn't show the netdiag1 in the list of drivers either in the gui. It is in the /stand/system file however. This must be a case where the driver is not included in the GUI.

I'll post the results of my reboot shortly.
jack...

[Jeff Schussele]

Hi Jack,

What are the perms & ownership on those devices?

should both be:

crw-r--r-- bin bin

Rgds,
Jeff

[Jack C. Mahaffey]

Dave, thanks a bunch. Is it still ok to swremove the A.01 Version?

jack...

[Dave Olker]

Hi Jack,

I apologize - I don't know anything about EMS, so I hesitate to advise you on removing versions of a product that I know nothing about.

As you discovered, PHSS_26871 is looking for a base version of these filesets:

EMS-DiskMonitor.DISKMON-RUN, fr=A.03.20,v=HP
EMS-MIBMonitor.MIBMON-RUN, fr=A.03.20,v=HP
EMS-RdbmsMon.RDBMSMON-RUN,fr=A.03.20,v=HP

none of which exist on your system currently.

I guess my questions would be:

How did you install EMS on this system initially? Did you install A.03.20?

What does this command return:

# swlist -l fileset | grep EMS

Do you have EMS installed on mutliple systems? Does the above swlist command return different fileset information for different systems?

Regards,

Dave

[Jack C. Mahaffey]

Permissions and ownership was incorrect when I created the files. They are correct now. No errors in syslog or rc.log.

Results from swlist:
[5799]root:/etc # swlist -l fileset | grep EMS
# EMS-Config A.03.20 EMS Config
EMS-Config.EMS-GUI A.03.20 EMS GUI
# EMS-Core A.03.20 EMS Core Product
EMS-Core.EMS-CORE A.03.20 Event Monitoring Services Core Files
EMS-Core.EMS-MX A.03.20 Event Monitoring Services SCMgr Tools
# EMS-KRMonitor A.11.00.04 EMS Kernel Resource Monitor
EMS-KRMonitor.KRMON-DRV-CMN A.11.00.04 EMS Kernel Resource Monitor Common Files for Driver
EMS-KRMonitor.KRMON-DRV-DRV A.11.00.04 EMS Kernel Resource Monitor 64-bit Driver
EMS-KRMonitor.KRMON-MAN A.11.00.04 EMS Kernel Resource Monitor Manual
EMS-KRMonitor.KRMON-RUN A.11.00.04 EMS Kernel Resource Monitor Runtime
# EMS-MIBMonitor A.03.20 EMS MIB Resource Monitor Product
EMS-MIBMonitor.MIBMON-RUN A.03.20 MIB Resource Monitor
# Isee_EmsListener A.11.07.13 ISEE TCP listener for EMS events
Isee_EmsListener.ISEE-EMSCONF A.11.07.05 ISEE TCP EMS listener
Isee_EmsListener.ISEE-EMSLSTNR A.11.07.09 ISEE TCP EMS listener
# PHSS_26871 1.0 EMS (A.03.20) & HA Monitors (A.03.20) patch
PHSS_26871.EMS-CORE 1.0 Event Monitoring Services Core Files
PHSS_26871.EMS-GUI 1.0 EMS GUI
PHSS_26871.MIBMON-RUN 1.0 EMS Core Files
[5800]root:/etc #

[Jack C. Mahaffey]

Aha.. Looks like the A.10 version went away. Here's swlist at the product level:

5800]root:/etc # swlist -l product | grep EMS
EMS-Config A.03.20 EMS Config
EMS-Core A.03.20 EMS Core Product
EMS-KRMonitor A.11.00.04 EMS Kernel Resource Monitor
EMS-MIBMonitor A.03.20 EMS MIB Resource Monitor Product
Isee_EmsListener A.11.07.13 ISEE TCP listener for EMS events
PHSS_26871 1.0 EMS (A.03.20) & HA Monitors (A.03.20) patch
[5801]root:/etc #

[Jack C. Mahaffey]

Looks like its only missing the following two now:

EMS-DiskMonitor.DISKMON-RUN, fr=A.03.20,v=HP
EMS-RdbmsMon.RDBMSMON-RUN,fr=A.03.20,v=HP

[Dave Olker]

Do you have another system with EMS installed that lists these filesets when queried with swlist? I'm just curious why the patch is looking for these filesets as a prerequisite for installing if they are not part of the EMS default bundle. Are these optional products?

Again, my lack of EMS knowledge is glaring...

Dave

[Jack C. Mahaffey]

Output from swlist -l product | grep EMS on other server:

[8138]root:/root # swlist -l product | grep EMS
EMS-Config A.03.20 EMS Config
EMS-Core A.03.20 EMS Core Product
EMS-KRMonitor A.11.00.04 EMS Kernel Resource Monitor
EMS-MIBMonitor A.03.20 EMS MIB Resource Monitor Product
PHSS_23592 1.0 EMS (A.03.20) & HA Monitors (A.03.20) patch
[8139]root:/root #


output from -l fileset | grep EMS
[8140]root:/root # swlist -l fileset | grep EMS
# EMS-Config A.03.20 EMS Config
EMS-Config.EMS-GUI A.03.20 EMS GUI
# EMS-Core A.03.20 EMS Core Product
EMS-Core.EMS-CORE A.03.20 Event Monitoring Services Core Files
EMS-Core.EMS-MX A.03.20 Event Monitoring Services SCMgr Tools
# EMS-KRMonitor A.11.00.04 EMS Kernel Resource Monitor
EMS-KRMonitor.KRMON-DRV-CMN A.11.00.04 EMS Kernel Resource Monitor Common Files for Driver
EMS-KRMonitor.KRMON-DRV-DRV A.11.00.04 EMS Kernel Resource Monitor 64-bit Driver
EMS-KRMonitor.KRMON-MAN A.11.00.04 EMS Kernel Resource Monitor Manual
EMS-KRMonitor.KRMON-RUN A.11.00.04 EMS Kernel Resource Monitor Runtime
# EMS-MIBMonitor A.03.20 EMS MIB Resource Monitor Product
EMS-MIBMonitor.MIBMON-RUN A.03.20 MIB Resource Monitor
# PHSS_23592 1.0 EMS (A.03.20) & HA Monitors (A.03.20) patch
PHSS_23592.EMS-CORE 1.0 Event Monitoring Services Core Files
PHSS_23592.EMS-GUI 1.0 EMS GUI
[8141]root:/root #

Very good questions... They are apparently different. I didn't see the Disk monitor or RDBMS monitor filesets there either.

It's been a long day. I should have dug further.

Thanks... Not going to worry about it any more. :)

jack...