03.developer Guide (Performance)
03.developer Guide (Performance)
System
V200R015C50
Issue 02
Date 2015-08-15
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: [email protected]
Related Versions
The following table lists the product versions related to this document.
Intended Audience
Focusing on the performance management of the XML NBI (northbound interface), this
document describes the secondary development of the NBI from the aspects as follows: basic
information, interface function, interface model, object attributes, notification format and sample
message.
This document provides the reference information about the performance management of the
XML NBI.
l Application Developer
l Data Configuration Engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Contents
3 Interface Model..............................................................................................................................9
3.1 PerformanceManagementRetrieval............................................................................................................... ...............10
3.1.1 getAllCurrentPerformanceMonitoringData...............................................................................................................10
3.1.2 getHistoryPerformanceMonitoringData.................................................................................... ................................11
3.1.3 getAllPerformanceMonitoringPoints............................................................................................ .............................12
3.1.4 getPfmInstanceByResource.......................................................................................................................................12
3.2 PerformanceManagementControl............................................................................................. ....................................13
3.2.1 createPerformanceMonitoringData............................................................................................................... .............13
3.2.2 deletePerformanceMonitoringData............................................................................................................................14
3.2.3 disablePerformanceMonitoringData....................................................................................... ...................................15
3.2.4 enablePerformanceMonitoringData...........................................................................................................................16
3.3 ThresholdCrossingAlertControl............................................................................................ .......................................17
3.3.1 setTcaTpParameter...................................................................................................... ..............................................17
3.3.2 getTcaTpParameter....................................................................................................................................................18
4 Object Attributes.........................................................................................................................20
4.1 PerformanceManagementRetrieval........................................................................................... ...................................21
4.1.1 PerformanceMonitoringObjectSelectType........................................................................................ ........................21
4.1.2 PerformanceMonitoringObjectSelectListType..........................................................................................................23
4.1.3 PerformanceMonitoringParameterNameListType....................................................................................................23
4.1.4 PerformanceMonitoringMeasurementType...............................................................................................................23
4.1.5 PerformanceMonitoringMeasurementListType........................................................................................................24
4.1.6 PerformanceMonitoringDataType.......................................................................................... ...................................24
6 Sample Message...........................................................................................................................48
1 Overview
Unless otherwise specified, the XML NBI described in this document refers to the standardized
NBI that complies with the MTOSI 2.0 standard.
1.1 Introduction
1.2 Introduction to Performance Function
1.1 Introduction
Compliant with MTOSI 2.0 standards, the XML northbound interface (NBI) have functions of
querying the current and historical performance data, and performance threshold-crossing alert
events. This document mainly describes the XML interfaces that are already realized to help
OSS developers and technical support engineers to better understand the functions of the
interfaces.
Querying the current Querying the current PTN and transport domains
performance data performance by monitoring
conditions and parameter
names
A message exchange pattern (MEP) is a template that establishes a pattern for the mapping and
exchange of messages between SOAP (short for simple object access protocol) nodes.
2.2 SIT
Synchronous iterator pattern (SIT) is a message exchange pattern in which the response
information of a request is returned in an iterative way.
2.3 SIT-ITERATOR
Synchronous iterator pattern - iterator (SIT-ITERATOR) is a message exchange pattern similar
to SIT. When the sequence number of a request packet is greater than one, SIT is called SIT-
ITERATOR.
2.4 AFB
Asynchronous file bulk (AFB) is a message exchange pattern in which the response information
of a request is exported as files.
2.1 SRR
Synchronous request response (SRR) is a message exchange pattern in which all response
information is returned at a time for each request.
2.2 SIT
Synchronous iterator pattern (SIT) is a message exchange pattern in which the response
information of a request is returned in an iterative way.
2.3 SIT-ITERATOR
Synchronous iterator pattern - iterator (SIT-ITERATOR) is a message exchange pattern similar
to SIT. When the sequence number of a request packet is greater than one, SIT is called SIT-
ITERATOR.
2.4 AFB
Asynchronous file bulk (AFB) is a message exchange pattern in which the response information
of a request is exported as files.
3 Interface Model
3.1 PerformanceManagementRetrieval
This interface is used to query current performances, historicalperformance data, and
performance instances.
3.2 PerformanceManagementControl
This interface is used to manage performance instances.
3.3 ThresholdCrossingAlertControl
This object is used to specify the performance threshold query and setting operations.
3.1 PerformanceManagementRetrieval
This interface is used to query current performances, historicalperformance data, and
performance instances.
3.1.1 getAllCurrentPerformanceMonitoringData
This interface is used to query all current performancedata.
Definition
MultiplePerformanceMonitoringDataObjectsResponseType
getAllCurrentPerformanceMonitoringData (Holder<Header> mtopHeader,
getAllCurrentPerformanceMonitoringDataRequest mtopBody) throws
GetAllCurrentPerformanceMonitoringDataException
Function
Query the current performance data according to the specified monitoring condition and
parameter names.
Parameters
Parameter Description Value Remarks
Returned Values
Returned Value Type Description Remarks
Restrictions
Concurrency interface call is not more than four.
3.1.2 getHistoryPerformanceMonitoringData
This interface is used to query historical performance data.
Definition
MultiplePerformanceMonitoringDataObjectsResponseType
getHistoryPerformanceMonitoringData (Holder<Header> mtopHeader,
getHistoryPerformanceMonitoringDataRequest mtopBody) throws
GetHistoryPerformanceMonitoringDataException
Function
Query the historical performance data according to the specified monitoring condition and
parameter names.
Parameters
Parameter Description Value Remarks
Returned Values
Returned Value Type Description Remarks
Restrictions
The query of historical RMON performance data in the 30s period is not supported.
3.1.3 getAllPerformanceMonitoringPoints
This interface is used to query performance monitoring points.
Definition
MultiplePerformanceMonitoringPointObjectsResponseType
getAllPerformanceMonitoringPoints(Holder<Header> mtopHeader,
GetAllPerformanceMonitoringPointsRequest mtopBody) throws
GetAllPerformanceMonitoringPointsException
Function
Query performance monitoring points.
Parameters
Parameter Description Value Remarks
Returned Values
Returned Value Type Description Remarks
Restrictions
3.1.4 getPfmInstanceByResource
This interface is used to query information about performance monitoring instances.
Definition
GetPfmInstanceByResourceResponse getPfmInstanceByResource
(Holder<Header> mtopHeader, GetPfmInstanceByResourceRequest
mtopBody) throws GetPfmInstanceByResourceException
Function
Query information about performance monitoring instances based on the performance
monitoring instance index.
Parameters
Parameter Description Value Remarks
Returned Values
Returned Value Type Description Remarks
Restrictions
There is no restriction.
3.2 PerformanceManagementControl
This interface is used to manage performance instances.
3.2.1 createPerformanceMonitoringData
This interface is used to create a performance monitoring instance.
Definition
CreatePerformanceMonitoringDataResponse createPerformanceMonitoringData
(Holder<Header> mtopHeader, CreatePerformanceMonitoringDataRequest
mtopBody) throws CreatePerformanceMonitoringDataException
Function
Create a performance monitoring instance.
Parameters
Parameter Description Value Remarks
Returned Values
Returned Value Type Description Remarks
Restrictions
To create a performance instance, a non-admin user must be added to the operator group.
Currently, the supported interfaces are as follows: Atm (2049), Eth-Trunk (65539),
GigabitEthernet (1025) and subinterfaces, Vlanif (65544), Pos (2049), Ip-Trunk (65540) and
Rpr (65546).
3.2.2 deletePerformanceMonitoringData
This interface is used to delete a performance monitoring instance.
Definition
DeletePerformanceMonitoringDataResponse deletePerformanceMonitoringData
(Holder<Header> mtopHeader, DeletePerformanceMonitoringDataRequest
mtopBody) throws DeletePerformanceMonitoringDataException
Function
Delete a performance monitoring instance.
Parameters
Parameter Description Value Remarks
Returned Values
Returned Value Type Description Remarks
Restrictions
There is no restriction.
3.2.3 disablePerformanceMonitoringData
This interface is used to suspend a performance monitoring instance or disable performance
monitoring.
Definition
DisablePerformanceMonitoringDataResponse
disablePerformanceMonitoringData (Holder<Header> mtopHeader,
DisablePerformanceMonitoringDataRequest mtopBody) throws
DisablePerformanceMonitoringDataException
Function
Suspend a performance monitoring instance or disable performance monitoring.
Parameters
Parameter Description Value Remarks
Returned Values
Returned Value Type Description Remarks
Restrictions
There is no restriction.
3.2.4 enablePerformanceMonitoringData
This interface is used to enable a performance monitoring instance or enable performance
monitoring.
Definition
EnablePerformanceMonitoringDataResponse enablePerformanceMonitoringData
(Holder<Header> mtopHeader, EnablePerformanceMonitoringDataRequest
mtopBody) throws EnablePerformanceMonitoringDataException
Function
Enable a performance instance or enable performance monitoring.
Parameters
Parameter Description Value Remarks
Returned Values
Returned Value Type Description Remarks
Restrictions
There is no restriction.
3.3 ThresholdCrossingAlertControl
This object is used to specify the performance threshold query and setting operations.
3.3.1 setTcaTpParameter
This interface is used to set performance thresholds.
Definition
SetTcaTpParameterResponse setTcaTpParameter(Holder<Header> mtopHeader,
SetTcaTpParameterRequest mtopBody) throws SetTcaTpParameterException
Function
Set performance thresholds.
Parameters
Parameter Description Value Remarks
Returned Values
Returned Value Type Description Remarks
Restrictions
3.3.2 getTcaTpParameter
This interface is used to query performance thresholds.
Definition
GetTcaTpParameterResponse getTcaTpParameter(Holder<Header> mtopHeader,
GetTcaTpParameterRequest mtopBody) throws GetTcaTpParameterException
Function
Query performance thresholds.
Parameters
Parameter Description Value Remarks
Returned Values
Returned Value Type Description Remarks
Restrictions
4 Object Attributes
4.1 PerformanceManagementRetrieval
This interface is used to query performance data, including current performance data and
historical performance data.
4.2 PerformanceManagementControl
This interface is used to manage performances.
4.3 ThresholdCrossingAlertControl
This interface is used to query and set performance thresholds.
4.1 PerformanceManagementRetrieval
This interface is used to query performance data, including current performance data and
historical performance data.
4.1.1 PerformanceMonitoringObjectSelectType
This topic describes the data structure of the PerformanceMonitoringObjectSelectTypeobject.
The classpath information is as follows:
org.tmforum.mtop.nra.xsd.pmtgt.v1.PerformanceMonitoringObjectSelectType
4.1.2 PerformanceMonitoringObjectSelectListType
This topic describes the data structure of the PerformanceMonitoringObjectSelectListType
object. The classpath information is as follows:
org.tmforum.mtop.nra.xsd.pmtgt.v1.PerformanceMonitoringObjectSelectListType
4.1.3 PerformanceMonitoringParameterNameListType
This topic describes the data structure of the PerformanceMonitoringParameterNameListType
object. The classpath information is as follows:
org.tmforum.mtop.nra.xsd.pm.v1.PerformanceMonitoringParameterNameListType
4.1.4 PerformanceMonitoringMeasurementType
This topic describes the data structure of the PerformanceMonitoringMeasurementTypeobject.
The classpath information is as follows:
org.tmforum.mtop.nra.xsd.pmmsrt.v1.PerformanceMonitoringMeasurementType
4.1.5 PerformanceMonitoringMeasurementListType
This topic describes the data structure of the PerformanceMonitoringMeasurementListType
object. The classpath information is as follows:
org.tmforum.mtop.nra.xsd.pmmsrt.v1.PerformanceMonitoringParameterNameListType
4.1.6 PerformanceMonitoringDataType
This topic describes the data structure of the PerformanceMonitoringDataTypeobject. The
classpath information is as follows:
org.tmforum.mtop.nra.xsd.pmdata.v1.PerformanceMonitoringDataType
4.1.7 PerformanceMonitoringDataListType
This topic describes the data structure of the PerformanceMonitoringDataListType object. The
classpath information is as
follows:org.tmforum.mtop.nra.xsd.pmdata.v1.PerformanceMonitoringDataListType
4.1.8 GetAllCurrentPerformanceMonitoringDataRequest
This topic describes the data structure of the GetAllCurrentPerformanceMonitoringDataRequest
object. The classpath information is as follows:
org.tmforum.mtop.rpm.xsd.pmr.v1.GetAllCurrentPerformanceMonitoringDataRequest
4.1.9 MultiplePerformanceMonitoringDataObjectsResponseType
This topic describes the data structure ofthe
MultiplePerformanceMonitoringDataObjectsResponseType object. The classpath information
is as follows:
org.tmforum.mtop.rpm.xsd.pmr.v1.MultiplePerformanceMonitoringDataObjectsResponseTyp
e
4.1.10 GetHistoryPerformanceMonitoringDataRequest
This topic describes the data structure of the GetHistoryPerformanceMonitoringDataRequest
object. The classpath information is as follows:
org.tmforum.mtop.rpm.xsd.pmr.v1.GetHistoryPerformanceMonitoringDataRequest
4.1.11 PerformanceMonitoringThresholdType
This topic describes the data structure of the PerformanceMonitoringThresholdTypeobject. The
classpath information is as follows:
org.tmforum.mtop.nra.xsd.pmth.v1.PerformanceMonitoringThresholdType
4.1.12 ThresholdCrossingAlertType
This topic describes the data structure of the ThresholdCrossingAlertTypeobject. The classpath
information is as follows: org.tmforum.mtop.nra.xsd.tca.v1.ThresholdCrossingAlertType
4.1.13 ThresholdCrossingAlertListType
This object is used to specify the list of threshold-crossing alerts. The classpath information is
as follows: org.tmforum.mtop.nra.xsd.pmmsrt.v1.ThresholdCrossingAlertListType
4.1.14 GetPfmInstanceByResourceRequest
This topic describes the data structure of the GetPfmInstanceByResourceRequestobject. The
classpath information is as follows:
org.tmforum.mtop.rpm.xsd.pmr.v1.GetPfmInstanceByResourceRequest
4.1.15 GetPfmInstanceByResourceResponse
This topic describes the data structure ofthe GetPfmInstanceByResourceResponse object. The
classpath information is as follows:
org.tmforum.mtop.rpm.xsd.pmr.v1.GetPfmInstanceByResourceResponse
4.1.16 PerformanceMonitoringInstanceListType
This topic describes the data structure ofthe PerformanceMonitoringInstanceListType object.
The classpath information is as follows:
org.tmforum.mtop.nra.xsd.pmtgt.v1.PerformanceMonitoringInstanceListType
4.1.17 PerformanceMonitoringInstanceType
This object is used to specify the type of a performancemonitoring instance. The classpath
information is as follows:
org.tmforum.mtop.nra.xsd.pmtgt.v1.PerformanceMonitoringInstanceType
4.1.18 PmMonitorConditioningType
This topic describes the data structure of the PmMonitorConditioningType object. The classpath
information is as follows: org.tmforum.mtop.nra.xsd.pmtgt.v1.PmMonitorConditioningType
4.1.19 GetAllPerformanceMonitoringPointsRequest
This object is used to specify the request for querying performance monitoring points.
The classpath information is as follows:
org.tmforum.mtop.rpm.xsd.pmr.v1.GetAllPerformanceMonitoringPointsRequest
4.1.20 ActivityStatusEnumType
This topic describes the data structure of the ActivityStatusEnumTypeobject. The classpath
information is as follows: org.tmforum.mtop.nra.xsd.pm.v1.ActivityStatusEnumType
4.1.21 InstanceEnumType
This topic describes the data structure ofthe InstanceEnumType object. The classpath
information is as follows: org.tmforum.mtop.nra.xsd.pm.v1.InstanceEnumType
4.1.22
MultiplePerformanceMonitoringPointObjectsResponseType
This object is used to specify the response to the query of performance monitoring points. The
4.1.23 PerformanceMonitoringPointListType
This object is used to specify the list of performance monitoring points.
org.tmforum.mtop.nra.xsd.pmp.v1.PerformanceMonitoringPointListType
4.1.24 PerformanceMonitoringPointType
This object is used to specify performance monitoring point information.
org.tmforum.mtop.nra.xsd.pmp.v1.PerformanceMonitoringPointType
4.2 PerformanceManagementControl
This interface is used to manage performances.
4.2.1 CreatePerformanceMonitoringDataRequest
This topic describes the data structure ofthe CreatePerformanceMonitoringDataRequest object.
The classpath information is as follows:
org.tmforum.mtop.rpm.xsd.pmc.v1.CreatePerformanceMonitoringDataRequest
4.2.2 CreatePerformanceMonitoringDataResponse
This topic describes the data structure of the CreatePerformanceMonitoringDataResponse
object. The classpath information is as follows:
org.tmforum.mtop.rpm.xsd.pmc.v1.CreatePerformanceMonitoringDataResponse
4.2.3 PerformanceCreateInstanceType
This topic describes the data structure of the PerformanceCreateInstanceType object. The
classpath information is as follows:
org.tmforum.mtop.nra.xsd.pmtgt.v1.PerformanceCreateInstanceType
4.2.4 PerformanceCreateResourceType
This topic describes the data structure ofthe PerformanceCreateResourceType object. The
classpath information is as follows:
org.tmforum.mtop.nra.xsd.pmtgt.v1.PerformanceCreateResourceType
4.2.5 PerformanceTemplateType
This topic describes the data structure of the PerformanceTemplateType object. The classpath
information is as follows: org.tmforum.mtop.nra.xsd.pmtgt.v1.PerformanceTemplateType
4.2.6 DeletePerformanceMonitoringDataRequest
This topic describes the data structure of the DeletePerformanceMonitoringDataRequest object.
The classpath information is as follows:
org.tmforum.mtop.rpm.xsd.pmc.v1.DeletePerformanceMonitoringDataRequest
4.2.7 DeletePerformanceMonitoringDataResponse
This topic describes the data structure of the DeletePerformanceMonitoringDataResponse
object. The classpath information is as follows:
org.tmforum.mtop.rpm.xsd.pmc.v1.DeletePerformanceMonitoringDataResponse
4.2.8 DisablePerformanceMonitoringDataRequest
This topic describes the data structureof the DisablePerformanceMonitoringDataRequest object
or the request for disabling performance monitoring for OTN ports.
4.2.9 DisablePerformanceMonitoringDataResponse
This topic describes the data structure of the DisablePerformanceMonitoringDataResponse
object or the response to the disabling of performance monitoring for OTN ports.
4.2.10 EnablePerformanceMonitoringDataRequest
This topic describes the data structure of the EnablePerformanceMonitoringDataRequest object
or the request for enabling performance monitoring for OTN ports.
4.2.11 EnablePerformanceMonitoringDataResponse
This topic describes the data structure of the EnablePerformanceMonitoringDataResponse
object or the response to the enabling of performance monitoring for OTN ports.
The classpath information is as follows:
org.tmforum.mtop.rpm.xsd.pmc.v1.EnablePerformanceMonitoringDataResponse
4.3 ThresholdCrossingAlertControl
This interface is used to query and set performance thresholds.
4.3.1 SetTcaTpParameterRequest
This object is used to specify the request for setting OTN port performance thresholds.
The classpath information is as follows:
org.tmforum.mtop.rpm.xsd.tcac.v1.SetTcaTpParameterRequest
4.3.2 SetTcaTpParameterResponse
This object is used to specify the response to OTN port performance threshold setting.
The classpath information is as follows:
org.tmforum.mtop.rpm.xsd.tcac.v1.SetTcaTpParameterResponse
4.3.3 GetTcaTpParameterRequest
This object is used to specify the request for querying performance thresholds of OTN ports.
org.tmforum.mtop.rpm.xsd.tcac.v1.GetTcaTpParameterRequest
4.3.4 ThresholdCrossingAlertParametersType
This object is used to specify performance threshold parameters. The classpath
information is as follows:
org.tmforum.mtop.nra.xsd.tcapars.v1.ThresholdCrossingAlertParametersType
4.3.5 GetTcaTpParameterResponse
This object is used to specify the response to performance threshold queries.
The classpath information is as follows:
org.tmforum.mtop.rpm.xsd.tcac.v1.GetTcaTpParameterResponse
4.3.6 PerformanceMonitoringThresholdValueListType
This object is used to specify the performance threshold list. The classpath
information is as follows:
org.tmforum.mtop.nra.xsd.pmtv.v1.PerformanceMonitoringThresholdValueListType
4.3.7 PerformanceMonitoringThresholdValueType
This object is used to specify performance thresholds. The classpath information
is as follows:
org.tmforum.mtop.nra.xsd.pmtv.v1.PerformanceMonitoringThresholdValueType
Notification Example
Contents
header
objectType PTP
MD Huawei/
U2000
ME 3145739
PTP /shelf=1/
slot=3/
domain=sdh/
port=2
osTime 2009-03-12T05:20:21.000Z
isClearable true
perceivedSe INDETERMINATE
verity
layerRate LR_Section_OC48_STS48_
and_RS_STM16
granularity 15min
pmParamete PMP_BBE
rName
pmLocation PML_NEAR_END_Rx
trigger raise
Contents
thresholdVal 0.0
ue
thresholdUni block
t
thresholdVal 25
ue
thresholdUni block
t
acknowledge EVENT_ACKNOWL-
Indication EDGED
6 Sample Message
6.1 TCA
This topic provides a sample notification of performance threshold-crossing events
6.1 TCA
This topic provides a sample notification of performance threshold-crossing events
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<header xmlns="http://www.tmforum.org/mtop/fmw/xsd/hdr/v1"
xmlns:ns10="http://www.tmforum.org/mtop/fmw/xsd/cornot/v1"
xmlns:ns11="http://www.tmforum.org/mtop/nra/xsd/ps/v1"
xmlns:ns12="http://www.tmforum.org/mtop/nra/xsd/tca/v1"
xmlns:ns13="http://www.tmforum.org/mtop/nra/xsd/pmth/v1"
xmlns:ns14="http://www.tmforum.org/mtop/fmw/xsd/msg/v1"
xmlns:ns15="http://www.tmforum.org/mtop/rtm/xsd/mc/v1"
xmlns:ns16="http://www.tmforum.org/mtop/rtm/xsd/mr/v1"
xmlns:ns17="http://www.tmforum.org/mtop/fmw/xsd/avc/v1"
xmlns:ns18="http://www.tmforum.org/mtop/fmw/xsd/sc/v1"
xmlns:ns19="http://www.tmforum.org/mtop/nrb/xsd/rscsc/v1"
xmlns:ns2="http://www.tmforum.org/mtop/fmw/xsd/gen/v1"
xmlns:ns20="http://www.tmforum.org/mtop/fmw/xsd/oc/v1"
xmlns:ns21="http://www.tmforum.org/mtop/nra/xsd/eps/v1"
xmlns:ns22="http://www.tmforum.org/mtop/mri/xsd/rsc/v1"
xmlns:ns23="http://www.tmforum.org/mtop/mri/xsd/rsd/v1"
xmlns:ns24="http://www.tmforum.org/mtop/nrb/xsd/rscavc/v1"
xmlns:ns25="http://www.tmforum.org/mtop/nrb/xsd/rscoc/v1"
xmlns:ns26="http://www.tmforum.org/mtop/nrb/xsd/rscodel/v1"
xmlns:ns27="http://www.tmforum.org/mtop/fmw/xsd/coi/v1"
xmlns:ns28="http://www.tmforum.org/mtop/nrb/xsd/cri/v1"
xmlns:ns29="http://www.tmforum.org/mtop/nrf/xsd/snc/v1"
xmlns:ns3="http://www.tmforum.org/mtop/fmw/xsd/notmsg/v1"
xmlns:ns30="http://www.tmforum.org/mtop/nrb/xsd/lp/v1"
xmlns:ns31="http://www.tmforum.org/mtop/nrf/xsd/tpdata/v1"
xmlns:ns32="http://www.tmforum.org/mtop/nrf/xsd/com/v1"
xmlns:ns33="http://www.tmforum.org/mtop/mri/xsd/ancp/v1"
xmlns:ns34="http://www.tmforum.org/mtop/rp/xsd/ancp/v1"
xmlns:ns35="http://www.tmforum.org/mtop/nrf/xsd/me/v1"
xmlns:ns36="http://www.tmforum.org/mtop/nrb/xsd/lay/v1"
xmlns:ns37="http://www.tmforum.org/mtop/nrf/xsd/eq/v1"
xmlns:ns38="http://www.tmforum.org/mtop/nrf/xsd/eh/v1"
xmlns:ns39="http://www.tmforum.org/mtop/nrf/xsd/rs/v1"
xmlns:ns4="http://www.tmforum.org/mtop/fmw/xsd/cei/v1"
xmlns:ns40="http://www.tmforum.org/mtop/nrf/xsd/tl/v1"
xmlns:ns41="http://www.tmforum.org/mtop/nrf/xsd/ptp/v1"
xmlns:ns42="http://www.tmforum.org/mtop/nrf/xsd/ctp/v1"
xmlns:ns43="http://www.tmforum.org/mtop/nrf/xsd/ftp/v1"
xmlns:ns44="http://www.tmforum.org/mtop/nrf/xsd/cc/v1"
xmlns:ns45="http://www.tmforum.org/mtop/mri/xsd/vrrpr/v1"
xmlns:ns46="http://www.tmforum.org/mtop/nrf/xsd/fdfr/v1"
xmlns:ns47="http://www.tmforum.org/mtop/nrf/xsd/tmd/v1"
xmlns:ns48="http://www.tmforum.org/mtop/nra/xsd/epg/v1"
xmlns:ns49="http://www.tmforum.org/mtop/nra/xsd/pgp/v1"
xmlns:ns5="http://www.tmforum.org/mtop/fmw/xsd/ei/v1"
xmlns:ns50="http://www.tmforum.org/mtop/nra/xsd/pg/v1"
xmlns:ns51="http://www.tmforum.org/mtop/nrf/xsd/route/v1"
xmlns:ns52="http://www.tmforum.org/mtop/nrf/xsd/tcp/v1"
xmlns:ns53="http://www.tmforum.org/mtop/fmw/xsd/fts/v1"
xmlns:ns54="http://www.tmforum.org/mtop/nra/xsd/ethoam/v1"
xmlns:ns6="http://www.tmforum.org/mtop/fmw/xsd/nam/v1"
xmlns:ns7="http://www.tmforum.org/mtop/nra/xsd/alm/v1"
xmlns:ns8="http://www.tmforum.org/mtop/nra/xsd/prc/v1"
xmlns:ns9="http://www.tmforum.org/mtop/nra/xsd/com/v1"/>
</soap:Header>
<soap:Body>
<ns3:notify xmlns="http://www.tmforum.org/mtop/fmw/xsd/hdr/v1"
xmlns:ns10="http://www.tmforum.org/mtop/fmw/xsd/cornot/v1"
xmlns:ns11="http://www.tmforum.org/mtop/nra/xsd/ps/v1"
xmlns:ns12="http://www.tmforum.org/mtop/nra/xsd/tca/v1"
xmlns:ns13="http://www.tmforum.org/mtop/nra/xsd/pmth/v1"
xmlns:ns14="http://www.tmforum.org/mtop/fmw/xsd/msg/v1"
xmlns:ns15="http://www.tmforum.org/mtop/rtm/xsd/mc/v1"
xmlns:ns16="http://www.tmforum.org/mtop/rtm/xsd/mr/v1"
xmlns:ns17="http://www.tmforum.org/mtop/fmw/xsd/avc/v1"
xmlns:ns18="http://www.tmforum.org/mtop/fmw/xsd/sc/v1"
xmlns:ns19="http://www.tmforum.org/mtop/nrb/xsd/rscsc/v1"
xmlns:ns2="http://www.tmforum.org/mtop/fmw/xsd/gen/v1"
xmlns:ns20="http://www.tmforum.org/mtop/fmw/xsd/oc/v1"
xmlns:ns21="http://www.tmforum.org/mtop/nra/xsd/eps/v1"
xmlns:ns22="http://www.tmforum.org/mtop/mri/xsd/rsc/v1"
xmlns:ns23="http://www.tmforum.org/mtop/mri/xsd/rsd/v1"
xmlns:ns24="http://www.tmforum.org/mtop/nrb/xsd/rscavc/v1"
xmlns:ns25="http://www.tmforum.org/mtop/nrb/xsd/rscoc/v1"
xmlns:ns26="http://www.tmforum.org/mtop/nrb/xsd/rscodel/v1"
xmlns:ns27="http://www.tmforum.org/mtop/fmw/xsd/coi/v1"
xmlns:ns28="http://www.tmforum.org/mtop/nrb/xsd/cri/v1"
xmlns:ns29="http://www.tmforum.org/mtop/nrf/xsd/snc/v1"
xmlns:ns3="http://www.tmforum.org/mtop/fmw/xsd/notmsg/v1"
xmlns:ns30="http://www.tmforum.org/mtop/nrb/xsd/lp/v1"
xmlns:ns31="http://www.tmforum.org/mtop/nrf/xsd/tpdata/v1"
xmlns:ns32="http://www.tmforum.org/mtop/nrf/xsd/com/v1"
xmlns:ns33="http://www.tmforum.org/mtop/mri/xsd/ancp/v1"
xmlns:ns34="http://www.tmforum.org/mtop/rp/xsd/ancp/v1"
xmlns:ns35="http://www.tmforum.org/mtop/nrf/xsd/me/v1"
xmlns:ns36="http://www.tmforum.org/mtop/nrb/xsd/lay/v1"
xmlns:ns37="http://www.tmforum.org/mtop/nrf/xsd/eq/v1"
xmlns:ns38="http://www.tmforum.org/mtop/nrf/xsd/eh/v1"
xmlns:ns39="http://www.tmforum.org/mtop/nrf/xsd/rs/v1"
xmlns:ns4="http://www.tmforum.org/mtop/fmw/xsd/cei/v1"
xmlns:ns40="http://www.tmforum.org/mtop/nrf/xsd/tl/v1"
xmlns:ns41="http://www.tmforum.org/mtop/nrf/xsd/ptp/v1"
xmlns:ns42="http://www.tmforum.org/mtop/nrf/xsd/ctp/v1"
xmlns:ns43="http://www.tmforum.org/mtop/nrf/xsd/ftp/v1"
xmlns:ns44="http://www.tmforum.org/mtop/nrf/xsd/cc/v1"
xmlns:ns45="http://www.tmforum.org/mtop/mri/xsd/vrrpr/v1"
xmlns:ns46="http://www.tmforum.org/mtop/nrf/xsd/fdfr/v1"
xmlns:ns47="http://www.tmforum.org/mtop/nrf/xsd/tmd/v1"
xmlns:ns48="http://www.tmforum.org/mtop/nra/xsd/epg/v1"
xmlns:ns49="http://www.tmforum.org/mtop/nra/xsd/pgp/v1"
xmlns:ns5="http://www.tmforum.org/mtop/fmw/xsd/ei/v1"
xmlns:ns50="http://www.tmforum.org/mtop/nra/xsd/pg/v1"
xmlns:ns51="http://www.tmforum.org/mtop/nrf/xsd/route/v1"
xmlns:ns52="http://www.tmforum.org/mtop/nrf/xsd/tcp/v1"
xmlns:ns53="http://www.tmforum.org/mtop/fmw/xsd/fts/v1"
xmlns:ns54="http://www.tmforum.org/mtop/nra/xsd/ethoam/v1"
xmlns:ns6="http://www.tmforum.org/mtop/fmw/xsd/nam/v1"
xmlns:ns7="http://www.tmforum.org/mtop/nra/xsd/alm/v1"
xmlns:ns8="http://www.tmforum.org/mtop/nra/xsd/prc/v1"
xmlns:ns9="http://www.tmforum.org/mtop/nra/xsd/com/v1">
<ns3:topic>Performance</ns3:topic>
<ns3:message>
<ns12:thresholdCrossingAlert>
<ns4:notificationId>0629201231268</ns4:notificationId>
<ns4:sourceTime>2010-06-30T10:00:40.000Z</ns4:sourceTime>
<ns5:objectType>EQ</ns5:objectType>
<ns5:objectName>
<ns6:rdn>
<ns6:type>MD</ns6:type>
<ns6:value>Huawei/U2000</ns6:value>
</ns6:rdn>
<ns6:rdn>
<ns6:type>ME</ns6:type>
<ns6:value>3145764</ns6:value>
</ns6:rdn>
<ns6:rdn>
<ns6:type>EH</ns6:type>
<ns6:value>/shelf=1/slot=2</ns6:value>
</ns6:rdn>
<ns6:rdn>
<ns6:type>EQ</ns6:type>
<ns6:value>1</ns6:value>
</ns6:rdn>
</ns5:objectName>
<ns5:osTime>2010-06-30T10:00:42.000Z</ns5:osTime>
<ns12:isClearable>true</ns12:isClearable>
<ns12:perceivedSeverity>INDETERMINATE</ns12:perceivedSeverity>
<ns12:layerRate>LR_Not_Applicable</ns12:layerRate>
<ns12:granularity>15min</ns12:granularity>
<ns12:pmParameterName>CPUUSAGEMAX</ns12:pmParameterName>
<ns12:pmLocation>PML_FAR_ENDTypex</ns12:pmLocation>
<ns12:thresholdType>
<ns13:thresholdType>TWM_HIGH</ns13:thresholdType>
<ns13:trigger>raise</ns13:trigger>
<ns13:thresholdValue>0.0</ns13:thresholdValue>
<ns13:thresholdUnit>%</ns13:thresholdUnit>
</ns12:thresholdType>
<ns12:thresholdValue>9.0</ns12:thresholdValue>
<ns12:thresholdUnit>%</ns12:thresholdUnit>
<ns12:acknowledgeIndication>NA</ns12:acknowledgeIndication>
</ns12:thresholdCrossingAlert>
</ns3:message>
</ns3:notify>
</soap:Body>
</soap:Envelope>
This section describes the naming rules of objects of the U2000 XML interface according to the
naming rules recommended by MTOSI.
7.1 AID
7.2 CC
7.3 CTP
7.4 EH
7.5 EPG
7.6 EQ
7.7 EXPLICITPATH
7.8 FDFR
7.9 FTP
7.10 ISIS
7.11 MAINTENANCEASSOCIATION
7.12 MAINTENANCEDOMAIN
7.13 MD
7.14 ME
7.15 MEP
7.16 MIP
7.17 MLSN
7.18 OAMMEASURE
7.19 OS
7.20 PG
7.21 PMINSTANCE
7.22 PTP
7.23 RESOURCESITE
7.24 RMEP
7.25 SNC
7.26 TC
7.27 TCPROFILE
7.28 TL
7.29 TMD
7.30 TS
7.31 TUNNELPOLICY
7.32 VRRP
7.1 AID
Object Name AID
Remarks N/A
7.2 CC
Object Name CC
Parameter Naming
<name>
Rules <nam:rdn>
Recommended by <nam:type>MD</nam:type>
MTOSI <nam:value>CompanyName /MDName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>MEName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>CC</nam:type>
<nam:value>CCName </nam:value>
</nam:rdn>
</name>
Object Name CC
Sample Parameter
<name>
Names of the U2000 <nam:rdn>
XML Interface <nam:type>MD</nam:type>
<nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>3145728</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>CC</nam:type>
<nam:value>PWSW=|556|12.12.12.156|456|455|557|
12.12.12.157|458|457|12</nam:value>
</nam:rdn>
</name>
7.3 CTP
Object Name CTP
Sample Parameter
<name>
Names of the U2000 <nam:rdn>
XML Interface <nam:type>MD</nam:type>
<nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>3145728</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>PTP</nam:type>
<nam:value>/shelf=1/slot=2/sub_slot=0/type=eth/
port=1/cli_name=GigabitEthernet2/0/1</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>CTP</nam:type>
<nam:value>/sub_port=234</nam:value>
</nam:rdn>
</name>
Remarks
7.4 EH
Object Name EH
Object Name EH
7.5 EPG
Object Name EPG
Parameter Naming
<name>
Rules <nam:rdn>
Recommended by <nam:type>MD</nam:type>
MTOSI <nam:value>CompanyName /MDName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>MEName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>EPG</nam:type>
<nam:value>EPGName </nam:value>
</nam:rdn>
</name>
Sample Parameter
<name>
Names of the U2000 <nam:rdn>
XML Interface <nam:type>MD</nam:type>
<nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>3145728</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>EPG</nam:type>
<nam:value>/pg=1/type=1</nam:value>
</nam:rdn>
</name>
7.6 EQ
Object Name EQ
Object Name EQ
Remarks For Huawei equipment, the value of Equipment is always 1, that is,
only one board can be installed in a slot.
7.7 EXPLICITPATH
Object Name EXPLICITPATH
Parameter Naming
<name>
Rules <nam:rdn>
Recommended by <nam:type>MD</nam:type>
MTOSI <nam:value>CompanyName /MDName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>MEName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>EXPLICITPATH</nam:type>
<nam:value>EXPLICITPATHName </nam:value>
</nam:rdn>
</name>
Sample Parameter
<name>
Names of the U2000 <nam:rdn>
XML Interface <nam:type>MD</nam:type>
<nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>3145728</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>EXPLICITPATH</nam:type>
<nam:value>ex_path</nam:value>
</nam:rdn>
</name>
Remarks
7.8 FDFR
Object Name FDFR
Parameter Naming
<name>
Rules <nam:rdn>
Recommended by <nam:type>MD</nam:type>
MTOSI <nam:value>CompanyName /MDName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>MEName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>FDFR</nam:type>
<nam:value>FDFRName </nam:value>
</nam:rdn>
</name>
<name>
<nam:rdn>
<nam:type>MD</nam:type>
<nam:value>CompanyName /MDName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>FD</nam:type>
<nam:value>1</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>FDFR</nam:type>
<nam:value>FDFRName </nam:value>
</nam:rdn>
</name>
Sample Parameter
<name>
Names of the U2000 <nam:rdn>
XML Interface <nam:type>MD</nam:type>
<nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>3145728</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>FDFR</nam:type>
<nam:value>VSI=555|vsinam</nam:value>
</nam:rdn>
</name>
Sample Parameter
<name>
Names of the U2000 <nam:rdn>
XML Interface (E2E <nam:type>MD</nam:type>
PWE3) <nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>FD</nam:type>
<nam:value>1</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>FDFR</nam:type>
<nam:value>PWE3TRAIL=123</nam:value>
</nam:rdn>
</name>
Sample Parameter
<name>
Names of the U2000 <nam:rdn>
XML Interface (E2E <nam:type>MD</nam:type>
VPLS) <nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>FD</nam:type>
<nam:value>1</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>FDFR</nam:type>
<nam:value>VPLS=123</nam:value>
</nam:rdn>
</name>
Remarks
7.9 FTP
Object Name FTP
Remarks For naming rules for the shelf, slot, and subslot in a FTP name, refer
to section "EquipmentHolder".
The values of domain include sdh, wdm, eth, atm, sonnet, and ptn.
Only the transport equipment has these attributes. The port names of
the equipment of other domains, such as router, do not contain the
domain field. For the IP domain, there is a cli_name field after the
port field, for example, /shelf=1/type=vlanif/port=1001/
cli_name=Vlanif1001.
7.10 ISIS
Object Name ISIS
7.11 MAINTENANCEASSOCIATION
Object Name MAINTENANCEASSOCIATION
Remarks N/A
7.12 MAINTENANCEDOMAIN
Object Name MAINTENANCEDOMAIN
Remarks N/A
7.13 MD
Object Name MD
7.14 ME
Object Name ME
Object Name ME
Remarks
7.15 MEP
Object Name MEP
Remarks N/A
7.16 MIP
Object Name MIP
Remarks N/A
7.17 MLSN
Object Name TL
Object Name TL
7.18 OAMMEASURE
Object Name OAMMEASURE
7.19 OS
Object Name OS
7.20 PG
Object Name PG
Parameter Naming
<name>
Rules <nam:rdn>
Recommended by <nam:type>MD</nam:type>
MTOSI <nam:value>CompanyName /MDName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>MEName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>PG</nam:type>
<nam:value>PGName </nam:value>
</nam:rdn>
</name>
Object Name PG
Sample Parameter
<name>
Names of the U2000 <nam:rdn>
XML Interface <nam:type>MD</nam:type>
<nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>3145728</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>PG</nam:type>
<nam:value>/shelf=1/pg=1/pos=17</nam:value>
</nam:rdn>
</name>
7.21 PMINSTANCE
Object Name PMINSTANCE
Remarks N/A
7.22 PTP
Object Name PTP
Remarks For naming rules for the shelf, slot, and subslot in a PTP name, refer
to section "EH".
The values of domain include sdh, wdm, eth, atm, sonnet, and ptn.
Only the transport equipment has these attributes. The port names of
the equipment of other domains, such as router, do not contain the
domain field. For the IP domain, there is a cli_name field after the
port field, for example, /shelf=1/slot=13/type=eth/port=0/
cli_name=Ethernet13/0/0.
7.23 RESOURCESITE
Object Name RESOURCESITE
Remarks This object is added by Huawei, which represents the transport WDM
NE.
7.24 RMEP
Object Name RMEP
Remarks N/A
7.25 SNC
Object Name SNC
Parameter naming
<name>
rules recommended <nam:rdn>
by MTOSI <nam:type>MD</nam:type>
<nam:value>CompanyName /MDName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>MEName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>SNC</nam:type>
<nam:value>SNCName </nam:value>
</nam:rdn>
</name>
U2000 Parameter
<name>
name example of the <nam:rdn>
XML NBI (RSVP- <nam:type>MD</nam:type>
TE Tunnel) <nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>3145728</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>SNC</nam:type>
<nam:value>TUNNEL=3||||100||||</nam:value>
</nam:rdn>
</name>
U2000 Parameter
<name>
name example of the <nam:rdn>
XML NBI (Static- <nam:type>MD</nam:type>
CR E2E Tunnel) <nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>MLSN</nam:type>
<nam:value>1</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>SNC</nam:type>
<nam:value>TUNNELTRAIL=190</nam:value>
</nam:rdn>
</name>
U2000 Parameter
<name>
name example of the <nam:rdn>
XML NBI (path) <nam:type>MD</nam:type>
<nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>MLSN</nam:type>
<nam:value>1</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>SNC</nam:type>
<nam:value>2007-08-22 07:14:05 - 35183-sdh</
nam:value>
</nam:rdn>
</name>
7.26 TC
Object Name TC
7.27 TCPROFILE
Object Name TCPROFILE
Parameter Naming
<name>
Rules <nam:rdn>
Recommended by <nam:type>MD</nam:type>
MTOSI <nam:value>CompanyName /MDName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>TCPROFILE</nam:type>
<nam:value>TCPROFILEName </nam:value>
</nam:rdn>
</name>
Sample Parameter
<name>
Names of the U2000 <nam:rdn>
XML Interface <nam:type>MD</nam:type>
<nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>TCPROFILE</nam:type>
<nam:value>/type=cbqosprofile/name=cbqosprofiletest</
nam:value>
</nam:rdn>
</name>
Remarks
7.28 TL
Object Name TL
Remarks
7.29 TMD
Object Name TMD
Parameter Naming
<name>
Rules <nam:rdn>
Recommended by <nam:type>MD</nam:type>
MTOSI <nam:value>CompanyName /MDName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>MEName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>TMD</nam:type>
<nam:value>TMDName </nam:value>
</nam:rdn>
</name>
Sample Parameter
<name>
Names of the U2000 <nam:rdn>
XML Interface <nam:type>MD</nam:type>
<nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>3145728</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>TMD</nam:type>
<nam:value>20|</nam:value>
</nam:rdn>
</name>
7.30 TS
Object Name TS
Object Name TS
7.31 TUNNELPOLICY
Object Name TUNNELPOLICY
Parameter Naming
<name>
Rules <nam:rdn>
Recommended by <nam:type>MD</nam:type>
MTOSI <nam:value>CompanyName /MDName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>MEName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>TUNNELPOLICY</nam:type>
<nam:value>TUNNELPOLICYName </nam:value>
</nam:rdn>
</name>
Sample Parameter
<name>
Names of the U2000 <nam:rdn>
XML Interface <nam:type>MD</nam:type>
<nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>3145728</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>TUNNELPOLICY</nam:type>
<nam:value>tnl_policy</nam:value>
</nam:rdn>
</name>
7.32 VRRP
Object Name VRRP
Parameter Naming
<name>
Rules <nam:rdn>
Recommended by <nam:type>MD</nam:type>
MTOSI <nam:value>CompanyName /MDName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>MEName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>PTP</nam:type>
<nam:value>PTPName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>CTP</nam:type>
<nam:value>CTPName </nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>VRRP</nam:type>
<nam:value>VRRPName </nam:value>
</nam:rdn>
</name>
Sample Parameter
<name>
Names of the U2000 <nam:rdn>
XML Interface <nam:type>MD</nam:type>
<nam:value>Huawei/U2000</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>ME</nam:type>
<nam:value>3145728</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>PTP</nam:type>
<nam:value>/shelf=1/slot=1/sub_slot=0/type=eth/
port=0/cli_name=GigabitEthernet1/0/0</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>CTP</nam:type>
<nam:value>/sub_port=2</nam:value>
</nam:rdn>
<nam:rdn>
<nam:type>VRRP</nam:type>
<nam:value>360</nam:value>
</nam:rdn>
</name>
Remarks
Performanc getAllPerforman- Queries the names of all This interface does not
eManagem ceMonitoring- performance monitoring implement any specific
entRetrieva PointNames points. service functions and
l returns the error message
"notImplemented".
Table 9-1 List of layer rates supported by the U2000 XML NBI
ID Layer Identifier Description
66 LR_FDDI
10 Glossary
E
Edge Termination An Edge Termination Point (Edge TP) is a Termination Point (TP) that is at an entrance
Point or exit point of a MultiLayer Subnetwork (i.e. add-drop or TPs that terminate topological
links between two Subnetworks).
Element Management The Element Management System (EMS) is used to manage (represent) a portion of a
System network which contains one or more MultiLayer Subnetworks. The EMS is used as the
root of the naming tree in the NML-EML interface.
Equipment An Equipment represents the manageable physical components of a Network Element
such as the circuit packs, the fans and any other type of replaceable unit within the
Network Element.
EquipmentHolder An Equipment Holder shall represent resources of the Network Element that are capable
of holding other physical components.
Specific resources that are represented by an Equipment Holder object shall be for
instance racks (bays), shelves, and slots or sub-slots.
L
Location An area, position, or portion of space that somebody or something can occupy. It is
further decomposed into a geographic place that relates to world-centric places and local
location that relates to locally defined coordinate systems.
M
Managed Element A Managed Element (ME) represents the EMS (management) view of a Network
Element (NE).
MultiLayer A MultiLayer Subnetwork represents the topology provided by the EMS system. The
Subnetwork main services provided within a MultiLayer Subnetwork are the set-up and tear-down
of Subnetwork Connection (SNC).
Network Element A Network Element (NE) is telecommunications hardware equipment that is addressable
and manageable. NEs provide support or services to the user and can be managed through
an Element Management System (EMS).
An NE is a combination of hardware and software that primarily performs a
telecommunications service function. A group of interconnected network elements form
a network.
P
Party Represents an individual, organization or organization unit. Party is an abstract concept
that should be used in places where the business says something.
PartyRole The part played by a party in a given context with any characteristics, such as expected
pattern of behavior, attributes, and/or associations that it entails. PartyRole is an abstract
concept that should be used in places where the business refers to a Party playing a Role.
Physical Termination A Physical Termination Point (PTP) represents the actual or potential endpoint of a
Point Topological Link. Essentially, this is a representation of a physical port.
ProductBundle A type of Product that is comprised of other Product(s). The other Product(s) may be
ProductBundle(s) or ProductComponent(s).
ProductSpecification A detailed description of a tangible or intangible object made available externally in the
form of a ProductOffering to Customers or other Parties playing a PartyRole. A
ProductSpecification may consist of other ProductSpecifications supplied together as a
collection. Members of the collection may be offered in their own right.
ProductSpecifications may also exist within groupings, such as ProductCategories,
ProductLines, and ProductTypes.
R
Route A Route represents the route of a Subnetwork Connection (SNC).
An SNC route is represented as a partially ordered series of Cross Connects through
which the SNC traverses.
S
Service All Services are characterized as either being a realization of a Product
(CustomerFacingService) facing the Customer or how a Service is provisioned within a
provider's infrastructure (ResourceFacingService) facing the resources.
Service Access Point A point of entry where the service can be accessed. This point of entry is always
associated (directly or indirectly) with a physical resource (such as a PTP, a CTP).
However, sometimes the SAP is an object or a logical resource that contains or identifies
the support of the physical resource. (Customer Premise Equipment, a Mobile Terminal,
a Set-top Box, an internet address).
ServiceCatalog A grouping of Service Specifications that share common characteristics. For example
one catalog could group all internet related Service Specifications.
ServiceCharacteristicV A ServiceCharacteristicValue is a value passed over the Activation Interface to convey
alue an individually set service characteristic (i.e. not reference in a ServiceTemplate) or to
override a globally set characteristic value (present in a ServiceTemplate). A
ServiceCharacteristicValue will apply only to the specific Service instance created.
ServiceDefinition A type of Service Specification (from the SID) introduced for the purposes of Service
Fulfillment. It defines ALL the ServiceSpecCharacteristics that must be used to create
corresponding Service instances:
The ones which are set globally (the corresponding values are defined only in
ServiceTemplates and are sometimes designated as "invariant" ).
the ones which are set individually (the corresponding values can be defined only over
the Activation Interface and are sometimes designated as "variant").
A ServiceSpecCharacteristic specified in a erviceDefinition may be associated with
ServiceSpecCharacteristicValues to restrict the typing information or to specify a default
value.
ServiceOrder A Service Order is a type of request (as defined in the SID model). In particular, a service
order is used to track and control the progress of a request for some action (e.g., provision
or activation) on the services that comprise a given product instance. It should be
mentioned that the OSS/J Order Management API (JSR 264) defines Service Order as
follows: "A type of Request that represents a Customer Order's products decomposed
into the services through which the products are realized. Service Orders are generated
within the confines of the SM&O layer."
ServiceOrderItem Service Order Items are used to represent the order aspects of the services associated
with a given service order. There is one service order item for each service associated
with a service order.
ServiceRequest A request made by the CRM layer to the SM&O layer as defined in the TMForum eTOM
to take an action on one or more CFS instances given a product identifier, a product
specification name and a related set of characteristics. This request can be realized by
Template and by Value.
ServiceSpecCharacteri A characteristic quality or distinctive feature of a Service as represented in a
stic ServiceSpecification (specialized as ServiceDefinition or ServiceTemplate). In
particular it contains typing information which can be arbitrarily complex.
A Service Spec Characteristic can be atomic or composite (also called "packages"). The
components of a composite Service Spec Characteristic can in turn be atomic or
composite.
ServiceSpecification Changeable as well as invariant attributes, methods, relationships and constraints which
define a Service. It can be conceptually thought of as a template that different Service
instances can be instantiated from. Each of these Service instances will have the same
invariant characteristics. However, the other characteristics of the instantiated Service
will be specific to each instance.
ServiceSpecificationTy The ServiceSpecificationType class defines a generic category of ServiceSpecifications.
pe
Each ServiceSpecificationType serves to group a set of particular ServiceSpecifications
that share the same behavior and other semantics. One result of this is to be able to more
efficiently define a set of related Services that can be grouped together to form a higher-
level Service.
For example, a given higher-level Service might include VPN and QoS Services. If these
Services are always used together, then they can be categorized using a common type.
ServiceTemplate A type of Service Specification (from the SID) introduced for the purposes of Service
Fulfillment.
It defines specific ServiceSpecCharacteristicsValues for the globally set
ServiceSpecCharacteristics that can be dynamically referenced by multiple Service
instances during their lifecycle span. A ServiceTemplate is checked against its associated
ServiceDefinition by verifying the presence of the ServiceSpecCharacteristics and the
validity of the corresponding assigned ServiceSpecCharacteristicsValues. Each of the
associated Service instances will have the same invariant characteristics which values
are taken from the ServiceTemplate.
However, when activating a Service, it may be possible to specify over the Activation
Interface a ServiceCharacteristicsValue which overrides the corresponding
ServiceSpecCharacteristicValue available in the associated ServiceTemplate.
In this case the new proposed value applies only to the Service instance created, and the
ServiceSpecCharacteristicValue in the ServiceTemplate is not modified.
In order not to descend into sub-classing, the ServiceTemplate is considered to be generic
such that it serves as a framework for defining technology or service specific templates.
Other TMForum groups, or service providers, may use the service template as a
foundation for building or populating service templates.
Subnetwork A Subnetwork Connection (SNC) represents the relationship between two of the
Connection following types on end points:
Subscriber A Subscriber is an entity (associated with one or more users) that is engaged in a service
subscription with a service provider. The subscriber is allowed to subscribe and
unsubscribe services, to register a user or a list of users authorized to use these services,
and also to set the limits relative to the use that associated users make of these services.
Termination Point A Termination Point (TP) represents a logical abstraction of an endpoint (actual or
potential) of either:
1. A Topological Link
2. A Subnetwork Connection (SNC)
3. A Flow Domain Fragment (FDFr)
4. A Cross Connection (CC)
Topological Link A Topological Link (TL) is a physical link between two Physical Termination Point
(PTP)s or a trail between two Termination Point (TP)s (e.g., an ATM link between two
ATM NI CTPs), which are called aEnd TP and zEnd TP of the TL.
TMD Transmission A Transmission Descriptor (TMD) represents a collection of attributes, which are used
Descriptor to define multi-layered transmission parameters, and additional information parameters
on a Termination Point (TP)
A
ABR Asynchronous batch response
AFB Asynchronous file bulk
AID Alarm identifier
ARR Asynchronous request/reply
ASN.1 Abstract Syntax Notation One
AVC Attribute value change
C
CDE Common desktop environment
CPU Central processing unit
E
EdgeTP Edge termination point
EH Equipmen holder
EQT Equipment
EMS Element management system
EOW Ethernet over WDM
F
FIFO First in first out
FTP File Transfer Protocol
G
GE Gigabit Ethernet
GNE Gate network element
GUI Graphical user interface
H
HA High availability
HTTP Hyper-Text Transmission Protocol
HTTPS Hypertext Transfer Protocol Secure
I
ID Identity
IMAP Integrated management application platform
IP Internet Protocol
ITU-T International Telecommunication Union- Telecommunication Standardization Sector
J
JMS Java message service
L
LAN Local area network
M
MAC Media access control MD
Management domain
MDP Message dispatch process
ME Managed element
MEP Message exchange pattern
MLSN Multi-layer sub network
MO Managed object
MTOSI Multi-Technology operations system interface
MTNM Multi-Technology network management
N
NE Network element
NEL Network element level NML
Network management level
NMS Network management system
O
OS Operations system
ONE Optical network element
OTN Optical transport network
P
PC Personal computer
PDH Plesiochronous digital hierarchy
PTP Physical termination point
S
SAP Service access point
SC State change
SDH Synchronous digital hierarchy
SFB Synchronous file bulk
SIT Synchronous iterator pattern
SNC Sub network connection
SOAP Simple Object Access Protocol
SONET Synchronous optical network
SRR Synchronous request response
SSL Security socket layer
SSM Synchronization status message
SFTP SSH FTP
SML Service management layer
SOA Service-oriented architecture
T
TCP Transport Control Protocol
TL Topological link
TMD Transmission descriptor
TMF Telecommunication Management Forum
TMN Telecommunication management network
TP Termination point
TCA Threshold crossed alert
U
UPC Usage parameter control
W
WAN Wide area network
WSDL Web service definition language
WSN Web services notification
X
XML Extensible markup language