Cisco Cisco Prime Optical 10.6 Technical References

Page of 115
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES  
4.6.2  Mapping to ITU-T States 
Table Error! No text of specified 
-89 ITU-T to MTNM State Mapping 
style in document.
ITU 
Operational 
State 
ITU 
Administrative 
State 
MTNM Service State  
unlocked IN_SERVICE 
locked OUT_OF_SERVICE_BY_MAINTENANCE 
enabled 
shutting down 
SERV_NA 
unlocked OUT_OF_SERVICE 
disabled 
locked OUT_OF_SERVICE_BY_MAINTENANCE 
 
4.7  Usage of Network Access Domains (NADs) 
A given NAD represents a domain to which a set of transmission network resources (e.g., PTPs, CTPs, SNCs) 
can be assigned and a given Functional Access Domain (FAD) or set of FADs). The FAD or FADs determines 
the functions which can be applied  to the NAD. A network resource can be assigned to only one NAD, or be 
unassigned (or free). In terms of the MTNM interface, the NMS may assign a NAD to a set of resources. The 
assignment of the FADs is outside the scope of the interface. This section provides an explanation of how the 
NAD/FAD concept can be used.  
The network administrator can  
a)  assign network resources to NADs (i.e. specify owners of various resources). This is done over the 
NMS-EMS interface by setting the NAD parameter (a v3.0 parameter within additionalInfo) for a set of 
resources, e.g., TPs and SNCs.   
b)  assign users (i.e., operators at NMS and EMS user interface) functional profiles (FAD) thereby allowing 
the users to perform specific functions on designated resources (as determined by the NAD previously 
assigned to the resource). One or more FADs can be associated to a given NAD. Thus according to 
type of user, different types of operations are permitted on the specific NAD. Again, management of the 
FADs is outside the scope of the MTNM interface.  
A given resource with its NetworkAccessDomain parameter set to the empty string is intended to be a “free” 
resource, i.e., any users can request only MTNM operation on the resource. A given FAD can be defined to 
permit or refuse access to “free” resources. 
Example use of NADs and FADs:   
•  some resources are marked for the  NetworkAccessDomain = ”owner23” 
•  user44 is defined by the network administrator at the EMS to be associated with FAD = “readonly” and 
to be given access to the “owner23” NAD. So, on the EMS side, “user44” is granted readonly access to 
the TPs and SNCs belonging to NAD = “owner23”. 
As another example, it is noted that the NAD/FAD mechanism can be used to define VPNs. In fact, a given VPN 
could be seen as NAD, where the VPN operator can create/activate, and deactivate/delete SNCs using only the 
routing resources belonging to such NAD/VPN (e.g., the NMS could include the NAD identifier in the 
additionalCreationInfo parameter of the createAndActivateSNC operation). At the EMS level, an SNC can be 
TMF814Av3.1 
TeleManagement Forum 2007 
Page  95 of 115