Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

ON THIS PAGE

Ethernet Network Domains

 

PSM uses the concept of Ethernet network domains to support one PSM server managing more than one Ethernet network. A domain is a mechanism used to segregate network elements in diverse networks that are not interconnected, and where there is reuse of service VLAN IDs. This allows for the proper handling of reused service VLAN IDs in service visualization and activation operations.

Network elements can be added to an Ethernet domain during network element discovery. Ethernet domains are not used and do not need to be defined for optical networks.

Note

Ethernet domains are part of the replicated data set when running with multiple servers. For more information on replicated data, see Running Multiple Servers with Server Replication.

Creating an Ethernet Domain

Use this procedure to create an Ethernet domain for an Ethernet network.

During a discovery operation, if the specified domain does not already exist, it is created, and all devices discovered during that operation are added to it. Domains appear in the Ethernet branch of the network tree when Ethernet services are created.

If you do not explicitly specify a domain, all devices discovered during this operation will be assigned to the Default domain.

  1. From the main menu, choose Tools >Network Element Discovery.
  2. Enter a name for the domain in the Domain field of the Network Element Discovery window.

    The domain name is case insensitive. You must not create multiple domains where the domain names differ only in the case. For example, if you create a domain called Belfast, you must not create a new domain called belfast as this differs only in case with the existing Belfast domain name.

  3. Enter the discovery criteria.
  4. Click OK.

    The discovered network elements are added to the new domain.

    Note

    Once a new domain is created, it cannot be deleted.

    Note

    To move a network element from one domain to another, simply discover the network element again and specify the desired domain. Moving NEs between domains might cause VLAN ID conflicts. If the same VLAN ID exists in two domains and an NE with one of those VLAN IDs in one domain is moved to the other domain, the services associated with the VLAN ID on the NE being moved are no longer recognized. Conflicting VLAN IDs should be resolved before NEs are moved between domains.

Checking Domain Membership for a Network Element

Use this procedure to check what domain a network element belongs to.

  1. Hover over the network element in the Network tree.

    For example:

  2. Alternatively, hover over the network element in the Topology view.

    For example: