- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
NMS300 unable to discover WAC720
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
I have 5 WAC720 running in ensemble mode (firmware 3.1.5.0). When I try to discover them using NMS300 the software reports "Credential Failure", while I am sure the credentails are correct. I have tried different authentication methods (HTTP, Telnet, SNMPv1) but nothing works.
Any help in troubleshooting this?
Thx
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
I've found the solution: the credential here should be snmpv2c not snmpv1 or 3.
Now they are all discovered without a hitch.
Thanks for your help.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: NMS300 unable to discover WAC720
Hi janaps,
Let me share this article and it might help. Kindly use it as a guide
Also, try to update the firmware of the WAC720 to v3.6.12.0. Be sure to perform a factory reset on the WAC720 after upgrading the firmware then reconfigure it from scratch. Let us know the result.
Regards,
DaneA
NETGEAR Community Team
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: NMS300 unable to discover WAC720
Hi
I've looked through the article and these steps (in general) I had allready taken
I've upgrade the ap's to v3.6.12 as you suggested, and I noticed the credential failure problem only occured when I put the ap in ensemble mode. So I upgraded, changed the password, tried discovery, and everything was OK
After joining it to the ensemble it was reported as down by the NMS30000
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
I've found the solution: the credential here should be snmpv2c not snmpv1 or 3.
Now they are all discovered without a hitch.
Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content