failed to find VPIF 0

[Alexandr_P]

Hi, all!

Have log in stack of X670V
10/28/2015
11:24:07.40 Slot-2: exvlan: setVpifState:3075: KERNEL_EXVLAN_ERROR: failed to find VPIF 0 [slot 256 port 32] on VLAN 1000020
10/28/2015 11:24:07.40 Slot-2: exvlan: setVpifState:3075: KERNEL_EXVLAN_ERROR: failed to find VPIF 0 [slot 256 port 31] on VLAN 1000020

After that vlan 2935 is automatically disabled.
After enable this vlan - enable vlan "VLAN_2935_SIP" this logs appear again
10/28/2015 13:13:56.69 Slot-2: exvlan: setVpifState:3075: KERNEL_EXVLAN_ERROR: failed to find VPIF 0 [slot 256 port 32] on VLAN 1000020 10/28/2015 13:13:56.69 Slot-2: exvlan: setVpifState:3075: KERNEL_EXVLAN_ERROR: failed to find VPIF 0 [slot 256 port 32] on VLAN 1000020

10/28/2015 13:13:56.69 Slot-2: exvlan: setVpifState:3075: KERNEL_EXVLAN_ERROR: failed to find VPIF 0 [slot 256 port 31] on VLAN 1000020

Any ideas?

Thank you!

[BrandonC]

Hi Alexandr,

'show tech all' does include 'show conf', but the .cfg is actually an XML file, which is the actual config file that the switch reads on boot. I'm thinking that there may be something strange in the config, so having the actual XML file that the switch loads the config from would be helpful. You can see the config file that was booted in the output of 'show switch', and you can TFTP this file off to a TFTP server.

If you do 'upload debug', this will also get the current .cfg file.

-Brandon

[Alexandr_P]

Hi, Brandon!

Case is opened.
Isn't "show tech-sup all" contain "sh conf" section?

Thank you!

[Alexandr_P]

First time - almost at once with login to switch:
10/28/2015 11:24:07.40 Slot-2: exvlan: setVpifState:3075: KERNEL_EXVLAN_ERROR: failed to find VPIF 0 [slot 256 port 32] on VLAN 1000020 10/28/2015 11:24:07.40 Slot-2: exvlan: setVpifState:3075: KERNEL_EXVLAN_ERROR: failed to find VPIF 0 [slot 256 port 31] on VLAN 1000020

10/28/2015 11:23:56.73 Slot-1: Msg from Master : Did password authentication for user duzhvenko (10.10.200.24)

10/28/2015 11:23:56.73 Slot-1: Login passed for user duzhvenko through ssh (10.10.200.24)

Second time after enable vlan.

New configuration - it's create 4 new vlans with tags and ports.

Thank you!

[BrandonC]

Does this error pop up immediately after enabling the VLAN? Or is there a delay between the VLAN being enabled and the logs appearing?

Also, was this working previously, or is this a new implementation? If it was working, were there any changes recently made?

-Brandon