Understanding how lim determines host models and types

The lim (load information manager) daemon/service automatically collects information about hosts in an EGO cluster, and accurately determines running host models and types. At most, 1024 model types can be manually defined in ego.shared:

  • Windows: %EGO_CONFDIR%\ego.shared

  • Linux/UNIX: $EGO_CONFDIR/ego.shared

If ego.shared is not fully defined with all known host models and types found in the EGO cluster, the lim attempts to match an unrecognized running host to one of the models and types that is defined.

The lim supports both exact matching of host models and types, and "fuzzy" matching (where an entered host model name or type is slightly different from what is defined in ego.conf).

How does "fuzzy" matching work?

The lim reads host models and types that have been manually configured in ego.shared. The format for entering host models and types in ego.shared is model_bogomips_architecture (for example, x15_4604_OpterontmProcessor142, IA64_2793, or SUNWUltra510_360_sparc). Names can be up to 64 characters long.

When the lim attempts to match running host model with what’s entered in ego.shared, it first attempts an exact match, then proceeds to make a fuzzy match. Here is a summary on how the lim attempts to make matches, depending on given information:

Architecture name of running host

What the lim reports

Additional information about the lim process

Same as definition in ego.shared (exact match)

Reports the reference index of exact match

The lim detects an exact match between model and input architecture string

Similar to what is defined in ego.shared (fuzzy match)

Reports fuzzy match based on detection of 1or 2 fields in the input architecture string

  • For input architecture strings with only one field:

    If the lim cannot detect an exact match for the input string, then the lim reports the best match; a "best match" is defined as a model field with the most characters shared by the input string

  • For input architecture strings with two fields:

    1. If the lim cannot detect an exact match, it attempts to find a best match by identifying the model field with the most characters that match the input string

    2. The lim then attempts to find the best match on the bogomips field

  • For architecture strings with three fields:

    1. If the lim cannot detect an exact match, it attempts to find a best match by identifying the model field with the most characters that match the input string

    2. After finding the best match for the model field, the lim attempts to find the best match on the architecture field

    3. The lim then attempts to find the closest match on the bogomips field, with wildcards supported (where the bogomips field is a wildcard)

Has an illegal name

Reports default host model

An illegal name is one that does not follow the permitted format for entering an architecture string where the first character of the string is not an English-language character.

Related tasks
Fix UNKNOWN or DEFAULT Matched Models and Matched Types