cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1827
Views
5
Helpful
3
Replies

WLC SNMP Error 604

doodles6970
Level 1
Level 1

Hello,

 

I have just deployed an HA deployment of Prime Infrastructure 3.4 and are running the latest patches and device packs.

I have just tried to discover my WLC'c via SNMP v3 but I keep getting SNMP Sync Error. I have checked and double checked the settings on the WLC with the Credential profile and they are correct.

 

I have debugged this on the WLC and I can see the traffic getting to the WLC but I get this error.

 

Packet from: *IP OF PRIME SERVER*:49730, in_packet_len = 137

*SNMPTask: Apr 02 16:42:41.928: [PA] SNMPD: Failed to build SnmpMessage error code = 604

*SNMPTask: Apr 02 16:42:41.928: [PA] SNMPD: *NOT* sending out packet, out_packet_len = 0

I have tried SNMP 2c and this works fine without a problem. I cannot just use 2c though as it violates security policy.

 

Does anyone know what this could be? WLC's are 5520's running 8.5.140.0

3 Replies 3

marce1000
VIP
VIP

 

  = There have been numerous reports concerning Prime's snmp v3 capabilities in the past. If it all works with SNMP Manager software quering a controller with v3, then Prime is to blame.

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Hi Marce,

I would tend to agree with that. SNMP Manager software? Which software is this, can you point me in the right direction of this?
I may have to open a TAC Case.

Ryan

I have managed to get this resolved.

 

Although, I'm not too sure what the actual issue was.

I setup both controllers in P.I for SNMP v2c and discovered them, I then deleted them, modified the credential profile for SNMP v3 and discovered again and this has seemed to work.

 

I have since disabled SNMP v2c and re-synced the controllers and they are still connected. Fingers crossed for this. It seems to P.I issue here. I did use the SNMP tester tool from Paessler to verify SNMP v3 was working.

 

Thanks for the advice guys.

Review Cisco Networking for a $25 gift card