SlarWinds Technical Reference Preparing an Orin Failver Engine Installatin Intrductin t the Orin Failver Engine... 1 General... 1 Netwrk Architecture Optins and... 3 Server Architecture Optins and... 4 This technical reference prvides an verview f sftware, hardware and netwrk requirements fr each f the fllwing supprted installatin cnfiguratins: Physical-t-physical (P2P) Physical-t-virtual (P2V) Virtual-t-virtual (V2V) netwrk management simplified - slarwinds.cm
Cpyright 1995-2014 SlarWinds, Inc. all rights reserved wrldwide. N part f this dcument may be reprduced by any means nr mdified, decmpiled, disassembled, published r distributed, in whle r in part, r translated t any electrnic medium r ther means withut the written cnsent f SlarWinds. All right, title and interest in and t the sftware and dcumentatin are and shall remain the exclusive prperty f SlarWinds and its licensrs. SlarWinds, the SlarWinds lg, ipmnitr, LANsurveyr, and Orin are amng the trademarks r registered trademarks f the cmpany in the United States and/r ther cuntries. All ther trademarks cntained in this dcument and in the Sftware are the prperty f their respective wners. SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS OR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Micrsft, Windws 2000 Server, Windws 2003 Server, and Windws 2008 Server are either registered trademarks r trademarks f Micrsft Crpratin in the United States and/r ther cuntries. Graph Layut Tlkit and Graph Editr Tlkit 1992-2001 Tm Sawyer Sftware, Oakland, Califrnia. All Rights Reserved. Prtins Cpyright CmpnentOne, LLC 1991-2002. All Rights Reserved. Dcument Revised: 2/25/2014
Preparing an Orin Failver Engine Installatin 1 Intrductin t the Orin Failver Engine The Orin Failver Engine is a Windws-based service specifically designed t prvide high availability prtectin fr SlarWinds Orin NPM installatins withut requiring any specialized hardware. Fr mre detailed infrmatin abut the Orin Failver Engine, see the SlarWinds Orin Failver Engine Administratr Guide. As indicated in the fllwing graphic, the server fr which the Orin Failver Engine prvides failver prtectin is designated as the primary The server t which the Orin Failver Engine switches peratin in the event f a primary server failure is designated as the secndary Failver Engine can be deplyed in a LAN fr high availability r acrss a WAN t prvide disaster recvery. This dcument prvides an verview f deplyment ptins and prerequisites fr successfully implementing Failver Engine. The fllwing deplyment scenari table prvides a visual reference t cnfiguratin ptins supprted by Failver Engine. Netwrk Clne Technique Cmpnent LAN WAN Pre Clne Install Clne Failver Engine V2V X X X X P2V X X X X X P2P X X X X During the installatin prcess, Failver Engine perfrms a variety f checks t ensure yur Orin server meets the minimum requirements fr a successful installatin. A critical stp r warning message appears if the server fails a check. Yu must reslve critical stps befre yu can prceed with setup. Fr mre infrmatin, see Setup Errr Messages in the SlarWinds Orin Failver Engine Administratr Guide. General The fllwing requirements are in additin t the hardware and sftware requirements utlined in the sectin T cnfirm in Windws Server 2008: 1. Click Start > Cntrl Panel > Netwrk and Internet > Netwrk and Sharing Center. 2. Click Manage Netwrk Cnnectins. 3. Click Advanced > Advanced Settings, and then use the arrws t rder bindings as needed.
2 Preparing an Orin Failver Engine Installatin T cnfirm in Windws Server 2012: 1. Click Cntrl Panel > Netwrk and Sharing Center. 2. Click Change adapter settings. 3. Type the Alt key, and then click Advanced > Advanced Settings. 4. Use the arrws t rder bindings as needed. Netwrk Architecture Optins and n page 2. Micrsft Windws Autmatic Updates must nt be cnfigured t apply updates autmatically. Updates may be dwnladed autmatically, but they can nt be applied manually due t the pssibility that an autmatically updated server may rebt unexpectedly. An accunt with lcal administratr rights is required t cmplete Orin Failver Engine installatin. All applicatins t be prtected n the primary server must be fully installed and cnfigured n the primary server prir t installing the Orin Failver Engine. Bth the primary and secndary servers must have identical system date, time, and time zne settings. Once cnfigured crrectly, the time zne shuld nt be changed. If installing in a Windws 2008 server envirnment, User Accunt Cntrl (UAC) must be disabled during the installatin prcess. Because Failver Engine nly prtects the SlarWinds Orin Server, n ther critical business applicatins shuld be installed n the prtected The Failver Engine is unable t prtect any server cnfigured in any f the fllwing rles: Dmain cntrller Glbal catalg DNS. The principal netwrk adapter must be the first adapter listed in the netwrk cnnectins bind rder. T cnfirm in Windws Server 2003: 1. Click Start > Run. 2. Enter ncpa.cpl, and then click OK. 3. Click Advanced > Advanced Settings, and then use the arrws t rder bindings as needed. T cnfirm in Windws Server 2008: 4. Click Start > Cntrl Panel > Netwrk and Internet > Netwrk and Sharing Center. 5. Click Manage Netwrk Cnnectins. 6. Click Advanced > Advanced Settings, and then use the arrws t rder bindings as needed. T cnfirm in Windws Server 2012: 5. Click Cntrl Panel > Netwrk and Sharing Center. 6. Click Change adapter settings. 7. Type the Alt key, and then click Advanced > Advanced Settings. 8. Use the arrws t rder bindings as needed.
Preparing an Orin Failver Engine Installatin 3 Netwrk Architecture Optins and The netwrk architecture yu select is largely determined by the intended purpse f yur Orin Failver Engine installatin, as fllws: If yu are using the Orin Failver Engine as a High Availability (HA) slutin, a LAN cnfiguratin is required. Fr mre infrmatin, see LAN n page 3. If yu are using the Orin Failver Engine fr Disaster Recvery (DR), a WAN cnfiguratin is required. Fr mre infrmatin, see WAN n page 4. LAN When deplyed in a LAN envirnment, the Failver Engine requires that bth servers use the same principal, public IP address. Each server als requires a separate SlarWinds Channel IP address n a separate dedicated subnet. LAN High Availability Netwrk Interface Cards NetBIOS 2 dedicated netwrk interface cards, defined as fllws: Nte: A third NIC is recmmended fr redundancy n the SlarWinds Channel between the primary and secndary servers. 1 static IP (nn-dhcp) as the public address, shared between the active and passive servers. Verify that the principal netwrk adapter is listed first in the netwrk cnnectins bind rder. 1 IP n each server, defining the SlarWinds Channel, bth f which are utside the subnet f the shared public IP. SlarWinds Channel NICs are standard 100BaseT Ethernet cards with thrughput f 100 Mbits per secnd acrss standard Cat-5 crssver cabling. In a WAN deplyment, cnfigure the SlarWinds Channel t use static rutes ver switches and ruters t maintain cntinuus cmmunicatins, independent f crprate r public traffic Enabled n the static, principal cnnectin t the public netwrk. Disabled during installatin, but therwise enabled n the SlarWinds Channel between the primary and secndary servers Secndary Server Same as primary server Same as primary server Three NICs (1 x Public; 2 x Channel) are recmmended fr redundancy in the event that any single channel fails. A minimum f tw NICs (ne fr the Channel, and ne fr the principal cnnectin) are required in this cnfiguratin. Additinally, Split-brain avidance shuld be cnfigured. The principal, public netwrk cnnectin is cnfigured with the fllwing: Static IP address Crrect netwrk mask Crrect Gateway and preferred and secndary DNS server addresses NetBIOS enabled Channel netwrk cnnectins are cnfigured with the fllwing: Static IP address in a different subnet than the principal, public netwrk with a different IP address than the secndary server channel NIC Crrect netwrk mask N Gateway IP address r DNS server address NetBIOS enabled (disabled during the installatin prcess)
4 Preparing an Orin Failver Engine Installatin Secndary Server Netwrking cmpnents n the secndary server must be cnfigured as fllws: Same number f NICs as the primary server Principal, public netwrk cnnectin cnfigured with temprary netwrk settings Channel netwrk cnnectin(s) cnfigured with the fllwing: Static IP address in a different subnet than the public netwrk with a different IP address than the primary server channel NIC. Crrect netwrk mask N Gateway r DNS IP address NetBIOS enabled (disabled during the installatin prcess) File and print sharing enabled WAN Server Architecture Optins and The netwrk and server architectures yu select affect bth hardware requirements and the technique used t clne the primary server, as fllws: If yu are using the Orin Failver Engine t prtect a physical server, yu can failver t either a physical (P2P) r virtual (P2V) If yu are using the Orin Failver Engine t prtect a virtual server, yu can nly failver t a virtual server (V2V). The fllwing server architecture ptins are supprted in bth LAN and WAN envirnments: Physical t Physical (P2P) Physical t Virtual (P2V) Virtual t Virtual (V2V) Physical t Physical (P2P) P2P architecture is used in envirnments where bth the primary and secndary servers are physical servers. Using P2P limits installatin ptins as it requires using the Install Clne technique. This architecture requires attentin t detail when preparing fr installatin as bth hardware and sftware must meet specific prerequisites. Servers in a P2P cnfiguratin must meet the fllwing hardware requirements: P2P Hardware CPU Memry The minimum CPU requirement may vary depending n the Orin mdules installed. Fr mre infrmatin, see the SlarWinds Orin Netwrk Perfrmance Mnitr Administratr Guide and the Administratr Guides fr each installed mdule. 1 GB (2 GB is recmmended) Nte: During the setup prcess, the ipmnitr verifies that a minimum f 1GB RAM is available. T ensure prper peratin, 2GB is Secndary Server Similar if nt the same as the primary server Same as the primary server
Preparing an Orin Failver Engine Installatin 5 P2P Hardware Hard Disk Space Netwrk Interface Cards recmmended in additin t any ther memry requirements fr the perating system r SlarWinds Orin mdules. The minimum hard disk space requirement may vary depending n the Orin mdules installed. Fr mre infrmatin, see the SlarWinds Orin Netwrk Perfrmance Mnitr Administratr Guide and the Administratr Guides fr each installed mdule. Nte: Drive letters must match the secndary 2 dedicated netwrk interface cards, defined as fllws: Nte: A third NIC is recmmended fr redundancy n the SlarWinds Channel between the primary and secndary servers. 1 static IP (nn-dhcp) as the public address, shared between the active and passive servers. Verify that the principal netwrk adapter is listed first in the netwrk cnnectins bind rder. 1 IP n each server, defining the SlarWinds Channel, bth f which are utside the subnet f the shared public IP. SlarWinds Channel NICs are standard 100BaseT Ethernet cards with thrughput f 100 Mbits per secnd acrss standard Cat-5 crssver cabling. In a WAN deplyment, cnfigure the SlarWinds Channel t use static rutes ver switches and ruters t maintain cntinuus cmmunicatins, independent f crprate r public traffic ACPI (Advanced Cnfiguratin The standard Orin Failver Engine implementatin prcess assumes and Pwer identical ACPI cmpliance n bth machines. Interface) Servers in a P2P cnfiguratin must als meet the fllwing sftware requirements: Secndary Server Same if nt greater than the primary Nte: Drive letters must Same as primary server ACPI cmpliance must Nte: Befre installing the Orin Failver Engine, primary and secndary servers must be in the same wrkgrup with different machine names. All date, time, and timezne settings must als be cnsistent. P2P Sftware Supprted Operating Systems Supprted SlarWinds Orin Mdules Windws Server 2003 x86 Standard r Enterprise, SP1 and SP2 Windws Server 2003 x64 Enterprise SP2 Windws Server 2008 x86 r x64, SP1 and SP2, including R2 Windws Server 2012 Nte: SlarWinds recmmends all Micrsft security updates. SlarWinds Orin NPM MP v10.0 SP1 and higher SlarWinds Orin IPAM v1.7.1 and higher SlarWinds Orin APM v3.5 and higher SlarWinds Orin APM MP v4.0.1 and higher SlarWinds Orin IPSLA Manager v3.5 and higher SlarWinds Orin NTA v3.6 and higher SlarWinds Orin NCM v6.0 and higher Nte: NCM v7.0 is supprted, but it must be updated t NCM v7.0.1 if additinal plling engines r additinal web sites are in use. SlarWinds Orin SEUM v1.0 and higher SlarWinds Orin UDT v1.0 and higher SlarWinds Orin EOC v1.2 and higher Nte: Individual Orin mdules may impse additinal requirements n the primary server that supercede the requirements prvided here. Fr mre infrmatin, see the SlarWinds Orin Netwrk Perfrmance Mnitr Administratr Guide and the Administratr Guides fr yur installed mdules. Secndary Server Same as the primary server Nte: The perating system must be installed t the same driver letter and directry Same as the primary server
6 Preparing an Orin Failver Engine Installatin Physical t Virtual (P2V) The P2V architecture is used when the envirnment requires a mix f physical and virtual machines. Servers in a P2V cnfiguratin must meet the fllwing hardware and sftware requirements Nte: The secndary virtual machine must have pririty in resurce management settings t ensure that ther virtual machines d nt impact its perfrmance. P2V Hardware CPU Memry Hard Disk Space Netwrk Interface Cards The minimum CPU requirement may vary depending n the Orin mdules installed. Fr mre infrmatin, see the SlarWinds Orin Netwrk Perfrmance Mnitr Administratr Guide and the Administratr Guides fr each installed mdule. 1 GB (2 GB is recmmended) Nte: During the setup prcess, the ipmnitr verifies that a minimum f 1GB RAM is available. T ensure prper peratin, 2GB is recmmended in additin t any ther memry requirements fr the perating system r SlarWinds Orin mdules. The minimum hard disk space requirement may vary depending n the Orin mdules installed. Fr mre infrmatin, see the SlarWinds Orin Netwrk Perfrmance Mnitr Administratr Guide and the Administratr Guides fr each installed mdule. Nte: Drive letters must match the secndary 2 dedicated netwrk interface cards, defined as fllws: Nte: A third NIC is recmmended fr redundancy n the SlarWinds Channel between the primary and secndary servers. 1 static IP (nn-dhcp) as the public address, shared between the active and passive servers. Verify that the principal netwrk adapter is listed first in the netwrk cnnectins bind rder. 1 IP n each server, defining the SlarWinds Channel, bth f which are utside the subnet f the shared public IP. SlarWinds Channel NICs are standard 100BaseT Ethernet cards with thrughput f 100 Mbits per secnd acrss standard Cat-5 crssver cabling. In a WAN deplyment, cnfigure the SlarWinds Channel t use static rutes ver switches and ruters t maintain cntinuus cmmunicatins, independent f crprate r public traffic ACPI (Advanced Cnfiguratin The standard Orin Failver Engine implementatin prcess assumes and Pwer identical ACPI cmpliance n bth machines. Interface) Servers in a P2V cnfiguratin must als meet the fllwing sftware requirements: Secndary Server Similar if nt the same as the primary server Same as the primary server Same if nt greater than the primary Nte: Drive letters must Same as primary server, but each dedicated virtual NIC must have its wn virtual switch ACPI cmpliance must Nte: Befre installing the Orin Failver Engine, primary and secndary servers must be in the same wrkgrup with different machine names. All date, time, and timezne settings must als be cnsistent. P2V Sftware Supprted Operating Systems Supprted SlarWinds Orin Mdules Windws Server 2003 x86 Standard r Enterprise, SP1 and SP2 Windws Server 2003 x64 Enterprise SP2 Windws Server 2008 x86 r x64, SP1 and SP2, including R2 Windws Server 2012 Nte: SlarWinds recmmends all Micrsft security updates. Orin Cre Services 2010.0, Orin NPM v10.0, Orin APM v3.0, Orin IPAM v1.6, Orin IPSLA Manager v3.5, Orin NTA v3.6, Orin NCM v6.0, Orin EOC v1.2 Ntes: NCM v7.0 is supprted, but it must be updated t NCM v7.0.1 if additinal plling engines r additinal web sites are in use. Individual Orin mdules may impse additinal requirements n the primary server that supercede the requirements prvided here. Fr mre infrmatin, see the Administratr Guides fr yur installed mdules. Secndary Server Same as the primary server Nte: The perating system must be installed t the same driver letter and directry Same as the primary server
Preparing an Orin Failver Engine Installatin 7 Virtual t Virtual (V2V) The V2V architecture is supprted if SlarWinds Orin is already installed n a virtual primary Servers in a V2V cnfiguratin must meet the fllwing hardware and sftware requirements Nte: The primary and secndary virtual machines must have apprpriate pririty in resurce management settings t ensure that ther virtual machines d nt impact perfrmance. Each virtual machine in the V2V pair must als be n its wn separate hst t guard against failure at the hst level. V2V Hardware CPU Memry Hard Disk Space Netwrk Interface Cards The minimum CPU requirement may vary depending n the Orin mdules installed. Fr mre infrmatin, see the SlarWinds Orin Netwrk Perfrmance Mnitr Administratr Guide and the Administratr Guides fr each installed mdule. 1 GB (2 GB is recmmended) Nte: During the setup prcess, the ipmnitr verifies that a minimum f 1GB RAM is available. T ensure prper peratin, 2GB is recmmended in additin t any ther memry requirements fr the perating system r SlarWinds Orin mdules. The minimum hard disk space requirement may vary depending n the Orin mdules installed. Fr mre infrmatin, see the SlarWinds Orin Netwrk Perfrmance Mnitr Administratr Guide and the Administratr Guides fr each installed mdule. Nte: Drive letters must match the secndary 3 dedicated virtual netwrk interface cards, each with its wn virtual switch, defined as fllws: 1 static IP (nn-dhcp) as the public address, shared between the active and passive servers. Verify that the principal netwrk adapter is listed first in the netwrk cnnectins bind rder. 2 IPs n each server, defining the SlarWinds Channel, all fur f which are utside the subnet f the shared public IP. Nte: SlarWinds Channel NICs are standard 100BaseT Ethernet cards with thrughput f 100 Mbits per secnd acrss standard Cat-5 crssver cabling. In a WAN deplyment, cnfigure the SlarWinds Channel t use static rutes ver switches and ruters t maintain cntinuus cmmunicatins, independent f crprate r public traffic ACPI (Advanced The standard Orin Failver Engine implementatin prcess assumes Cnfiguratin and identical ACPI cmpliance n bth machines. Pwer Interface) Servers in a V2V cnfiguratin must als meet the fllwing sftware requirements: Secndary Server Similar if nt the same as the primary server Same as the primary server Same if nt greater than the primary Nte: Drive letters must Same as primary server, but each dedicated virtual NIC must have its wn virtual switch ACPI cmpliance must Nte: Befre installing the Orin Failver Engine, primary and secndary servers must be in the same wrkgrup with different machine names. All date, time, and timezne settings must als be cnsistent. V2V Sftware Supprted Operating Systems Supprted SlarWinds Orin Mdules Windws Server 2003 x86 Standard r Enterprise, SP1 and SP2 Windws Server 2003 x64 Enterprise SP2 Windws Server 2008 x86 r x64, SP1 and SP2, including R2 Windws Server 2012 Nte: SlarWinds recmmends all Micrsft security updates. Orin Cre Services 2010.0, Orin NPM v10.0, Orin APM v3.0, Orin IPAM v1.6, Orin IPSLA Manager v3.5, Orin NTA v3.6, Orin NCM v6.0, Orin EOC v1.2 Ntes: NCM v7.0 is supprted, but it must be updated t NCM v7.0.1 if additinal plling engines r additinal web sites are in use. Individual Orin mdules may impse additinal requirements n the primary server that supercede the requirements prvided here. Fr mre infrmatin, see the Administratr Guides fr yur installed mdules. Secndary Server Same as the primary server Nte: The perating system must be installed t the same driver letter and directry Same as the primary server
8 Preparing an Orin Failver Engine Installatin