×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

AIR-CAP702W local ethernet ports

Answered Question
Jul 14th, 2014
User Badges:

Hi all,

The new AIR-CAP702W AP have 4 10/100/1000Base-T local Ethernet ports.
On the data-sheet it's written "for wired devices connectivity".

http://www.cisco.com/c/en/us/products/collateral/wireless/aironet-700-se...

 

That's very good, but how do we manage the traffic on these ports?

  • Are we able to configure theses ports in access-mode with different VLAN-IDs?
    So in that case the uplink of the AP should be in trunk-mode.
    And where do we configure the ports of the AP, on the WLC?
     
  • Or is the traffic from the devices connected into these ports encapsulated into CAPWAP tunnel, like the wireless data traffic, and is terminated into the WLC(s)?
    In that case, can we choose what port is associated to what VLAN/SSID on the WLC?
     
  • Or something else maybe?


Thank you for your help.
Jerome

 

Correct Answer by Moin Ilyas about 3 years 4 weeks ago

The 4 x 10/100/1000BASE-T local Ethernet ports support half and full duplex mode, auto-negotiation, and MDI/MDIX Auto-Sensing. Devices you connect must support auto negotiation if you connect with another mode, say hard configured speed and so on. The port may not be enabled and depending on the version of code, for example 7.6.100.120 the initial release, the ports are not managed.

For now, (until more control is added in the software) all the LAN ports are locally switched, are mapped to the 702W VLAN, and do not appear on the Wireless LAN Controller or AP.

Initially, the ports are disabled and may be enabled manually via CLI.

This was done to minimize any security risks. Here are the CLI commands to enable the ports.

(Cisco Controller)> config ap lan <port id> <enable/disable> <AP-NAME>

(Cisco Controller)> show ap lan <port id> <AP-NAME>

(Cisco Controller)> show ap lan port-summary <AP-NAME>

Hope that helps.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Moin Ilyas Mon, 07/21/2014 - 19:02
User Badges:
  • Bronze, 100 points or more

The 4 x 10/100/1000BASE-T local Ethernet ports support half and full duplex mode, auto-negotiation, and MDI/MDIX Auto-Sensing. Devices you connect must support auto negotiation if you connect with another mode, say hard configured speed and so on. The port may not be enabled and depending on the version of code, for example 7.6.100.120 the initial release, the ports are not managed.

For now, (until more control is added in the software) all the LAN ports are locally switched, are mapped to the 702W VLAN, and do not appear on the Wireless LAN Controller or AP.

Initially, the ports are disabled and may be enabled manually via CLI.

This was done to minimize any security risks. Here are the CLI commands to enable the ports.

(Cisco Controller)> config ap lan <port id> <enable/disable> <AP-NAME>

(Cisco Controller)> show ap lan <port id> <AP-NAME>

(Cisco Controller)> show ap lan port-summary <AP-NAME>

Hope that helps.

Jerome Tissieres Tue, 07/22/2014 - 02:16
User Badges:

Thank you.

Do you know if there's any plan to integrate this into the WLC GUI in a future release?
And also the possibility to tag theses ports with other VLAN-id in the future?

Thank you.
Jerome

David Ritter Wed, 07/23/2014 - 08:25
User Badges:
  • Bronze, 100 points or more

all things come to he who waits..

all will be as expected in Ver 8 code.

of course we all might croak before then.

 

For my purpose, the current state is functional..  my 7942 on lan4 finds its way home and the attached workstation functions.

My expectations are that the lan ports will remain LOCAL/TRUNK and not RLAN like OEAP602's.

Basically I think of it as an AP in a 5 port switch.. one port be the AP and the rest come out to play.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode