Overview Package Class Deprecated Help

svt
VccvTraceDefinition

DEPRECATED: 8.0 R5 - OBSOLETE: Should Not Be Used

Test definition. Represents an OAM:VCCV trace action used to verify the the hop-by-hop connectivity of a service.

public class VccvTraceDefinition

Properties
forwardingClass Specifies the forwarding class the vccv trace used.

type=qos.FcEnum
default=be
Displayed(tab/group)=Forwarding Class (Test Parameters/Test Probe)
initialTimeToLive The TTL value for the VC label of the echo request message for the first hop of the MS-PW for which the results are to be displayed.

type=int
default=1
minimum=1
maximum=255
Displayed(tab/group)=Initial Time To Live
maxTimeToLive The TTL value for the VC label of the echo request message for the last hop of the MS-PW for which the results are to be displayed.

type=int
default=8
minimum=1
maximum=255
Displayed(tab/group)=Maximum Time To Live
mplsTpSendMode Specifies the encapsulation of the launched echo request, when testing an MPLS-TP LSP

type=svt.MplsTpSendMode
default=notApplicable
Displayed(tab/group)=Send Mode (/Test Object/MPLS-TP VCCV Trace)
profile Specifies the profile value that was used with the forwarding class specified in forwardingClass.

type=qos.Profile
default=out
Displayed(tab/group)=Forwarding Profile (Test Parameters/Test Probe)
replyType The method of reply due to the vccv-trace request message.

type=svt.ReplyType
default=controlChannel
Displayed(tab/group)=Reply Type (Test Parameters/VCCV Trace Detail)
targetFecType Specifies the type of downstream FEC (Forward Equivalence Class) segment to be tested

type=svt.TargetFECType
access=read-create
default=none
Displayed(tab/group)=Target FEC Type (/Test Object)
testSubMode Specifies the type of LSP ping or LSP trace route test to perform.

type=svt.TestSubMode
default=unspecified
Displayed(tab/group)=Test Type (/Test Object)
 
Overridden Properties
maxFailures The value of this property indicates the maximum number of consecutive timeouts allowed before terminating the Trace Route request.

minimum=1
packetInterval specifies the time to wait between the transmission of one OAM Echo request and the next. The UNITS are specified by tmnxOamPingCtlIntervalUnits. For example, if tmnxOamPingCtlInterval has the value 1, and tmnxOamPingCtlIntervalUnits has the value 'centiseconds(2)', the interval between OAM Echo requests is 0.01 seconds. The applicability, range, and default value of the interval specified using the tmnxOamPingCtlInterval and tmnxOamPingCtlIntervalUnits pair vary with tmnxOamPingCtlTestMode and tmnxOamIcmpPingCtlRapid, as shown in the following table. tmnxOamPingCtlTestMode Supported Values (sec) Default (sec) 'ethCfmLoopback' 1, 2, .. 10 5 'ethCfmTwoWayDelay' 0.1, 0.2, .. 0.9; 1, 2, .. 10 5 'ethCfmTwoWaySlm' 0.1, 0.2, .. 0.9; 1, 2, .. 10 5 'icmpPing' with RAPID 0.01, 0.02, .. 100.00 0.01 'icmpPing' without RAPID 1, 2, .. 10000 1 'p2mpLspPing' not applicable otherwise 1, 2, .. 10 1

maximum=255
packetSize VCCV Trace is using 88 as the minimum value.

default=88
minimum=88
packetTimeout specifies the size of the OAM Echo message. This parameter is optional and is valid only if tmnxOamPingCtlTestMode has a value of 'sdpPing', 'macPing', 'lspPing', 'vprnPing', 'mfibPing', 'vccvPing', 'icmpPing', 'p2mpLspPing', 'ethCfmLoopback' or 'ethCfmTwoWaySlm'. The minimum, maximum, and default values for the tmnxOamPingCtlTestMode cases are: "The value of tmnxOamPingCtlTimeOut specifies the time-out value, in seconds, to be used during a test run. Timers (with duration configured using the tmnxOamPingCtlTimeOut value) are used in one of two ways during a test run. 1. Per Probe: a timer is started each time a probe is sent. If the timer expires before the probe response arrives, the probe is declared failed. This is the traditional time-out method for a sequence of probes. OR 2. Per Test: a timer is started once per test run, when the last probe of the test run is sent. ANY probe which does not have a response when the timer expires is declared failed. SROS chooses 'Per Probe' or 'Per Test' based on the tmnxOamPingCtlTestMode value. The choice is not configurable. The accepted minimum, maximum, and default values for tmnxOamPingCtlTimeOut depend on tmnxOamPingCtlTestMode, as shown in the following table. The table also shows the timer usage for the test mode. tmnxOamPingCtlTestMode Min Max Def Timer Usage ---------------------- --- --- --- ----------- 'atmPing' 1 10 5 Per Probe 'dnsPing' 1 120 5 Per Probe 'ethCfmLoopback' 1 10 5 Per Probe 'ethCfmTwoWayDelay' 1 10 5 Per Test 'ethCfmTwoWaySlm' 1 10 5 Per Test 'icmpPing' 1 10 5 Per Test 'lspPing' 1 10 5 Per Probe 'macPing' 1 10 5 Per Probe 'mfibPing' 1 100 5 Per Probe 'mtuPing' 1 10 5 Per Probe 'p2mpLspPing' 1 120 10 Per Probe 'sdpPing' 1 10 5 Per Probe 'vccvPing' 1 10 5 Per Probe 'vprnPing' 1 100 5 Per Probe otherwise ......... the value of tmnxOamPingCtlTimeOut is irrelevant

 
Properties inherited from sas.TraceDefinition
assurance, maxFailures, maxHistoryRows, packetInterval, packetSize, packetTimeout, packetsToSend, trapGenerationPolicy
 
Properties inherited from sas.TestDefinition
executionOrder, nePersistent, neSchedulable, probeHistory, publishTopic, sas.ThresholdEventDefinition-Set, testDefinitionmodified
 
Properties inherited from sas.AbstractTest
administrativeState, description, displayedName, failures, globalId, id, lastRunResult, runs, weight
 
Properties inherited from ManagedObject
actionMask, children-Set, deploymentState, isFaultSquelched, name, objectFullName, selfAlarmed
 
Methods inherited from sas.AbstractTest
execute, stop