ExamTopics Logo
Mail Us[email protected]
Menu
Cisco Discussions
exam questions

Exam 300-425 All Questions

View all questions & answers for the 300-425 exam
Go to Exam

Exam 300-425 topic 1 question 107 discussion

Actual exam question from Cisco's 300-425
Question #: 107
Topic #: 1
[All 300-425 Questions]


Refer to the exhibit. An enterprise is using wireless as the main network connectivity for clients. To ensure service continuity, a pair of controllers will be installed in a datacenter. An engineer is designing SSO on the pair of controllers. What needs to be included in the design to avoid having the secondary controller go into maintenance mode?

  • A. The redundancy port must be the same subnet as the redundancy mgmt.
  • B. The keep alive timer is too low, which causes synchronization problems.
  • C. The connection between the redundancy ports is missing.
  • D. The Global Configuration of SSO is set to Disabled on the controller.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️
by Coffee313 at Aug. 27, 2021, 3:57 p.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
ft75
Highly Voted 2 years, 1 month ago
D, according to this document: https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/HA_SSO_DG/High_Availability_DG.html#pgfId-43357
upvoted 5 times
Liselot
1 year, 11 months ago
This! The question is formulated a bit oddly. The secondary controller goes in maintenance mode when SSO will be enabled. If you want to avoid that, you should disable SSO.
upvoted 3 times
...
...
Farhad123
Most Recent 4 months, 1 week ago
Selected Answer: C
At first glance, you might think that option D is correct, and it may even seem logical. Since if SSO is disabled, then obviously, the SSO functionality won’t work... However, pay attention to the question! It is asking what causes the secondary controller to go into maintenance mode. This happens when the redundancy port encounters an issue. I believe the diagram provided in the question is meant to be misleading.
upvoted 1 times
...
Araghas
9 months ago
Management & Redundancy-management should be on same subnet. Each unit need to have unique redundancy-management IP address & management IP address is shared between units.
upvoted 1 times
Araghas
9 months ago
"As a final thought, let’s return to the question originally posed, “Where Did That IP Address 169.254.0.1 Come From?” Many client operating systems use something called Automatic Private IP Addressing. This process assigns an IP address even in the absence of a DHCP server. If a DISCOVER message is not answered, the client picks a random 16-bit number and prepends it with 169.254.x.x. It performs a gratuitous ARP and assigns that address to itself."
upvoted 1 times
...
Araghas
9 months ago
Redundancy Port This interface has a very important role in the new HA architecture. Bulk configuration during boot up and incremental configuration are synced from the Active WLC to the Standby WLC using the Redundant Port. WLCs in a HA setup will use this port to perform HA role negotiation. The Redundancy Port is also used in order to check peer reachability sending UDP keep-alive messages every 100 msec (default timer) from the Standby WLC to the Active WLC. Also, in the event of a box failure, the Active WLC will send notification to the Standby WLC via the Redundant Port. If the NTP server is not configured, a manual time sync is performed from the Active WLC to the Standby WLC on the Redundant Port. This port in case of standalone controller and redundancy VLAN in case of WISM-2 will be assigned an auto generated IP Address where last 2 octets are picked from the last 2 octets of Redundancy Management Interface (the first 2 octets are always 169.254).
upvoted 1 times
...
...
RSC357
11 months, 3 weeks ago
C - Alonzo: My reason we wrong but the answer is "C" as you pointed out.
upvoted 2 times
...
Alonzo_Harris
1 year ago
Selected Answer: C
The answer is C Maintenance Mode: There are few scenarios where the Standby WLC may go into Maintenance Mode and not be able to communicate with the network and peer: -Non reachability to Gateway via Redundant Management Interface -WLC with HA SKU which had never discovered peer ***Redundant Port is down*** -Software version mismatch (WLC which boots up first goes into active mode and the other WLC in Maintenance Mode)
upvoted 4 times
...
RSC357
1 year, 4 months ago
C - 169.254.x.x indicates no DHCP or static assignment was given. The engineer needs to configure that.
upvoted 1 times
...
mqoltn
1 year, 4 months ago
C, look at the comment from mohanak here: https://community.cisco.com/t5/wireless/wlc-ha-maintenance-mode/td-p/2927232 There are few scenarios where the Standby WLC may go into Maintenance Mode and not be able to communicate with the network and peer: - Non reachability to Gateway via Redundant Management Interface - WLC with HA SKU which had never discovered peer - Redundant Port is down - Software version mismatch (WLC which boots up first goes into active mode and the other WLC in Maintenance Mode) A / not correct, RP is l2 port where RMI is l3 B/ not correct keepalives doesnt matter and wont cause hotstandby to go to maintenance mode C/ correct, if RP is down that indeed causes standby to go to maintenance mode D/ incorrect, according to the phrasing of the question, engineer is just preparing the confgiuration. enabling SSO is the final step after all the rest of config is finished. Once enabled WLCs will reboot and discover the HA SSO neighbors and join the HA SSO stack. C/
upvoted 3 times
...
Rastacuache
1 year, 7 months ago
The right answer is C. According to this URL: https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/HA_SSO_DG/High_Availability_DG.html#pgfId-105076 -The Standby WLC sends Keepalive to the Active WLC and expects and acknowledgment within 100 msec as per the default timer. This can be configured in range from 100-400 msec - So B is not correct 2. SSO must be enabled ir order to pair both controllers so D is not correct 3. Once SSO is enabled, it will reboot the WLCs. While it boots, the WLCs negotiate the HA role as per the configuration via Redundant Port. If the WLCs cannot reach each other via Redundant Port or via the Redundant Management Interface, the WLC configured as Secondary may go in to Maintenance Mode. So the correct answer is C
upvoted 2 times
...
udemy_learner
1 year, 10 months ago
The question states "An engineer is designing SSO on pair of controllers". Why would you disable SSO when you are trying to build a SSO connection? I think it is C
upvoted 3 times
...
ASV2020
2 years, 2 months ago
Answer: C
upvoted 1 times
...
RogerTheLodger
2 years, 3 months ago
C - ‘There are few scenarios where the Standby WLC may go into Maintenance Mode and not be able to communicate with the network and peer: • Non reachability to Gateway via Redundant Management Interface • WLC with HA SKU which had never discovered peer • Redundant Port is down • Software version mismatch (WLC which boots up first goes into active mode and the other WLC in Maintenance Mode)’ High Availability (SSO) Deployment Guide - Cisco
upvoted 4 times
Liselot
1 year, 11 months ago
The question is how to AVOID having the secondary controller go into maintenance mode
upvoted 2 times
...
...
Coffee313
2 years, 4 months ago
D is correct
upvoted 3 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel