nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

R730 negotiating 100M no matter what I do

unknown

I've got a brand new batch of about 20 R730 APs. They're all connected to Cisco 2960X PoE+ Switchgear.

I don't know if I have a power issue or LLDP issue. but all of them running any version of the firmware with or without a controller etc.

They all are negotiating 100Mb max and I can't even set the speed to 100 through the CMD.

Haaaaaaalp!!

Find more posts tagged with

Accepted answers

All comments

syamantakomer

Hi Ray,

I don't think there is any known issues with R730, which is related to port speed.

You may try below and confirm the results.

Power up a R730 using POE injector or power adapter and connect a laptop directly with it. Check if laptop negotiates with 1000/Full
Check and make sure LLDP is enabled on both sides (SW and AP). Command for AP is "get lldp".
Confirm the firmware version of some of the APs (get version).
If possible, do a port mirror on CISCO SW and connect R730 to mirrored port and see what is going on with LLDP.
Try connecting AP to a different switch and see the results.

I am also suspecting if this is something with CISCO switch so take a look at SW config as well.

If still can't find the solution, open a support case.

Regards,
Syamantak Omer

DarrelRhodes

Hi Ray,

As well as Syamantak's excellent advice, also bear in mind the R730 requires high-power PoE (802.3bt) for full performance, as per the data-sheet extract I've attached.

Image_ images_messages_5f91c448135b77e2479fed48_4a22f7bfa465a1c7994110bdff3b2300_RackMultipart20200813761171u4m-f8ff746b-2118-4852-9803-d1a185b33f06-597970267.png1597319509

Image_ images_messages_5f91c448135b77e2479fed48_4a22f7bfa465a1c7994110bdff3b2300_RackMultipart20200813761171u4m-f8ff746b-2118-4852-9803-d1a185b33f06-597970267.png1597319509

Therefore, when being powered by your Cisco PoE+ (802.3at) switches, certain features will be disabled.

HTH,
Darrel.

syamantakomer

Hi Darrel,

Thanks for additional thoughts. However, even with 802.3af power, AP port (PoE port) should still be functional with 10M/100M/1G/5G speeds.

Image dataimagepngbase64iVBORw0KGgoAAAANSUhEUgAAAkUAAABYCAYAAAD7qYOtAAAgAElEQVR4Ae3dh29cS5vn943DQP22Ls7nt31eg0DNgysjV3MALPr2ZnZ933nDXPzVc6iIkVSiaRIiqSoRAUq55yzrm54yg8xRJbLVLqpkR1Uc00Gx2n3Oq6tSp8K3f81

Image dataimagepngbase64iVBORw0KGgoAAAANSUhEUgAAAkUAAABYCAYAAAD7qYOtAAAgAElEQVR4Ae3dh29cS5vn943DQP22Ls7nt31eg0DNgysjV3MALPr2ZnZ933nDXPzVc6iIkVSiaRIiqSoRAUq55yzrm54yg8xRJbLVLqpkR1Uc00Gx2n3Oq6tSp8K3f81

Regards,
Syamantak Omer

DarrelRhodes

Absolutely! I just wanted the customer to be aware of the of the other AP functionality impacts of low-power mode. The wouldn't be an issue with a Ruckus ICX7150-24P/48P/48PF or multi-gig 7150-48ZP switch, for example. 🙂

syamantakomer

Thanks! It is a major point many users miss and later face issues like low throughput, low coverage area and unable to use second eth port.

Regards,
Syamantak Omer

albert_pierson

One simple but common problem when AP's cannot negotiate above 100Mbps maybe cabling.
100MBps uses only 2 pairs of UTP while 1000MBps (GiGE) requires all 4 pairs. Check the cabling infrastructure to make sure all 4 pairs are properly terminated from AP to Switch. Setting the AP to auto negotiate (default) and also configuring switch port to auto negotiate should result in 1000MBps operation without further configuration.

unknown

That's a sensible recommendation, however the issue is only present with R730 APs and it's every one of them in the district which is 25 of them across 10 or so different switch stacks.

syamantakomer

Another important point we missed.

Thanks Albert!

Regards,
Syamantak Omer

syamantakomer

Hi Ray,

In that case you may need to follow what I have suggested in my first comment.

Regards,
Syamantak Omer

unknown

Hi everyone, update on this, I've completed a packet capture for one of the trouble APs on start up. Please see a breakdown of the LLDP packet below ->

Frame 6: 160 bytes on wire (1280 bits), 160 bytes captured (1280 bits) on interface \Device\NPF_{CC6F43DD-B306-4894-A15E-51A78BC9AB47}, id 0
Ethernet II, Src: 70:ca:97:2f:f2:00 (70:ca:97:2f:f2:00), Dst: LLDP_Multicast (01:80:c2:00:00:0e)
Link Layer Discovery Protocol
Chassis Subtype = MAC address, Id: 70:ca:97:2f:f2:00
0000 001. .... .... = TLV Type: Chassis Id (1)
.... ...0 0000 0111 = TLV Length: 7
Chassis Id Subtype: MAC address (4)
Chassis Id: 70:ca:97:2f:f2:00 (70:ca:97:2f:f2:00)
Port Subtype = MAC address, Id: 70:ca:97:2f:f2:00
0000 010. .... .... = TLV Type: Port Id (2)
.... ...0 0000 0111 = TLV Length: 7
Port Id Subtype: MAC address (3)
Port Id: 70:ca:97:2f:f2:00 (70:ca:97:2f:f2:00)
Time To Live = 120 sec
0000 011. .... .... = TLV Type: Time to Live (3)
.... ...0 0000 0010 = TLV Length: 2
Seconds: 120
System Name = AP04
0000 101. .... .... = TLV Type: System Name (5)
.... ...0 0000 0100 = TLV Length: 4
System Name: AP04
System Description = Ruckus R730 Multimedia Hotzone Wireless AP/SW Version: 5.1.2.0.373
0000 110. .... .... = TLV Type: System Description (6)
.... ...0 0100 0010 = TLV Length: 66
System Description: Ruckus R730 Multimedia Hotzone Wireless AP/SW Version: 5.1.2.0.373
Capabilities
0000 111. .... .... = TLV Type: System Capabilities (7)
.... ...0 0000 0100 = TLV Length: 4
Capabilities: 0x001c
Enabled Capabilities: 0x001c
Management Address
0001 000. .... .... = TLV Type: Management Address (8)
.... ...0 0000 1100 = TLV Length: 12
Address String Length: 5
Address Subtype: IPv4 (1)
Management Address: 10.0.104.48
Interface Subtype: Unknown (1)
Interface Number: 0
OID String Length: 0
Port Description = eth1
0000 100. .... .... = TLV Type: Port Description (4)
.... ...0 0000 0100 = TLV Length: 4
Port Description: eth1
Ieee 802.3 - Link Aggregation
1111 111. .... .... = TLV Type: Organization Specific (127)
.... ...0 0000 1001 = TLV Length: 9
Organization Unique Code: 00:12:0f (Ieee 802.3)
IEEE 802.3 Subtype: Link Aggregation (0x03)
Aggregation Status: 0x01
Aggregated Port Id: 0
Ieee 802.3 - MAC/PHY Configuration/Status
1111 111. .... .... = TLV Type: Organization Specific (127)
.... ...0 0000 1001 = TLV Length: 9
Organization Unique Code: 00:12:0f (Ieee 802.3)
IEEE 802.3 Subtype: MAC/PHY Configuration/Status (0x01)
Auto-Negotiation Support/Status: 0x03
PMD Auto-Negotiation Advertised Capability: 0x84c1
Same in inverse (wrong) bitorder
Operational MAU Type: 100BaseTXFD - 2 pair category 5 UTP, full duplex mode (0x0010)
End of LLDPDU
0000 000. .... .... = TLV Type: End of LLDPDU (0)
.... ...0 0000 0000 = TLV Length: 0

Thanks

unknown

100BaseTXFD - 2 pair category 5 UTP, full
needs 2 more pair to work.

unknown

I'm totally willing to except that, however it's every R730 in the building that's doing this and all other AP models are negotiating full 1000 full duplex... unless my R730's somehow all got connected to 2 pair wires which would be horrific coincidence. There's 25 of them throughout the building on roughly 6 different switch stacks.

unknown

Perhaps pull the easiest / most accessible AP down and test all cables, keystones, and patches. if the cables/keystones are all punched down correctly, then I would bench your R730, and see if the problem re-appears when it's not at the end of the cable run. Ruckus has been known to run bad batches of APs (ZF7982 V1 board for example).