Технические ссылки для Cisco Cisco Transport Manager 9.1

MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES

TMF 814Av3.0

TeleManagement Forum 2003

Name: AcmeTech_3274293785
NativeEMSName:
AbcInc_9thWashAve_PittPA
UserLabel: AbcInc_3837

EMS Domain 1

Subnetwork B

EMS Domain 2

Name: AcmeTech_9393987589
NativeEMSName:
AbcInc_27SouthBroadSt_PhilaPA
UserLabel: AbcInc_3837

Name: AcmeTech_1993754343
NativeEMSName:
AbcInc_131East54thSt
UserLabel: AbcInc_3837

Subnetwork A

Subnetwork C

Link Connection
between two SNCs

Figure 4-1. SNC Naming Example 1: Non-unique UserLabels

As a second example, consider the end-to-end connection shown in Figure 4-2. The end-to-end
connection and component SNCs are the same as in the previous example, only the naming
scheme is different. In this approach, the service provider wants the EMS to ensure that unique
userLabels are used for each SNC within an EMS’s management domain. If the NMS attempts to
setup an SNC using a userLabel that has already been assigned, the EMS will reject the request.
This prevents the mistaken re-use of the SNC names selected by the service provider (this could
happen during manual entry of SNC names via the NMS GUI, for example). Related SNCs can
still be associated. However, in this case, the NativeEMSName is used to associate related
SNCs.

Name: AcmeTech_3274293785
NativeEMSName: AbcInc_3837
UserLabel:
AbcInc_9thWashAve_PittPA

EMS Domain 1

Subnetwork B

EMS Domain 2

Name: AcmeTech_9393987589
NativeEMSName: AbcInc_3837
UserLabel:
AbcInc_27SouthBroadSt_PhilaPA

Name: AcmeTech_1993754343
NativeEMSName: AbcInc_3837
UserLabel:
AbcInc_131East54thSt

Subnetwork A

Subnetwork C

Figure 4-2. SNC Naming Example 2: Unique UserLabels

In another approach, each EMS domain consists of a single subnetwork. The userLabel and
nativeEMSName of an SNC are same. Further, the component SNCs of an end-to-end
connection have the same userLabel and nativeEMSName, as shown in Figure 4-3. This