Hi All I am currently in the process of setting up TACACS+ for a new WLC 9800 deployment and have come across a 'feature' where only standard ASCII characters are permitted in passwords. This isn't particularly helpful for deployments outside the US...
Hi AllDoes anybody know if there is a replacement for the once wonderful Wireless Bridge Calculation Utility? I am proposing a short wireless bridge link, no more than 40m, and need an understanding of the expected data rates. I can't seem to find ...
Merry Christmas Everyone! I have a quick query...I have a pair of ISE nodes running 2.4 Patch 10 that seems to insist on trying to use FIPS for SSH/SFTP which I believe is causing the connecttion to fail as the remote server is not FIPS capable. FIPS...
Hi AllI am trying to enable authentication to the ISE Sponsor Portal using LDAP lookup to AD groups. Security policy dictates that the ISE nodes cannot be domain joined to the AD so I have to use LDAP lookup. This works fine with standard Distributi...
Hi All Hopefully an easy one... Is IPSK supported with mobility anchor? I can't find anything to say it is though I also can't find anything to say it isn't... As the RADIUS request is coming from the foreign controller I can't see why it wouldn't ...
Hi Patoberli No problem at all and thanks for taking the time to test and confirming your results. I am glad that it is not just me, though saying that, if it was, it could have been fixable. I'll get a feature request raised through our account man...
Hi Patoberli Thanks for your messages and apologies, I don't mean to sound rude, but I'm not mixing up anything. The WLC 9800-CL, I haven't other instances to test from, won't accept passwords, whether local or TACACS+ if they contain non-ASCII char...
Unfortunately that isn't the case. Even when trying to set a local user account on the 9800 WLC the ASCII error flags. I was hoping that there is someway of expanding the character set, though there doesn't appear to be alas.
Hi Davsnet Apologies for the delay, my issue was the opposite, I had FIPS disabled however the connection was defaulting to FIPS enabled. The issue appear to resolve itself unfortunately and I could no longer replicate. Apologies.
Hi All Sorry to dredge up an old post, but I have been experiencing this issue also. Queue link error due to invalid ISE Messaging cert. We have a simple primary/secondary node deployment and I could see that the Certificate Services Node CA in the ...
