Vyatta Network OS Documentation

Learn how to install, configure and operate the Vyatta NOS, which helps drive our virtual networking & physical platforms portfolio.

Show Page Sections

VRF Support

This section gives information on VRF command support, and VRF support for the following:

  • DHCP
  • DNS
  • TWAMP

VRF support for SSH

An overview VRF support for SSH and example commands.

You can configure SSH on any routing instance. If you configure SSH without specifying a routing instance, the default routing instance is used.

The following example shows how to configure SSH for the default routing instance.
vyatta@R1# set service ssh listen-address 10.0.0.1 
vyatta@R1# set service ssh port 21
vyatta@R1# run show configuration
service {
    ssh {
        listen-address 10.0.0.1
        port 21
                        }
}

The following example shows the same configuration sequence for the BLUE routing instance.

vyatta@R1# set routing routing-instance BLUE service ssh listen-address 10.0.0.1 
vyatta@R1# set routing routing-instance BLUE service ssh port 21
vyatta@R1# commit
vyatta@R1# run show configuration
routing {
        routing-instance BLUE {
                service {
                        ssh {
                           listen-address 10.0.0.1
                           port 21
                        }
                
                }
        }
}

For more information about SSH and configuring SSH, see Ciena Vyatta Network OS Basic System Configuration Guide .

VRF support for Telnet

AN overview of VRF support for Telnet and example commands.

You can configure Telnet on any routing instance. If you configure Telnet without specifying a routing instance, the default routing instance is used.

When you configure Telnet service in a routing instance, the external user can connect to the vRouter through a Telnet session by using the configuration parameters for that instance.

The Telnet service can be started with parameters that are specified in the configuration. If parameters are not specified, Telnet service starts on the default port (port 23).

The following example shows how to configure Telnet for the default routing instance.

vyatta@R1# set service telnet listen-address 42.42.42.42
vyatta@R1# set service telnet port 1234
vyatta@R1# commit
vyatta@R1# run show configuration
service {
        telnet {
                listen-address 42.42.42.42
                port 1234
        }
}

The following example shows the same configuration sequence for the BLUE routing instance.

vyatta@R1# set routing routing-instance BLUE service telnet listen-address 42.42.42.42
vyatta@R1# set routing routing-instance BLUE service telnet port 1234
vyatta@R1# commit
vyatta@R1# run show configuration
routing {
        routing-instance BLUE {
                service {
                        telnet {
                                listen-address 42.42.42.42
                                port 1234
                        }
                }
        }
}

VRF support for SNMP

VRF support for SNMP, the related configuration and commands.

The vRouter supports the implementation of SNMP on a routing instance, which allows the following associations and configurations:

  • An SNMP client to be associated with a specific routing instance and handle context-based access to MIBs.
  • An SNMP trap target to be associated with a routing instance for sending SNMP notifications that are specific to the routing instance.
  • An SNMP agent to be configured to listen for incoming requests from a specific routing instance.

The SNMP V2 clients are associated with a routing instance by mapping the SNMP community strings with a routing instance, as shown in the following command:

  • set service snmp community <comm-string> [context <routing-instance>]

When a V2 request with a community string that is mapped to a routing instance is received, an SNMP agent retrieves MIB information that is specific to the routing instance.

The SNMP V3 clients are associated with a routing instance by specifying the routing instance as context in their requests. An SNMP agent returns context-based MIB information for these requests.

The SNMP V2 and V3 trap targets can be configured to receive routing instance-specific SNMP notifications. Traps to these targets are sent out on the configured routing instance, as shown in the following sample:

  • set service snmp trap-target <ip-addr> [routing-instance <name>]
  • set service snmp v3 trap-target <ip-addr> [routing-instance <name>]

When no routing instance is configured for a trap target, traps are sent over a default routing instance.

An SNMP agent can be configured to accept client requests from a specific routing instance:

  • set service snmp [routing-instance <name>]

When no routing instance is configured, an SNMP agent listens for client requests on a default routing instance.

Configuring SNMP on a routing instance

The following sections provide examples of configuration mode commands.

Associating an SNMP client on a routing instance

The following configuration associates the commA community string with the RED routing instance and the commB community string with the BLUE routing instance. Only one context name can be mapped to a community, but multiple communities can be mapped to the same context name. A community string that is mapped to a context must have a defined view.

Table 1. Associating an SNMP client on a routing instance
Step Command

Set the SNMP version 1 and version 2 community as commA and context as RED.

vyatta@R1# set service snmp community commA context red

Set the SNMP version 1 and version 2 community as commB and context as BLUE.

vyatta@R1# set service snmp community commB context blue
vyatta@R1# set service snmp view all oid 1

Associate all views with the commA SNMP community.

vyatta@R1# set service snmp community commA view all

Associate all views with the commB SNMP community.

vyatta@R1# set service snmp community commB view all

View the configuration.

vyatta@R1# show service snmp community 
 community commA {
        context red
        view all
 }
 community commB {
        context blue
        view all
 }
vyatta@vyatta#

Associating a trap target with a routing instance

The following configuration associates an SNMPv2 trap target with the 1.1.1.1 IP address on the RED routing instance.
Table 2. Associating SNMPv2 trap targets on a routing instance
Step Command

Set the SNMPv2 trap target with the 1.1.1.1 IP address on the RED routing instance.

vyatta@R1# set service snmp v2 trap-target 1.1.1.1 routing-instance red

Define the test community configuration node.

vyatta@R1# set service snmp v2 trap-target 1.1.1.1 community test

Commit the configuration.

vyatta@R1# commit

View the configuration.

vyatta@R1# show service snmp v2 trap-target
 trap-target 1.1.1.1 {
        community test
        routing-instance red
 }
vyatta@vyatta#

The following configuration associates an SNMPv3 trap target with IP address 2.2.2.2 on the RED routing instance.

Table 3. Associating an SNMPv3 trap target on a routing instance
Step Command

Set the SNMPv3 trap target with the 2.2.2.2 IP address on the RED routing instance.

vyatta@R1# set service snmp v3 trap-target 2.2.2.2 routing-instance red

Define the usr2 SNMPv3 user.

vyatta@R1# set service snmp v3 trap-target 2.2.2.2 user usr2

Define a cleartext password to authenticate a user.

set service snmp v3 trap-target 2.2.2.2 auth plaintext-key "usr2usr2"

Commit the configuration.

vyatta@R1# commit

View the configuration.

vyatta@R1# show service snmp v3 trap-target
 trap-target 2.2.2.2 {
        auth {
                plaintext-key "********"
        }
        user usr2
        routing-instance red
 }
vyatta@vyatta#

Configuring an SNMP agent to listen on a routing instance

The following configuration shows how to configure an SNMP agent to listen for incoming requests from the RED routing instance.

Table 4. Configuring an SNMP agent on a routing instance
Step Command

Set an SNMP agent to listen for incoming requests from the RED routing instance.

vyatta@R1# set service snmp routing-instance red

View the configuration.

vyatta@R1# show service snmp routing-instance 
 routing-instance red
vyatta@vyatta#

Supported VRF-aware SNMP MIBs

The following table lists the VRF aware SNMP MIBs and traps that are supported by the vRouter.

Table 5. Supported VRF aware SNMP MIBs

MIB Name

Document Title

OIDs

Notes

IP-MIB

RFC 4113, Management Information Base for the User Datagram Protocol (UDP)

1.3.6.1.2.1.4

The following tables are VRF aware:
  • ipAddrTable (1.3.6.1.2.1.4.20)
  • inetCidrRoute (1.3.6.1.2.1.4.21);
  • ipIfStatsTable (1.3.6.1.2.1.4.31)
  • ipAddressPrefixTable (1.3.6.1.2.1.4.32)
  • ipAddressTable (1.3.6.1.2.1.4.34)
  • ipDefaultRouteTable (1.3.6.1.2.1.4.37)

IPV6-MIB

RFC 2465, Management Information Base for IP Version 6

1.3.6.1.2.1.55.1

The following tables are VRF aware:
  • ipv6IfTable (1.3.6.1.2.1.55.1.5)

IP-FORWARD-MIB

RFC 4292, IP Forwarding Table MIB

RFC 2096, IP Forwarding Table MIB

1. .3.6.1.2.1.4.24

The following tables are VRF aware:
  • inetCidrRouteTable (1.3.6.1.2.1.4.24.7)
  • ipCidrRouteTable (1.3.6.1.2.1.4.24.4)
Note: For non-default VRF context, the above MIBs are read-only, and the variables of these MIBs cannot be set or modified.

Command support for VRF routing instances

Use the guidelines in this section to determine correct syntax when adding VRF routing instances to commands. For more information about VRF, refer to . This guide includes an overview of VRF, VRF configuration examples, information about VRF-specific features, and a list of commands that support VRF routing instances.

Adding a VRF routing instance to a Configuration mode command

For most Configuration mode commands, specify the VRF routing instance at the beginning of a command. Add the appropriate VRF keywords and variable to follow the initial action (set, show, or delete) and before the other keywords and variables in the command.

Configuration mode example: syslog

The following command configures the syslog logging level for the specified syslog host. The command does not include a VRF routing instance, so the command applies to the default routing instance.

vyatta@R1# set system syslog host 10.10.10.1 facility all level debug
vyatta@R1# show system syslog
syslog {
    host 10.10.10.1 {
            facility all {
                    level debug
            }
    }
}

The following example shows the same command with the VRF routing instance (GREEN) added. Notice that routing routing-instance GREEN has been inserted between the basic action (set in the example) and the rest of the command. Most Configuration mode commands follow this convention.

vyatta@R1# set routing routing-instance GREEN system syslog host 10.10.10.1 facility all level debug
vyatta@R1# show routing 
routing {
     routing-instance GREEN {
             system {
                     syslog {
                            host 11.12.13.2:514 {
                                     facility all {
                                             level debug
                                     }
                             }
                     }
             }
     }
}

Configuration mode example: SNMP

Some features, such as SNMP, are not available on a per-routing instance basis but can be bound to a specific routing instance. For these features, the command syntax is an exception to the convention of specifying the routing instance at the beginning of Configuration mode commands.

The following example shows how to configure the SNMPv1 or SNMPv2c community and context for the RED and BLUE routing instances. The first two commands specify the RED routing instance as the context for community A and BLUE routing instance as the context for community B. The subsequent commands complete the configuration.

For more information about configuring SNMP, refer to Ciena Vyatta Network OS Remote Management Configuration Guide.

vyatta@R1# set service snmp community commA context RED
vyatta@R1# set service snmp community commB context BLUE
vyatta@R1# set service snmp view all oid 1
vyatta@R1# set service snmp community commA view all
vyatta@R1# set service snmp community commB view all
vyatta@R1# show service snmp community 
 community commA {
        context RED
        view all
 }
 community commB {
        context BLUE
        view all
 }
[edit]
vyatta@vyatta#

Adding a VRF routing instance to an Operational mode command

The syntax for adding a VRF routing instance to an Operational mode command varies according to the type of command parameters:

  • If the command does not have optional parameters, specify the routing instance at the end of the command.
  • If the command has optional parameters, specify the routing instance after the required parameters and before the optional parameters.

Operational mode examples without optional parameters

The following command displays dynamic DNS information for the default routing instance.

vyatta@vyatta:~$ show dns dynamic status

The following command displays the same information for the specified routing instance (GREEN). The command does not have any optional parameters, so the routing instance is specified at the end of the command.

vyatta@vyatta:~$ show dns dynamic status routing-instance GREEN

Operational mode example with optional parameters

The following command obtains multicast path information for the specified host (10.33.2.5). A routing instance is not specified, so the command applies to the default routing instance.

vyatta@vyatta:~$ mtrace 10.33.2.5 detail

The following command obtains multicast path information for the specified host (10.33.2.5) and routing instance (GREEN). Notice that the routing instance is specified before the optional detail keyword.

vyatta@vyatta:~$ mtrace 10.33.2.5 routing-instance GREEN detail

Operational mode example output: SNMP

The following SNMP show commands display output for routing instances.

vyatta@vyatta:~$ show snmp routing-instance 
Routing Instance SNMP Agent is Listening on for Incoming Requests:
Routing-Instance            RDID
-----------------           ----
RED                         5

vyatta@vyatta:~$ show snmp community-mapping
SNMPv1/v2c Community/Context Mapping:
Community                   Context
---------                   -------
commA                       'RED'
commB                       'BLUE'
deva                        'default'


vyatta@vyatta:~$ show snmp trap-target 
SNMPv1/v2c Trap-targets:
Trap-target                   Port   Routing-Instance Community
-----------                   ----   ---------------- ---------
1.1.1.1                              'RED'           'test'


vyatta@vyatta:~$ show snmp v3 trap-target
SNMPv3 Trap-targets:
Trap-target                   Port   Protocol Auth Priv Type   EngineID              Routing-Instance User
-----------                   ----   -------- ---- ---- ----   --------              ---------------- ----
2.2.2.2                       '162'  'udp'    'md5      'infor                       'BLUE'           'test'