Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

Moving a DCO DR node to a different subnet

EcoStruxure IT forum

Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • EcoStruxure IT
  • EcoStruxure IT forum
  • Moving a DCO DR node to a different subnet
Options
  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
Cory_McDonald
Admiral Cory_McDonald Admiral
124
Jef
Admiral Jef Admiral
109
gsterling
Captain gsterling Captain
71
APC_Steve
Captain APC_Steve Captain
62
View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Solved Go to Solution
Back to EcoStruxure IT forum
Solved
DCIM_Support
Picard DCIM_Support
Picard

Posted: ‎2020-07-04 05:16 PM . Last Modified: ‎2024-04-04 11:58 PM

0 Likes
3
659
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-04 05:16 PM . Last Modified: ‎2024-04-04 11:58 PM

Moving a DCO DR node to a different subnet

I have a customer who will be moving an existing DCO DR node from one site to another. There existing infrastructure consists of a DCO server with an attached DR node in the same rack. They also have a spare server of the same type which they wish to build as a standalone DCO server, relocate it interstate then have it assume the role of the DR node. They wish to minimize the time that they are without a DR node. They have 2 HA licences FYI...

Questions:-

  1. Can they just add the new DR IP address to the DCO server then attach the second DR node? (is this supported? i.e. can DCO support 2 DR nodes?)

  2. Should they just shut down the existing DR node then add the interstate DR node as per normal procedure? (will this cause any conflict with the original DR entry that the DCO server already knows about?)

I would appreciate any thoughts on the best way to "migrate" the DR node interstate.

Regards

Jim Davis - NIE Melbourne/AU

(CID:130683435)

Labels
  • Labels:
  • Data Center Operation
Reply

Link copied. Please paste this link to share this article on your social media post.

  • All forum topics
  • Previous Topic
  • Next Topic

Accepted Solutions
DCIM_Support
Picard DCIM_Support
Picard

Posted: ‎2020-07-04 05:16 PM . Last Modified: ‎2024-04-04 11:58 PM

0 Likes
0
659
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-04 05:16 PM . Last Modified: ‎2024-04-04 11:58 PM

Hi Jim,

  1. The new server (as second DR) cannot be added to an exiting setup "Standalone + DR". Setup will allow only 1 DR node!
  2.  Shutting down the existing DR node would not help, but it may help if it is promoted. Then it can be off-lined, if you wish. After promoting the existing DR node (via Webmin interface > StruxureWare DC Operation > Disaster Recovery > "Promote disaster recovery node"), then you would be able to add the new server as DR node.

Kind regards

(CID:131336255)

See Answer In Context

Reply

Link copied. Please paste this link to share this article on your social media post.

Replies 3
DCIM_Support
Picard DCIM_Support
Picard

Posted: ‎2020-07-04 05:16 PM . Last Modified: ‎2024-04-04 11:58 PM

0 Likes
0
660
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-04 05:16 PM . Last Modified: ‎2024-04-04 11:58 PM

Hi Jim,

  1. The new server (as second DR) cannot be added to an exiting setup "Standalone + DR". Setup will allow only 1 DR node!
  2.  Shutting down the existing DR node would not help, but it may help if it is promoted. Then it can be off-lined, if you wish. After promoting the existing DR node (via Webmin interface > StruxureWare DC Operation > Disaster Recovery > "Promote disaster recovery node"), then you would be able to add the new server as DR node.

Kind regards

(CID:131336255)

Reply

Link copied. Please paste this link to share this article on your social media post.

DCIM_Support
Picard DCIM_Support
Picard

Posted: ‎2020-07-04 05:16 PM . Last Modified: ‎2024-04-04 11:58 PM

0 Likes
0
659
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-04 05:16 PM . Last Modified: ‎2024-04-04 11:58 PM

After working with the customer today we identified the following error during the DR attachment process:-

The cluster time is 36080 seconds off from our time. Please correct the time.

36080 works out to 10 hours so we established that the server they were attempting to attach as a DR node had its system time out by 10 hours. Once a valid NTP server was configured and both servers times were closely matched, the DR attachment was successful.

Even though these are both standalone DCO servers, the reference to cluster time does not just refer to a DCO clustered environment.

(CID:132666154)

Reply

Link copied. Please paste this link to share this article on your social media post.

DCIM_Support
Picard DCIM_Support
Picard

Posted: ‎2020-07-04 05:16 PM . Last Modified: ‎2023-10-22 03:05 AM

0 Likes
0
659
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-04 05:16 PM . Last Modified: ‎2023-10-22 03:05 AM

superhero.png

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.

Reply

Link copied. Please paste this link to share this article on your social media post.

To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of