Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

You can configure the following Grid properties for Microsoft servers that are managed by a Grid member:

|#bookmark2623.

For more information about configuring other Grid properties for Microsoft servers, see Setting Grid Properties for Managing Microsoft Servers .








1320NIOS Administrator Guide (Rev. A)NIOS 8.1
Configuring Grid Properties for Managing Microsoft Servers

Defining Monitor and Control Settings for DNS and DHCP Services

You can enable or disable monitor and control settings of DNS and DHCP services for a specific Microsoft server. The appliance enables this by default when you add a Microsoft server. When you upgrade the existing Microsoft servers, the managed member inherits values from the Grid. You can monitor and control the DNS and DHCP services on a Microsoft service only if both the management setting of the respective service and the monitor and control settings of the corresponding Microsoft server for the selected service are enabled. To know more about how to enable monitor and control settings, see Setting Grid Properties for Managing Microsoft Servers .

Note: The original setting that controls the overall management of a given service is referred to as the management setting. It controls whether the synchronization of the corresponding service is enabled or not, with no change to the existing synchronization behavior. Note that synchronization does not depend on the value of the monitor and control setting for the Microsoft server.

You can configure Microsoft server settings at the Grid level. Note that Microsoft servers inherit these settings by default, and you can override these settings at the Microsoft server level.
When you enable monitor and control settings for DNS and DHCP services, the managing member verifies the corresponding service status on the Microsoft server every 30 seconds. The Grid Master is notified of the status through Grid replication.
When you disable monitor and control setting for DNS and DHCP services, the managing member stops verifying the service status. NIOS administrators cannot start or stop DNS or DHCP service on the Microsoft server. When you try to start or stop these services through the Infoblox API, the appliance generates an error message. The pending service control requests made before disabling the monitor and control settings are sent to the Microsoft server.
For information about the displayed status, see Viewing DNS and DHCP Service Status on Microsoft Servers on page 1337.

Output Destination for Log Messages

You can configure an output destination for Microsoft server log messages at the Grid level and override it at the Microsoft server level. You can choose to save log messages related to Microsoft synchronization in the syslog or Microsoft log. For information, see Viewing the Syslog .
When you change the setting, the Grid Master notifies the managing member about the new setting through Grid replication and sends log messages to the selected destination. The new setting takes effect for synchronization only after the managing member is notified. The synchronization, which is already in progress continues to log messages to the destination based on the old setting. To know more about how to select output destination for log messages, see Setting Grid Properties for Managing Microsoft Servers .

Maximum Simultaneous Connections for Microsoft Servers

You can specify a maximum number of simultaneous RPC connections that can be configured for the respective Microsoft server, which are managed by the Grid. You can override this value at the Microsoft server level. To know more about how to define maximum simultaneous connections for Microsoft servers, see Setting Grid Properties for Managing Microsoft Servers .

Note: When you increase the maximum number of simultaneous connections above the recommended setting for a given Microsoft server, it may consume additional bandwidth, memory, and CPU usage.












NIOS 8.1NIOS Administrator Guide (Rev. A) 1321
Managing Microsoft Windows Servers

Configuring RPC Timeout Settings

You can specify an RPC (Remote Procedure Call) timeout value to control network connectivity for Microsoft servers. You can configure an RPC timeout value at the Grid level and override it for each Microsoft server. The default value at the Grid level is ten seconds and the member inherits this value from the Grid. You can specify a value between one and 60 seconds. To know more about how to configure RPC timeout settings, see Setting Grid Properties for Managing Microsoft Servers .

Setting Grid Properties for Managing Microsoft Servers

To configure Grid properties for managing Microsoft servers, complete the following:

  1. Grid: From the Grid tab -> Grid Manager tab, expand the Toolbar and click Grid Properties -> Edit. Select Microsoft Sync Settings tab in the Grid Properties Editor wizard.

Microsoft Server: From the Grid tab -> Microsoft Servers tab -> Servers tab, select a Microsoft server and click the Edit icon, or click the Action icon next to the respective Microsoft server and select Edit from the menu. In the Microsoft server editor, click the General tab.
Standalone appliance: From the System tab -> System Manager tab, expand the Toolbar and click System Properties -> Edit.

  1. Complete the following in the Basic tab:
    • Monitor and Control Services: Select this to enable monitor and control settings for DNS and DHCP services for a specific Microsoft server. This is enabled by default. Each monitor and control setting applies only to the corresponding service and is applicable only to the respective Microsoft server. You can override the settings for each Microsoft server.
      • DNS: Select this to enable monitoring and the ability to control DNS service.
      • DHCP: Select this to enable monitoring and the ability to control DHCP service.
    • Logging output destination: From the drop-down list, select an output destination to which the appliance saves log messages for Microsoft servers. When you select Microsoft Log, the appliance logs the messages that are generated for the respective Microsoft server in the existing Microsoft log. This is selected by default. For more information, see Viewing Synchronization Logs 9. When you select Syslog, NIOS logs the messages that are generated for the respective Microsoft server in the syslog. For more information about the syslog, see Viewing the Syslog . Click Override to select an output destination to save the log messages at the member level.
  2. Optionally, select the Microsoft Server Settings tab in the Grid Properties Editor wizard and complete the following in the Advanced tab or click the Advanced tab in the General tab in a Microsoft server editor:
    • Maximum simultaneous connections: Specify a maximum number of simultaneous RPC connections that can be configured for the respective Microsoft server, which are managed by the Grid. The default is five. You can specify a value between two and 40.

You can click Override at the member level to specify a new value. The Override button changes to Inherit. Click Inherit to inherit the value from the Grid.

    • RPC timeout: Specify the RPC timeout value in seconds to control the network communication timeout. The default is ten seconds. You can specify a value between one and 60.

You can click Override at the member level to specify a new value. The Override button changes to Inherit. Click Inherit to inherit the value from the Grid.

  1. Save the configuration.












1322NIOS Administrator Guide (Rev. A)NIOS 8.1
Managing Microsoft Servers

Forwarding WINS Packets to Microsoft Servers

If your Infoblox Grid includes legacy Microsoft DNS and DHCP servers, you can configure NIOS to forward WINS packets to dedicated Microsoft servers. Infoblox provides the set wins_forwarding and show wins_forwarding CLI commands you can use to perform this task. For detailed information about these commands, refer to the Infoblox CLI Guide.
When you enable port redundancy in NIOS, the LAN1 and LAN2 ports are grouped into one logical interface. They share one IP address and appear as one interface to the network. If a link to one of the ports fails or is disabled, the appliance fails over to the other port, avoiding a service disruption. When you enable port redundancy, WINS packet forwarding is not supported on the LAN2 interface. You must use the LAN1 interface.

Note: Ensure that port 137 is not used for any services in your Grid; otherwise you will not be able to configure the appliance to forward WINS packets to Microsoft DNS and DHCP servers. Likewise, if you have enabled this feature, you will not be able to configure port 137 for any other services in your Grid.





  • No labels