Hi. 1: The VLAN tag exists on the switch. So that should not be a problem. (Have checked dot1qVlanCurrentEntry and it's there)
2: All ports are set to admitAll(1)
----- Ursprungligt meddelande ----- Från: "John Magne Bredal" email@example.com Till: "Mattias Söderholm" firstname.lastname@example.org Kopia: "Morten Brekkevold" email@example.com, "nav-users" firstname.lastname@example.org Skickat: måndag, 14 mar 2016 11:00:30 Ämne: Re: Portadmin - Problem with changing Vlan
On 08. mars 2016 12:24, Mattias Söderholm wrote:
What I'm getting with tcpdump is the following: GetRequest(33) 126.96.36.199.188.8.131.52 GetResponse(35) 184.108.40.206.220.127.116.11=<VLANTAG NOW> SetRequest(35) 18.104.22.168.22.214.171.124=<NEWVLANTAG> GetResponse(35) inconsistentValue@1 126.96.36.199.188.8.131.52=<NEWVLANTAG>
The RAW response with OID View looks like this: 184.108.40.206.220.127.116.11.18.104.22.168.1.1 GAUGE <VLANTAG> ( That is OID, TYPE, VALUE)
Hm, the communication looks normal. I can only see two possible errors:
1: The NEWVLANTAG does not exist on the device. This should not happen as PortAdmin fetches all available vlans before presenting them as choices in the web interface. Could you please verify that the vlan is defined on the device?
2: We've recently discovered that the oid dot1qPortAcceptableFrameTypes exists, as this lead to problems here in Uninett. This was set to admitOnlyVlanTagged and lead to problems setting vlans for PortAdmin. A get on this oid on the interface should reveal if this is set to something else than admitAll.
----- Ursprungligt meddelande ----- Från: "John Magne Bredal" email@example.com Till: "Morten Brekkevold" firstname.lastname@example.org, "Mattias Söderholm" email@example.com Kopia: "nav-users" firstname.lastname@example.org Skickat: måndag, 7 mar 2016 14:35:09 Ämne: Re: Portadmin - Problem with changing Vlan
On 07. mars 2016 10:14, Morten Brekkevold wrote:
On Fri, 4 Mar 2016 09:49:43 +0200 Mattias Söderholm email@example.com wrote:
For a couple of week ago we could change Vlan in portadmin and save with our HP 5130 switches. But now with Nav 4.4.2 it only show error when saving. It says: Error setting vlan: SNMP Error: inconsistentValue (The set value is illegal or unsupported in some way).
What can be the problem?
There have been some recent bugfixes to the Portadmin tool, specifically regarding HP switches. I'll have John-Magne look into it.
Hm, the bugfixes related to PortAdmin has been related to saving the interface-data to the database and access-control for users when that has been turned on. Nothing related to switching vlans has been changed.
You are however experiencing a problem, so lets try to debug it. The error message is for once describing quite well what is wrong, so we need to see what NAV tries to set. To do this you need to run some form of packet sniffer, for instance use tcpdump to capture and then use Wireshark to inspect the traffic. If you sniff when trying to set the vlan, it should give you the SNMP-command issued.