no telnet, ping ok...

Applications Infrastructure Monitoring
1

We have a Sun Solaris Netra 20 server. Our O&M Server gets Alarm Processor
not responding. When Alarm occurs, you can ping the sun server but cannot telnet it. We keep getting Interrupt level not serviced. var/adm/message log is

> tail -f messages

Apr 12 20:09:56 cama pcisch: [ID 370704 kern.info] PCI-device: pci1214,334a@1, pci64492
Apr 12 20:09:56 cama genunix: [ID 936769 kern.info] pci64492 is /pci@8,700000/pci1214,334a@1
Apr 12 20:09:56 cama pci6449: [ID 787935 kern.notice] [PT-334a] SolwayTech PT-334a 64bit Driver (November 2004)
Apr 12 20:10:01 cama unix: [ID 882636 kern.warning] WARNING: interrupt level 1 not serviced
Apr 12 20:10:07 cama /usr/lib/snmp/snmpdx: [ID 702911 daemon.error] unable to get my IP address: gethostbyname(cama) failed [h_errno: host not found(1
)]
Apr 12 20:10:09 cama unix: [ID 882636 kern.warning] WARNING: interrupt level 1 not serviced
Apr 12 20:10:18 cama last message repeated 12 times
Apr 12 20:10:18 cama pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Apr 12 20:10:18 cama genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Apr 12 20:10:19 cama unix: [ID 882636 kern.warning] WARNING: interrupt level 1 not serviced

Kindly help. Thanks in advance

2

Telnet may not be running on your Sun server.

3

check if telnet is enabled and the telnet port is open

#exec 3>/dev/tcp/$serverip/23

4

My thread title is changed to no telent ping ok :mad:. Problem is not of telent
, problem is we keep getting messages
Interrupt Level 1 not serviced. What is it? Kindly also explain the log :confused:
Thanks for the reply

5

I probably used the wrong thread title. sorry.

6

the title was changed from "sun solaris" which was "non descriptive" at all... which is against the rules.

is your server configured to recive or send snmp packages? this has maybe to do with the warning messages...

7

Yes. It recieves records from server and forwards it to another sever.

8

Message `WARNING:interrupt level 1 not serviced`

This issue has been permanently fixed in Solaris 8 and 9 by software
patches. See the Corrective Action section below for the recommended
patches and an additional workaround procedure.

9

thanks. Kindly can you explain why this warning occurs.

10

its basically due to some bugs...