1 / 4

MP Failover DNS Option 1 for API Failover

MP Failover DNS Option 1 for API Failover. The same DNS structure that allows ERCOT to fail over services between sites can also be used to allow MPs to transparently fail over services during a move to their Backup site.

chico
Download Presentation

MP Failover DNS Option 1 for API Failover

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MP Failover DNS Option 1 for API Failover • The same DNS structure that allows ERCOT to fail over services between sites can also be used to allow MPs to transparently fail over services during a move to their Backup site. • Market Participants provide and maintain their own DNS server which must be accessible over the ERCOT WAN if they wish to make use of this option. • After implementation, when a MP Backup site failover is desired, the participant simply updates the zone file with their disaster recovery IP addresses and pushes it out to the ERCOT DNS servers and the change will take effect immediately.

  2. Web-Based DNS Option 2 for API Failover • Currently being evaluated as an alternative method for those who do not wish to maintain their own DNS servers. • Changes are made active in a matter of seconds. • Easy to use web based interface. • Password based authentication allows users to only see servers they are authoritative for. • To fail over to a Disaster Recovery site you simply need to update the IP address of the existing entry. ERCOT servers will pick up the change and start using the new IP immediately.

  3. RTU and ICCP Communications For Backup Sites • Inventory of current ICCP and RTU connections. • Defining current options for both ICCP and DNP (RTU). • Defining the requirements, maintenance and testing procedures for both ICCP and DNP • Present to ERCOT System Operations findings and different options

  4. Next Steps • Revise ERCOT Operating Guides to include DNS option 1 & 2 for API communications with Primary and Backup sites. • Migrate each QSE on WAN to either option 1 or 2 • Migrate ERCOT’s API’s to use DNS for QSE URL’s • Example: API.QSEX.COM • Completion by end of November 2005. • QSE’s with backup sites will be migrated first • Potential changes in ERCOT Operating Guides for RTU and ICCP communications to Backup sites. • Potential changes in ERCOT Operating Guides for Testing Backup sites

More Related