-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
sum_giais May 4, 2017 7:46 PM (in response to teja0909)I recently had enabled a SolarWinds HA pool for our primary server and had a boat load of questions. I opened a case with support around expected functionality and they pointed out a couple links.
Here's one specifically towards your scenario. This setup that support pointed me to I thought was intriguing. Not sure if SolarWinds supports it though but...
https://thwack.solarwinds.com/thread/109227
Also here is a good read for SolarWinds HA...
High Availability in NPM - SolarWinds Worldwide, LLC. Help and Support
Failing over in my environment takes approximately 1-2 min. Note web console sessions will expire and all users will need to log back in as necessary.
Hope this helps!
giais
-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
teja0909 May 5, 2017 9:44 AM (in response to sum_giais)Thanks for the response Giais. I am unable to understand the Process. We are implementing the Orion Servers on esxi. Can you explain How I can choose Ip's for primary and secondary in the same subnet?
-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
sum_giais May 5, 2017 12:14 PM (in response to teja0909)From what I understood from the post, is that each SolarWinds server that is going to be part of the pool is given an additional network interface with an IP subnet of your choosing. This subnet would not route, or have connectivity, and the 'shared' IP is also in that shared non-routed subnet. It's simply to get around the requirement that the servers in the HA pool need to be in the same subnet.
If I were going to implement something like that (which I'm not), my HA setup is all in the same subnet -- I'd work with SolarWinds support directly to see if it's supported, recommended, etc..
-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
neomatrix1217 May 8, 2017 9:35 PM (in response to teja0909)You need to create a virtual IP so that the failover is seemless.
What is a Virtual IP address in NPM? - SolarWinds Worldwide, LLC. Help and Support
-
-
-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
rschroederMay 8, 2017 9:46 PM (in response to teja0909)
2 of 2 people found this helpfulI've done what you're trying--two HA servers, different data centers. I implemented Cisco's NX-OS and leveraged their Overlay Transport Virtualization--OTV. It enables you to extend a Layer 2 VLAN / Subnet between two different sites, while retaining the ability to block broadcast storms between the two data centers. We ended up with many HA servers on the same IP network but in two different locations through using OTV.
-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
sum_giais May 9, 2017 6:13 AM (in response to rschroeder)1 of 1 people found this helpfulNow that's pretty cool.
-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
teja0909 May 9, 2017 11:38 AM (in response to rschroeder)But in my environment, we are not using nexus 7k .Is there any other way to connect with catalyst environment?.Thanks in advance.
-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
aLTeReGoMay 9, 2017 1:32 PM (in response to teja0909)
teja0909, do you own High Availability licenses or are you evaluating HA in your environment?
-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
rschroederMay 9, 2017 2:11 PM (in response to teja0909)
To the best of my knowledge, no, there is not a different way to extend an L2 subnet/VLAN between two physically separate/remote sites that meets HA criteria. Although you should work with your data center / WAN architect and VAR to confirm you can't come up with something elegant. You shouldn't kluge together a one-off that isn't robust and doesn't follow network design best practices.
I think most of us could build a kluge that might accomplish this--maybe you'd create a GRE tunnel between the sites, maybe you'd dedicate a Layer 2 Interface at both sites and physically span your L2 between them--certainly not a best practice!
Work with your VAR and WAN hardware manufacture's Sales Engineer and technical support staff to ensure your end result is something that will do the job right for you and your company for years to come.
-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
rschroederAug 23, 2017 9:02 AM (in response to teja0909)
Work with your Cisco reseller and with Cisco itself to see if there's a solution. Who knows, maybe you can work something out with a GRE tunnel.
But as far as I know, OTV is restricted to the Nexus environment, and I implemented it in pairs of 7009's and 7010's. Maybe you can get it running 5596's?
It's complex, and making changes to an OTV environment require a perfect process and thorough understanding of the steps. I recommend using a step-by-step template that eliminates any possibility for error. Once you depend on OTV, breaking it is a "career limiting opportunity."
-
-
-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
piharrison Aug 22, 2017 10:50 AM (in response to teja0909)I was able to accomplish what you are trying to do by choosing a "fake" shared subnet between the HA Active and HA Passive pair as I have documented in my post. Let me know if you need some guidance following some of the madness I posted... ;-)
This will answer how to implement HA without having to actually share a subnet between 2 data centers.
SOLARWINDS HIGH AVAILABILITY - HA - IN A WAN ENVIRONMENT!!!
Best Regards,
-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
neomatrix1217 Aug 22, 2017 2:20 PM (in response to piharrison)1 of 1 people found this helpful- Integrated Disaster Recovery Engine - Disaster recovery will provide redundancy to the Orion platform in multi-subnet deployment configurations.
-
-
Re: WHILE UPGRADING TO HIGH AVAILABILITY MODE THE PRIMARY AND SECONDARY SERVER SHOULD BE ON SAME SUBNET(BUT PRIMARY AND SECONDARY SERVERS ARE IN DIFFERENT LOCATIONS)
aLTeReGoAug 23, 2017 9:09 AM (in response to teja0909)
HIgh Availability 2.0 Release Candidate is available now and can be downloaded from your customer portal. It's incorporated into the NPM 12.2 Release Candidate. High Availability 2.0 supports multi-subnet failover, and no longer requires both members in a pool to be on the same subnet.