Exam 350-401 topic 1 question 41 discussion

Gentlemen, i strongly agree with Goathammer and Amansoor. Here is my thinking to the topic. since we are configuring a NEW member of HSRP> I ASSUME !!!! that router 1 is the active and already in the network forwarding traffic. if i changed the remote ip address to my newly configured 10.1.1.25 then i run the danger of disrupting network forwarding even for a short time. to not cause any CHANGE to the state of the existing network i would opt to change the NEWLY Configured router 10.1.1.25 to the already running one of 10.1.1.1 long story short the message says that members of the group do not agree on the same virtual ip. so it is up to you to change the running router(s) to the new config risking a short downtime due to Role Selection OR to be on the safe side, just change the NEWLY added router to match the existing setup. i hope my explanations or the way i thought about the problem makes sense. thanks all

Syslog points to local router having VIP ip 10.1.1.25, and remote router in g0/0 interface having 10.1.1.1. We want latter to all routers in HSRP so we need to configure local router, hence B. "is different to the locally configured..."

Router1(config-if)# standby 1 ip 192.168.1.1 and Router2(config-if)# standby 1 ip 192.168.1.1 must be the same

B. is correct Verified in CML 2: R2(config-if)#int g0/1 R2(config-if)#standby 1 ip 192.168.1.25 R2(config-if)# *Sep 19 15:37:54.589: %HSRP-4-DIFFVIP1: GigabitEthernet0/1 Grp 1 active routers virtual IP address 192.168.1.3 is different to the locally configured address 192.168.1.25 *Sep 19 15:38:14.110: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Speak -> Standby *Sep 19 15:38:26.004: %HSRP-4-DIFFVIP1: GigabitEthernet0/1 Grp 1 active routers virtual IP address 192.168.1.3 is different to the locally configured address 192.168.1.25 *Sep 19 15:38:56.261: %HSRP-4-DIFFVIP1: GigabitEthernet0/1 Grp 1 active routers virtual IP address 192.168.1.3 is different to the locally configured address 192.168.1.25 R2(config-if)#standby 1 ip 192.168.1.3 No more messages...

B is correct

The question makes zero sense, analyzing the log message notwithstanding An network engineer configures the router with 10.1.1.1 and now has to change the router he is *currently configuring with 10.1.1.1 to 10.1.1.1* Unless the engineer made a typo and typed .25 when he meant to type .1 Unless he watches the terminal of the other router as he configures the new router, but that STILL doesn't make sense. This is the typical rotten, dirty, low-down, sneaky question I have come to expect of Cisco, instead of asking clear-cut questions, they leave everything open to 2-3 different interpretations. If a customer gave me this info I would tell him to go away and come back when he has more than just confusing nonsense as info.

What confused me was that the syslog said the remote router's VIP was 10.1.1.1 while the local router's VIP was 10.1.1.25. But how could the local VIP be 10.1.1.25 if it says the engineer configured it for 10.1.1.1? Then figured WHILE the engineer was configuring. Perhaps he intended to make it 10.1.1.1 but made a typo in the process.

B is correct

B is the best answer. You could make an argument for C, but as an engineer, you should avoid disrupting operations as much as possible. If you follow through with C, there will have to be a reconvergence and disrupt forwarding until HSRP goes through its states. Moreover! and probably a good possibility, the DHCP servers for endpoints more than likely are already configured with the Active Router's virtual IP as the default gateway when assigning addresses within the subnet, and changing that will prevent endpoints from communicating outside their domain.

Definitly B

B is correct

the ip just ip (10.1.1.25) is diferrent to te Virtual Ip (10.1.1.1),should to change it to the VIp

I tested it on Packet tracer, configure HSRP group first with VIP 10.1.1.25. And then try to configure a new VIP 10.1.1.1. You will get the exact same syslog message. To stop that error you have to make the same change (Configuring new VIP in the remote router 10.1.1.1)

Tested in GNS3 and correct.