[Nut-upsdev] [Nut-upsuser] Powerware 9155 with SNMP card

[Bernd Markgraf]

Hi,

> Excellent! I'm cross posting this to the development mailinglist, since
> this is going beyond the scope of the user mailinglist.
no problem... 

> > So would one go ahead and add these values to ietf_pwr_info[] ?
> > Or would one rather extend that inside pwmib.h? The latter seems more
> > obvious to me, since XUPS.mib states that it extends upsOutputSource
> > from the rfc1628 MIB.
> That would be the best way to deal with this, since other vendors may
> extend this too, which may lead to incompatibilities. That's why we
> support different ones.
Very well. You provided the patch yourself already :-)

> Clients expect the system to be either OL or OB (actually, this is an
> indication of the linestatus). So we may need to add OL to other power
> states as well, to make sure the notifications work as expected. For the
> moment you'll be fine (as long as OB and OB LB can be detected, the
> clients will know when to shutdown).
I haven't tried that out yet... Didn't have the guts to temper with the
main switch on the wall yet 8-)

> > As for the missing variables in the MIB these are
> >
> > su_ups_get: output.current 1.3.6.1.4.1.534.1.4.4.1.3
> > [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.4.4.1.3: Error in packet:
> > (noSuchName) There is no such variable name in this MIB.
> > => Failed
> >
> > Check inphases
> > inphases is set
> > su_ups_get: input.L1.realpower 1.3.6.1.4.1.534.1.3.4.1.4.1
> > [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.1: Error in packet:
> > (noSuchName)
> > There is no such variable name in this MIB.
> > => Failed
> > Check inphases
> > inphases is set
> > su_ups_get: input.L2.realpower 1.3.6.1.4.1.534.1.3.4.1.4.2
> > [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.2: Error in packet:
> > (noSuchName)
> > There is no such variable name in this MIB.
> > => Failed
> > Check inphases
> > inphases is set
> > su_ups_get: input.L3.realpower 1.3.6.1.4.1.534.1.3.4.1.4.3
> > [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.3: Error in packet:
> > (noSuchName)
> > There is no such variable name in this MIB.
> > => Failed
> >
> >
> > I haven't figured them out yet...
> 
> Apparently, the autodetection failed here and it selects the default ietf
> MIB, where these are not set. This will probably be fixed by adding
> 
> 	mibs = pw
> 
> to the ups.conf entry for these devices (to select the data from pwmib.h
> file). See also 'man snmp-ups' for an example.
Na, I already run the pw mib... The ietf mib didn't even so more than a single 
imput phase... The above should be hidden inside the XUPS.mib I guess.

> You'll probably want to add the folliwing to "pwmib.h" (I'm not in favor
> of adding ups.status words):
> 
> info_lkp_t pw_pwr_info[] = {
> 	{ 1, ""       /* other */ },
> 	{ 2, "OFF"    /* none */ },
> 	{ 3, "OL"     /* normal */ },
> 	{ 4, "BYPASS" /* bypass */ },
> 	{ 5, "OB"     /* battery */ },
> 	{ 6, "OL BOOST"  /* booster */ },
> 	{ 7, "OL TRIM"   /* reducer */ },
> 	{ 8, "OL"   /* parallel capacity */ },
> 	{ 9, "OL"   /* parallel redundancy */ },
> 	{10, "OL"   /* high efficiancy */ },
> 	{ 0, "NULL" }
> };
Agreed. But I would suggest to add PCAP, PRED or anything along those lines to 
the OL so one knows that we are running in parallel mode. I don't know whether
this status changes if the other UPS goes down for some reason. So it
would be handy if on could differentiate those.

> and change
> 
> { "ups.status", ST_FLAG_STRING, SU_INFOSIZE, PW_OID_POWER_STATUS, "OFF",
> SU_STATUS_PWR, &ietf_pwr_info[0] },
> 
> to
> 
> { "ups.status", ST_FLAG_STRING, SU_INFOSIZE, PW_OID_POWER_STATUS, "OFF",
> SU_STATUS_PWR, &pw_pwr_info[0] },