This Knowledgebase article provides information on how to configure a management IP address in a Neverfail Heartbeat environment.
The management IP address for each server should be set up on a network card that is physically connected to the Principal (Public) network. This may be on the Principal (Public) network card itself or an additional network card when present. The management IP address should be a unique static IP address in a different subnet from the hosting server’s Principal (Public) address and should be unique to each server.
When configuring Neverfail
for use with Microsoft Exchange, it is important to remember that Microsoft
Exchange servers frequently use reverse DNS lookup for authenticating
the origin of email. Since Microsoft Exchange inserts the first IP address
of the sending server into the header of an SMTP packet, reverse DNS
lookup may check against the management IP address, consequently failing
to validate the address and inadvertently marking the email as spam.
As a result, management IP addressing should not be used when Microsoft
Exchange is installed.
For Microsoft Exchange servers, see Knowledgebase Article #491 — Neverfail for Exchange is not supported with WINS registration using management IP addresses in a WAN environment .
|NOTE:||If configuring a management IP address for use on a Neverfail for BlackBerry Enterprise server installation, port 3101 must be open for access to RIM. Failure to open port 3101 will prevent the BlackBerry Enterprise Server from properly communicating with RIM. If port 3101 cannot be opened, a management IP address should not be used.|
On Windows 2003, to allow the server to route successfully through the management address, it must be the first address specified on the card with all other Principal (Public) addresses acting as secondary addresses.
If the management address will be configured on an additional network card, Neverfail Packet Filter Driver should not be enabled on this card to allow it to communicate over the network.
To configure a management address on the Principal (Public) network card itself:
- Open Network Connections .
- Right-click the required Principal (\Public) network connection and click on Properties .
- Under the TCP/IP protocol, click Properties .
- The first IP address of the NIC is displayed.
- Note the first IP address and then adjust the first IP address of the card to the management IP address.
To add the Principal (Public) IP address (old first address) back
in as a secondary address, click the
NOTE: For Windows 2008, the order of addresses is unimportant.
- Specify the Principal (Public) address and clear the Register this connection in DNS check box from the DNS tab.
- Static DNS entries must now be added to the DNS server in order to maintain connectivity, as this was previously carried out dynamically. Please consult appropriate Microsoft documentation on how to Add Static Host and PTR records as required.
From a command prompt, run c:>route print to verify the main
Principal (Public) IP address does not appear in the
- only the MANAGEMENT address, addresses on other NICs, and 127.0.0.1 should
appear in this column.
NOTE: Normal TCP/IP troubleshooting commands can be used to verify connectivity, for example,