XAP 9.6 Documentation > Back to Table of Contents
How to Configure an Environment With Multiple Network-Cards (Multi-NIC)
Summary: Configuring GigaSpaces for a machine with multiple network cards. By default all network cards are used; you can limit GigaSpaces to specific ones.
OverviewGigaSpaces 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. The 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. The NIC_ADDR environment variable is exposed as part of the <GigaSpaces Root>\bin\setenv script. By default, this value is configured to use the hostname of the machine. Since the 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 setenv script.
Configuring GigaSpaces for Multiple NICs
|
![]() |
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence |