topic for now I have not tested in Wireless

PI 2.2.2 /CT8540 snmp : device is unreachable

said.sayah — Mon, 05 Jul 2021 11:14:13 GMT

I can't add my CT8540 8.1.102 to my PI 2.2.2, I use snmp V3

I add a SNMP V3 user to my CT8540 ( user, authen Proto HMAC-SHA and Privac Proto CFB-AES-128).

I add the devise to my PI , I use snmp V3 and SSH , when I check credential I have only this message (snmp : device is unreachable).

can someone help me to resolve this.

Tanks

Did you try this with SNMPv2

Rasika Nayanajith — Mon, 16 Nov 2015 18:51:23 GMT

Did you try this with SNMPv2 ?

I have got a 8540 configure in next couple of days. Once I tested, I will let you know

HTH

Rasika

for now I have not tested

said.sayah — Mon, 16 Nov 2015 18:57:53 GMT

for now I have not tested with SNMPv2 , I will test soon
Thanks for your feedback

Make sure your SNMP Trap

Scott Fella — Mon, 16 Nov 2015 20:30:00 GMT

Make sure your SNMP Trap Reciever allows the ip address. Also double check that what you setup for smnp v3 on the WLC is the same on PI 3.0. The defaults on the WLC and PI is different.

-Scott

my SNMP Trap reciever is my

said.sayah — Mon, 16 Nov 2015 20:52:21 GMT

my SNMP Trap reciever is my PI ( Version 2.2).
I use the same parameters to configure the SNMP v3 in both equipment

If SNMPv2 doesn't work, I'm

Scott Fella — Mon, 16 Nov 2015 21:01:10 GMT

If SNMPv2 doesn't work, I'm assuming that your on PI v2.2.1, v2.2.2 or v2.2.3 which has support for WLC v8.1.x

http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html#pgfId-148410

-Scott

I would do the test tomorrow

said.sayah — Mon, 16 Nov 2015 21:23:49 GMT

I would do the test tomorrow with SNMP v2

Same problem with SNMPv2 no

said.sayah — Tue, 17 Nov 2015 22:47:20 GMT

Same problem with SNMPv2 no issue !

In Prime i have message when I add device and try crediantial :

Verfication of one or more of following fields failed : SNMP read community, SNMP write community. Please fix this and retry

when I try to discover my WLC I have this me

Failure Reason

 Device : /172.20x.x got snmp timeout when querying system table from the device

I had some trap log in my CT8540 :

SNMP Authentication Failure: IP Adress:172.20.x.x

My Prime is in version 2.2.2

My couple of CT 8540 are in version : 8.1.102.0

After this :

I delete my old snmpv3user
I fix the NTP parameter in my WLC
I create new SNMPv3 user
I reboot the both WLC

And when I add my device and try my crediantial, I have his message :

SNMP : Device is Unreachble

Hello,

GERALD LECAILLIER — Mon, 23 Nov 2015 18:47:27 GMT

Hello,

We have same problem with PI 2.2.2 and WLC 8540 8.1.102.0. in snmp V3 or V2c.

> no problem between switchs 6880, 3850 and PI

> with monitor session (source: wlc port-channel, dest: my laptop), we noticed that WLC sends no traps

I have added my 8540 to PI3.0

Rasika Nayanajith — Mon, 23 Nov 2015 18:59:08 GMT

I have added my 8540 to PI3.0 using SNMPv3 without any trouble. I dit it via CLI on WLC

config snmp v3user create <user> rw hmacsha aescfb128 <authkey> <encrypkey>

May be this is specific to PI 2.2

HTH

Rasika

Our CT8540 does not generate

said.sayah — Mon, 23 Nov 2015 22:00:17 GMT

Our CT8540 does not generate the snmp trap,

In which version is your CT8540 ? mine is in 8.1.102.0

Saïd,

Hi Rasika,

said.sayah — Tue, 01 Dec 2015 21:31:44 GMT

Hi Rasika,

I upgrade my CT8540 to version AIR-CT8540-K9-8-1-131-0 but we have the same issue with PI2.2.2, PI2.2.3 and we try also today with PI 3.0.

Can you tell me in witch version are your CT8540 ?

Hi Said,

Rasika Nayanajith — Tue, 01 Dec 2015 22:16:41 GMT

Hi Said,

Here is my 8540 details. I simply created snmpv3 user (with R/W permission) on WLC and add that WLC to prime using same credentials.

(8540-WLC) >show snmpv3user

SNMP v3 User Name AccessMode Authentication Encryption 
-------------------- ----------- -------------- ---------- 
primexxx Read/Write HMAC-SHA CFB-AES

(8540-WLC) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.1.131.0
RTOS Version..................................... 8.1.131.0
Bootloader Version............................... 8.1.102.0
Emergency Image Version.......................... 8.1.102.0

HTH

Rasika

I don't know why you are

Scott Fella — Tue, 01 Dec 2015 22:35:37 GMT

I don't know why you are having issues. I have used snmpv3 a t a few customers with no no issues but most stick with snmpv2.

-Scott

Hello,

GERALD LECAILLIER — Thu, 03 Dec 2015 09:24:04 GMT

Hello,

We noticed something interesting (i'm Said's colleague):

- our prime and wlc are in different

- if we set an interface for the WLC in same vlan as the prime: it works

On the cores (VSS Cisco 6880), intervlan routing works fine and there is no acl.

Gateways and masks are ok, we dont undersand...

Can you tell us what ports on

Scott Fella — Thu, 03 Dec 2015 13:35:44 GMT

Can you tell us what ports on the 8540 you have connected to the network? I would just have one 10G/1G port connected and also make sure that the service port IP address is not routable on the network. I don't know how your 8540's are setup, so I'm just stating things that can cause issues.

-Scott

Try to download a free snmp

Scott Fella — Thu, 03 Dec 2015 13:46:36 GMT

Try to download a free snmp test tool that also supports v3. Run this on a device that is connected to the same vlan as your PI 2.2 and see if you get a response back or not. At least this will determine is something on the network is the issue or the 8540.

-Scott

Hello,

GERALD LECAILLIER — Thu, 03 Dec 2015 13:47:36 GMT

Hello,

Thanks for your help:

- WLC 1 (active)

port 1 to 6880 active - lag to etherchannel 15

port 2 to 6880 active - lag to etherchannel 15

- WLC 2 (HA-standby)

port 1 to 6880 passive - lag to etherchannel 16

port 2 to 6880 passive - lag to etherchannel 16

-Service port on both WLC: not plugged, no ip address

Thanks 🙂

Unplug port 2 on both

Scott Fella — Thu, 03 Dec 2015 13:51:04 GMT

Unplug port 2 on both controllers and just have port 1 for now. Setup an IP address on the service port like 192.0.2.x.

-Scott

Scott,

GERALD LECAILLIER — Thu, 03 Dec 2015 14:08:10 GMT

Scott,

We made the test you asked:

1/ with snmp tool, we dont recieve traps in the vlan 3

(vlan 3= PI)

(vlan 6= WLC)

In the vlan 6, we recieve the traps.

2/ then we shut down port 2 on both WLC, and set ip service port to 192.0.2.1/24 (but not plugged)

We made the test with snmp too in vlan 3 : no traps

thanks