cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

520
Views
5
Helpful
2
Replies
Highlighted
Beginner

PI3.3.1U1: Job: Wired Client Status results in SNMP error VLAN4095

Hi everyone.

I have some minor alarms in PI that I would like to ask if anyone else have stumbled upon.

 

When this job runs:

PI_job.PNG

 

It results in this minor alarm in PI:

PI_error_message.PNG

 

As far as I can see the reason is that PI sends a SNMP getBulkRequest asking the switch something on VLAN4095

WS_getbulkrequest.PNG

 

 

The access switch replies with a trap resulting in a authenticationFailure:

WS_trap_response.PNG

 

 

Does anyone know why PI is requesting information about VLAN4095 on an access switch? I thought 4095 was a VLAN used for internal purposes only.

 

 

-Petter

 

1 ACCEPTED SOLUTION

Accepted Solutions
Beginner

Re: PI3.3.1U1: Job: Wired Client Status results in SNMP error VLAN4095

Hi.

Based on what you wrote I have concluded that the following row is causing my issue:

 

switchport voice vlan untagged

Seems like this row ends up using VLAN 4095 in replies from Prime Infrastructure (SNMP getBulkRequest MIB 1.3.6.1.4.1.9.9.68.1.5.1.1 which is vmVoiceVlanEntry). Since VLAN 4095 is not present in vlan.dat like a normal VLAN number it all ends up in an authenticationFailure trap from the switch to PI. I think the error is how PI handles SNMP responses when VLAN 4095 shows up!

2 REPLIES 2
Beginner

Re: PI3.3.1U1: Job: Wired Client Status results in SNMP error VLAN4095

Hi,

 

i have had a similar problem and the reason was configured VLAN on access port, that doesn't exist in vlan.dat

for example this configuration will result in authentication error

Interface gi1/1
switchport access vlan 5
exit
no vlan 5
Beginner

Re: PI3.3.1U1: Job: Wired Client Status results in SNMP error VLAN4095

Hi.

Based on what you wrote I have concluded that the following row is causing my issue:

 

switchport voice vlan untagged

Seems like this row ends up using VLAN 4095 in replies from Prime Infrastructure (SNMP getBulkRequest MIB 1.3.6.1.4.1.9.9.68.1.5.1.1 which is vmVoiceVlanEntry). Since VLAN 4095 is not present in vlan.dat like a normal VLAN number it all ends up in an authenticationFailure trap from the switch to PI. I think the error is how PI handles SNMP responses when VLAN 4095 shows up!

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards