12-22-2014 05:15 AM
I have an existing 3AP943 network in a VC. I am trying to add an additional 103 and it will not join the VC. I hd left it connected over the weekend but no luck.
Any ideas why it doesn't show?
Solved! Go to Solution.
12-22-2014 05:28 AM
I cannot access the 103 thru the gui. Once i put the address into the address bar, the page is redirected to my vc. if i use port 4343 i get a login page, but i cannot login in using the default or my existing AP password. Is there some other port i can use to get into it? I had this same issue on a different 103, and i had it swapped out for this one. its the same problem with both.
12-22-2014 05:47 AM
When you are able to ping , the issue should be with image sync. IAP 103 is a Pegasus and IAP 93 is a Orion hence they will not sync the Image automatically. it is possible either mannually or through Airwave server.
So update the IAP with same Image as IAP 93 then connect it to the network.
hope got some clarity,
Please feel free for any further clarity on this.
[Is my post helped you ? Give Kudos :) ]
12-22-2014 05:48 AM
10-15-2015 03:57 PM - edited 10-15-2015 03:58 PM
Having the same issue with IAP-92's. They are running the latest 126.96.36.199-188.8.131.52_51810.
The 103 is stuck in some degraded CLI state which makes it impossible to upgrade - even the GUI won't let me login. Needless to say we will start looking for a different vendor for AP remote deployments, these Instant APs are getting far too buggy to deal with. When you can't even add it to an existing group without breaking it, completely ridiculous.
Is this going to be the case for every upgrade moving forward with a mix of firmware/APs? One of the models will break until manually upgraded? Also, it would help if in the firmware download section you actually listed what the 103's use (Pegasus for anyone dealing with this headache).