resumen capitulo 6 cisco ccna 1

resumen capitulo 6 cisco ccna 1.The managementinterface controls the communication of all physical ports in the network. The traffic flowing through this interface13.2 Basic Topics 177Since the VLAN identifier is set to 0, the frames sent by this controller do not contain 802.lq tags, i.e., the frames are sent untagged for the VLAN. This means that if traffic going to the management interface flows through a trunk port on the switch to which the controller is attached, the traffic will be in the nativeVLAN±0 of that trunk port The AP uses the management interface to discover the controller, and the mobile group uses the management interface to exchange information.The AP manager interface is another static interface. The address assigned to this interface is used as the source address for communication between the wireless controller and the Cisco AP. This means that this address is unique, but this address can be on the same subnet as the management interface.Another type of static interface is called a virtualinterface. The virtual interface controls the communication between Layer 3 Security and Mobility Manager for all physical ports on the controller. The virtual interface also has the DNS gateway hostname used by Layer 3 Security and Mobility Manager, so the origin of the certificate can be verified. When Layer 3 Web Authorization is enabled, the wireless side will use the virtual interface to enforce authorization. For example, a user associates to an AP that is configured for Web Authorization. then the user opens a Web browser which attempts to access the default home page. With Web authorization enabled, the Web browser is redirected to the virtual interface IP address, which is typically set to 1XP1.1.At this point, the user will need to enter credentials for Web authorization. After authorization, the user is redirected to his home page. Or, he may be redirected to the terms of use page instead of his home page.One more static interface is the service port. The service port on the 4400 Series controller is a 10/100 copper Ethernet interface. This service port is designed for out-of-band management and can also be used for system recovery and maintenance. This is the only port that is active when the controller is in boot mode. Note that the service port is not autodetected (autosense)-you must use the correct cable type for it. Therefore, if you intend to plug a switch into a service port, you must use the correct cable, because this port is not autosense. Also, since there is no VLAN tag assigned to this port, it should not be configured as a trunk port on the switch.Another service port feature of interest is that you cannot configure a default gateway for this port through the web interface, but you can go into theCLI and define a static route. Static routes are defined using the configroute command. It may feel a little difficult to understand these new terms at first, but once you get interested in the controller interface and start creating a wirelessLAN, you will be able to understand these terms properly.