Cisco Cisco Prime Optical 10.3 Références techniques
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES
Name: AcmeTech_3274293785
NativeEMSName:
AbcInc_9thWashAve_PittPA
UserLabel: AbcInc_3837
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
NativeEMSName:
AbcInc_27SouthBroadSt_PhilaPA
UserLabel: AbcInc_3837
Name: AcmeTech_1993754343
NativeEMSName:
AbcInc_131East54thSt
UserLabel: AbcInc_3837
NativeEMSName:
AbcInc_131East54thSt
UserLabel: AbcInc_3837
Subnetwork A
Subnetwork C
Link Connection
between two SNCs
between two SNCs
Figure Error! No text of specified
-1. SNC Naming Example 1: Non-unique UserLabels
style in document.
As a second example, consider the end-to-end connection shown in Figure E
. 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.
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.
Figure Error! No text of specified
-2. SNC Naming Example 2: Unique UserLabels
Name: AcmeTech_3274293785
NativeEMSName: AbcInc_3837
UserLabel:
AbcInc_9thWashAve_PittPA
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
NativeEMSName: AbcInc_3837
UserLabel:
AbcInc_27SouthBroadSt_PhilaPA
Name: AcmeTech_1993754343
NativeEMSName: AbcInc_3837
UserLabel:
AbcInc_131East54thSt
NativeEMSName: AbcInc_3837
UserLabel:
AbcInc_131East54thSt
Subnetwork A
Subnetwork C
style in document.
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 E
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 E
. This example has the
same advantages as Example 1 and also allows the NMS to request userLabel uniqueness from the EMS as in
Example 2. The main disadvantage is that the EMS domain cannot be subdivided into multiple subnetworks.
Example 2. The main disadvantage is that the EMS domain cannot be subdivided into multiple subnetworks.
TMF814Av3.1
TeleManagement Forum 2007
Page 89 of 115