Implementing Cisco Data Center Unified Fabric
Question No: 1 – (Topic 1)
Which two statements about Cisco Nexus 7000 line cards are true? (Choose two.)
M1, M2, and F1 cards are allowed in the same VDC.
M line cards are service-oriented and likely face the access layer and provide Layer 2 connectivity.
F line cards are performance-oriented and likely connect northbound to the core layer for Layer 3 connectivity.
M line cards support Layer 2, Layer 3, and Layer 4 with large forwarding tables and a rich feature set.
The F2 line card must reside in the admin VDC.
Answer: A,D Explanation:
Cisco is introducing a new line card called as F3 Module which has rich feature set and offers high performance 40G/100G port density to the Nexus 7000 product family. Cisco also introduced a new feature in NX-OS 6.2(2) where the F2e line card can be in the same VDC as M1 or M2 Line Card. The objective of this session is to cover detailed steps and methodology of migrating Nexus 7000 with VDC types prior to NX-OS 6.2 to the newer F3 or M/F2e VDC types. The session also covers the effect of VDC migration with commonly used Network features, firewall and load balancer services.
M-Series XL modules support larger forwarding tables. M-Series modules are frequently required at network core, peering, and aggregation points. When used with the F1-Series, the M-Series modules provide inter-VLAN services and form a pool of Layer 3 resources for the system.
And http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Data_Center/VMDC/2- 6/vmdctechwp.html
Question No: 2 DRAG DROP – (Topic 1)
Drag the network characteristics on the left to the most appropriate design layer on the
Question No: 3 – (Topic 1)
Which statement about RADIUS configuration distribution using Cisco Fabric Services on a Cisco Nexus 7000 Series Switch is true?
Cisco Fabric Services does not distribute the RADIUS server group configuration or
server and global keys.
Enabling Cisco Fabric Services causes the existing RADIUS configuration on your Cisco NX-OS device to be immediately distributed.
When the RADIUS configuration is being simultaneously changed on more than one device in a Cisco Fabric Services region, the most recent changes will take precedence.
Only the Cisco NX-OS device with the lowest IP address in the Cisco Fabric Services region can lock the RADIUS configuration.
Answer: A Explanation:
CFS does not distribute the RADIUS server group configuration or server and global keys. The keys are unique to the Cisco NX-OS device and are not shared with other Cisco NX- OS devices.
Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/nx- os/security/configuration/guide/b_Cisco_Nexus_7000_NX- OS_Security_Configuration_Guide Release_6-x/b_Cisco_Nexus_7000_NX- OS_Security_Configuration_Guide Release_6-x_chapter_0101.html
Question No: 4 – (Topic 1)
Which statement about SNMP support on Cisco Nexus switches is true?
Cisco NX-OS only supports SNMP over IPv4.
Cisco NX-OS supports one instance of the SNMP per VDC.
SNMP is not VRF-aware.
SNMP requires the LAN_ENTERPRISE_SERVICES_PKG license.
Only users belonging to the network operator RBAC role can assign SNMP groups.
Answer: B Explanation:
Cisco NX-OS supports one instance of the SNMP per virtual device context (VDC). By default, Cisco NX-OS places you in the default VDC. SNMP supports multiple MIB module instances and maps them to logical network entities. SNMP is also VRF aware. You can configure SNMP to use a particular VRF to reach the SNMP notification host receiver. You can also configure SNMP to filter notifications to an SNMP host receiver based on the VRF where the notification occurred.
Question No: 5 – (Topic 1)
By default it will take 10 seconds for authentication to fail due to an unresponsive RADIUS server before a Cisco Nexus series switch reverts to another RADIUS server or local authentication. What is one efficient way to improve the reaction time to a RADIUS server failure?
Decrease the global RADIUS retransmission count to 1.
Decrease the global RADIUS timeout interval to 5 seconds.
Configure the RADIUS retransmission count and timeout interval per server, versus globally.
Configure per server a test idle timer, along with a username and password.
Answer: D Explanation:
You can monitor the availability of RADIUS servers. These parameters include the username and password to use for the server and an idle timer. The idle timer specifies the interval during which a RADIUS server receives no requests before the Nexus 5000 Series switch sends out a test packet. You can configure this option to test servers periodically.
The test idle timer specifies the interval during which a RADIUS server receives no requests before the Nexus 5000 Series switch sends out a test packet. The default idle timer value is 0 minutes. When the idle time interval is 0 minutes, the Nexus 5000 Series switch does not perform periodic RADIUS server monitoring.
Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration/guid e/cli_rel_4_0_1a/CLIConfigurationGuide/sec_radius.html
Question No: 6 – (Topic 1)
Refer to the command below. When configuring an SVS connection on the Cisco Nexus 5000 Series Switch, which device is being referenced as the remote IP address?
nexus5500-2(config-svs-conn)# remote ip address 10.10.1.15 port 80 vrf management
ESX or ESXi host
vPC peer switch
Cisco IMC management
Answer: B Explanation:
This command specifies the hostname or IP address for the vCenter Server. Optionally, specifies the port number and VRF.
Question No: 7 – (Topic 1)
Which three items must be configured in the port profile client in Cisco UCS Manager? (Choose three.)
vCenter IP address
VM port group
Answer: B,C,D Explanation:
After associating an ESX host to a DVS, you can migrate existing VMs from the vSwitch to the DVS, and you can create VMs to use the DVS instead of the vSwitch. With the hardware-based VN-Link implementation, when a VM uses the DVS, all VM traffic passes through the DVS and ASIC-based switching is performed by the fabric interconnect.
In Cisco UCS Manager, DVSes are organized in the following hierarchy: vCenter
Folder (optional) Datacenter
Folder (required) DVS
At the top of the hierarchy is the vCenter, which represents a VMware vCenter instance. Each vCenter contains one or more datacenters, and optionally vCenter folders with which you can organize the datacenters. Each datacenter contains one or more required datacenter folders. Datacenter folders contain the DVSes.
Reference: http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/1-3- 1/b_UCSM_GUI_Configuration_Guide_1_3_1/UCSM_GUI_Configuration_Guide_1_3_1_c hapter28.html
Question No: 8 – (Topic 1)
Which GLBP load-balancing algorithm ensures that a client is always mapped to the same VMAC address?
shortest-path and weighting
Answer: D Explanation:
Host dependent-GLBP uses the MAC address of the host to determine which virtual MAC address to direct the host to use. This algorithm guarantees that a host gets the same virtual MAC address if the number of virtual forwarders does not change.
Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/5_x/nx- os/unicast/configuration/guide/l3_cli_nxos/l3_glbp.html
Question No: 9 – (Topic 1)
Which protocol is the foundation for unified fabric as implemented in Cisco NX-OS?
Data Center Bridging
Fibre Channel over Ethernet
N proxy virtualization
N Port identifier virtualization
Answer: C Explanation:
Fibre Channel over Ethernet (FCoE) is one of the major components of a Unified Fabric. FCoE is a new technology developed by Cisco that is standardized in the Fibre Channel Backbone 5 (FC-BB-5) working group of Technical Committee T11 of the International Committee for Information Technology Standards (INCITS). Most large data centers have huge installed bases of Fibre Channel and want a technology that maintains the Fibre Channel model. FCoE assumes a lossless Ethernet, in which frames are never dropped (as in Fibre Channel) and that therefore does not use IP and TCP.
Reference: http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series- switches/white_paper_c11-495142.html
Question No: 10 – (Topic 1)
Which statement about the Layer 3 card on the Cisco Nexus 5500 Series Switch is true?
BGP support is not provided, but RIP, EIGRP, and OSPF support is provided.
Up to two 4-port cards are supported with up to 160 Gb/s of Layer 3 forwarding capability.
Up to 16 FEX connections are supported.
Port channels cannot be configured as Layer 3 interfaces.
Answer: C Explanation:
From the Cisco NX-OS 5.1(3)N1(1) release and later releases, each Cisco Nexus 5500 Series device can manage and support up to 24 FEXs without Layer 3. With Layer 3, the number of FEXs supported per Cisco Nexus 5500 Series device is 8. With Enhanced vPC and a dual-homed FEX topology each FEX is managed by both Cisco Nexus 5000 Series devices. As a result, one pair of Cisco Nexus 5500 Series devices can support up to 24
FEXs and 16 FEXs for Layer 2 and Layer 3.
|Lowest Price Guarantee||Yes||No||No|
|Free VCE Simulator||Yes||No||No|