All4Certs Cisco Archive,Exam Archive [Latest Version] Free CertBus Cisco 400-101 PDF Download with 100% Pass Guarantee

[Latest Version] Free CertBus Cisco 400-101 PDF Download with 100% Pass Guarantee

CertBus 2018 Valid Cisco 400-101 CCIE Exam VCE and PDF Dumps for Free Download!

400-101 CCIE Exam PDF and VCE Dumps : 1063QAs Instant Download: https://www.certgod.com/400-101.html [100% 400-101 Exam Pass Guaranteed or Money Refund!!]
☆ Free view online pdf on CertBus free test 400-101 PDF: https://www.certgod.com/online-pdf/400-101.pdf
☆ CertBus 2018 Valid 400-101 CCIE exam Question PDF Free Download from Google Drive Share: https://drive.google.com/file/d/0B_3QX8HGRR1mdEpkTFZvSDJDc2c/view?usp=sharing

Following 400-101 1063QAs are all new published by Cisco Official Exam Center

How to pass Latest 400-101 vce dumps exam easily with less time? CertBus provides the most valid Newest 400-101 vce dumps exam preparation material to boost your success rate in Cisco CCIE Newest 400-101 exam questions CCIE Routing and Switching Written v5.0 exam. If you are one of the successful candidates with CertBus May 11,2018 Newest 400-101 free download PDF and VCEs, do not hesitate to share your reviews on our Cisco CCIE materials.

CertBus – help you to pass all 400-101 certification exams! CertBus – leader of it certifications. best practice, certify for sure! CertBus – help all candidates pass the 400-101 certification exams easily. CertBus – the most professional provider of all 400-101 certifications. pass all the 400-101 exam easily.

We CertBus has our own expert team. They selected and published the latest 400-101 preparation materials from Cisco Official Exam-Center: https://www.certgod.com/400-101.html

QUESTION NO:1

Which two commands are required to enable multicast on a router, knowing that the receivers only

support IGMPv2? (Choose two.)

A. ip pim rp-address

B. ip pim ssm

C. ip pim sparse-mode

D. ip pim passive

Answer: A,C

Explanation:

Sparse mode logic (pull mode) is the opposite of Dense mode logic (push mode), in Dense mode

it is supposed that in every network there is someone who is requesting the multicast traffic so

PIM-DM routers begin by flooding the multicast traffic out of all their interfaces except those from

where a prune message is received to eliminate the


QUESTION NO:3

A new backup connection is being deployed on a remote site router. The stability of the connection

has been a concern. In order to provide more information to EIGRP regarding this interface, you

wish to incorporate the “reliability” cost metric in the EIGRP calculation with the command metric

weights 1 0 1 0 1.

What impact will this modification on the remote site router have for other existing EIGRP

neighborships from the same EIGRP domain?

A. Existing neighbors will immediately begin using the new metric.

B. Existing neighbors will use the new metric after clearing the EIGRP neighbors.

C. Existing neighbors will resync, maintaining the neighbor relationship.

D. All existing neighbor relationships will go down.

Answer: D

Explanation:


QUESTION NO:4

Refer to the exhibit.

R1 has an EBGP session to ISP 1 and an EBGP session to ISP 2. R1 receives the same prefixes

through both links.

Which configuration should be applied so that the link between R1 and ISP 2 will be preferred for

outgoing traffic (R1 to ISP 2)?

A. Increase local preference on R1 for received routes

B. Decrease local preference on R1 for received routes

C. Increase MED on ISP 2 for received routes

D. Decrease MED on ISP 2 for received routes

Answer: A

Explanation: Explanation

Local preference is an indication to the AS about which path has preference to exit the AS in order

to reach a certain network. A path with higher local preference is preferred more. The default value

of preference is 100.

Reference

http://www.cisco.com/en/US/tech/tk872/technologies_configuration_example09186a0080b82d1f.s

html?

referring_site=smartnavRD


QUESTION NO:7

Which statement is true about TCN propagation?

A. The originator of the TCN immediately floods this information through the network.

B. The TCN propagation is a two step process.

C. A TCN is generated and sent to the root bridge.

D. The root bridge must flood this information throughout the network.

Answer: C

Explanation:

Explanation

New Topology Change Mechanisms

When an 802.1D bridge detects a topology change, it uses a reliable mechanism to first notify the

root bridge.

This is shown in this diagram:

Once the root bridge is aware of a change in the topology of the network, it sets the TC flag on the

BPDUs it sends out, which are then relayed to all the bridges in the network. When a bridge

receives a BPDU with the TC flag bit set, it reduces its bridging-table aging time to forward delay

seconds. This ensures a relatively quick flush of stale information. Refer to Understanding

Spanning-Tree Protocol Topology Changes for more information on this process. This topology

change mechanism is deeply remodeled in RSTP. Both the detection of a topology change and its

propagation through the network evolve.

Topology Change Detection

In RSTP, only non-edge ports that move to the forwarding state cause a topology change. This

means that a loss of connectivity is not considered as a topology change any more, contrary to

802.1D (that is, a port that moves to blocking no longer generates a TC). When a RSTP bridge

detects a topology change, these occur:

It starts the TC While timer with a value equal to twice the hello-time for all its non-edge

designated ports and its root port, if necessary.

It flushes the MAC addresses associated with all these ports.

Note: As long as the TC While timer runs on a port, the BPDUs sent out of that port have the TC

bit set.

BPDUs are also sent on the root port while the timer is active.

Topology Change Propagation

When a bridge receives a BPDU with the TC bit set from a neighbor, these occur:

It clears the MAC addresses learned on all its ports, except the one that receives the topology

change.

It starts the TC While timer and sends BPDUs with TC set on all its designated ports and root port

(RSTP no longer uses the specific TCN BPDU, unless a legacy bridge needs to be notified).

This way, the TCN floods very quickly across the whole network. The TC propagation is now a one

step process. In fact, the initiator of the topology change floods this information throughout the

network, as opposed to 802.1D where only the root did. This mechanism is much faster than the

802.1D equivalent. There is no need to wait for the root bridge to be notified and then maintain the

topology change state for the whole network for seconds.

In just a few seconds, or a small multiple of hello-times, most of the entries in the CAM tables of

the entire network (VLAN) flush. This approach results in potentially more temporary flooding, but

on the other hand it clears potential stale information that prevents rapid connectivity restitution.

Reference

http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfa.shtml


QUESTION NO:8

Which statement is true about loop guard?

A. Loop guard only operates on interfaces that are considered point-to-point by the spanning tree.

B. Loop guard only operates on root ports.

C. Loop guard only operates on designated ports.

D. Loop guard only operates on edge ports.

Answer: A

Explanation:

Explanation

Understanding How Loop Guard Works

Unidirectional link failures may cause a root port or alternate port to become designated as root if

BPDUs are absent. Some software failures may introduce temporary loops in the network. Loop

guard checks if a root port or an alternate root port receives BPDUs. If the port is receiving

BPDUs, loop guard puts the port into an inconsistent state until it starts receiving BPDUs again.

Loop guard isolates the failure and lets spanning tree converge to a stable topology without the

failed link or bridge.

You can enable loop guard per port with the set spantree guard loop command.

Note When you are in MST mode, you can set all the ports on a switch with the set spantree

global-defaults loop-guard command.

When you enable loop guard, it is automatically applied to all of the active instances or VLANs to

which that port belongs. When you disable loop guard, it is disabled for the specified ports.

Disabling loop guard moves all loop-inconsistent ports to the listening state.

If you enable loop guard on a channel and the first link becomes unidirectional, loop guard blocks

the entire channel until the affected port is removed from the channel. Figure 8-6 shows loop

guard in a triangle switch configuration.

Figure 8-6 Triangle Switch Configuration with Loop Guard

Figure 8-6 illustrates the following configuration:

Switches A and B are distribution switches.

Switch C is an access switch.

Loop guard is enabled on ports 3/1 and 3/2 on Switches A, B, and C.

Use loop guard only in topologies where there are blocked ports. Topologies that have no blocked

ports, which are loop free, do not need to enable this feature. Enabling loop guard on a root switch

has no effect but provides protection when a root switch becomes a nonroot switch.

Follow these guidelines when using loop guard:

Do not enable loop guard on PortFast-enabled or dynamic VLAN ports.

Do not enable PortFast on loop guard-enabled ports.

Do not enable loop guard if root guard is enabled.

Do not enable loop guard on ports that are connected to a shared link.

Note: We recommend that you enable loop guard on root ports and alternate root ports on access

switches.

Loop guard interacts with other features as follows:

Loop guard does not affect the functionality of UplinkFast or BackboneFast.

Root guard forces a port to always be designated as the root port. Loop guard is effective only if

the port is a root port or an alternate port. Do not enable loop guard and root guard on a port at the

same time.

PortFast transitions a port into a forwarding state immediately when a link is established. Because

a PortFast-enabled port will not be a root port or alternate port, loop guard and PortFast cannot be

configured on the same port. Assigning dynamic VLAN membership for the port requires that the

port is PortFast enabled. Do not configure a loop guard-enabled port with dynamic VLAN

membership.

If your network has a type-inconsistent port or a PVID-inconsistent port, all BPDUs are dropped

until the misconfiguration is corrected. The port transitions out of the inconsistent state after the

message age expires. Loop guard ignores the message age expiration on type-inconsistent ports

and PVID-inconsistent ports. If the port is already blocked by loop guard, misconfigured BPDUs

that are received on the port make loop guard recover, but the port is moved into the type-

inconsistent state or PVID-inconsistent state.

In high-availability switch configurations, if a port is put into the blocked state by loop guard, it

remains blocked even after a switchover to the redundant supervisor engine. The newly activated

supervisor engine recovers the port only after receiving a BPDU on that port.

Loop guard uses the ports known to spanning tree. Loop guard can take advantage of logical ports

provided by the Port Aggregation Protocol (PAgP). However, to form a channel, all the physical

ports grouped in the channel must have compatible configurations. PAgP enforces uniform

configurations of root guard or loop guard on all the physical ports to form a channel.

These caveats apply to loop guard:


400-101 PDF Dumps400-101 Study Guide400-101 Exam Questions

QUESTION NO:9

Which two are effects of connecting a network segment that is running 802.1D to a network

segment that is running 802.1w? (Choose two.)

A. The entire network switches to 802.1D and generates BPDUs to determine root bridge status. B.

A migration delay of three seconds occurs when the port that is connected to the 802.1D bridge

comes up.

C. The entire network reconverges and a unique root bridge for the 802.1D segment, and a root

bridge for the 802.1w segment, is chosen.

D. The first hop 802.1w switch that is connected to the 802.1D runs entirely in 802.1D compatibility

mode and converts the BPDUs to either 802.1D or 802.1w BPDUs to the 802.1D or 802.1w

segments of the network.

E. Classic 802.1D timers, such as forward delay and max-age, will only be used as a backup, and

will not be necessary if point-to-point links and edge ports are properly identified and set by the

administrator.

Answer: B,E

Explanation:

Each port maintains a variable that defines the protocol to run on the corresponding segment. A

migration delay timer of three seconds also starts when the port comes up. When this timer runs,

the current STP or RSTP mode associated to the port is locked. As soon as the migration delay

expires, the port adapts to the mode that corresponds to the next BPDU it receives. If the port

changes its mode of operation as a result of a BPDU received, the migration delay restarts.

802.1D works by the concept that the protocol had to wait for the network to converge before it

transitioned a port into the forwarding state. With Rapid Spanning Tree it does not have to rely on

any timers, the only variables that that it relies on is edge ports and link types.

Any uplink port that has an alternate port to the root can be directly placed into the forwarding

state (This is the Rapid convergence that you speak of “restored quickly when RSTP is already in

use?”). This is what happened when you disconnected the primary look; the port that was ALT,

moved to FWD immediately, but the switch also still needs to create a BDU with the TC bit set to

notify the rest of the network that a topology has occurred and all non-edge designated ports will

transition to BLK, LRN, and then FWD to ensure there are no loops in the rest of the network. This

is why if you have a host on a switchport, and you know for a fact that it is only one host, enable

portfast to configure the port as an edgeport so that it does not have to transition to all the STP

states.

Reference

http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfa.shtml


QUESTION NO:10

Which command is used to enable EtherChannel hashing for Layer 3 IP and Layer 4 port-based

CEF?

A. mpls ip cef

B. port-channel ip cef

C. mpls ip port-channel cef

D. port-channel load balance

E. mpls ip load-balance

F. ip cef EtherChannel channel-id XOR L4

G. ip cef connection exchange

Answer: D

Explanation:


QUESTION NO:16

In 802.1s, how is the VLAN to instance mapping represented in the BPDU?

A. The VLAN to instance mapping is a normal 16-byte field in the MST BPDU.

B. The VLAN to instance mapping is a normal 12-byte field in the MST BPDU.

C. The VLAN to instance mapping is a 16-byte MD5 signature field in the MST BPDU.

D. The VLAN to instance mapping is a 12-byte MD5 signature field in the MST BPDU.

Answer: C

Explanation:

MST Configuration and MST Region

Each switch running MST in the network has a single MST configuration that consists of these

three attributes:

1. An alphanumeric configuration name (32 bytes)

2. A configuration revision number (two bytes)

3. A 4096-element table that associates each of the potential 4096 VLANs supported on the

chassis to a given instance.

In order to be part of a common MST region, a group of switches must share the same

configuration attributes.

It is up to the network administrator to properly propagate the configuration throughout the region.

Currently, this step is only possible by the means of the command line interface (CLI) or through

Simple Network

Management Protocol (SNMP). Other methods can be envisioned, as the IEEE specification does

not explicitly mention how to accomplish that step.

Note: If for any reason two switches differ on one or more configuration attribute, the switches are

part of different regions. For more information refer to the Region Boundary section of this

document.

Region Boundary

In order to ensure consistent VLAN-to-instance mapping, it is necessary for the protocol to be able

to exactly identify the boundaries of the regions. For that purpose, the characteristics of the region

are included in the BPDUs. The exact VLANs-to-instance mapping is not propagated in the BPDU,

because the switches only need to know whether they are in the same region as a neighbor.

Therefore, only a digest of the VLANs-toinstance mapping table is sent, along with the revision

number and the name. Once a switch receives a BPDU, the switch extracts the digest (a

numerical value derived from the VLAN-to-instance mapping table through a mathematical

function) and compares this digest with its own computed digest. If the digests differ, the port on

which the BPDU was received is at the boundary of a region.

In generic terms, a port is at the boundary of a region if the designated bridge on its segment is in

a different region or if it receives legacy 802.1d BPDUs. In this diagram, the port on B1 is at the

boundary of region A, whereas the ports on B2 and B3 are internal to region B:

MST Instances

According to the IEEE 802.1s specification, an MST bridge must be able to handle at least these

two instances:

One Internal Spanning Tree (IST)

One or more Multiple Spanning Tree Instance(s) (MSTIs)

The terminology continues to evolve, as 802.1s is actually in a pre-standard phase. It is likely

these names will change in the final release of 802.1s. The Cisco implementation supports 16

instances: one IST (instance 0) and 15 MSTIs.

show vtp status

Cisco switches “show vtp status” Field Descriptions has a MD5 digest field that is a 16-byte

checksum of the

VTP configuration as shown below

Router# show vtp status

VTP Version: 3 (capable)

Configuration Revision: 1

Maximum VLANs supported locally: 1005

Number of existing VLANs: 37

VTP Operating Mode: Server

VTP Domain Name: [smartports]

VTP Pruning Mode: Disabled

VTP V2 Mode: Enabled

VTP Traps Generation: Disabled

MD5 digest : 0x26 0xEE 0x0D 0x84 0x73 0x0E 0x1B 0x69

Configuration last modified by 172.20.52.19 at 7-25-08 14:33:43

Local updater ID is 172.20.52.19 on interface Gi5/2 (first layer3 interface fou)

VTP version running: 2

Reference

http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfc.shtml

http://www.cisco.com/en/US/docs/ios-xml/ios/lanswitch/command/lsw-cr-book.pdf


QUESTION NO:18

Refer to the exhibit.

Which statement is correct about the prefix 160.0.0.0/8?

A. The prefix has encountered a routing loop.

B. The prefix is an aggregate with an as-set.

C. The prefix has been aggregated twice, once in AS 100 and once in AS 200.

D. None of these statements is true.

Answer: B

Explanation:


QUESTION NO:19

Which two options does Cisco PfR use to control the entrance link selection with inbound

optimization? (Choose two.)

A. Prepend extra AS hops to the BGP prefix.

B. Advertise more specific BGP prefixes (longer mask).

C. Add (prepend) one or more communities to the prefix that is advertised by BGP.

D. Have BGP dampen the prefix.

Answer: A,C

Explanation: PfR Entrance Link Selection Control Techniques

The PfR BGP inbound optimization feature introduced the ability to influence inbound traffic. A

network advertises reachability of its inside prefixes to the Internet using eBGP advertisements to

its ISPs. If the same prefix is advertised to more than one ISP, then the network is multihoming.

PfR BGP inbound optimization works best with multihomed networks, but it can also be used with

a network that has multiple connections to the same ISP. To implement BGP inbound

optimization, PfR manipulates eBGP advertisements to influence the best entrance selection for

traffic bound for inside prefixes. The benefit of implementing the best entrance selection is limited

to a network that has more than one ISP connection.

To enforce an entrance link selection, PfR offers the following methods:

BGP Autonomous System Number Prepend When an entrance link goes out-of-policy (OOP) due

to delay, or in images prior to Cisco IOS Releases 15.2(1) T1 and 15.1(2)S, and PfR selects a

best entrance for an inside prefix, extra autonomous system hops are prepended one at a time (up

to a maximum of six) to the inside prefix BGP advertisement over the other entrances. In Cisco

IOS Releases 15.2(1)T1, 15.1(2)S, and later releases, when an entrance link goes out-of policy

(OOP) due to unreachable or loss reasons, and PfR selects a best entrance for an inside prefix,

six extra autonomous system hops are prepended immediately to the inside prefix BGP

advertisement over the other entrances. The extra autonomous system hops on the other

entrances increase the probability that the best entrance will be used for the inside prefix. When

the entrance link is OOP due to unreachable or loss reasons, six extra autonomous system hops

are added immediately to allow the software to quickly move the traffic away from the old entrance

link. This is the default method PfR uses to control an inside prefix, and no user configuration is

required.

BGP Autonomous System Number Community Prepend

When an entrance link goes out-of-policy (OOP) due to delay, or in images prior to Cisco IOS

Releases 15.2

(1)T1 and 15.1(2)S, and PfR selects a best entrance for an inside prefix, a BGP prepend

community is attached one at a time (up to a maximum of six) to the inside prefix BGP

advertisement from the network to another autonomous system such as an ISP. In Cisco IOS

Releases 15.2(1)T1, 15.1(2)S, and later releases, when an entrance link goes out-of-policy (OOP)

due to unreachable or loss reasons, and PfR selects a best entrance for an inside prefix, six BGP

prepend communities are attached to the inside prefix BGP advertisement. The BGP prepend

community will increase the number of autonomous system hops in the advertisement of the

inside prefix from the ISP to its peers. Autonomous system prepend BGP community is the

preferred method to be used for PfR BGP inbound optimization because there is no risk of the

local ISP filtering the extra autonomous system hops. There are some issues, for example, not all

ISPs support the BGP prepend community, ISP policies may ignore or modify the autonomous

system hops, and a transit ISP may filter the autonomous system path. If you use this method of

inbound optimization and a change is made to an autonomous system, you must issue an

outbound reconfiguration using the “clear ip bgp” command.

Reference

http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-2s/pfr-bgp-inbound.html#GUID-

F8A59E241D59-

4924-827D-B23B43D9A8E0

http://www.cisco.com/en/US/products/ps8787/products_ios_protocol_option_home.html


CertBus exam braindumps are pass guaranteed. We guarantee your pass for the 400-101 exam successfully with our Cisco materials. CertBus CCIE Routing and Switching Written v5.0 exam PDF and VCE are the latest and most accurate. We have the best Cisco in our team to make sure CertBus CCIE Routing and Switching Written v5.0 exam questions and answers are the most valid. CertBus exam CCIE Routing and Switching Written v5.0 exam dumps will help you to be the Cisco specialist, clear your 400-101 exam and get the final success.

400-101 Latest questions and answers on Google Drive(100% Free Download): https://drive.google.com/file/d/0B_3QX8HGRR1mdEpkTFZvSDJDc2c/view?usp=sharing

400-101 Cisco exam dumps (100% Pass Guaranteed) from CertBus: https://www.certgod.com/400-101.html [100% Exam Pass Guaranteed]

Why select/choose CertBus?

Millions of interested professionals can touch the destination of success in exams by certgod.com. products which would be available, affordable, updated and of really best quality to overcome the difficulties of any course outlines. Questions and Answers material is updated in highly outclass manner on regular basis and material is released periodically and is available in testing centers with whom we are maintaining our relationship to get latest material.

BrandCertbusTestkingPass4sureActualtestsOthers
Price$45.99$124.99$125.99$189$69.99-99.99
Up-to-Date Dumps
Free 365 Days Update
Real Questions
Printable PDF
Test Engine
One Time Purchase
Instant Download
Unlimited Install
100% Pass Guarantee
100% Money Back
Secure Payment
Privacy Protection

Leave a Reply

Your email address will not be published. Required fields are marked *