Cisco Cisco Transport Manager 9.1 기술 참조
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES
TMF 814Av3.0
TeleManagement Forum 2003
84
TimeOut
30 minutes for alarms and
TCAs; 24 hours for all other
notifications
TCAs; 24 hours for all other
notifications
The recommended value is
30 minutes for NT_TCA and
NT_ALARM events, and 24
hours for all other events.
30 minutes for NT_TCA and
NT_ALARM events, and 24
hours for all other events.
2.27.3 Proprietary LayerRates
The EML vendor should publish a list of proprietary layerRates that are used along with their
definition. When a layerRate has been subsumed into the standard this list should be augmented
with the equivalence and obsolescence statement.
definition. When a layerRate has been subsumed into the standard this list should be augmented
with the equivalence and obsolescence statement.
The proprietary layerRate should be used where:
A transport technology within a product is as yet to be incorporated in the MTNM model
o
This layerRate should be marked as “being standardized” in its definition in the
conformance statement
o
When the transport technology is incorporated the vendor should identify the
equivalence and obsolescence in their conformance statement
A proprietary transport technology has been used which is necessary to expose over the
interface for monitoring and/or configuration purposes
o
This layerRate should be marked as “proprietary” in its definition in the
conformance statement
Where an NE only provides partial information on the layerRate, e.g., the NE only
indicates that the layerRate is SONET or ATM
o
This layerRate should be marked as “partial” in its definition and should (where
possible) be related to layerRates that it covers
Where a proprietary layerRate is used it may be necessary to name a TP (CTP or FTP) from that
layerRate. In this case a name-string similar in structure to that used for a standardize layerRate
(in the layerRate list) should be allocated by the vendor and recorded in the conformance
statement. To conform to the specification this name-string will start with “PROP” (e.g.
“PROP_sts_291c”).
layerRate. In this case a name-string similar in structure to that used for a standardize layerRate
(in the layerRate list) should be allocated by the vendor and recorded in the conformance
statement. To conform to the specification this name-string will start with “PROP” (e.g.
“PROP_sts_291c”).
Table 2-61. Proprietary LayerRate Table
Layer Rate Number
(integer greater than
or equal to 10,000)
Layer Rate Name
(the names of all proprietary layer
rates start with “PROP”)
Status (either “Being Standardized”,
“Proprietary”, “Partial” or “Obsolete”
10,000 PROP_DSR_OC3072_and_STM1024
Being
Standardized
10,001 PROP_STS_291c
Proprietary
10,002 PROP_SONET
Partial