Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
79228members
343850posts

AP9630 can't set upsBasicIdentName.0

Solved
MASHtm_apc
Crewman
Crewman
0 Likes
3
110

AP9630 can't set upsBasicIdentName.0

This was originally posted on APC forums on 7/14/2009


Hi!

Since APC is not willing to open microlink protocol we were forced to buy a NMC 2 AP9630.

Now I try to configure it and I'm not able to set
PowerNet-MIB::upsBasicIdentName.0

System Name is set in webinterface, but doesn't show up as BasicIdent. Even setting it with snmpset succeeds, but the value doesn't show up using snmpget afterwards. It's empty all the time.

Firmware is v5.0.1. UPS is a RT3000.

Any suggestions?


Accepted Solutions
MASHtm_apc
Crewman
Crewman
0 Likes
0
110

Re: AP9630 can't set upsBasicIdentName.0

This was originally posted on APC forums on 7/20/2009


no, I'm talking about

.1.3.6.1.4.1.318.1.1.1.1.1.2.0 == PowerNet-MIB::upsBasicIdentName.0

which is documented as read/write value. In fact this value is empty (not set by any web interface field), and a snmpset is successful, but the value is still empty on the next read.

apcupsd reads this value as name. so i need to set that value as defined in APC PowerNet MIB documentation.

See Answer In Context

3 Replies 3
voidstar_apc
Janeway
Janeway
0 Likes
0
110

Re: AP9630 can't set upsBasicIdentName.0

This was originally posted on APC forums on 7/20/2009


>
no, I'm talking about

.1.3.6.1.4.1.318.1.1.1.1.1.2.0 == PowerNet-MIB::upsBasicIdentName.0

which is documented as read/write value. In fact this value is empty (not set by any web interface field), and a snmpset is successful, but the value is still empty on the next read.

apcupsd reads this value as name. so i need to set that value as defined in APC PowerNet MIB documentation.
>

Your UPS model doesn't support storing a name. On the NMC web interface, we're using the system name (system.sysName.0) instead. In the future, I suspect we won't respond to upsBasicIdentName if the UPS does not support it.

voidstar_apc
Janeway
Janeway
0 Likes
0
109

Re: AP9630 can't set upsBasicIdentName.0

This was originally posted on APC forums on 7/14/2009


If you're talking about the Identification information in the web interface under Administration->General->Identification, the corresponding OID is system.sysName.0 (.1.3.6.1.2.1.1.5.0). Location and Contact are under the same MIB branch.

Let me know if that helps.

MASHtm_apc
Crewman
Crewman
0 Likes
0
111

Re: AP9630 can't set upsBasicIdentName.0

This was originally posted on APC forums on 7/20/2009


no, I'm talking about

.1.3.6.1.4.1.318.1.1.1.1.1.2.0 == PowerNet-MIB::upsBasicIdentName.0

which is documented as read/write value. In fact this value is empty (not set by any web interface field), and a snmpset is successful, but the value is still empty on the next read.

apcupsd reads this value as name. so i need to set that value as defined in APC PowerNet MIB documentation.