Cisco IP Communicator V.8.6.rar.rar

To create and configure a vFCoE gateway, you must first perform a kitting for Cisco IP Communicator design. To perform a kitting, see How to Design for Cisco IP Communicator . In the kitting scenario, there cannot be a FCoE service. You must create the FCoE use case on the design server only. To create a FCoE use case, see

To be configured successfully, a server must add certain IP addresses (not all servers are checked for this requirement) to the defined IP address pools. These IP addresses belong to the cluster of servers forming a virtual FCoE gateway (vFCoE Gateway). Note that the FCoE service can be running on these servers, but it does not have to be running to create a vFCoE gateway. This vFCoE gateway must have a physical path to the FCoE forwarding engines array (FEEA). The FCoE service starts as soon as a vFCoE gateway is defined and has successfully completed the physical path verify phase.

Use the Activate or Deactivate button, or the related commands, to control the services of the server. These services are restarted automatically after an inactivity timeout interval (active hours) of up to 24 hours. However, you cannot manage restart options for the Cisco TFTP service.

Collect: This check box is checked by default. Before you use this check box, you must run the Troubleshoot Unified Communications connection feature. For more information, see Collect logs in the Troubleshoot Unified Communications feature. 7211a4ac4a