– The Management interface is the default interface for in-band management of the WLC and connectivity to enterprise services such as AAA servers. If the service port is in use, the management interface must be on a different subnet from the service port. The management interface is also used for layer 2 communications between the WLC and access points. The Management interface is the only consistently “pingable” in-band interface IP address on the WLC.
– The Virtual Interface is used to support mobility management, DHCP relay, and embedded layer 3 security like guest web authentication and VPN termination. The Virtual Interface must be configured with an unassigned and unused gateway IP address. A typical virtual interface is “1.1.1.1″. The Virtual Interface address will not be pingable and should not exist in any routing table in your network. If multiple WLCs are configured in a mobility group, the Virtual Interface IP address must be the same on all WLC devices to allow seamless roaming.
Note: The management interface on the WLC is the only consistently pingable interface from outside of the WLC. So it is an expected behavior if you are not able to ping the AP manager interface from outside of the WLC.
AP Manager
“used for all Layer 3 communications between the controller and lightweight access points
Dynamic
“Dynamic interfaces, also known as VLAN interfaces, are created by users and designed to be analogous to VLANs for wireless LAN clients”
Managment
“The management interface has the only consistently “pingable” in-band interface IP address on the controller”
Service port
“It is also the only port that is active when the controller is in boot mode”
Virtual
“used to support mobility management, Dynamic Host Configuration Protocol (DHCP) relay, and embedded Layer 3 security such as guest web authentication”
LOL… Angelo, just read the link Fuzzied posted. It’s not from Wikipedia… it’s Cisco official product page! And yes, according to Cisco info the answer int this site is wrong.
I just found out that I passed my Pass4sure 640-722 test. Thank you very much cisexams for these wonderful Unified Wireless Networking Essentials training materials.I will recommend your practice test questions to everyone.
This is straight from my notes, which comes from the Cisco Press book:
– Controller Ports
○ Service Port – Used for out-of-band management, system recovery, and initial boot functions; always connects to a switch port in access mode
○ Distributed system port – Used for all normal AP and management traffic, usually connects to a switch port in 802.1Q trunk mode.
○ Console port – used for out-of-band management, system recovery, and initial boot functions; asynchronous connection to a terminal emulator.
○ Redundancy port – used to connect to a peer controller for redundant operations
– Controller Interfaces
○ Management Interface – used for normal management traffic, such as RADIUS user authentication, WLC-to-WLC communication, web-based and SSH sessions, SNMP, NTP, syslog
○ AP-manager interface – used to terminate CAPWAP tunnels between the controller and its APs
○ Virtual interface – Used to relay client DHCP requests, client web authentication, and to support client mobility
○ Service port interface – Bound to the service port and used for out-of-band management
○ Dynamic interface – used to connect a VLAN to a WLAN
this is not correct.
Management and Virtual should reverse.
this is correct:
– The Management interface is the default interface for in-band management of the WLC and connectivity to enterprise services such as AAA servers. If the service port is in use, the management interface must be on a different subnet from the service port. The management interface is also used for layer 2 communications between the WLC and access points. The Management interface is the only consistently “pingable” in-band interface IP address on the WLC.
– The Virtual Interface is used to support mobility management, DHCP relay, and embedded layer 3 security like guest web authentication and VPN termination. The Virtual Interface must be configured with an unassigned and unused gateway IP address. A typical virtual interface is “1.1.1.1″. The Virtual Interface address will not be pingable and should not exist in any routing table in your network. If multiple WLCs are configured in a mobility group, the Virtual Interface IP address must be the same on all WLC devices to allow seamless roaming.
http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a0080665cdf.shtml
Note: The management interface on the WLC is the only consistently pingable interface from outside of the WLC. So it is an expected behavior if you are not able to ping the AP manager interface from outside of the WLC.
All answers found here:
http://www.cisco.com/en/US/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1167723
AP Manager
“used for all Layer 3 communications between the controller and lightweight access points
Dynamic
“Dynamic interfaces, also known as VLAN interfaces, are created by users and designed to be analogous to VLANs for wireless LAN clients”
Managment
“The management interface has the only consistently “pingable” in-band interface IP address on the controller”
Service port
“It is also the only port that is active when the controller is in boot mode”
Virtual
“used to support mobility management, Dynamic Host Configuration Protocol (DHCP) relay, and embedded Layer 3 security such as guest web authentication”
Not much input from me except, LISTEN TO FUZZIE 🙂 (He is correct)
The answer on this site is wrong…
no, it’s not… it’s correct
LOL… Angelo, just read the link Fuzzied posted. It’s not from Wikipedia… it’s Cisco official product page! And yes, according to Cisco info the answer int this site is wrong.
I just found out that I passed my Pass4sure 640-722 test. Thank you very much cisexams for these wonderful Unified Wireless Networking Essentials training materials.I will recommend your practice test questions to everyone.
This is straight from my notes, which comes from the Cisco Press book:
– Controller Ports
○ Service Port – Used for out-of-band management, system recovery, and initial boot functions; always connects to a switch port in access mode
○ Distributed system port – Used for all normal AP and management traffic, usually connects to a switch port in 802.1Q trunk mode.
○ Console port – used for out-of-band management, system recovery, and initial boot functions; asynchronous connection to a terminal emulator.
○ Redundancy port – used to connect to a peer controller for redundant operations
– Controller Interfaces
○ Management Interface – used for normal management traffic, such as RADIUS user authentication, WLC-to-WLC communication, web-based and SSH sessions, SNMP, NTP, syslog
○ AP-manager interface – used to terminate CAPWAP tunnels between the controller and its APs
○ Virtual interface – Used to relay client DHCP requests, client web authentication, and to support client mobility
○ Service port interface – Bound to the service port and used for out-of-band management
○ Dynamic interface – used to connect a VLAN to a WLAN