Upto my knowledge, border manager can well understand the requests from the Cisco products. so, I dont think compatibility can be an issue here. Better, you send the border manager server configuration and also the details of the user who got rejected. I will compare both these details and find out the cause of this error.
Novell Border Manager does not support any of the EAP protocols used for authentication with Wireless.
We endedup using either the Funk Odyssey Client or the Meetinghouse Aegis client to support WPA with backend PAP authentication. The Radius server we settled with was Funk Steel Belted Radius that queries Novell eDirectory via LDAP.
You won't be able to do authentication against Novell BorderManager without passing your credentials in the clear through the air.
IntroductionHow to use the Wireless LAN Controller Configuration Analyzer (WLCCA)
Javier Contreras is a Senior Tech Lead for the Wireless Business Unit in Cisco, with over 2 decades of experi...
< PRE >
(#)For this reason being that : - application that doesn't use multicast, sends one copy of each packet ( data unit of traffic at layer 3 ) to each client (" who seeks the traffic ).- application that does use multicast, sends ...
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...