This section provides information to configure Virtual Private Routed Network (VPRN) services using the command line interface.
The following fields require specific input (there are no defaults) to configure a basic VPRN service:
The following is a sample configuration output of a VPRN service.
This section provides a brief overview of the tasks that must be performed to configure a VPRN service and provides the CLI commands.
Use the following CLI syntax to create a VRPN service. A route distinguisher must be defined in order for VPRN to be operationally active.
The following is a sample VPRN service configuration output.
Refer to VPRN Services Command Reference for CLI syntax to configure VPRN parameters.
The following is a sample VPRN service with configured parameters.
Refer to the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Router Configuration Guide for command descriptions and syntax information to configure router interfaces.
The following is a sample router interface configuration output.
The autonomous system number and router ID configured in the VPRN context only applies to that particular service.
The minimal parameters that should be configured for a VPRN BGP instance are:
VPRN BGP is administratively enabled upon creation. Minimally, to enable VPRN BGP in a VPRN instance, you must associate an autonomous system number and router ID for the VPRN service, create a peer group, neighbor, and associate a peer ASN. There are no default VPRN BGP groups or neighbors. Each VPRN BGP group and neighbor must be explicitly configured.
All parameters configured for VPRN BGP are applied to the group and are inherited by each peer, but a group parameter can be overridden on a specific basis. VPRN BGP command hierarchy consists of three levels:
For example:
Note that the local-address must be explicitly configured if two systems have multiple BGP peer sessions between them for the session to be established.
For more information about the BGP protocol, refer to the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Router Configuration Guide.
A group is a collection of related VPRN BGP peers. The group name should be a descriptive name for the group. Follow your group, name, and ID naming conventions for consistency and to help when troubleshooting faults.
All parameters configured for a peer group are applied to the group and are inherited by each peer (neighbor), but a group parameter can be overridden on a specific neighbor-level basis.
After a group name is created and options are configured, neighbors can be added within the same autonomous system to create IBGP connections and/or neighbors in different autonomous systems to create EBGP peers. All parameters configured for the peer group level are applied to each neighbor, but a group parameter can be overridden on a specific neighbor basis.
Use the syntax to configure VPRN BGP parameters (BGP Configuration Commands).
The following is a sample VPRN BGP configuration output.
Interface names associate an IP address to the interface, and then associate the IP interface with a physical port. The logical interface can associate attributes like an IP address, port, Link Aggregation Group (LAG) or the system.
There are no default interfaces.
Note that you can configure a VPRN interface as a loopback interface by issuing the loopback command instead of the sap sap-id command. The loopback flag cannot be set on an interface where a SAP is already defined and a SAP cannot be defined on a loopback interface.
When using mtrace/mstat in a Layer 3 VPN context then the configuration for the VPRN should have a loopback address configured which has the same address as the core instance's system address (BGP next-hop).
Refer to OSPF Configuration Commands (IPv4 only) for CLI commands and syntax.
The following is a sample VPRN interface configuration output.
A SAP is a combination of a port and encapsulation parameters which identifies the service access point on the interface and within the 7210 SAS. Each SAP must be unique within a router. A SAP cannot be defined if the interface loopback command is enabled.
When configuring VPRN interface SAP parameters, a default QoS policy is applied to each ingress and egress SAP. Additional QoS policies and scheduler policies must be configured in the config>qos context. Filter policies are configured in the config>filter context and must be explicitly applied to a SAP. There are no default filter policies.
The following is a sample VPRN interface SAP configuration output.
In a VPRN interface, each VPN routing instance is isolated from any other VPN routing instance, and from the routing used across the backbone. OSPF can be run with any VPRN, independently of the routing protocols used in other VPRNs, or in the backbone itself. For more information about the OSPF protocol, refer to the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Routing Protocols Guide.
The following is a sample output of the VPRN OSPF previous configuration.
For more information about the OSPF protocol, refer to the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Routing Protocols Guide.
This section describes the service management tasks.
Use the CLI syntax to modify VPRN parameters (VPRN Services Command Reference).
The following is a sample VPRN service configuration output.
An VPRN service cannot be deleted until SAPs and interfaces are shut down and deleted. If protocols and/or a spoke-SDP are defined, they must be shut down and removed from the configuration as well.
Use the following syntax to delete a VPRN service.
Use the following syntax to shut down a VPRN service without deleting any service parameters.
Use the following syntax to re-enable a VPRN service that was shut down.