XAP can be configured for a multiple network-card environment. For security reasons, network administrators may choose to configure their network with limited access of one card open to outside connections, and another card for internal connections. The default network card configuration is not always set to the network card used for internal connection, and thus needs to be configured.
java.rmi.server.hostname system property is used to resolve the NIC address for all services, which bind to a specific network interface, e.g. Jini unicast discovery lookup host, Webster, etc. More specifically, multicast and unicast discovery both use this property to limit and set the desired network interface card.
NIC_ADDR environment variable is exposed as part of the
<XAP Root>\bin\setenv script. By default, this value is configured to use the hostname of the machine.
java.rmi.server.hostname system property is set by default to the
NIC_ADDR environment variable, and propagated across all product components/layers; in most cases, you don’t need to edit the
setenv file or any other configuration file.
To apply this configuration easily, the
NIC_ADDR variable can be passed at the script level of each node startup, before the call to
setenv, thus overriding the default value set for this property in the
The following procedure explains the general configuration process required to test and configure the Multi-NIC settings in XAP. Please refer to these sections only if the out-of-the-box settings fail to work.
Make sure your network and machines running XAP are configured to have multicast enabled. See the Multicast Configuration section for details on how to enable multicast.
Configuring XAP for Multiple NICs
- Viewing the network interface information (optional)
- Specifying a network card to bind the lookup service
- Limiting use to a specific network interface (multicast only) (optional)
- Using unicast to register with a lookup service (optional)
- Testing your configuration
- Troubleshooting your configuration, if you experience problems
For more details, refer to the Advanced Multi-NIC Configuration section.