![]() |
Contents |
ISS Node - Field HelpEdit any of the following settings on the ISS Node panel and click Update Configuration. Internal net (local cell only)A machine name or Internet address (in dotted decimal notation) that specifies the network interface used for ISS internal network traffic (communications with the ISS monitor). This keyword allows you to define separate network interfaces for ISS monitor traffic and for normal service traffic. Node weight (local cell only)The Node weight is a floating-point number used in calculating the node's priority. After an aggregate load score has been calculated for each node, each of these load scores is then multiplied by the appropriate NodeWeight to determine that node's priority. Thus, a higher NodeWeight will result in a higher priority. NOTE: Setting the node weight to 0 can be used to temporarily take the node out of consideration. Monitor (local cell only)Determines whether the node is available for use as an ISS monitor. By default all nodes are available in this role, but you can choose to specify that a node cannot perform monitoring functions. ISS agent (local cell only)Determines whether the node is running an ISS agent or not. By default all nodes will be ISS agents. If you wish to configure cells that include servers that are not running ISS (for instance, if their operating system is unsupported), then you need to tell ISS that these servers will not be running an ISS agent by setting this field to "Is Not ISS Agent." If nodes in the call are "Not ISS Agents" then you can only use the ROUNDROBIN selection method. NOTE: If you designate a node as "Not ISS Agent" the ISS monitor will no longer send update information to that node. Dynamic updates will not be propogated to nodes that are not ISS agents. (Typically such nodes will not have a configuration file, as they are not running ISS, but if you want to return them to ISS Agent status, you will need to edit the configuration file manually.) Authentication key (local cell only)The authentication key that will be used by this node. It should consist of up to 40 hexadecimal characters. This field is optional. If no authentication key is specified for a cell or it's nodes, then ISS will use a key of all 0s. Authentication key is used internally for security in inter-ISS node communications. The authentication key is passed in all communications between nodes. The receiving node verifies that the received authentication key is the one expected from that node. The following information is also displayed on the ISS Node panel: Node nameThe hostname that will resolve to the correct service IP address for that node Node ID numberA unique number that identifies the node and determines its priority level for being selected as monitor. The lower the number, the higher the priority. Interface ListA list of interface addresses available on a node. A machine with multiple network interface cards and/or alias addresses can have those addresses listed here. A service can use an interface from an interface list of a node to reference a node in the nodelist of a service. All nodes always have at least one interface - the node name for the node. The interface list for a global cell is information only (not selectable), and can have only the default interface, which is the cell itself. NOTES on interfaces to nodes: You can store as many IP addresses per node as you want. This might be important if you have more than one network adapter in a node, or if you have multiple virtual IP addresses (alias addresses) configured onto a single physical network adapter. A node can have multiple interfaces, and these interfaces can be listed in the node interface list of services. However, for any given node, each interface must be in the node interface list of a different service. Or, only one interface per node can be in the node interface list of any one service. Using this mechanism, you could, for example, have three different applications running on a node. Each application is bound to, and accessed via its own interface. Each application corresponds to a service, and each service has one of the interfaces in its node interface list. Multiple such nodes could be configured, and via this configuration, you can load balance between the services of each of them. |