Administer > Connect multiple NNMi Management Servers (NNMi Advanced) > About Multi-Tenancy and Global Network Management > Troubleshooting Tenants in Global Network Management

Troubleshooting Tenants in Global Network Management

You need to understand how NNMi determines the Tenant and Security Group setting per replicated Node. For more information, see About Multi-Tenancy and Global Network Management.

The following scenarios explain the results of a potential series of changes when Tenant Best Practices for Global Network Management was not followed:

  1. The first time the Regional Manager forwards information about discovery and monitoring results to the Global Manager. ClosedClick here for details.

    When a Regional Manager's Nodes are assigned to a custom Tenant (other than Default) and those Nodes are replicated to the Global Manager, if the Global Manager's database does not contain a Tenant object with the same UUID:

    • The Global Manager creates a new Tenant object with the same UUID and Name.
    • The Global Manager automatically creates a new Security Group with the same Name as the Tenant. This happens whether a Security Group by that name already exists (the duplicate has a unique UUID).
    Node Attribute Original Node's Attribute Value on NNMi's Regional Manager Replicated Node's Attribute Value on NNMi's Global Manager
    Tenant

    UUID: uniqueTenant#one

    Name: MyCustomer

    → Same UUID as Regional Setting.

    → Same Name as Regional Setting.
    Security Group

    UUID: uniqueSecurityGrp#one

    Name: Tier1Support

    NNMi creates a new Security Group with same Name as the Regional Manager's custom Tenant name. All other attributes of this Security Group have no relation to the Regional Manager's Tenant object.

    UUID: uniqueSecurityGrp#two

    Name: MyCustomer
  2. Regional Manager's NNMi administrator changes the name of the MyCustomer Tenant object. ClosedClick here for details.

    Changes to the NNMi Regional Manager's Tenant Name or Description are not replicated to the NNMi Global Manager. (No change on the Global Manager.)

    Previously Replicated Node
    Node Attribute Original Node's Attribute Value on NNMi's Regional Manager Replicated Node's Attribute Value on NNMi's Global Manager
    Tenant

    UUID: uniqueTenant#one

    Name: MyNewestCustomer

    → Same UUID as Regional Setting.

    Name: MyCustomer (name NNMi established during initial replication cycle, see 1).
    Security Group

    UUID: uniqueSecurityGrp#one

    Name: Tier1Support

    UUID: uniqueSecurityGrp#two

    Name: MyCustomer
    Newly Replicated Nodes
    Node Attribute Original Node's Attribute Value on NNMi's Regional Manager Replicated Node's Attribute Value on NNMi's Global Manager
    Tenant

    UUID: uniqueTenant#one

    Name: MyNewestCustomer

    → Same UUID as Regional Setting.

    Name: MyCustomer (name NNMi established during initial replication cycle, see 1).
    Security Group

    UUID: uniqueSecurityGrp#one

    Name: Tier1Support

    UUID: uniqueSecurityGrp#two

    Name: MyCustomer
  3. Global Manager's NNMi administrator changes the assigned Security Group for a specific Replicated Node. ClosedClick here for details.

    (No change on the Regional Manager.)

    Node Attribute Original Node's Attribute Value on NNMi's Regional Manager Replicated Node's Attribute Value on NNMi's Global Manager
    Tenant

    UUID: uniqueTenant#one

    Name: MyNewestCustomer

    → Same UUID as Regional Setting.

    Name: MyCustomer (name NNMi established during initial replication cycle, see 1).
    Security Group

    UUID: uniqueSecurityGrp#one

    Name: Tier1Support

    UUID: uniqueSecurityGrp#seven

    Name: Region1Security
  4. Regional Manager's NNMi administrator changes the assigned Security Group for a specific Node. ClosedClick here for details.

    (No change on the Global Manager.)

    Node Attribute Original Node's Attribute Value on NNMi's Regional Manager Replicated Node's Attribute Value on NNMi's Global Manager
    Tenant

    UUID: uniqueTenant#one

    Name: MyNewestCustomer

    → Same UUID as Regional Setting.

    Name: MyCustomer (name NNMi established during initial replication cycle, see 1).
    Security Group

    UUID: uniqueSecurityGrp#four

    Name: Building4

    UUID: uniqueSecurityGrp#seven

    Name: Region1Security
  5. Global Manager's NNMi administrator changes the MyCustomer Tenant object's definition to have a different Initial Discovery Security Group: RockyMountRegion. ClosedClick here for details.

    Any Nodes replicated for the first time have Security Group set to the new Initial Discovery Security Group attribute value: RockyMountRegion.

    Newly Replicated Nodes
    Node Attribute Original Node's Attribute Value on NNMi's Regional Manager Replicated Node's Attribute Value on NNMi's Global Manager
    Tenant

    UUID: uniqueTenant#one

    Name: MyNewestCustomer

    → Same UUID as Regional Setting.

    Name: MyCustomer (name NNMi established during initial replication cycle, see 1).
    Security Group

    UUID: uniqueSecurityGrp#four

    Name: Building4

    UUID: uniqueSecurityGrp#ten

    Name: RockyMountRegion

    All previously replicated Node's Security Group settings remain unchanged (unless manually changed). NNMi does not change any Node settings when the Tenant object's Initial Discovery Security Group attribute value changes.

    Previously Replicated Node
    Node Attribute Original Node's Attribute Value on NNMi's Regional Manager Replicated Node's Attribute Value on NNMi's Global Manager
    Tenant

    UUID: uniqueTenant#one

    Name: MyNewestCustomer

    → Same UUID as Regional Setting.

    Name: MyCustomer (name NNMi established during initial replication cycle, see 1).
    Security Group

    UUID: uniqueSecurityGrp#four

    Name: Building4

    UUID: uniqueSecurityGrp#seven

    Name: Region1Security

Send Help Center feedback