Re: [nv-l] lansafe smux

[James Shanks <jshanks@us.ibm.com>]

I think you are expecting too much here.
 Your best source is going to be the LanSafe vendor.   snmpd
is only going to tell you that he has a problem talking to that daemon,
not what the daemon's problem is.  Does this agent have a log of his
own?  That's the only place where you might see a clue as to what's
wrong, but even then you'll probably have to know the code to understand
the error.

If you go to your NetView machine, and
look at the snmpd.log and the trapgend or mgragent logs, you will see that
this all looks perfectly normal down to the no response part, though I
must say that I even see that on my box(es) some times.  Here's a
case in point.

from snmpd.log
06/28/04 09:01:31 NOTICE: SMUX open: 2 ibm.6.4.1.4.1 "IBM Trap Sub-Agent" (12/ 127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX packet from (127.0.0.1+32775+3)
06/28/04 09:01:31 NOTICE: SMUX open: 3 ibm.6.4.6.4.1 "IBM NetView Manager Sub-Agent" (13/ 127.0.0.1+32775+3)
06/28/04 09:01:31 NOTICE: SMUX packet from (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.5.1 in = -1 out = 0 (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX packet from (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.6.4.1 in = -1 out = 0 (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX packet from (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.6.4.2 in = -1 out = 0 (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX packet from (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.6.4.3 in = -1 out = 0 (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX packet from (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.6.4.4 in = -1 out = 0 (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX packet from (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.6.4.5 in = -1 out = 0 (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX packet from (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX trap: (0 0) (127.0.0.1+32774+2)
06/28/04 09:01:31 NOTICE: SMUX packet from (127.0.0.1+32775+3)
06/28/04 09:01:31 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.6.4.6 in = -1 out = 0 (127.0.0.1+32775+3)
06/28/04 09:06:47 EXCEPTIONS: no response after 15 seconds  (SMUX 127.0.0.1+32774+2)
06/28/04 09:06:53 NOTICE: SMUX relation started with (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX packet from (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX open: 4 ibm.6.4.1.4.1 "IBM Trap Sub-Agent" (12/ 127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX packet from (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.5.1 in = -1 out = 0 (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX packet from (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.6.4.1 in = -1 out = 0 (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX packet from (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.6.4.2 in = -1 out = 0 (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX packet from (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.6.4.3 in = -1 out = 0 (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX packet from (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.6.4.4 in = -1 out = 0 (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX packet from (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX register: readOnly 1.3.6.1.4.1.2.6.4.5 in = -1 out = 0 (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX packet from (127.0.0.1+33049+4)
06/28/04 09:06:53 NOTICE: SMUX trap: (1 0) (127.0.0.1+33049+4)

from trapgend.log
Mon Jun 28 09:01:30 EDT 2004 (12646) trapgend   - TME 10 NetView SNMP Trap sub-agent for AIX V3.2.5 and AIX 4.1, version 4.1, created Wed Dec  3 23:23:22 CST 2003
Mon Jun 28 09:01:31 EDT 2004 (12646) trapgend   - SNMP connected: trapgend (trapgend.4.1)
Mon Jun 28 09:01:31 EDT 2004 (12646) trapgend   - SMUX registration requested: alert, priority -1
Mon Jun 28 09:01:31 EDT 2004 (12646) trapgend   - SMUX registration requested: trapgend, priority -1
Mon Jun 28 09:01:31 EDT 2004 (12646) trapgend   - SMUX registration requested: nv6saTrap, priority -1
Mon Jun 28 09:01:31 EDT 2004 (12646) trapgend   - SMUX registration requested: nv6saIcmp, priority -1
Mon Jun 28 09:01:31 EDT 2004 (12646) trapgend   - SMUX registration requested: nv6saFileSystem, priority -1
Mon Jun 28 09:01:31 EDT 2004 (12646) trapgend   - SMUX registration requested: nv6saComputerSystem, priority -1
Mon Jun 28 09:01:31 EDT 2004 (12646) trapgend   - coldstart trap emitted
Mon Jun 28 09:01:31 EDT 2004 (12646) trapgend   - SMUX registration accepted: priority 0
Mon Jun 28 09:01:31 EDT 2004 (12646) trapgend   - SMUX registration accepted: priority 0
Mon Jun 28 09:01:31 EDT 2004 (12646) trapgend   - SMUX registration accepted: priority 0
Mon Jun 28 09:06:33 EDT 2004 (12646) trapgend   - SMUX registration accepted: priority 0
Mon Jun 28 09:06:33 EDT 2004 (12646) trapgend   - SMUX registration accepted: priority 0
Mon Jun 28 09:06:33 EDT 2004 (12646) trapgend   - SMUX registration accepted: priority 0
Mon Jun 28 09:06:33 EDT 2004 (12646) trapgend   - Warning after recv_icmp_msg.  icmp_msg_type==3
Mon Jun 28 09:06:33 EDT 2004 (12646) trapgend   - Unexpected ICMP message ret = 3 errno=11, Resource temporarily unavailable

Mon Jun 28 09:06:34 EDT 2004 (12646) trapgend   - Unexpected ICMP message ret = 0 errno=11, Resource temporarily unavailable

Mon Jun 28 09:06:36 EDT 2004 (12646) trapgend   - Warning after recv_icmp_msg.  icmp_msg_type==3
Mon Jun 28 09:06:36 EDT 2004 (12646) trapgend   - Unexpected ICMP message ret = 3 errno=11, Resource temporarily unavailable

Mon Jun 28 09:06:37 EDT 2004 (12646) trapgend   - Warning after recv_icmp_msg.  icmp_msg_type==3
Mon Jun 28 09:06:37 EDT 2004 (12646) trapgend   - Unexpected ICMP message ret = 3 errno=11, Resource temporarily unavailable

Mon Jun 28 09:06:37 EDT 2004 (12646) trapgend   - Unexpected ICMP message ret = 0 errno=11, Resource temporarily unavailable

Mon Jun 28 09:06:38 EDT 2004 (12646) trapgend   - Unexpected ICMP message ret = 0 errno=11, Resource temporarily unavailable

Mon Jun 28 09:06:39 EDT 2004 (12646) trapgend   - Unexpected ICMP message ret = 0 errno=11, Resource temporarily unavailable

Mon Jun 28 09:06:41 EDT 2004 (12646) trapgend   - Warning after recv_icmp_msg.  icmp_msg_type==3
Mon Jun 28 09:06:41 EDT 2004 (12646) trapgend   - Unexpected ICMP message ret = 3 errno=11, Resource temporarily unavailable

Mon Jun 28 09:06:43 EDT 2004 (12646) trapgend   - Warning after recv_icmp_msg.  icmp_msg_type==3
Mon Jun 28 09:06:43 EDT 2004 (12646) trapgend   - Unexpected ICMP message ret = 3 errno=11, Resource temporarily unavailable

Mon Jun 28 09:06:46 EDT 2004 (12646) trapgend   - Unexpected ICMP message ret = 0 errno=11, Resource temporarily unavailable

Mon Jun 28 09:06:48 EDT 2004 (12646) trapgend   - Unexpected ICMP message ret = 0 errno=11, Resource temporarily unavailable

Mon Jun 28 09:06:48 EDT 2004 (12646) trapgend   - Unexpected ICMP message ret = 0 errno=11, Resource temporarily unavailable

Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - Warning: Ping timed out, timeout=5
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - process_snmp(): smux_wait(): youLoseBig (ps2pe: I/O Error, A connection with a remote socket was reset by that socket.)
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SNMP disconnected - reason=4
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SNMP connected: trapgend (trapgend.4.1)
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SMUX registration requested: alert, priority -1
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SMUX registration requested: trapgend, priority -1
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SMUX registration requested: nv6saTrap, priority -1
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SMUX registration requested: nv6saIcmp, priority -1
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SMUX registration requested: nv6saFileSystem, priority -1
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SMUX registration requested: nv6saComputerSystem, priority -1
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - warmstart trap emitted
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SMUX registration accepted: priority 0
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SMUX registration accepted: priority 0
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SMUX registration accepted: priority 0
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SMUX registration accepted: priority 0
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SMUX registration accepted: priority 0
Mon Jun 28 09:06:53 EDT 2004 (12646) trapgend   - SMUX registration accepted: priority 0

So here we see that trapgend had some kind of internal problem, and finally disconnectd himself, and then reconnected.  But you would never know that
just from looking at the snmpd.log.  So you aren't going to be able to debug the problem with the LanSafe agent, or any other agent,  
just by looking at the snmpd.log


James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

"Lucian Vanghele" <lucian.vanghele@bisnet.ro>
Sent by: owner-nv-l@lists.us.ibm.com

07/09/2004 03:32 AM

Please respond to
nv-l

To	<nv-l@lists.us.ibm.com>
cc
Subject	Re: [nv-l] lansafe smux

James, you are right! Mea culpa... and there is no excuse for this (maybe only the rush)
 
back to the problem now:
- I have a cluster on AIX 5.1.0.0 using snmpv1  (this is a SWIFT cluster not netview so I don't have trapgend or mgragentd entries in snmpd.conf)
- on each machine is one Powerware UPS, connected with serial cable
- I want to manage these UPS's using LanSafe 5.0.3 (this is Powerware software)
- after installing LanSafe (and it's snmp agent component) snmpd.conf and snmpd.peers are correctly modified so they contain the correct entries for the LanSafe smux agent
- in /var/tmp/snmpd.log I see these:
 
07/08/04 15:32:15 NOTICE: SMUX packet from (192.168.3.5+50239+2)
07/08/04 15:32:15 NOTICE: SMUX open: 2 mib-2.33.1 "LanSafe SMUX Peer daemon" (10/ 192.168.3.5+50239+2)
07/08/04 15:32:15 NOTICE: SMUX packet from (192.168.3.5+50239+2)
07/08/04 15:32:15 DEBUG: sending register response to (SMUX 192.168.3.5+50239+2)
07/08/04 15:32:15 NOTICE: SMUX register: readWrite 1.3.6.1.2.1.33.1 in = -1 out = 0 (192.168.3.5+50239+2)
07/08/04 15:32:20 DEBUG: add route: 2/0.0.0.0 w/mask NONE on interface 0x328ac268 with flags 65539
07/08/04 15:32:20 DEBUG: add route: 2/127.0.0.0 w/mask 255.0.0.0 on interface 0x8cee18 with flags 1
07/08/04 15:32:20 DEBUG: add route: 2/149.134.0.0 w/mask 255.255.0.0 on interface 0x328ac268 with flags 65539
07/08/04 15:32:20 DEBUG: add route: 2/192.168.0.0 w/mask 255.255.255.0 on interface 0x328ac268 with flags 1
07/08/04 15:32:20 DEBUG: add route: 2/192.168.0.4 w/mask NONE on interface 0x8cee18 with flags 2055
07/08/04 15:32:20 DEBUG: add route: 2/192.168.1.0 w/mask 255.255.255.0 on interface 0x328ac134 with flags 1
07/08/04 15:32:20 DEBUG: add route: 2/192.168.1.6 w/mask NONE on interface 0x8cee18 with flags 2055
07/08/04 15:32:20 DEBUG: add route: 2/192.168.3.0 w/mask 255.255.255.0 on interface 0x328ac000 with flags 1
07/08/04 15:32:20 DEBUG: add route: 2/192.168.3.5 w/mask NONE on interface 0x8cee18 with flags 2055
07/08/04 15:32:20 DEBUG: add route: 2/192.168.4.0 w/mask 255.255.255.0 on interface 0x328ac39c with flags 1
07/08/04 15:32:20 DEBUG: add route: 2/192.168.4.7 w/mask NONE on interface 0x8cee18 with flags 2055
07/08/04 15:32:20 DEBUG: add route: 24/ w/mask NONE on interface 0x8cee18 with flags 5
07/08/04 15:32:20 DEBUG: sending request to  (SMUX 192.168.3.5+50239+2)
07/08/04 15:32:35 EXCEPTIONS: no response after 15 seconds  (SMUX 192.168.3.5+50239+2)
07/08/04 15:32:35 DEBUG: sending request to  (SMUX 127.0.0.1+50231+1)
 
- trying to browse the UPS mib tree (1.3.6.1.2.1.33.1) I receive "no values returned for query"
 
- on the other hand, there is a smux agent for hacmp, correctly configured (clsmuxpd 1.3.6.1.4.1.2.3.1.2.1.5  "clsmuxpd_password" # HACMP for AIX clsmuxpd )
- when I try to browse risc6000clsuxpd mib tree (1.3.6.1.4.1.2.3.1.2.1.5) I receive "no values returned for query"
 
So, if none of these two is working, what could be wrong? Now I'll try to resolve first the clsmuxpd problem (in order to be sure the mechanism is functional) and then I'll try the LanSafe agent.
I hope this time the email is complete.
 
thanks a lot for the time and patience...
 
 
Sincerely Yours / al Dvs.
Lucian Vanghele,
----- Original Message -----
From: James Shanks
To: nv-l@lists.us.ibm.com
Sent: Thursday, July 08, 2004 3:35 PM
Subject: Re: [nv-l] lansafe smux


Lucian,
I don't mean to be rude, but when are you going to start providing information when you ask questions?  How can anyone even try to help you with weird stuff if you don't tell us what you have done so far, or what your configuration looks like?  risc6000clsuxpd?   So I take it you are on AIX?  What level?  Version 5?    Is snmpd operating as snmpdv3 or v1?  If v3, are you sure your agent supports that?

On AIX smux requires matching entries in the /etc/snmpd.peers file and the /etc/snmpd.conf file.  One, the peers,  tells the agent what community name to use and  MIB OID to respond to.  The other, the conf, tells snmpd the same thing.  Take a look at the NetView entries for  trapgend or mgragentd and you'll see what I mean.  Those work don't they?  Well if they do and the others don't, then those other agents are not configured properly.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

lucian.vanghele@bisnet.ro
Sent by: owner-nv-l@lists.us.ibm.com

07/08/2004 07:35 AM

Please respond to
nv-l

To	nv-l@lists.us.ibm.com
cc
Subject	Re: [nv-l] lansafe smux

you are right! I already contacted powerware local distribuitor. On the other hand I tried to browse the risc6000clsmuxpd mib tree and I have the same error!!

Sincerely Yours / al Dvs.
Lucian Vanghele,

Paul <pstroud@bellsouth.net> Sent by: owner-nv-l@lists.us.ibm.com 07/08/2004 06:05 AST Please respond to nv-l@lists.us.ibm.com	To	nv-l@lists.us.ibm.com
	cc
	bcc
	Subject	Re: [nv-l] lansafe smux

This really looks like a problem with the agent. You should be talking
to lansafe, they should be able to assist you.

Paul

Lucian Vanghele wrote:
> no ideas?
>
> Sincerely Yours / al Dvs.
> Lucian Vanghele,
>
> ----- Original Message -----
> From: <lucian.vanghele@bisnet.ro>
> To: <nv-l@lists.us.ibm.com>
> Sent: Wednesday, July 07, 2004 2:58 PM
> Subject: [nv-l] lansafe smux
>
>
>
>>
>>
>>
>>hi there!
>>I'm trying to manage some UPSs via LanSafe Agent and I have some problems
>>
>>- after I installed the LanSafe Agent in snmpd.log I saw something like
>>EXCEPTIONS: duplicate listeners 0.0.0.0.0
>>NOTICE: SMUX relation started with (192.168.3.5+45649+2)
>>NOTICE: SMUX open: 2 mib-2.33.1 "LanSafe SMUX Peer Daemon" (10/
>
> 192.168.3.5
>
>>+45649+2)
>>NOTICE: SMUX register readWrite 1.3.6.1.2.1.33.1 in = -1 out = 0
>>(192.168.3.5+45649+2)
>>EXCEPTIONS: no response after 15 seconds (SMUX 192.168.3.5+45649+2)
>>
>>trying to browse the .33 tree I receive "no values returned for query"
>>any ideea will be welcome!
>>thanks
>>Sincerely Yours / al Dvs.
>>Lucian Vanghele
>>
>
>
>