In this blog, I will setup link redundancy to the switch, using two fiber uplinks, and then configure SSO on the standalone 9800 series controller.
First, I create a port channel and then configure the uplinks on the Primary 9800 controller.
interface Port-channel7
description edh001-011-wc01
switchport trunk allowed vlan 25,34,300,2346,3200,3201
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
!
interface TenGigabitEthernet0/0/0
description WLAN Controller trunk uplink
switchport trunk allowed vlan 25,34,300,2346,3200,3201
switchport mode trunk
switchport nonegotiate
logging event trunk-status
no negotiation auto
channel-group 7 mode on
!
interface TenGigabitEthernet0/0/1
description WLAN Controller trunk uplink
switchport trunk allowed vlan 25,34,300,2346,3200,3201
switchport mode trunk
switchport nonegotiate
logging event trunk-status
no negotiation auto
channel-group 7 mode on
!
Now I create the other end of the configuration – which happens to be the core switch:
!
interface Port-channel7
description edh001-011-wc01
switchport trunk allowed vlan 25,34,300,2346,3200,3201
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
!
interface TenGigabitEthernet1/1/1
description edh001-011-wc01
switchport trunk allowed vlan 25,34,300,2346,3200,3201
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
channel-group 7 mode on
!
interface TenGigabitEthernet1/1/2
description edh001-011-wc01
switchport trunk allowed vlan 25,34,300,2346,3200,3201
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
channel-group 7 mode on
!
Next, I create the configuration on the core switch to talk to the second, “base configured” 9800 series controller that we will put into SSO.
!
interface Port-channel8
description edh001-011-wc01
switchport trunk allowed vlan 25,34,300,2346,3200,3201
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
!
interface TenGigabitEthernet1/1/3
description edh001-011-wc01-
switchport trunk allowed vlan 25,34,300,2346,3200,3201
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
channel-group 8 mode on
!
interface TenGigabitEthernet1/1/4
description edh001-011-wc01
switchport trunk allowed vlan 25,34,300,2346,3200,3201
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
channel-group 8 mode on
!
Now back to the 9800 series controller, the one that we will call Primary. It has a configuration on it and it basically a standalone controller.
I am going to configure this controller as the primary, since I just want a specific controller to be the primary. A higher chassis = higher priority.
edh001-011-wc01#chassis 1 renumber 2
WARNING: Changing the switch number may result in a configuration change for that switch. The interface configuration associated with the old switch number will remain as a provisioned configuration. New Switch Number will be effective after next reboot. Do you want to continue?[y/n]? [yes]: yes ß Note that I have not rebooted it yet!!!
edh001-011-wc01#sho chassis
Chassis/Stack Mac Address : 4cec.0f2a.a3a0 - Local Mac Address
Mac persistency wait time: Indefinite
Local Redundancy Port Type: Twisted Pair
H/W Current
Chassis# Role Mac Address Priority Version State IP
-------------------------------------------------------------------------------------
*1 Active 4cec.0f2a.a3a0 1 V02 Ready 0.0.0.0 ß Note that I have not rebooted it yet!!!
edh001-011-wc01#chassis 1 priority 2
edh001-011-wc01#sho chassis
Chassis/Stack Mac Address : 4cec.0f2a.a3a0 - Local Mac Address
Mac persistency wait time: Indefinite
Local Redundancy Port Type: Twisted Pair
H/W Current
Chassis# Role Mac Address Priority Version State IP
-------------------------------------------------------------------------------------
*1 Active 4cec.0f2a.a3a0 2 V02 Ready 0.0.0.0 ß Note that I have not rebooted it yet!!!
A little heads up. I’m running 17.9.3, and I was going to use IP address of 169.254.5.6, since the management vlan (25) is 10.64.25.x. This was an epic failure and when I tried to configure it I got my hand slapped:
!!! configuring 169.254.X.Y(f) is not allowed
Therefore, don’t waste your time. Grab two IP addresses off your management subnet and use them for SSO and be done with it.
*remember*, this is now chassis two, not one. ß Note that I have not rebooted it yet!!! When I reboot it, it will be chassis 2. So we are configuring it now as if it is chassis 2. If you are confused, just reboot your controller, I suppose.
edh001-011-wc01(config)#redun-management interface vlan 25 chassis 2 address 10.64.25.253 chassis 1 address 10.64.25.254
edh001-011-wc01#wr mem
=========== NOW MOVING TO THE OTHER CONTROLLER – THE ONE THAT WILL MAKE THEM AN SSO PAIR============
Now, let’s go to the SSO controller. I put a base config on it which consists of an IP address on the g0 so I could install the same exact code on it that is running on the Primary 9800 controller.
Armed with a console cable, I slowly approach the controller and quickly plug it in to the console port. Success!
*create a port channel and then configure the uplinks on the 9800 controller* use the steps at the beginning of this HowTo.
<output omitted>
edh001-011-wc02(config)#
edh001-011-wc02(config)#redun-management interface vlan 25 chassis 1 address 10.64.25.254 chassis 2 address 10.64.25.253
WARNING: Reload HA Chassis for RMI configuration to take effect ß Note this is a subtle hint for me to go BACK to the Primary controller and reboot it.
*note – this chassis is chassis #1, just like the other one. We are going to leave this one as chassis #1, per config line above.
=========== NOW MOVING TO THE PRIMARY CONTROLLER (for rebooting purposes) ============
edh001-011-wc01#reload
Reload command is being issued on Active unit, this will reload the whole stack
Proceed with reload? [confirm] Y
<output omitted>
Now I am going to just paste console outputs from both controllers, since the Primary has rebooted and the SSO pair is successful. edh001-011-wc01 is Primary, edh001-011-wc01-stby is the standby.
edh001-011-wc01#sho chassis
Chassis/Stack Mac Address : 4cec.0f2a.a3a0 - Local Mac Address
Mac persistency wait time: Indefinite
Local Redundancy Port Type: Twisted Pair
H/W Current
Chassis# Role Mac Address Priority Version State IP
-------------------------------------------------------------------------------------
1 Standby 648f.3e83.fb20 1 V02 HA sync in progress 169.254.25.254 ß The standby controller has not synced yet
*2 Active 4cec.0f2a.a3a0 2 V02 Ready 169.254.25.253 ß This is the Primary, recall we renumbered it to chassis 2.
#sho chassis
Chassis/Stack Mac Address : 4cec.0f2a.a3a0 - Local Mac Address
Mac persistency wait time: Indefinite
Local Redundancy Port Type: Twisted Pair
H/W Current
Chassis# Role Mac Address Priority Version State IP
-------------------------------------------------------------------------------------
1 Standby 648f.3e83.fb20 1 V02 Ready 169.254.25.254ß synchronized
*2 Active 4cec.0f2a.a3a0 2 V02 Ready 169.254.25.253 ß synchronized
Now look at the management VLAN’s config: The secondary IP address has been added to the management VLAN’s configuration.
edh001-011-wc01#sho run int vlan 25
Building configuration...
Current configuration : 144 bytes
!
interface Vlan25
description WLAN_MGMT_10.64.25.0
ip address 10.64.25.253 255.255.255.0 secondary
ip address 10.64.25.5 255.255.255.0
end
Here’s a trick if you want to be able use console in to the standby controller and issue *some* commands. I’m not an expert on what commands are available.
edh001-011-wc01#conf t
Enter configuration commands, one per line. End with CNTL/Z.
edh001-011-wc01(config)#
edh001-011-wc01(config)#redundancy
edh001-011-wc01(config-red)#main-cpu
edh001-011-wc01(config-r-mc)#standby console enable
edh001-011-wc01(config-r-mc)#do wr mem
Building configuration...
=========== NOW MOVING TO THE SECONDARY CONTROLLER (to see what commands are available on console) ============
Username: admin123
Password: ChangeMe
edh001-011-wc01-stby>ena
Password: PleaseChangeMeNow
edh001-011-wc01-stby#sho chassis
Chassis/Stack Mac Address : 4cec.0f2a.a3a0 - Local Mac Address
Mac persistency wait time: Indefinite
Local Redundancy Port Type: Twisted Pair
H/W Current
Chassis# Role Mac Address Priority Version State IP
-------------------------------------------------------------------------------------
*1 Standby 648f.3e83.fb20 1 V02 Ready 169.254.25.254
2 Active 4cec.0f2a.a3a0 2 V02 Ready 169.254.25.253
edh001-011-wc01-stby#sho chassis rmi
Chassis/Stack Mac Address : 4cec.0f2a.a3a0 - Local Mac Address
Mac persistency wait time: Indefinite
Local Redundancy Port Type: Twisted Pair
H/W Current
Chassis# Role Mac Address Priority Version State IP RMI-IP
--------------------------------------------------------------------------------------------------------
*1 Standby 648f.3e83.fb20 1 V02 Ready 169.254.25.254 10.64.25.254
2 Active 4cec.0f2a.a3a0 2 V02 Ready 169.254.25.253 10.64.25.253
edh001-011-wc01-stby#
You’re done! SSO is configured.
🇺🇸🇺🇸🏴🏴Investment is one of the best ways to achieve financial freedom. For a beginner there are so many challenges you face. It's hard to know how to get started. Trading on the Cryptocurrency market has really been a life changer for me. I almost gave up on crypto at some point not until saw a recommendation on Elon musk successfully success story and I got a proficient trader/broker Mr Bernie Doran , he gave me all the information required to succeed in trading. I made more profit than I could ever imagine. I'm not here to converse much but to share my testimony; I have made total returns of $10,500.00 from an investment of just $1000.00 within 1 week. Thanks to Mr Bernie I'm really grateful,I have been able to make a great returns trading with his signals and strategies .I urge anyone interested in
ReplyDeleteINVESTMENT to take bold step in investing in the Cryptocurrency Market, you can reach him on WhatsApp : +1(424) 285-0682 or his Gmail : BERNIEDORANSIGNALS@GMAIL.COM, bitcoin is taking over the world, tell him I referred you🇺🇸🇺🇸🏴🏴
BEST STEPS TO TAKE TO RECOVER YOUR MONEY BACK AFTER BEEN SCAMMED
ReplyDeleteI'm overwhelmed with gratitude towards Jetwebhackers for their invaluable assistance in recovering the $38,540 I had lost to a crypto scam. This amount was meant for my kids' school fees, and I was deceived by a fraudster posing as Agent David, who promised me a return of $380,940 - but it was all a scam. Thanks to Jetwebhackers' expertise and dedication, I was able to recover not only the initial investment but also the profit I was promised. Their help has taken a huge weight off my shoulders, and I can now provide for my children's education. I highly recommend Jetwebhackers to anyone who has fallen victim to crypto scams. They are trustworthy, efficient, and reliable. Thank you, Jetwebhackers, for your exceptional service
CONTACT THEM VIA
EMAIL:jetwebhackers @