Cisco Systems LAIRCTVM5K9 manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

Ir a la página of

Buen manual de instrucciones

Las leyes obligan al vendedor a entregarle al comprador, junto con el producto, el manual de instrucciones Cisco Systems LAIRCTVM5K9. La falta del manual o facilitar información incorrecta al consumidor constituyen una base de reclamación por no estar de acuerdo el producto con el contrato. Según la ley, está permitido adjuntar un manual de otra forma que no sea en papel, lo cual últimamente es bastante común y los fabricantes nos facilitan un manual gráfico, su versión electrónica Cisco Systems LAIRCTVM5K9 o vídeos de instrucciones para usuarios. La condición es que tenga una forma legible y entendible.

¿Qué es un manual de instrucciones?

El nombre proviene de la palabra latina “instructio”, es decir, ordenar. Por lo tanto, en un manual Cisco Systems LAIRCTVM5K9 se puede encontrar la descripción de las etapas de actuación. El propósito de un manual es enseñar, facilitar el encendido o el uso de un dispositivo o la realización de acciones concretas. Un manual de instrucciones también es una fuente de información acerca de un objeto o un servicio, es una pista.

Desafortunadamente pocos usuarios destinan su tiempo a leer manuales Cisco Systems LAIRCTVM5K9, sin embargo, un buen manual nos permite, no solo conocer una cantidad de funcionalidades adicionales del dispositivo comprado, sino también evitar la mayoría de fallos.

Entonces, ¿qué debe contener el manual de instrucciones perfecto?

Sobre todo, un manual de instrucciones Cisco Systems LAIRCTVM5K9 debe contener:
- información acerca de las especificaciones técnicas del dispositivo Cisco Systems LAIRCTVM5K9
- nombre de fabricante y año de fabricación del dispositivo Cisco Systems LAIRCTVM5K9
- condiciones de uso, configuración y mantenimiento del dispositivo Cisco Systems LAIRCTVM5K9
- marcas de seguridad y certificados que confirmen su concordancia con determinadas normativas

¿Por qué no leemos los manuales de instrucciones?

Normalmente es por la falta de tiempo y seguridad acerca de las funcionalidades determinadas de los dispositivos comprados. Desafortunadamente la conexión y el encendido de Cisco Systems LAIRCTVM5K9 no es suficiente. El manual de instrucciones siempre contiene una serie de indicaciones acerca de determinadas funcionalidades, normas de seguridad, consejos de mantenimiento (incluso qué productos usar), fallos eventuales de Cisco Systems LAIRCTVM5K9 y maneras de solucionar los problemas que puedan ocurrir durante su uso. Al final, en un manual se pueden encontrar los detalles de servicio técnico Cisco Systems en caso de que las soluciones propuestas no hayan funcionado. Actualmente gozan de éxito manuales de instrucciones en forma de animaciones interesantes o vídeo manuales que llegan al usuario mucho mejor que en forma de un folleto. Este tipo de manual ayuda a que el usuario vea el vídeo entero sin saltarse las especificaciones y las descripciones técnicas complicadas de Cisco Systems LAIRCTVM5K9, como se suele hacer teniendo una versión en papel.

¿Por qué vale la pena leer los manuales de instrucciones?

Sobre todo es en ellos donde encontraremos las respuestas acerca de la construcción, las posibilidades del dispositivo Cisco Systems LAIRCTVM5K9, el uso de determinados accesorios y una serie de informaciones que permiten aprovechar completamente sus funciones y comodidades.

Tras una compra exitosa de un equipo o un dispositivo, vale la pena dedicar un momento para familiarizarse con cada parte del manual Cisco Systems LAIRCTVM5K9. Actualmente se preparan y traducen con dedicación, para que no solo sean comprensibles para los usuarios, sino que también cumplan su función básica de información y ayuda.

Índice de manuales de instrucciones

  • Página 1

    Cisco Virtual Wireless Controller Deployment Guide Document ID: 113677 Introduction Prerequisites Virtual Controller Support Virtual WLAN Controller Unsupported Features Single Virtual Controller Resource Requirement Suggested Hardware Recommendations for Hosting Cisco Virtual Controllers AP Requirement Components Used Topology Conventions Release [...]

  • Página 2

    VMware benefits with the vWLC: vSphere : A virtualization infrastructure package from VMware, which includes ESX/ESXi hypervisor, vMotion, DRS, HA, Fault Tolerance, vSphere Distributed Switch, and more. • vCenter Server : The VMware vCenter Server (formerly VMware VirtualCenter) provides a scalable and extensible platform that forms the foundatio[...]

  • Página 3

    Suggested Hardware Recommendations for Hosting Cisco Virtual Controllers UCS R210−2121605W Rack Mount Server (2 RU): 2 * Intel Xeon CPU X5670 @ 2.93 GHz ♦ 16 G memory ♦ • IBM x3550 M3 Server: 2 * Intel Xeon 5600 series processors with 4 cores each and each core capable of doing hyper threading which gives you 16 CPUs in total @3.6 GHz ♦ 1[...]

  • Página 4

    and local access to Internet). Conventions Refer to Cisco Technical Tips Conventions for more information on document conventions. Release Notes Cisco Unified Wireless Network (CUWN) 7.3 Release Notes contain important information about this release. Log in to Cisco.com for the latest release notes before loading and testing software. Virtual Contr[...]

  • Página 5

    Virtual Controller Virtual Interfaces Management Interface • Virtual Interface • Dynamic Interface • AP Manager Interface • Switch Interface Configuration Connected to UCS Server This section provides a sample configuration of the Cisco Catalyst interface connection to the ESXi server for the virtual switch as trunk interface. The managemen[...]

  • Página 6

    interface GigabitEthernet1/1/3 description ESXi Trunk switchport trunk encapsulation dot1q switchport mode trunk end Complete these steps: Create two separate virtual switches in order to map to the virtual controller Service and Data Port. Go to ESX > Configuration > Networking , and click Add Networking . 1. Select Virtual Machine , and cli[...]

  • Página 7

    Click Next . 7. Here, you see vSwitch1 is created for vWLC Service Port. Click Add Networking in order to repeat for the Data Port. 8. For the new vSwitch, select the physical NIC(s) connected on a trunk port if there are multiple NICs / portgroup assigned to an etherchannel on the switch. 9. Add the NIC. 10. Click Next . 11. Provide a label (in th[...]

  • Página 8

    Click Next until you complete the steps to add the vSwitch. 14. VMware Promiscuous Mode Definition Promiscuous mode is a security policy which can be defined at the virtual switch or portgroup level in vSphere ESX/ESXi. A virtual machine, Service Console, or VMkernel network interface in a portgroup which allows the use of promiscuous mode can see [...]

  • Página 9

    In the Properties window, select the Security tab. 3. Check the box for Promiscuous Mode , choose Accept from the drop−down list, and click OK . 4. Confirm the change, and click Close . 5.[...]

  • Página 10

    The virtual controller software is posted as an .ovf package in the Cisco software center. You can download the .ova/.ovf package and install to any other virtual application. The software comes with a free 60−day evaluation license. After the VM is started, the evaluation license can be activated and a purchased license can be automatically inst[...]

  • Página 11

    Provide a name for the vWLC or accept the default, and click Next . 10. Accept the default Thick Provision Lazy Zeroed setting, and click Next . 11. Accept the Network Mapping default, and click Next . 12.[...]

  • Página 12

    Confirm the Deployment settings, and click Finish in order to begin installation. 13. Click Close when Deployment is complete. 14. Two important things to note regarding upgrading virtual controllers: The OVA image is needed only for first time installation. • The .AES image can be subsequently used for upgrading/downgrading. • Virtual Controll[...]

  • Página 13

    Select Network adapter 1 to vWLC Service Port (vSwitch created in ESX networking). 2. Map Network adapter 2 to vWLC Data Port . 3. Confirm the correct mapping. 4. Virtual Controller Console Port The console port gives access to the console prompt of the WLC. As a result, the VM can be provisioned with serial ports in order to connect to these. In t[...]

  • Página 14

    Physical Serial Port on the Host : The vWLCs virtual serial port is mapped to the hardware serial port on the server. This option is limited to the number of physical serial port(s) on the host. If in a multi−tenant vWLC scenario, this may not be ideal. • Connect via Network : The vWLCs virtual serial port can be accessed using Telnet ses[...]

  • Página 15

    Click Next in order to review the Options, and click Finish . 5. Click OK in order to complete the configured settings. In order to enable for the serial via network, ESX must be configured to allow for such requests. 6. Navigate to the ESX, click the Configuration tab, go to Software > Security Profile , and click on Properties . 7.[...]

  • Página 16

    In the Firewall Properties window, select VM serial port connected to vSPC , and click OK . 8. Start up the vWLC Complete these steps: Start the vWLC, and select the console in order to observe the first−time installation process. 1.[...]

  • Página 17

    Monitor the progress until the VM console shows that the vWLC has restarted (this is automatic). 2. Open a Telnet session to the vWLC as shown here: 3. The Telnet session will now manage the console to the vWLC. 4.[...]

  • Página 18

    Note: Only one mode of console can be operational at any time, such as a VM console (by key−interrupt at startup) or serial console (physical/network). It is not possible to maintain both at the same time. Continue to wait until the vWLC has come online fully and prompts you to start the configuration tool wizard. 5. Configure the management inte[...]

  • Página 19

    configuration, which may result in APs not joining in the process. Complete the configuration and allow the vWLC to reset. 8. It is suggested that you ping the vWLC management interface in order to ensure that it has come online. Log in to the vWLC. 9. You can issue the show interface summary command and ping the gateway from the vWLC. 10. Connect [...]

  • Página 20

    Initially, there are 0 (zero) Access Points Supported. Enable the evaluation license in order to allow the AP to join. 12. Go to Management > Software Activation > Licenses . Select base−ap−count , and set the Priority to High . 13.[...]

  • Página 21

    Click OK , and Accept the EULA in order to continue. 14. Click OK , and reset the vWLC in order for the evaluation license to take effect. 15. Reboot the vWLC. 16.[...]

  • Página 22

    Log back in to the vWLC, and note that the 200 APs are now supported with the evaluation license enabled. 17. Connect an AP, and monitor for the join message to occur. 18. From the browser, go to WIRELESS and confirm that the AP has joined. 19. Click the AP, and change the AP Mode to FlexConnect . Only FlexConnect is supported (central and local sw[...]

  • Página 23

    It may be useful to consider using the autoconvert function of the controller (for example, any mode AP joining the vWLC will be converted automatically to FlexConnect). Issue this command in order to implement: (Cisco Controller) > config ap autoconvert flexconnect enable 21. Virtual Controller Management with Cisco Prime 1.2 Cisco Prime Infras[...]

  • Página 24

    In Device Work Center, click Add Device . 3. Enter the IP Address and SNMP Community string (Read/Write). By default, the SNMP RW for the controller is Private. Click Add . 4.[...]

  • Página 25

    Cisco Prime Infrastructure will discover and synchronize with the virtual controller. Click refresh in order to update the screen. 5. When the virtual controller is discovered, it is listed as Managed and Reachable (shown in green). Add any other virtual controller(s) at this point, if available. 6. The new controller will be listed in Device Type [...]

  • Página 26

    Navigate to Home for a Summary view (in Lifecycle Theme) of the devices being managed. 8. For the remainder of this guide, the Classic Theme is used to perform similar task of adding the virtual controller, as well as updating the system image. Go to and select Switch to Classic Theme . 9. Go to Configure > Controllers . 10. In order to add a ne[...]

  • Página 27

    Enter the IP Address, Read/Write SNMP Community string, and click Add . 12. Cisco Prime Infrastructure will display this notification: 13. Go to Configure > Controllers . The virtual controller will be listed as Reachable once it has been successfully discovered and added. Otherwise, and as shown above, the device will appear in the Unknown Devi[...]

  • Página 28

    Upgrade the Virtual Controller In the early steps of installation, the Cisco Virtual Controller initially required an OVA file for new virtual appliance creation. However, maintaining virtual controller features and software upgrades require a common AES file downloadable from the Cisco website. Complete these steps: Download the AS*7_3*aes file to[...]

  • Página 29

    Click Save and Reboot . 4. Cisco Prime Infrastructure can also be useful for upgrading one virtual controller or many virtual controllers at the same time. Go to Configure > Controllers . Select (check box) one or more virtual controllers. Select Download Software (TFTP) from the command drop−down list. This example uses TFTP mode for image up[...]

  • Página 30

    This screen is an example of the AES image being transferred to the virtual controllers: 7. Cisco Prime Infrastructure will update the status until the software has transferred successfully. 8. Similar to the experience directly from the controller, a reboot is required when the transfer is complete. In Cisco Prime Infrastructure, go to Configure &[...]

  • Página 31

    Cisco Prime Infrastructure will prompt for reboot parameters such as save configuration, and so forth. Click OK . 10. Cisco Prime Infrastructure will notify the administrator that the virtual controllers are being rebooted. 11. When complete, Cisco Prime Infrastructure will provide the results of the process. 12. Troubleshooting AP Considerations K[...]

  • Página 32

    The hash validation, which is an extra authorization step, will be performed only if the AP is joining a virtual controller. There will be a knob to turn on/off hash key validation. • By default, hash validation is enabled, which means that the AP needs to have the virtual controller hash key in its flash before it can successfully complete assoc[...]

  • Página 33

    The AP may have an older SSC hash, either from an old installation or joining other controllers. It is possible to configure the WLC to not validate SSC, allow APs to join the vWLC, then re−enabling the validation again. (Cisco Controller) > configure certificate ssc hash validation disable • Perform the test capwap <erase/restart> com[...]