VRF support for TWAMP
The vRouter supports the configuration of a TWAMP service for individual routing instances and the operation of the twping TWAMP client in the context of a specified routing instance.
To specify the routing instance in which a TWAMP server runs, use the optional routing routing-instance routing-instance keywords and variable. For example, the following command configures a TWAMP server to run in the BLUE routing instance.
$ set routing routing-instance BLUE service twamp serverIf you do not specify a routing instance, the TWAMP server runs in the context of the default routing instance.
TWAMP message logging
TWAMP messages that are logged by twampd in the context of a user-configured routing instance are prepended with the name of the instance, as shown in the following example. In this example, the log message was logged in the context of the GREEN routing instance.
Apr 08 07:31:24 vm-next-1 twampd[22829]: [twampd@green.service] StartSessions 1 sessionsTWAMP messages that are logged by twampd in the context of the default routing instance do not specify the name of the instance, as shown in the following example.
Apr 05 15:32:47 vm-torrance-1 twampd[5149]: StartSessions 1 sessionstwping RPC VRF support
When making twping RPC calls, you can specify a routing instance, as specified by the leaf definition of the routing instance in the YANG model.
leaf routing-instance {
description "The routing instance context for this session";
type routing:routing-instance-name;
default "default";
}The following is an example of a twping RPC call.
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="3">
<twping xmlns="urn:vyatta.com:mgmt:vyatta-service-twamp:1">
<host>10.10.3.2</host>
<routing-instance>blue</routing-instance>
</twping>
</rpc>]]>]]>