Up-to-Date 350-080 Exam BrainDumps

More documents

Recommendations

Info

The port channel protocol expands the port channel functional model in Cisco SAN switches. It uses the exchange peer parameters (EPP) services to communicate across peer ports in an ISL. Each switch uses the information received from the peer ports along with its local configuration and operational values to decide if it should be part of a SAN port channel. The protocol ensures that a set of ports are eligible to be part of the same SAN port channel. They are only eligible to be part of the same port channel if all the ports have a compatible partner. Explanation: Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/san_switching/b_Cisco _Nexus_5000_Series_NX-OS_SAN_Switching_Configuration_Guide/Cisco_Nexus_5000_Series_NX - OS_SAN_Switching_Configuration_Guide_chapter7.html (san port channel protocol) Question: 7 Which statement about SAN port channels configured on Cisco Nexus 5000 Series Switches is true? A. A single SAN port channel can have both Fibre Channel and virtual Fibre Channel interfaces. B. SAN port channels can include up to 16 interfaces. C. SAN port channels distribute traffic across all links in the port channel when source ID and destination ID load balancing are used. D. The links in SAN port channels can be connected to different sets of switches. E. The On mode of operation means ports only operate as part of a SAN port channel or remain inactive. Question: 8 Answer: E Explanation: You can configure each SAN port channel with a channel group mode parameter to determine the port channel protocol behavior for all member ports in this channel group. The possible values for a channel group mode are as follows: On (default)—The member ports only operate as part of a SAN port channel or remain inactive. In this mode, the port channel protocol is not initiated. However, if a port channel protocol frame is received from a peer port, the software indicates its nonnegotiable status. Port channels configured in the On mode require you to explicitly enable and disable the port channel member ports at either end if you add or remove ports from the port channel configuration. You must physically verify that the local and remote ports are connected to each other. Active—The member ports initiate port channel protocol negotiation with the peer port(s) regardless of the channel group mode of the peer port. If the peer port, while configured in a channel group, does not support the port channel protocol, or responds with a nonnegotiable status, it will default to the On mode behavior. The Active port channel mode allows automatic recovery without explicitly enabling and disabling the port channel member ports at either end. Explanation: Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/san_switching/b_Cisco _Nexus_5000_Series_NX-OS_SAN_Switching_Configuration_Guide/Cisco_Nexus_5000_Series_NX - OS_SAN_Switching_Configuration_Guide_chapter7.html Which capabilities are not supported in DCNM device manager?
A. manage SNMPv3 security access to switches B. save and copy configuration files and software images C. configure VLANs and Ethernet port channels D. manage 2148T FEX, 2232PP FEX, and 2248TP FEX E. configure FCoE Question: 9 Answer: C Explanation: Device Manager provides two views: Device View and Summary View. Use Summary View to monitor interfaces on the switch. Use Device View to perform switch-level configurations including the following: Configure virtual Fibre Channel interfaces. Configure Fibre Channel over Ethernet (FCoE). Configure zones for multiple VSANs. Manage ports, PortChannels, and trunking. Manage SNMPv3 security access to switches. Manage CLI security access to the switch. Manage alarms, events, and notifications. Save and copy configuration files and software image. View hardware configuration. View chassis, module, port status, and statistics. Explanation: Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/5_2/configuration/guides /fund/DCNM-SAN-LAN_5_2/DCNM_Fundamentals/dm.html If the default VDC is configured to limit resources to a specific module type, what happens when a module that does not match the resource type is installed? A. The module is powered up, and interfaces are in an “admin down” state. B. The module is denied power, and a syslog message is generated. C. The module is powered up, and interfaces are allocated to VDC0. D. The module is powered up, and interfaces are allocated to VDC100. Answer: C Explanation: Starting with Cisco NX-OS Release 6.2(2), there is no need to support the interoperability of F1 and F2 Series modules in any VDC, either in a dedicated mode or in a shared mode. If you have configured F1 and F2 Series modules as supported line cards in a storage VDC during an In-Service Software Upgrade (ISSU) to Cisco NX-OS Release 6.2(2) or later releases, before ISSU, reconfigure your storage VDC by using the limit-resource module-type command to avoid any unnecessary disruption to the system. Explanation: Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/nx-
Page 1 and 2: Cisco 350-080 CCIE Data Center Writ
Page 3 and 4: A. A, B, C, and D are valid. B. A a
Page 5: physical security, network security
Page 9 and 10: they each have a CMP. Although only
Page 11 and 12: local user accounts should be ident

Up-to-Date 350-080 Exam BrainDumps

Create successful ePaper yourself

Delete template?

Save as template?