01-15-2007 12:28 AM - edited 07-03-2021 01:28 PM
I have a WISM running code 4.0.179.11.
~250 APs connected (1131) all switchports configured on 100/full.
Around 30% of the Aps are having duplex/speed mismatches. If i change the connected switchports to AUTO the APs nicely return on 100/Full.
Anyone has the same issue?
Reg
Goen
01-17-2007 01:05 PM
Goen:
Due to the nature of duplex negotiation, if you force one side and not the other, you are VERY likely to get a mismatch. For this reason, Cisco considers it best practice to leave APs and switchports they connect to at auto to ensure the best handshake.
-Eric
Please remember to rate all helpful posts.
04-05-2007 01:43 PM
Yes, same here
And for us, auto/auto on both sides is not desireable since we have had occasional problems when we leave the APs/switches to negotiate. If you have serial console access you can set the duplex by entering "debug lwapp console cli" and then you'll be able to config term, BUT...
If you try to do a wr on a LWAPP, you'll corrupt the configs and have to redo the whole cert chain and such. You cannot get the settings to stick -- they are all stored in the private-multiple-fs file, which has in it all the files in nvram: IOS (JA) doesn't seem to be able to write these files correctly, only the WCS, and there is no "config ap ?" command for hardwire duplex settings.
Sigh.
05-07-2007 09:05 AM
solved in version 4.1.171
"config ap ethernet" on the CLI
05-11-2007 10:53 AM
Any idea on how this could be done to a 1010 AP?
I tried that command and it's saying that the configuring ethernet port settings is not supported by the AP.
05-14-2007 06:23 PM
Just configure your switch ports to auto speed and duplex and be done with it. The last issue with a 10/100 NIC that had an auto negotiation problem with a Cisco switch was 10 years ago using specific Catalyst 5000 blades.
If you search these forums you will find hundreds of reports similar to what you describe, and the resolution is always the same: configure both ends of the connection to auto speed and duplex and your problem will go away.
What most people don't realize is that you *CANNOT* negotiate duplex if you don't negotiate speed. Therefore, if you plug an auto speed and duplex AP into a hardset speed and duplex port, the AP's Ethernet port will detect the 100 Mbit speed (carrier) but cannot negotiate the duplex and will default to half duplex, which is a mismatch.
By definition, a port set to auto speed and duplex on one side (AP or PC) and speed 100 and duplex full on the other (switch port), you will have a duplex mismatch. Always. Not sometimes.
05-14-2007 07:59 PM
Yes no way to force duplex and speed on an LWAPP AP.
Should configure the switchport as auto.
12-13-2007 01:45 PM
I too would like to be able to nail up the speed and duplex on the LWAPP AP. I have some at the end of a fiber run with a fiber to copper transceiver. I ran the upgrade tool on some 1231s and the switch negotiates to 100/half. I have no idea what the AP is negotiating to. If it were all copper, then Auto would be not problem. But the transceivers get in the way of the negotiation. So I want to explicitly set the speed and duplex on the AP and the switch port. The controller should allow us to configure this remotely.
05-12-2008 02:18 AM
There is a document on Cisco site that details entering the following command into a Wireless controller:
configure ap ethernet duplex
The document can be found here:
http://www.cisco.com/en/US/products/hw/wireless/ps430/products_qanda_item09186a00808b4c61.shtml
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide