Exam 350-401 All QuestionsBrowse all questions from this exam
Go to Exam
Question 754

SIMULATION

-

Guidelines

-

This is a lab item in which tasks will be performed on virtual devices.

• Refer to the Tasks tab to view the tasks for this lab item.

• Refer to the Topology tab to access the device console(s) and perform the tasks.

• Console access is available for all required devices by clicking the device icon or using the tab(s) above the console window.

• All necessary preconfigurations have been applied.

• Do not change the enable password or hostname for any device.

• Save your configurations to NVRAM before moving to the next item.

• Click Next at the bottom of the screen to submit this lab and move to the next question.

• When Next is clicked, the lab closes and cannot be reopened.

Topology

-

Tasks

-

Implement GLBP between DISTRO-SW1 and DISTRO-SW2 on VLAN100 for hosts connected to ACCESS-SW1 to achieve these goals:

1. Configure group 30 using the virtual IP address of 192.168.1.254.

2. Configure DISTRO-SW1 as the AVG using a priority value of 130.

3. If DISTRO-SW1 suffers a failure and recovers, ensure that it automatically resumes the AVG role after waiting for a minimum of 35 seconds.

    Correct Answer:

Discussion
olaniyijt

Primary Switch: interface Vlan100 ip address 192.168.1.2 255.255.255.0 glbp 30 ip 192.168.1.254 glbp 30 priority 130 glbp 30 preempt delay minimum 35 end Secondary Switch: interface Vlan100 ip address 192.168.1.3 255.255.255.0 glbp 30 ip 192.168.1.254 https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipapp_fhrp/configuration/15-mt/fhp-15-mt-book/Configuring-GLBP.html

larsis

Tbh I wouldn't touch the counters. I think they want us to configure preempt delay instead: Primary SW: glbp 30 ip 192.168.1.254 glbp 30 priority 130 glbp 30 preempt delay minimum 35 Secondary SW: glbp 30 ip 192.168.1.254

HungarianDish

You are right! Thank you!

MJane

i actually would put the preempt command with the delay on the second too, just in case the second boots up first and takes the active role

JackDRipper

The way I understand it is, SW1 has a higher priority + preempt so as soon as it is up, it will count 35 seconds then take over the Active role from SW2.

sledgey121

Just passed but had 3 labs that are not detailed on this site. All good though and should be well within the capabilities of CCNA/CCNP network engineers.

f490efc

What were those about?

HungarianDish

SW2(config)#do sh glbp Vlan100 - Group 30 State is Standby 3 state changes, last state change 00:01:54 Virtual IP address is 192.168.1.254 Hello time 3 sec, hold time 35 sec Next hello sent in 2.048 secs Redirect time 600 sec, forwarder timeout 14400 sec Preemption disabled Active is 192.168.1.2, priority 130 (expires in 35.296 sec) Standby is local Priority 100 (default) Weighting 100 (default 100), thresholds: lower 1, upper 100 Load balancing: round-robin Group members: 5254.0017.8064 (192.168.1.3) local 5254.001a.8064 (192.168.1.2) There are 2 forwarders (1 active) Forwarder 1 State is Active 1 state change, last state change 00:01:57 MAC address is 0007.b400.1e01 (default) Owner ID is 5254.0017.8064 Preemption enabled, min delay 30 sec Active is local, weighting 100 Forwarder 2 State is Listen MAC address is 0007.b400.1e02 (learnt) Owner ID is 5254.001a.8064 Time to live: 14400.000 sec (maximum 14400 sec) Preemption enabled, min delay 30 sec Active is 192.168.1.2 (primary), weighting 100 (expires in 37.280 sec)

HungarianDish

It was requested to configure the hold time 35 sec on SW1. SW2 is not mentioned. Thus, I only configured it on SW1. Actually, SW2 (standby AVG) took the timer values from SW1 (active AVG) anyways.

HungarianDish

This exercise requires to change the hold time value. The hello time is not mentioned. I suppose that it is better to leave the hello time on the default 3 sec, and only change the hold time to 35 sec (from 10 sec). interface Vlan100 ip address 192.168.1.2 255.255.255.0 glbp 30 ip 192.168.1.254 glbp 30 timers 3 35 glbp 30 priority 130 glbp 30 preempt #show glbp Vlan100 - Group 30 State is Init (interface down) Virtual IP address is 192.168.1.254 Hello time 3 sec, hold time 35 sec Redirect time 600 sec, forwarder timeout 14400 sec Preemption enabled, min delay 0 sec Active is unknown Standby is unknown Priority 130 (configured)

fasttony77

It is the preempt delay timer that it is asking for, not the hold time. glbp 30 preempt delay minimum 35

IgorLVG

i understand the hold time is the fisrt thing in mind but i would like to refer that when the hold time is overcome, the protocol recalculates who will be the AVG. In delay is more bounded

Wanessamgp

"Use the optional delay and minimum keywords and the seconds argument to specify a minimum delay interval in seconds before preemption of the AVG takes place. " https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipapp_fhrp/configuration/15-mt/fhp-15-mt-book/Configuring-GLBP.html

wengzaii96

is the exam LAB allow tab ?

EAC84

yes you can tab out the commands like a normal

Tadese

Primary Switch: interface Vlan100 ip address 192.168.1.2 255.255.255.0 glbp 30 ip 192.168.1.254 glbp 30 priority 130 glbp 30 preempt delay minimum 35 end Secondary Switch: interface Vlan100 ip address 192.168.1.3 255.255.255.0 glbp 30 ip 192.168.1.254

danman32

I agree, hold timer manipulation is not the means of delaying preempt. The hold time is when an AVG will determine a failure has occurred. If the question was asked to delay action on failure, then managing the timers would be appropriate, though in real world probably not ideal. But criteria is about the primary delaying taking back AVG role.