READ Free Dumps For Cisco- 400-101
| Question ID 18507 | Which two Cisco IOS XE commands can install a subpackage onto a router? (Choose two.)
|
| Option A | request platform software package install rp rpSlotNumber file fileURL
|
| Option B | boot system flash bootflash:filename
|
| Option C | copy sourceUrl destinationUrl
|
| Option D | license install file storedLocationUrl
|
| Option E | issu loadversion rp identifier file diskType imageFilename
|
| Option F | config-register value
|
| Correct Answer | A ,C |
Explanation Explanation: ✑ Managing and Configuring a Consolidated Package Using the request platform software package install Command In the following example, the request platform software package install command is used to upgrade a consolidated package running on RP 0. The force option, which forces the upgrade past any prompt (such as already having the same consolidated package installed), is used in this example. Router# request platform software package install rp 0 file bootflash:asr1000rp1- adventerprisek9.02.01.00.122-33.XNA.bin force To upgrade a consolidated package on the Cisco ASR 1000 Series Routers using the copy command, copy the consolidated package into the bootflash: directory on the router using the copy command as you would on most other Cisco routers. After making this copy, configure the router to boot using the consolidated package file. In the following example, the consolidated package file is copied onto the bootflash: file system from TFTP. The config-register is then set to boot using boot system commands, and the boot system commands instruct the router to boot using the consolidated package stored in the bootflash: file system. The new configuration is then saved using the copy running-config startup-config command, and the system is then reloaded to complete the process. Router# dir bootflash: Directory of bootflash:/ 11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found 86401 drwx 4096 Dec 4 2007 06:06:24 -08:00.ssh 14401 drwx 4096 Dec 4 2007 06:06:36 -08:00.rollback_timer 28801 drwx 4096 Mar 18 2008 17:31:17 -07:00.prst_sync 43201 drwx 4096 Dec 4 2007 04:34:45 -08:00.installer 13 -rw- 45977 Apr 9 2008 16:48:46 -07:00 target_support_output.tgz.tgz 928862208 bytes total (712273920 bytes free) Router# copy tftp bootflash: Address or name of remote host []? 172.17.16.81 Source filename []? /auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.00.122- 33.XNA.bin Destination filename [asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin]?
| Question ID 18508 | Which two statements about Cisco Express Forwarding are true? (Choose two.)
|
| Option A | Cisco Express Forwarding tables contain reachability information and adjacency tables contain forwarding information.
|
| Option B | Cisco Express Forwarding tables contain forwarding information and adjacency tables contain reachability information.
|
| Option C | Changing MAC header rewrite strings requires cache validation.
|
| Option D | Adjacency tables and Cisco Express Forwarding tables can be built separately.
|
| Option E | Adjacency tables and Cisco Express Forwarding tables require packet process- switching.
|
| Correct Answer | A,D |
Explanation Explanation: Main Components of CEF Information conventionally stored in a route cache is stored in several data structures for Cisco Express Forwarding switching. The data structures provide optimized lookup for efficient packet forwarding. The two main components of Cisco Express Forwarding operation are the forwarding information base (FIB) and the adjacency tables. The FIB is conceptually similar to a routing table or information base. A router uses this lookup table to make destination-based switching decisions during Cisco Express Forwarding operation. The FIB is updated when changes occur in the network and contains all routes known at the time. Adjacency tables maintain Layer 2 next-hop addresses for all FIB entries. This separation of the reachability information (in the Cisco Express Forwarding table) and the forwarding information (in the adjacency table), provides a number of benefits: ✑ The adjacency table can be built separately from the Cisco Express Forwarding table, allowing both to be built without any packets being process-switched. ✑ The MAC header rewrite used to forward a packet is not stored in cache entries, so changes in a MAC header rewrite string do not require validation of cache entries. Reference: http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipswitch_cef/configuration/15- mt/isw-cef-15-mt-book/isw-cef-overview.html