- Preface
- Chapter 1 - Overview
- Chapter 2 - Using the Web-Browser and CLI Interfaces
- Chapter 3 - Configuring Ports and Interfaces
- Chapter 4 - Configuring Controller Settings
- Chapter 5 - Configuring Security Solutions
- Chapter 6 - Configuring WLANs
- Chapter 7 - Controlling Lightweight Access Points
- Chapter 8 - Controlling Mesh Access Points
- Chapter 9 - Managing Controller Software and Configurations
- Chapter 10 - Managing User Accounts
- Chapter 11 - Configuring Radio Resource Management
- Chapter 12 - Configuring Mobility Groups
- Chapter 13 - Configuring Hybrid REAP
- Appendix A - Safety Considerations and Translated Safety Warnings
- Appendix B - Declarations of Conformity and Regulatory Information
- Appendix C - End User License and Warranty
- Appendix D - Troubleshooting
- Appendix E - Logical Connectivity Diagrams
- Index
Logical Connectivity Diagrams
This appendix provides logical connectivity diagrams and related software commands for integrated controllers. It contains these sections:
- Cisco WiSM
- Cisco 28/37/38xx Integrated Services Router
- Catalyst 3750G Integrated Wireless LAN Controller Switch
This section provides logical connectivity diagrams for the controllers integrated into other Cisco products, specifically the Catalyst 3750G Integrated Wireless LAN Controller Switch, the Cisco WiSM, and the Cisco 28/37/38xx Series Integrated Services Router. These diagrams show the internal connections between the switch or router and the controller. The software commands used for communication between the devices are also provided.
Cisco WiSM
Figure 1 Logical Connectivity Diagram for the Cisco WiSM
The commands used for communication between the Cisco WiSM, the Supervisor 720, and the 4404 controllers are documented in Configuring a Cisco Wireless Services Module and Wireless Control System at this URL:
http://www.cisco.com/c/en/us/td/docs/wireless/technology/wism/technical/reference/appnote.html#wp39498
Cisco 28/37/38xx Integrated Services Router
Figure 2 Logical Connectivity Diagram for the Cisco 28/37/38xx Integrated Services Router
These commands are used for communication between the 28/37/38xx Integrated Services Router and the controller network module. They are initiated from the router. The commands vary depending on the version of the network module.
These commands are used for communication between the router and Fast Ethernet versions of the controller network module:
- interface wlan-controller slot/unit (and support for subinterfaces with dot1q encap)
- show interfaces wlan-controller slot/unit
- show controllers wlan-controller slot/unit
- test service-module wlan-controller slot/unit
- test HW-module wlan-controller slot/unit reset {enable | disable}
- service-module wlan-controller slot/port { reload | reset | session [ clear ] | shutdown | status }
These commands are used for communication between the router and Gigabit Ethernet versions of the controller network module:
- interface integrated-service-engine slot/unit (and support for subinterfaces with dot1q encap)
- show interfaces integrated-service-engine slot/unit
- show controllers integrated-service-engine slot/unit
- test service-module integrated-service-engine slot/unit
- test HW-module integrated-service-engine slot/unit reset { enable | disable }
- service-module integrated-service engine slot / port { reload | reset | session [ clear ] | shutdown | status }
Note Refer to the Cisco Wireless LAN Controller Network Module Feature Guide for more information. You can find this document at this URL:
http://www.cisco.com/c/en/us/products/hw/tsd_products_support_end-of-sale_and_end-of-life_products_list.html
Catalyst 3750G Integrated Wireless LAN Controller Switch
Figure 3 Logical Connectivity Diagram for the Catalyst 3750G Integrated Wireless LAN Controller Switch
These commands are used for communication between the Catalyst 3750G switch and the 4402 controller.
This command is used to initiate a telnet session from the switch to the controller:
session switch_number processor 1
Because there can be several switches in a stack, the switch_number parameter is used to indicate to which controller in the stack this session should be directed. Once a session is established, the user interacts with the controller CLI. Entering exit terminates the session and returns the user to the switch CLI.
These commands are used to view the status of the internal controller. They are initiated from the switch.
Information similar to the following appears:
Information similar to the following appears:
The Wireless Control Protocol (WCP) is an internal keep-alive protocol that runs between the switch and the controller. It enables the switch to monitor the health of the controller and to report any problems. It uses UDP and runs over the two internal Gigabit ports, but it creates an internal VLAN 4095 to separate control traffic from data traffic. Every 20 seconds the switch sends a keep-alive message to the controller. If the controller does not acknowledge 16 consecutive keep-alive messages, the switch declares the controller dead and sends a reset signal to reboot the controller.
These commands are used to monitor the health of the internal controller.
This command is initiated from the controller.
where ? is one of the following:
Information similar to the following appears:
This command is initiated from the switch.
where ? is one of the following:
These two commands (in this order) are used to reset the controller from the switch. They are not yet available but will be supported in a future release.
Note A direct console connection to the controller does not operate when hardware flow control is enabled on the PC. However, the switch console port operates with hardware flow control enabled.