Cisco Cisco Prime Optical 9.8 テクニカルリファレンス
TM FORUM Implementation Statement (IS) Template and Guidelines
4.3 Usage of the Various Resource Names
The MTNM interface allows several identifiers to be assigned to a managed resource, i.e., name, userLabel,
and nativeEMSName.
and nativeEMSName.
• The name is assigned by the EMS and it is the unique identifier of resource to be used across the
NMS-EMS interface. The NMS has no control over a resource’s name.
• The userLabel is typically assigned by the NMS via the setUserLabel operation or a create operation
for resources that can be created by an NMS request, e.g., SNCs. If a resource is created by the EMS
(actually the interface object representing a resource), then the EMS sets the userLabel to the
nativeEMSName.
(actually the interface object representing a resource), then the EMS sets the userLabel to the
nativeEMSName.
o Further, the createSNC, createAndActivateSNC, checkValidSNC, and setUserLabel operations
accept a parameter that allows the NMS to request that the EMS check the supplied userLabel
for uniqueness. If the supplied userLabel is not unique, the request is rejected.
for uniqueness. If the supplied userLabel is not unique, the request is rejected.
• If the NMS fails, the EMS GUI could be used to create connections crossing multiple subnetworks. After
it has recovered, the NMS could discover the SNC associations by looking at the userLabels of the
newly created SNCs.
newly created SNCs.
• The nativeEMSName was originally intended to be the name of a resource as shown on an EMS
display. This usage is not mandatory and other uses are possible. The nativeEMSName can be set by
the EMS (typically through the EMS GUI) or it can be set by the NMS (if allowed by the EMS vendor)
using the setNativeEMSName operation.
the EMS (typically through the EMS GUI) or it can be set by the NMS (if allowed by the EMS vendor)
using the setNativeEMSName operation.
As an example use of the three resource names, consider the end-to-end connection shown in Figure E
(as represented by the solid horizontal line). In this example, SNC
AbcInc_3837 crosses three subnetworks, two of which are in one EMS domain (i.e., Subnetworks A and B are
in EMS Domain 1) and the other subnetwork (i.e., C) is in another EMS domain (i.e., Domain 2). The EMS uses
the Name attribute to uniquely identify an SNC within its domain (this is always true for EMSs that follow the
MTNM interface specifications). The network provider uses the NativeEMSName to store its identifier for an
SNC. The NativeEMSName can be assigned via the EMS GUI or through the setNativeEMSName operations.
The service provider uses the userLabel to associate the three SNCs that comprise the end-to-end connection.
In this case, the NMS does not want to force uniqueness of the userLabel. Of course, the NMS could use its
own internal mechanism to associate connections that cross several subnetworks. The advantages of using the
userLabel in this case are as follows:
in EMS Domain 1) and the other subnetwork (i.e., C) is in another EMS domain (i.e., Domain 2). The EMS uses
the Name attribute to uniquely identify an SNC within its domain (this is always true for EMSs that follow the
MTNM interface specifications). The network provider uses the NativeEMSName to store its identifier for an
SNC. The NativeEMSName can be assigned via the EMS GUI or through the setNativeEMSName operations.
The service provider uses the userLabel to associate the three SNCs that comprise the end-to-end connection.
In this case, the NMS does not want to force uniqueness of the userLabel. Of course, the NMS could use its
own internal mechanism to associate connections that cross several subnetworks. The advantages of using the
userLabel in this case are as follows:
• If the NMS fails, the EMS user can still determine the association among related SNCs in different
subnetworks (the EMS GUI would need to have appropriate search functions). If the connection
crosses multiple EMS domains, correlation becomes more complicated and is likely to require more
analysis on the part of the EMS user.
crosses multiple EMS domains, correlation becomes more complicated and is likely to require more
analysis on the part of the EMS user.
Page 88 of 115
TeleManagement Forum 2007
TMF814Av3.1