<head><META http-equiv="Content-Type" content="text/html; charset=UTF-8"> <link rel="stylesheet" type="text/css" href="mof.css" xmlns:lxslt="http://xml.apache.org/xslt"> <title>DMTF Schema Documentation Schema Documentation</title> </head><html> <body bgcolor="White"> <hr> </hr> <a name="CIM_MPLSTunnel"></a> <H1>Class CIM_MPLSTunnel<BR>extends <a href="CIM_EnabledLogicalElement.html">CIM_EnabledLogicalElement</a> </H1>This class represents an MPLS traffic engineering tunnel as defined in RFC 3031.<h3> Table of Contents<br> <a href="#c_hierarchy">Hierarchy</a> <br> <a href="#c_subclasses">Direct Known Subclasses</a> <br> <a href="#c_qualifiers">Class Qualifiers</a> <br> <a href="#c_properties">Class Properties</a> <br> <a href="#c_methods">Class Methods</a> <br> </h3> <hr> </hr> <H2> <a name="c_hierarchy">Class Hierarchy</a> </H2> <a href="CIM_ManagedElement.html">CIM_ManagedElement</a> <br data="@NAME"> |<br> +--<a href="CIM_ManagedSystemElement.html">CIM_ManagedSystemElement</a> <br data="@NAME"> |<br> +--<a href="CIM_LogicalElement.html">CIM_LogicalElement</a> <br data="@NAME"> |<br> +--<a href="CIM_EnabledLogicalElement.html">CIM_EnabledLogicalElement</a> <br data="@NAME"> |<br> +--<b>CIM_MPLSTunnel</b> <br data="CIM_MPLSTunnel -- CIM_EnabledLogicalElement"> <H2> <a name="c_subclasses">Direct Known Subclasses</a> </H2> <H2> <a name="c_qualifiers">Class Qualifiers</a> </H2> <TABLE BORDER="1" CELLPADDING="1" WIDTH="100%"> <TR> <TH>Name</TH><TH>Data Type</TH><TH>Value</TH> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">This class represents an MPLS traffic engineering tunnel as defined in RFC 3031.</TD> </TR> <TR> <TD VALIGN="TOP">Experimental</TD><TD VALIGN="TOP">boolean</TD><TD VALIGN="TOP">true</TD> </TR> <TR> <TD VALIGN="TOP">UMLPackagePath</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">CIM::Network::MPLS</TD> </TR> <TR> <TD VALIGN="TOP">Version</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">2.19.0</TD> </TR> </TABLE> <H2> <a name="c_properties">Class Properties</a> </H2> <H3>Local Class Properties</H3> <TABLE WIDTH="100%" CELLPADDING="1" BORDER="1"> <TR> <TH ROWSPAN="2"><B>Name</B></TH><TH ROWSPAN="2"><B>Data Type</B></TH><TH ROWSPAN="2"><B>Default Value</B></TH><TH COLSPAN="5"><B>Qualifiers</B></TH> </TR> <TR> <TH>Name</TH><TH>Data Type</TH><TH>Value</TH> </TR> <TR> <TH ROWSPAN="4" VALIGN="TOP">ActiveBandwidth</TH><TD ROWSPAN="4" VALIGN="TOP">uint32</TD><TD ROWSPAN="4" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Active bandwidth for this tunnel in kilobits per second. If the tunnel is not yet Established, then this property has no meaning. Knowing current Bandwidth is important because several path options may be configured for the tunnel. Note that it is possible to signal 0 bandwidth for a pure best- effort tunnel.</TD> </TR> <TR> <TD VALIGN="TOP">PUnit</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">bit / second * 10^3</TD> </TR> <TR> <TD VALIGN="TOP">Units</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">KiloBits per Second</TD> </TR> <TR> <TH ROWSPAN="4" VALIGN="TOP">Bandwidth</TH><TD ROWSPAN="4" VALIGN="TOP">uint32</TD><TD ROWSPAN="4" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">The bandwidth property denotes the complete bandwidth (in kilobits per second) required to be transported by the tunnel. Note, that the bandwidth is not directly implemented/ configured in a router, but the MPLSTunnel's Reserved Bandwidth property might be derived from this information.</TD> </TR> <TR> <TD VALIGN="TOP">PUnit</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">bit / second * 10^3</TD> </TR> <TR> <TD VALIGN="TOP">Units</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">KiloBits per Second</TD> </TR> <TR> <TH ROWSPAN="2" VALIGN="TOP">EgressLSRId</TH><TD ROWSPAN="2" VALIGN="TOP">uint32</TD><TD ROWSPAN="2" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">ID of egress LSR.</TD> </TR> <TR> <TH ROWSPAN="3" VALIGN="TOP">ElementName</TH><TD ROWSPAN="3" VALIGN="TOP">string</TD><TD ROWSPAN="3" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">The canonical name assigned to the tunnel. This name can be used to refer to the tunnel on the LSR's console port.</TD> </TR> <TR> <TD VALIGN="TOP">Override</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">ElementName</TD> </TR> <TR> <TH ROWSPAN="3" VALIGN="TOP">Established</TH><TD ROWSPAN="3" VALIGN="TOP">boolean</TD><TD ROWSPAN="3" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Boolean indicating whether or not the tunnel is currently signaled. Note that if the tunnel is not established, then the OperationalStatus properties inherited from Managed SystemElement have no meaning.</TD> </TR> <TR> <TD VALIGN="TOP">Write</TD><TD VALIGN="TOP">boolean</TD><TD VALIGN="TOP">true</TD> </TR> <TR> <TH ROWSPAN="3" VALIGN="TOP">ExcludeAllAffinity</TH><TD ROWSPAN="3" VALIGN="TOP">uint32</TD><TD ROWSPAN="3" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Resource classes and resource class affinities are described in [RFC2702]. Resource classes can be associated with links and advertised in routing protocols. Resource class affinities are used by RSVP-TE [RFC3209]. In order to be used, a link MUST pass three tests. One of them is against this property. ExcludeAllAffinity is one type of resource class affinity. It specifies a set of attribute filters for the tunnel, and a match on any of the filters renders a link unacceptable (it is excluded for consideration). This test takes the form, (MPLSProtocolEndpoint.ResourceClass & ExcludeAllAffinity) == 0.</TD> </TR> <TR> <TD VALIGN="TOP">MappingStrings</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">MIB.IETF|MPLS-TE-MIB.MPLSTunnelExcludeAllAffinity</TD> </TR> <TR> <TH ROWSPAN="5" VALIGN="TOP">HoldingPriority</TH><TD ROWSPAN="5" VALIGN="TOP">uint8</TD><TD ROWSPAN="5" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Property to indicate the holding priority of an established tunnel. If the tunnel is not yet established, this property has no meaning. A new tunnel is allowed to preempt the resources of this tunnel only if its SetupPriority is smaller than the HoldingPriority of the established one. (See RFC3209 for additional information.) The value 0 is the highest priority.</TD> </TR> <TR> <TD VALIGN="TOP">MappingStrings</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">MIB.IETF|MPLS-TE-MIB.mplsTunnelHoldingPrio</TD> </TR> <TR> <TD VALIGN="TOP">MaxValue</TD><TD VALIGN="TOP">sint64</TD><TD VALIGN="TOP">7</TD> </TR> <TR> <TD VALIGN="TOP">MinValue</TD><TD VALIGN="TOP">sint64</TD><TD VALIGN="TOP">0</TD> </TR> <TR> <TH ROWSPAN="3" VALIGN="TOP">IncludeAllAffinity</TH><TD ROWSPAN="3" VALIGN="TOP">uint32</TD><TD ROWSPAN="3" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Resource classes and resource class affinities are described in [RFC2702]. Resource classes can be associated with links and advertised in routing protocols. Resource class affinities are used by RSVP-TE [RFC3209]. In order to be used, a link MUST pass three tests. One of them against this property. IncludeAllAffinity is one type of resource class affinity. It specifies a set of attribute filters for the tunnel, and all of the filters must match for a link to be acceptable (i.e., pass this test). If IncludeAllAffinity is zero, then the test automatically passes. The test takes the form, (IncludeAllAffinity == 0) || (((MPLSProtocolEndpoint.ResourceClass & IncludeAllAffinity) ^ IncludeAllAffinity) == 0)</TD> </TR> <TR> <TD VALIGN="TOP">MappingStrings</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">MIB.IETF|MPLS-TE-MIB.MPLSTunnelIncludeAllAffinity</TD> </TR> <TR> <TH ROWSPAN="3" VALIGN="TOP">IncludeAnyAffinity</TH><TD ROWSPAN="3" VALIGN="TOP">uint32</TD><TD ROWSPAN="3" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Resource classes and resource class affinities are described in [RFC2702]. Resource classes can be associated with links and advertised in routing protocols. Resource class affinities are used by RSVP-TE [RFC3209]. In order to be used, a link MUST pass three tests. One of them against this property. IncludeAnyAffinity is one type of resource class affinity. It specifies a set of attribute filters for the tunnel, and any of the filters must match for a link to be acceptable (i.e., pass this test). If IncludeAllAffinity is zero, then the test automatically passes. The test takes the form, (IncludeAnyAffinity == 0) || ((MPLSProtocolEndpoint.ResourceClass & IncludeAnyAffinity) != 0)</TD> </TR> <TR> <TD VALIGN="TOP">MappingStrings</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">MIB.IETF|MPLS-TE-MIB.MPLSTunnelIncludeAnyAffinity</TD> </TR> <TR> <TH ROWSPAN="3" VALIGN="TOP">IngressLSRId</TH><TD ROWSPAN="3" VALIGN="TOP">uint32</TD><TD ROWSPAN="3" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">The purpose of this object is to uniquely identity a tunnel within a network. When the MPLS signaling protocol is rsvp(3), this value SHOULD mimic the Extended Tunnel Id field in the SESSION object. When the MPLS signaling protoocol is crldp(4), this value SHOULD mimic the Ingress LSR Router ID field in the LSPID TLV object.</TD> </TR> <TR> <TD VALIGN="TOP">ModelCorrespondence</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">CIM_MPLSTunnel.TunnelSignalingProtocol</TD> </TR> <TR> <TH ROWSPAN="2" VALIGN="TOP">IngressMayReroute</TH><TD ROWSPAN="2" VALIGN="TOP">boolean</TD><TD ROWSPAN="2" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Flag to indicate that the tunnel ingress node may choose to reroute this tunnel without tearing it down.</TD> </TR> <TR> <TH ROWSPAN="4" VALIGN="TOP">InstanceID</TH><TD ROWSPAN="4" VALIGN="TOP">string</TD><TD ROWSPAN="4" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">InstanceID opaquely identifies a unique instance of SettingData. The InstanceID must be unique within a namespace. In order to ensure uniqueness, the value of InstanceID SHOULD be constructed in the following manner: <Vendor ID><ID> <Vendor ID> MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity or a registered ID that is assigned to the business entity that is defining the InstanceID. (This is similar to the <Schema Name>_<Class Name> structure of Schema class names). The purpose of <Vendor ID> is to ensure that <ID> is truly unique across multiple vendor implementations. If such a name is not used, the defining entity MUST assure that the <ID> portion of the Instance ID is unique when compared with other instance providers. For DMTF defined instances, the <Vendor ID> is 'CIM'. <ID> MUST include a vendor specified unique identifier.</TD> </TR> <TR> <TD VALIGN="TOP">Key</TD><TD VALIGN="TOP">boolean</TD><TD VALIGN="TOP">true</TD> </TR> <TR> <TD VALIGN="TOP">Override</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">InstanceID</TD> </TR> <TR> <TH ROWSPAN="2" VALIGN="TOP">IsAdaptive</TH><TD ROWSPAN="2" VALIGN="TOP">boolean</TD><TD ROWSPAN="2" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">In some situations, it is necessary to reroute a tunnel without disrupting traffic. This flag indicates whether the tunnel's route is adaptive.</TD> </TR> <TR> <TH ROWSPAN="2" VALIGN="TOP">IsDynamicallyRouted</TH><TD ROWSPAN="2" VALIGN="TOP">boolean</TD><TD ROWSPAN="2" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Flag to indicate whether the route for the tunnel is selected dynamically based on routing protocols - as opposed to being specified 'statically' via configuration, where a network operator or other external entity specifies the path of the tunnel hop by hop.</TD> </TR> <TR> <TH ROWSPAN="2" VALIGN="TOP">IsPersistent</TH><TD ROWSPAN="2" VALIGN="TOP">boolean</TD><TD ROWSPAN="2" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Flag to indicate that this tunnel should be restored automatically after a failure occurs.</TD> </TR> <TR> <TH ROWSPAN="2" VALIGN="TOP">IsPinned</TH><TD ROWSPAN="2" VALIGN="TOP">boolean</TD><TD ROWSPAN="2" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Flag to indicate whether the loosely-routed hops of this tunnel are to be pinned.</TD> </TR> <TR> <TH ROWSPAN="2" VALIGN="TOP">IsResilient</TH><TD ROWSPAN="2" VALIGN="TOP">boolean</TD><TD ROWSPAN="2" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">The IsResilient property indicates the recovery procedure to be applied to tunnels whose paths are impacted by faults. More specifically, it contains a boolean value that determines whether the tunnel is to be rerouted or not, when segments of its path fail. If set to true, the tunnel should be rerouted in case of failure; if false, it should not (which means that other means are applied, e.g. lower layer technologies for rerouting.)</TD> </TR> <TR> <TH ROWSPAN="2" VALIGN="TOP">LocalProtectionAvailable</TH><TD ROWSPAN="2" VALIGN="TOP">boolean</TD><TD ROWSPAN="2" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Flag to indicate that transit routers are permitted to use a local repair mechanism which may result in violation of the explicit routing of this tunnel. When a fault is detected on an adjacent downstream link or node, a transit router can reroute traffic for fast service restoration.</TD> </TR> <TR> <TH ROWSPAN="2" VALIGN="TOP">Lockdown</TH><TD ROWSPAN="2" VALIGN="TOP">boolean</TD><TD ROWSPAN="2" VALIGN="TOP">true</TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Indicates whether the tunnel is a candidate for re-optimization at all. If true the ReoptimizationFreq property should be taken into account. By default, a tunnel is re-optimized periodically.</TD> </TR> <TR> <TH ROWSPAN="5" VALIGN="TOP">ReoptimizationFreq</TH><TD ROWSPAN="5" VALIGN="TOP">uint32</TD><TD ROWSPAN="5" VALIGN="TOP">3600</TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Due to changes in network and traffic characteristics, there may be a need to periodically change the paths of tunnels for optimization purposes. This should not be done too frequently as it could adversely affect the stability of the network. This property indicates how often such reoptimization should be performed for a specific tunnel. Note that the class, CIM_MPLSTEService, also has a reoptimization frequency property. The frequency specified in this class is specific to a particular tunnel, whereas the MPLSTEService's frequency is per service, on a Label Switched Router.</TD> </TR> <TR> <TD VALIGN="TOP">MaxValue</TD><TD VALIGN="TOP">sint64</TD><TD VALIGN="TOP">604800</TD> </TR> <TR> <TD VALIGN="TOP">PUnit</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">second</TD> </TR> <TR> <TD VALIGN="TOP">Units</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Seconds</TD> </TR> <TR> <TH ROWSPAN="4" VALIGN="TOP">ReservedBandwidth</TH><TD ROWSPAN="4" VALIGN="TOP">uint32</TD><TD ROWSPAN="4" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Reserved bandwidth for this tunnel in kilobits per second. In a load sharing environment, the bandwidth on each tunnel is set to be proportional to how traffic should be balanced. An LSR then load-shares into the tunnels based on the aggregate bandwidth. Note that it is possible to signal 0 bandwidth for a pure best-effort tunnel.</TD> </TR> <TR> <TD VALIGN="TOP">PUnit</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">bit / second * 10^3</TD> </TR> <TR> <TD VALIGN="TOP">Units</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">KiloBits per Second</TD> </TR> <TR> <TH ROWSPAN="5" VALIGN="TOP">SetupPriority</TH><TD ROWSPAN="5" VALIGN="TOP">uint8</TD><TD ROWSPAN="5" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Guaranteed bandwidth tunnels can have setup and preemption priorities associated with them. These priorities determine if an existing tunnel can be preempted by a new one. The SetupPriority of the new tunnel is compared to the Holding Priority of the established one, to determine if the new tunnel can preempt the existing one. It does preempt if the SetupPriority in smaller than the HoldingPriority. Note that the value 0 is the highest priority.</TD> </TR> <TR> <TD VALIGN="TOP">MappingStrings</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">MIB.IETF|MPLS-TE-MIB.mplsTunnelSetupPrio</TD> </TR> <TR> <TD VALIGN="TOP">MaxValue</TD><TD VALIGN="TOP">sint64</TD><TD VALIGN="TOP">7</TD> </TR> <TR> <TD VALIGN="TOP">MinValue</TD><TD VALIGN="TOP">sint64</TD><TD VALIGN="TOP">0</TD> </TR> <TR> <TH ROWSPAN="2" VALIGN="TOP">TunnelInstancePriority</TH><TD ROWSPAN="2" VALIGN="TOP">uint32</TD><TD ROWSPAN="2" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">This value represents the priority for a tunnel in descending order, with 0 indicating the lowest priority, within a group of tunnels used for redundancy/load sharing. Tunnel group priorities are used to denote the priority at which a particular tunnel instance will supercede another. Instances of tunnels containing the same TunnelInstancePriority will be used for load sharing.</TD> </TR> <TR> <TH ROWSPAN="4" VALIGN="TOP">TunnelManagementOwner</TH><TD ROWSPAN="4" VALIGN="TOP">uint8</TD><TD ROWSPAN="4" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Indicates which protocol created and is responsible for managing this tunnel. Values rsvp(3) and crldp(4) should NOT be used at the head-end of an MPLS tunnel.</TD> </TR> <TR> <TD VALIGN="TOP">ValueMap</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">0, 1, 2, 3, 4, 5</TD> </TR> <TR> <TD VALIGN="TOP">Values</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Unknown, Other, Admin, RSVP, CRDLP, Policy Agent</TD> </TR> <TR> <TH ROWSPAN="4" VALIGN="TOP">TunnelRole</TH><TD ROWSPAN="4" VALIGN="TOP">uint16</TD><TD ROWSPAN="4" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">This property signifies the role that this tunnel entry/instance represents. The value MUST be set to head(2) at the originating point of the tunnel, to transit(3) at transit points along the tunnel (if transit points are supported), and to tail(4) at the terminating point of the tunnel (if tunnel tails are supported).</TD> </TR> <TR> <TD VALIGN="TOP">ValueMap</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">0, 2, 3, 4</TD> </TR> <TR> <TD VALIGN="TOP">Values</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Unknown, Head, Transit, Tail</TD> </TR> <TR> <TH ROWSPAN="4" VALIGN="TOP">TunnelSignalingProtocol</TH><TD ROWSPAN="4" VALIGN="TOP">uint8</TD><TD ROWSPAN="4" VALIGN="TOP"></TD> </TR> <TR> <TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">The signaling protocol, if any, which was used to setup this tunnel.</TD> </TR> <TR> <TD VALIGN="TOP">ValueMap</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">0, 1, 2, 3, 4</TD> </TR> <TR> <TD VALIGN="TOP">Values</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Unknown, Other, None, RSVP, CRLDP</TD> </TR> </TABLE> <H3>Inherited Properties</H3> <TABLE BORDER="1" CELLPADDING="1" WIDTH="60%"> <TR> <TH>Name</TH><TH>Data Type</TH><TH>Class Origin</TH> </TR> <TR> <TH VALIGN="TOP">Caption</TH><TD VALIGN="TOP">string</TD><TD VALIGN="TOP"><a href="CIM_ManagedElement.html">CIM_ManagedElement</a></TD> </TR> <TR> <TH VALIGN="TOP">CommunicationStatus</TH><TD VALIGN="TOP">uint16</TD><TD VALIGN="TOP"><a href="CIM_ManagedSystemElement.html">CIM_ManagedSystemElement</a></TD> </TR> <TR> <TH VALIGN="TOP">Description</TH><TD VALIGN="TOP">string</TD><TD VALIGN="TOP"><a href="CIM_ManagedElement.html">CIM_ManagedElement</a></TD> </TR> <TR> <TH VALIGN="TOP">DetailedStatus</TH><TD VALIGN="TOP">uint16</TD><TD VALIGN="TOP"><a href="CIM_ManagedSystemElement.html">CIM_ManagedSystemElement</a></TD> </TR> <TR> <TH VALIGN="TOP">EnabledDefault</TH><TD VALIGN="TOP">uint16</TD><TD VALIGN="TOP"><a href="CIM_EnabledLogicalElement.html">CIM_EnabledLogicalElement</a></TD> </TR> <TR> <TH VALIGN="TOP">EnabledState</TH><TD VALIGN="TOP">uint16</TD><TD VALIGN="TOP"><a href="CIM_EnabledLogicalElement.html">CIM_EnabledLogicalElement</a></TD> </TR> <TR> <TH VALIGN="TOP">Generation</TH><TD VALIGN="TOP">uint64</TD><TD VALIGN="TOP"><a href="CIM_ManagedElement.html">CIM_ManagedElement</a></TD> </TR> <TR> <TH VALIGN="TOP">HealthState</TH><TD VALIGN="TOP">uint16</TD><TD VALIGN="TOP"><a href="CIM_ManagedSystemElement.html">CIM_ManagedSystemElement</a></TD> </TR> <TR> <TH VALIGN="TOP">InstallDate</TH><TD VALIGN="TOP">datetime</TD><TD VALIGN="TOP"><a href="CIM_ManagedSystemElement.html">CIM_ManagedSystemElement</a></TD> </TR> <TR> <TH VALIGN="TOP">Name</TH><TD VALIGN="TOP">string</TD><TD VALIGN="TOP"><a href="CIM_ManagedSystemElement.html">CIM_ManagedSystemElement</a></TD> </TR> <TR> <TH VALIGN="TOP">OperatingStatus</TH><TD VALIGN="TOP">uint16</TD><TD VALIGN="TOP"><a href="CIM_ManagedSystemElement.html">CIM_ManagedSystemElement</a></TD> </TR> <TR> <TH VALIGN="TOP">OtherEnabledState</TH><TD VALIGN="TOP">string</TD><TD VALIGN="TOP"><a href="CIM_EnabledLogicalElement.html">CIM_EnabledLogicalElement</a></TD> </TR> <TR> <TH VALIGN="TOP">PrimaryStatus</TH><TD VALIGN="TOP">uint16</TD><TD VALIGN="TOP"><a href="CIM_ManagedSystemElement.html">CIM_ManagedSystemElement</a></TD> </TR> <TR> <TH VALIGN="TOP">RequestedState</TH><TD VALIGN="TOP">uint16</TD><TD VALIGN="TOP"><a href="CIM_EnabledLogicalElement.html">CIM_EnabledLogicalElement</a></TD> </TR> <TR> <TH VALIGN="TOP">Status</TH><TD VALIGN="TOP">string</TD><TD VALIGN="TOP"><a href="CIM_ManagedSystemElement.html">CIM_ManagedSystemElement</a></TD> </TR> <TR> <TH VALIGN="TOP">TimeOfLastStateChange</TH><TD VALIGN="TOP">datetime</TD><TD VALIGN="TOP"><a href="CIM_EnabledLogicalElement.html">CIM_EnabledLogicalElement</a></TD> </TR> <TR> <TH VALIGN="TOP">TransitioningToState</TH><TD VALIGN="TOP">uint16</TD><TD VALIGN="TOP"><a href="CIM_EnabledLogicalElement.html">CIM_EnabledLogicalElement</a></TD> </TR> <TR> <TH VALIGN="TOP">AvailableRequestedStates</TH><TD VALIGN="TOP">uint16[]</TD><TD VALIGN="TOP"><a href="CIM_EnabledLogicalElement.html">CIM_EnabledLogicalElement</a></TD> </TR> <TR> <TH VALIGN="TOP">OperationalStatus</TH><TD VALIGN="TOP">uint16[]</TD><TD VALIGN="TOP"><a href="CIM_ManagedSystemElement.html">CIM_ManagedSystemElement</a></TD> </TR> <TR> <TH VALIGN="TOP">StatusDescriptions</TH><TD VALIGN="TOP">string[]</TD><TD VALIGN="TOP"><a href="CIM_ManagedSystemElement.html">CIM_ManagedSystemElement</a></TD> </TR> </TABLE> <h2> <a name="c_methods">Class Methods</a> </h2> <H3>Inherited Class Methods</H3> <TABLE BORDER="1" CELLPADDING="1" WIDTH="60%"> <TR> <TH>Name</TH><TH>Return Type</TH><TH>Class Origin</TH> </TR> <TR> <TH VALIGN="TOP">RequestStateChange</TH><TD VALIGN="TOP">uint32</TD><TD VALIGN="TOP"><a href="CIM_EnabledLogicalElement.html">CIM_EnabledLogicalElement</a></TD> </TR> </TABLE> </body> </html>
