Well, I can still change settings and they are changed in the switch. But I have tried to apply the patch and it's not working. I have tried to change the suffix without luck.
If I run snmpset manually from console it will save to memory.
/Mattias
----- Ursprungligt meddelande ----- Från: "Mattias Söderholm" mattias.soderholm@malax.fi Till: "John Magne Bredal" john.m.bredal@uninett.no Kopia: "nav-users" nav-users@uninett.no Skickat: torsdag, 2 feb 2017 14:17:09 Ämne: Re: PortAdmin - save changes in HP 5130 switch?
Well. When I go to Portadmin now I got an error saying: SNMP error when contacting <IP>. Values displayed are from database
I have only updated to NAV 4.6.1, noting else. We have also got a lot of emails today about Switches that don't respond and 1min later respond... The messages are: <IP/DNS> has stopped responding to SNMP requests. Verify that read-only SNMP community is configured correctly in NAV, and that no access lists are blocking SNMP.
Do I have some bug in NAV with SNMP?
/Mattias
----- Ursprungligt meddelande ----- Från: "John Magne Bredal" john.m.bredal@uninett.no Till: "Mattias Söderholm" mattias.soderholm@malax.fi Kopia: "nav-users" nav-users@uninett.no Skickat: torsdag, 2 feb 2017 9:30:29 Ämne: SV: PortAdmin - save changes in HP 5130 switch?
Hi!
Ouch, that sounded a bit painful :p There might have been some problems applying the pathc on the 4.6.0 version of NAV yes.
The test in SeedDB does not use the snmputils-library that was modified, so that one failing should not be related. An empty syslocation might lead to an error in the write test, as that is the value being written.
Installing 4.6.1 should overwrite the snmputils library and thus restore everything to the correct state again.
The simplest thing to do to test the patch to make sure everything is up to date is to just make a backup of the snmputils.py file and replace it with the file from the pullrequest, as that is the only thing changed. Then restart the web-server. If that still makes errors, then you can change files again and you should be ok.
-- John Magne Bredal john.m.bredal@uninett.no +4791897366
Abels gt. 5- Teknobyen NO-7465 Trondheim
________________________________________ Fra: Mattias Söderholm mattias.soderholm@malax.fi Sendt: 1. februar 2017 14:07 Til: John Magne Bredal Kopi: nav-users Emne: Re: PortAdmin - save changes in HP 5130 switch?
Hi. Sounds nice.
I have now tried to add the patch to NAV 4.6.0 but getting errors. I have uncommented the changes and restarted NAV but every time I try to access portadmin I get the following error: NameError: global name 'H3C' is not defined
So now I have updated NAV to 4.6.1 and can access portadmin. No patch for H3C mem write have been added. Instead I get errors about SNMP write. So I check connectivity in SeedDB and got errors there for SNMP write. This is the error: Write test failed. Error message: wrongLength (The set value has an illegal length from what the agent expects)
So what is wrong now?
Regards Mattias
----- Ursprungligt meddelande ----- Från: "John Magne Bredal" john.m.bredal@uninett.no Till: "Mattias Söderholm" mattias.soderholm@malax.fi Kopia: "nav-users" nav-users@uninett.no Skickat: onsdag, 1 feb 2017 12:27:22 Ämne: Re: PortAdmin - save changes in HP 5130 switch?
Hi Mattias!
This took some time to get started with. However, an implementation has been done - but we have no way of testing this yet.
Can you please comment on https://github.com/UNINETT/nav/pull/1452 and potentially test this if you are able to.
On 22. nov. 2016 10:33, John Magne Bredal wrote:
Thanks a lot for this Mattias! This looks quite straightforward – very good.
We are working hard on NAV 4.6 right now (hopefully released this month), but I promise we will look into this in time for one of the next bugfix releases.
Issue in Launchpad - https://bugs.launchpad.net/nav/+bug/1643807
On 18/11/2016, 10:43, "Mattias Söderholm" mattias.soderholm@malax.fi wrote:
Hi. I have been searching about how to get save working for H3C switches and here's how:
snmpset -v2c -c <community> IP 1.3.6.1.4.1.25506.2.4.1.2.4.1.2.1 i 1 1.3.6.1.4.1.25506.2.4.1.2.4.1.9.1 i 4
.1.3.6.1.4.1.25506.2.4.1.2.4.1.2 hh3cCfgOperateType OBJECT-TYPE -- FROM HH3C-CONFIG-MAN-MIB -- TEXTUAL CONVENTION ConfigOperationType SYNTAX INTEGER {running2Startup(1), startup2Running(2), running2Net(3), net2Running(4), net2Startup(5), startup2Net(6), running2File(7), file2Running(8)} MAX-ACCESS read-create STATUS current DESCRIPTION "Specify the type of operation on configuration."
.1.3.6.1.4.1.25506.2.4.1.2.4.1.9 hh3cCfgOperateRowStatus OBJECT-TYPE -- FROM HH3C-CONFIG-MAN-MIB -- TEXTUAL CONVENTION RowStatus SYNTAX INTEGER {active(1), notInService(2), notReady(3), createAndGo(4), createAndWait(5), destroy(6)} MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this table entry. When the status is active all the object's value in the entry is not allowed to be modified."
Would be nice if you can fix this in NAV, so we can have our changes saved directly in NAV. =)
/mattias
----- Ursprungligt meddelande ----- Från: "John Magne Bredal" john.m.bredal@uninett.no Till: "Mattias Söderholm" mattias.soderholm@malax.fi, "nav-users" nav-users@uninett.no Skickat: onsdag, 3 feb 2016 11:38:42 Ämne: Re: PortAdmin - save changes in HP 5130 switch?
On 03. feb. 2016 09:58, Mattias Söderholm wrote:
Hi. We have now inserted some HP 5130 EI (also HP 5700) switches in NAV and want to use PortAdmin. Everything works except saving to memory.
The problem is the save command! For HP Procurve switches you use "save" or "write memory" commands to save changes and it's done. HP 5130 EI is a little bit different. There you must use "save force", if you only use "save" command you have to answer some questions.
Can this be fixed?
For HP-devices Portadmin does not really execute a save-command on the device. When we implemented the support for HP-devices in Portadmin this was not necessary. For Cisco devices this is done by issuing a 'write mem' when the changes are done.
It is however very possible that upgrades on software and new types of equipment now requires the equivalent of a 'write mem' on HP aswell. In that case it must be implemented.
If you have any information about how to do this (mibs, oids or documentation regarding that) that would be very helpful.
Live long and prosper
-- John Magne Bredal john.m.bredal@uninett.no +4791897366
Abels gt. 5- Teknobyen NO-7465 Trondheim
-- John Magne Bredal john.m.bredal@uninett.no +4791897366
Abels gt. 5- Teknobyen NO-7465 Trondheim