Download CCIE Collaboration Written Exam v1-1.pass4sure.400-051.2019-12-04.1e.351q.vcex

Using the AFG will allow you to get this license mac before even touching the server. It is provided after filling in the main form of the AFG but it can also be found by looking at the last few lines of your platformconfig.xml file. 
Once you have the xml files, you will need to map those to the floppy drive of the VM (no usb support on the VM OVA). There are many ways to do this. I simply use a freeware virtual floppy app that I drop the platformconfig.xml file on and then copy the*.flp image out to the datastore. I’ll end up with a directory on my datastore called AFG that has the host named *.flp images that I will use during install. It also serves as archival of these files in the event the server needs to be re-imaged. This is important because the license mac will change if every parameter is not entered exactly as it was prior. If the license mac changes, you will have to go through the process of requesting new license files to be generated. 
References: http://angryciscoguy.com/jello/cisco-answer-file-generator-to-the-rescue/

VMware vCenter is 
optional when deploying on UC on UCS Tested Reference Configuration hardware 
mandatory when deploying on UC on UCS Specs-based and Third-party Server Specs-based hardware. 
vCenter Statistics Level 4 logging is mandatory so that Cisco TAC is able to provide effective support. 
Click here for how to configure VMware vCenter to capture these logs. If not configured by default, Cisco TAC may request enabling these settings in order to provide effective support. 
Also note that enablement of specific VMware vSphere management features may require vCenter and/or a higher feature Edition of vSphere ESXi. 
Cisco Collaboration does not require its own dedicated vCenter. 
Note that when VMware vCenter is not required and is not used, then VMware vSphere ESXi's default management interface is its free/included VMware vSphere Client (formerly branded VI Client). 
Reference: http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements

What does a TRC definition include? 
Definition of server model and local components (CPU, RAM, adapters, local storage) at the orderable part number level. 
Required RAID configuration (e.g. RAID5, RAID10, etc.) - including battery backup cache or SuperCap - when the TRC uses DAS storage 
Guidance on hardware installation and basic setup (e.g. click here). 
Click here for detailed Cisco UCS server documentation regarding hardware configuration procedures. 
Configuration of Virtual-to-physical network interface mapping is design-dependent and not included in TRC definition. 
Configuration of adapters (such as Cisco VIC, 3rd-party CNA / NIC / HBA) is design-dependent and not included in TRC definition. 
Configuration settings or step by step procedures for hardware BIOS, firmware, drivers, RAID setup are not included. Click here for detailed Cisco UCS server documentation. 
Design, installation and configuration of external hardware is not included in TRC definition, such as:
Network routing and switching (e.g. routers, gateways, MCUs, ethernet/FC/FCoE switches, Cisco Catalyst/Nexus/MDS, etc.) 
QoS configuration of route/switch network devices 
Cisco UCS B-Series chassis and switching components (e.g. Cisco UCS 6100/6200, Cisco UCS 2100/2200, Cisco UCS 5100) 
Storage arrays (such as those from EMC, NetApp or other vendors) 
Configuration settings, patch recommendations or step by step procedures for VMware software are not included in TRC definition. 
Infrastructure solutions such as Vblock from Virtual Computing Environment may also be leveraged for configuration details not included in the TRC definition. 
Reference: http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware#UC_on_UCS_Tested_Reference_Configurations

Definition of server model and local components (CPU, RAM, adapters, local storage) at the orderable part number level. 
Required RAID configuration (e.g. RAID5, RAID10, etc.) - including battery backup cache or SuperCap - when the TRC uses DAS storage 
Guidance on hardware installation and basic setup. 
Configuration of Virtual-to-physical network interface mapping is design-dependent and not included in TRC definition. 
Configuration of adapters (such as Cisco VIC, 3rd-party CNA / NIC / HBA) is design-dependent and not included in TRC definition. 
Design, installation and configuration of external hardware is not included in TRC definition, such as:
Network routing and switching (e.g. routers, gateways, MCUs, ethernet/FC/FCoE switches, Cisco Catalyst/Nexus/MDS, etc.) 
QoS configuration of route/switch network devices 
Cisco UCS B-Series chassis and switching components (e.g. Cisco UCS 6100/6200, Cisco UCS 2100/2200, Cisco UCS 5100) 
Storage arrays (such as those from EMC, NetApp or other vendors) 
Configuration settings, patch recommendations or step by step procedures for VMware software are not included in TRC definition. 
Infrastructure solutions such as Vblock from Virtual Computing Environment may also be leveraged for configuration details not included in the TRC definition. 

Cisco Discovery Protocol provides an additional capability not found in LLDP-MED that allows the switch to extend trust to the phone. In this case, the phone is now trusted to mark the packets received on the PC port accordingly. This feature can be used to off-load the switch because now it does not need to police the information being received from the phone.

Cisco EnergyWise Neighbor Discovery Process 
The Cisco EnergyWise neighbor discovery process is the mechanism by which domain members discover each other and populate their Cisco EnergyWise neighbor tables. Cisco EnergyWise queries can subsequently be distributed to all domain members using the neighbor relationships to monitor and control the power usage of devices within a domain. Cisco EnergyWise domain members automatically discover their neighbors through one of two mechanisms:
UDP broadcast packets are automatically sent out switch ports which support Cisco EnergyWise, regardless of whether the interfaces are configured with the no energywise interface-level command. CDP packets are sent when CDP is configured for the switch ports. 
References: http://www.cisco.com/en/US/docs/solutions/Enterprise/Borderless_Networks/Energy_Management/energywisedg.html?referring_site=smartnavRD#wp555927

We get option for Identity Trust list Files and Mobile Voice Access audio files.

Voice traffic cannot recapture lost packets. Rather than retransmitting a lost network connection, the phone resets and attempts to reconnect its network connection. 
References: http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/6921_6941_6961/7_1_2/english/admin/guide/6921trb.html#wp1031181

Choosing the Right Distribution Method 
Which of the three different image-distribution methods discussed so far is the best for a customer deployment? Each method has advantages and disadvantages, and they are summarized in Table 1. 
Table 1. Summary of Distribution Models 

  

References: http://www.cisco.com/en/US/prod/collateral/voicesw/ps6882/ps6884/white_paper_c11-583891.pdf

LLDP-MED supports both LAN speed and duplex discovery. Cisco Discovery Protocol supports duplex discovery only, but this limited support is not seen as a problem because if there is a speed mismatch, LLDP-MED and Cisco Discovery Protocol cannot be exchanged and thus cannot be used to detect the mismatch.