Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
Scrum
All Vendors
  2. Home
  3. Exams
  4. Cisco®
  5. 350-601

Free 350-601 Exam Braindumps (page: 55)

Page 54 of 132
PDF with 521 Questions

Which two components should be checked when a Cisco Nexus 9000 Series Switch fails to boot using POAP? (Choose two.)

  1. POAP feature license
  2. DHCP server to bootstrap IP information
  3. image noted in the script file against switch bootflash
  4. script signed with security key
  5. TFTP server that contains the configuration script

Answer(s): B,E

Explanation:

PowerOn Auto Provisioning (POAP) automates the process of upgrading software images and installing configuration files on devices that are being deployed in the network for the first time.
When a device with the POAP feature boots and does not find the startup configuration, the device enters POAP mode, locates a DHCP server, and bootstraps itself with its interface IP address, gateway, and DNS server IP addresses. The device also obtains the IP address of a TFTP server and downloads a configuration script that enables the switch to download and install the appropriate software image and configuration file.


Reference:

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/fundamentals/configuration/guide/b_Cisco_Nexus_9000_Series_NX-
OS_Fundamentals_Configuration_Guide_7x/b_Cisco_Nexus_9000_Series_NX-OS_Fundamentals_Configuration_Guide_7x_chapter_0100.html



A POAP-enabled Cisco Nexus switch will not enter POAP mode.
Which two conditions should be verified? (Choose two.)

  1. No startup configuration is available.
  2. The switch is in bootup process.
  3. The license file is missing on the switch.
  4. Bootflash must contain a special directory named POAP with poap.py file.
  5. No Cisco NX-OS image is present on the bootflash.

Answer(s): A,B

Explanation:

POAP configuration guidelines and limitations are as follows:
* The Cisco Nexus switch software image must support POAP for this feature to function.
* POAP does not support provisioning of the switch after it has been configured and is operational. Only auto-provisioning of a switch with no startup configuration is supported.


Reference:

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus7000/sw/fundamentals/config/cisco_nexus7000_fundamentals_config_guide_8x/
Using_PowerOn_Auto_Provisioning.html



An engineer enters these commands while in EEM on a Cisco Nexus 9000 Series Switch event manager applet Backup-config event timer watchdog time 1800 name timer event cli match "copy running-config startup-config"
What is the result of applying this configuration?

  1. It generates an error because no action is mentioned.
  2. It executes the copy running-config startup-confing command.
  3. It saves the running configuration every 1800 seconds.
  4. It blocks the copy running-config startup-config command.

Answer(s): D

Explanation:

See below for an example of the outcome:
SwitchA# sh ver | inc image -
NXOS image file is: bootflash:///nxos.7.0.3.I7.10.bin
SwitchA# conf t -
Enter configuration commands, one per line. End with CNTL/Z.
SwitchA(config)# event manager applet Backup-config
SwitchA(config-applet)# event timer watchdog time 1800 name timer
Configuration accepted successfully
SwitchA(config-applet)# event cli match "copy running-config startup-config"
SwitchA(config-applet)# end -
SwitchA# copy running-config startup-config
% Command blocked by event manager policy



An engineer must modify an overridden policy by changing the number of FCNS database entries to 1500 and then generate a message.
What configuration will accomplish this task?

  1. event manager applet fcns_policy event fcns entries max-per-switch 1500 action 1.0 syslog priority warnings msg FCNS DB entries have reached the EEM limit action 2.0 policy-default
  2. event manager applet fcns_policy override __fcns_entries_max_per_switch action 1.0 syslog priority errors "CNS DB entries have reached the EEM limit" action 2.0 policy-default
  3. event manager applet fcns_policy override __fcns_entries_max_per_switch event fcns entries max-per-switch 1500 action 1.0 syslog priority warnings msg FCNS DB entries have reached the EEM limit
  4. event manager applet fcns_policy action 1.0 syslog priority warnings msg FCNS DB entries have reached the EEM limit action 2.0 event-default

Answer(s): C

Explanation:

The following example modifies an overridden policy by changing the number of FCNS database entries to 1500. It also generates both the configured and the default syslog messages of the default system policy event manager applet fcns_policy override __fcns_entries_max_per_switch event fcns entries max-per-switch 1500 action 1.0 syslog priority warnings msg FCNS DB entries have reached the EEM limit


Reference:

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/8_x/config/system-management/cisco_mds9000_system_management_config_guide_8x/ configuring_the_embedded_event_manager.html






Post your Comments and Discuss Cisco® 350-601 exam with other Community members:

Exam Discussions & Posts