How to Discover NLB Using Command Line Utility

You can discover NLB by running the nlb.exe command line utility.

This utility runs with the params key and outputs information about all NLB clusters on a discovered machine.

  • If NLB is not installed on a Windows 2003 Server machine, the output is as follows:

  • WLBS Cluster Control Utility V2.4 (c) 1997-2003 Microsoft Corporation.
    WLBS is not installed on this system or you do not have sufficient privileges to administer the cluster.
    
  • If an NLB cluster is set up on the machine, the output is as follows:

  • Cluster 192.168.0.222
    Retrieving parameters
    Current time              = 9/3/2009 1:02:38 PM
    HostName                  = ddmvm-2k3-s
    ParametersVersion         = 4
    CurrentVersion            = 00000204
    EffectiveVersion          = 00000201
    InstallDate               = 4A9E51F5
    HostPriority              = 1
    ClusterIPAddress          = 192.168.0.222
    ClusterNetworkMask        = 255.255.255.0
    DedicatedIPAddress        = 192.168.0.2
    DedicatedNetworkMask      = 255.255.255.0
    McastIPAddress            = 0.0.0.0
    ClusterName               = cluster2.domain.com
    ClusterNetworkAddress     = 03-bf-c0-a8-00-de
    IPToMACEnable             = ENABLED
    MulticastSupportEnable    = ENABLED
    IGMPSupport               = DISABLED
    MulticastARPEnable        = ENABLED
    MaskSourceMAC             = ENABLED
    AliveMsgPeriod            = 1000
    AliveMsgTolerance         = 5
    NumActions                = 100
    NumPackets                = 200
    NumAliveMsgs              = 66
    DescriptorsPerAlloc       = 512
    MaxDescriptorAllocs       = 512
    TCPConnectionTimeout      = 60
    IPSecConnectionTimeout    = 86400
    
    FilterICMP                = DISABLED
    ClusterModeOnStart        = STARTED
    HostState                 = STARTED
    PersistedStates           = NONE
    ScaleSingleClient         = DISABLED
    NBTSupportEnable          = ENABLED
    NetmonAliveMsgs           = DISABLED
    IPChangeDelay             = 60000
    ConnectionCleanupDelay    = 300000
    RemoteControlEnabled      = DISABLED
    RemoteControlUDPPort      = 2504
    RemoteControlCode         = 00000000
    RemoteMaintenanceEnabled  = 00000000
    BDATeaming                = NO
    TeamID                    =
    Master                    = NO
    ReverseHash               = NO
    IdentityHeartbeatPeriod   = 10000
    IdentityHeartbeatEnabled  = ENABLED
    PortRules (1):
          VIP       Start  End  Prot   Mode   Pri Load Affinity
    --------------- ----- ----- ---- -------- --- ---- --------
    All                 0 65535 Both Multiple      Eql Single
    

    No special rules are used for mapping the output to the CITs; all CI attributes repeat the output data names. Data is verified by comparing it to cluster nodes that have already been discovered.