vprn service-id [customer customer-id] [create]
no vprn service-id
config>service
Supported on all 7210 SAS platforms as described in this document
This command creates or edits a Virtual Private Routed Network (VPRN) service instance.
If the service-id does not exist, a context for the service is created. If the service-id exists, the context for editing the service is entered.
VPRN services allow the creation of customer-facing IP interfaces in the same routing instance used for service network core routing connectivity. VPRN services require that the IP addressing scheme used by the subscriber must be unique between it and other addressing schemes used by the provider and potentially the entire Internet.
IP interfaces defined within the context of an VPRN service ID must have a SAP created as the access point to the subscriber network.
When a service is created, the customer keyword and customer-id must be specified to associate the service with a customer. The customer-id must already exist, having been created using the customer command in the service context. When a service is created with a customer association, it is not possible to edit the customer association. The service must be deleted and recreated with a new customer association.
When a service is created, the use of the customer customer-id is optional to navigate into the service configuration context. Attempting to edit a service with the incorrect customer-id results in an error.
Multiple VPRN services are created to separate customer-owned IP interfaces. More than one VPRN service can be created for a single customer ID. More than one IP interface can be created within a single VPRN service ID. All IP interfaces created within an VPRN service ID belong to the same customer.
The no form of this command deletes the VPRN service instance with the specified service-id. The service cannot be deleted until all the IP interfaces and all routing protocol configurations defined within the service ID have been shut down and deleted.
Specifies the service ID number identifying the service in the service domain. This ID must be unique to this service and may not be used for any other service of any type. The service-id must be the same number used for every 7210 SAS on which this service is defined.
Specifies an existing customer ID number to be associated with the service. This parameter is required on service creation and is optional for service editing or deleting.
[no] allow-export-bgp-vpn
config>service>vprn
7210 SAS-Mxp
This command causes the vrf-export and vrf-target commands to include BGP-VPN routes installed in the VPRN route table. These routes are usually not readvertisable as VPN-IP routes because of split horizon.
When a BGP-VPN route is reexported, the route distinguisher and label values are rewritten according to the configuration of the reexporting VPRN.
This command requires the VPRN context to be shut down and restarted for changes to take effect.
This command can be configured only with VPRN loopback interfaces.
Ensure that routing updates do not loop back to the source when this command is used, otherwise the routes could become unstable.
The no form of this command reverts to the default value.
no allow-export-bgp-vpn
auto-bind-tunnel
config>service>vprn
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure automatic binding of a VPRN service using tunnels to MP-BGP peers.
The user must configure the resolution option to enable auto-bind resolution to tunnels in the TTM. If the resolution option is explicitly set to disabled, auto-binding to tunnels is removed.
If the resolution is set to any, any supported tunnel type in a VPRN context is selected following the TTM preference. If one or more explicit tunnel types are specified using the resolution-filter option, only these tunnel types are selected again following the TTM preference.
The user must set the resolution command to filter to activate the list of tunnel types configured under resolution-filter.
When an explicit SDP to a BGP next hop is configured in a VPRN service (using the configure service vprn spoke-sdp command), it overrides the auto-bind-tunnel selection for that BGP next hop only. There is no support for reverting automatically to the auto-bind-tunnel selection if the explicit SDP goes down. The user must delete the explicit spoke-SDP in the VPRN service context to resume using the auto-bind-tunnel selection for the BGP next hop.
resolution {any | filter | disabled}
config>service>vprn>auto-bind-tunnel
Supported on all 7210 SAS platforms as described in this document
This command configures the resolution mode in the automatic binding of a VPRN service to tunnels to MP-BGP peers.
Keyword that enables the binding to any supported tunnel type in the VPRN context following the TTM preference.
Keyword that enables the binding to the subset of tunnel types configured under resolution-filter.
Keyword that disables the automatic binding of a VPRN service to tunnels to MP-BGP peers.
resolution-filter
config>service>vprn>auto-bind-tunnel
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure the subset of tunnel types that can be used in the resolution of VPRN prefixes within the automatic binding of VPRN services to tunnels to MP-BGP peers.
The following tunnel types are supported in a VPRN context: RSVP, LDP, and segment routing (SR). The BGP tunnel type is not explicitly configured and is therefore implicit. It is always preferred over any other tunnel type enabled in the auto-bind-tunnel context.
[no] ldp
config>service>vprn>auto-bind-tunnel>res-filter
Supported on all 7210 SAS platforms as described in this document
This command specifies the use of LDP tunnel types for the resolution of VPRN prefixes within the automatic binding of VPRN services to tunnels to MP-BGP peers.
When ldp is specified, BGP searches for an LDP LSP with a FEC prefix corresponding to the address of the BGP next hop.
The no form of this command disables the use of LDP tunnel types for the resolution of VPRN prefixes within the automatic binding of VPRN services to tunnels to MP-BGP peers.
no ldp
[no] rsvp
config>service>vprn>auto-bind-tunnel>res-filter
Supported on all 7210 SAS platforms as described in this document
This command specifies the use of RSVP tunnel types for the resolution of VPRN prefixes within the automatic binding of VPRN services to tunnels to MP-BGP peers.
When rsvp is specified, BGP searches for the best metric RSVP LSP to the address of the BGP next hop. This address can correspond to the system interface or to another loopback used by the BGP instance on the remote node. The LSP metric is provided by MPLS in the tunnel table. In the case of multiple RSVP LSPs with the same lowest metric, BGP selects the LSP with the lowest tunnel-id.
The no form of this command disables the use of RSVP tunnel types for the resolution of VPRN prefixes within the automatic binding of VPRN service to tunnels to MP-BGP peers.
no rsvp
[no] sr-isis
config>service>vprn>auto-bind-tunnel>res-filter
7210 SAS-Mxp
This command configures the use of SR-ISIS tunnel types for the resolution of VPRN prefixes within the automatic binding of VPRN service to tunnels to MP-BGP peers.
When this command is specified, an SR tunnel to the BGP next hop is selected in the TTM from the lowest numbered IS-IS instance.
The no form of this command disables the use of SR-ISIS tunnel types for the resolution of VPRN prefixes within the automatic binding of VPRN service to tunnels to MP-BGP peers.
no sr-isis
[no] sr-ospf
config>service>vprn>auto-bind-tunnel>res-filter
7210 SAS-Mxp
This command configures the use of SR-OSPF tunnel types for the resolution of VPRN prefixes within the automatic binding of VPRN service to tunnels to MP-BGP peers.
When sr-ospf is specified, an SR tunnel to the BGP next hop is selected in the TTM from the lowest numbered OSPF instance.
The no form of this command disables the use of SR-OSPF tunnel types for the resolution of VPRN prefixes within the automatic binding of VPRN service to tunnels to MP-BGP peers.
no sr-ospf
autonomous-system as-number
no autonomous-system
config>service>vprn
Supported on all 7210 SAS platforms as described in this document
This command defines the autonomous system (AS) to be used by this VPN routing/forwarding (VRF).
The no form of this command removes the defined AS from this VPRN context.
no autonomous-system
Specifies the AS number for the VPRN service.
enable-bgp-vpn-backup [ipv4] [ipv6]
no enable-bgp-vpn-backup
config>service>vprn
Supported on all 7210 SAS platforms as described in this document
This command enables only imported BGP-VPN routes from the remote PE to be considered when selecting the primary and backup paths. This command is required to support fast failover of ingress traffic from one remote PE to another remote PE.
7210 SAS platforms do not consider multiple paths learned from CE BGP peers when selecting primary and backup paths to reach the CE.
no enable-bgp-vpn-backup
Keyword that allows BGP-VPN routes to be used as backup paths for IPv4 prefixes.
Keyword that allows BGP-VPN routes to be used as backup paths for IPv6 prefixes.
vpls service-name
config>service
config>service>ies>if
config>service>vprn>if
Supported on all 7210 SAS platforms as described in this document
This command, in the IP interface context, is used to bind the IP interface to the specified service name.
The system does not attempt to resolve the provided service name until the IP interface is placed into the administratively up state (no shutdown). When the IP interface is administratively up, the system scans the available VPLS services that have the allow-ip-int-binding flag set for a VPLS service associated with the name. If the service name is bound to the service name when the IP interface is already in the administratively up state, the system immediately attempts to resolve the specific name.
If a VPLS service is found associated with the name and has the allow-ip-int-binding flag set, the IP interface is attached to the VPLS service, allowing routing to and from the service virtual ports when the IP interface is operational.
A VPLS service associated with the specified name that does not have the allow-ip-int-binding flag set, or a non-VPLS service associated with the name, is ignored and is not attached to the IP interface.
If the service name is applied to a VPLS service after the service name is bound to an IP interface and the VPLS service allow-ip-int-binding flag is set at the time the name is applied, the VPLS service is automatically resolved to the IP interface if the interface is administratively up or when the interface is placed in the administratively up state.
If the service name is applied to a VPLS service without the allow-ip-int-binding flag set, the system does not attempt to resolve the applied service name to an existing IP interface bound to the name. To rectify this condition, the flag must first be set, and then the IP interface must enter or reenter the administratively up state.
While the specified service name may be assigned to only one service context in the system, it is possible to bind the same service name to more than one IP interface. If two or more IP interfaces are bound to the same service name, the first IP interface to enter the administratively up state (if currently administratively down) or to reenter the administratively up state (if currently administratively up) when a VPLS service is configured with the name and has the allow-ip-int-binding flag set is attached to the VPLS service. Only one IP interface is allowed to attach to a VPLS service context. No error is generated for the remaining non-attached IP interfaces using the service name.
When an IP interface is attached to a VPLS service, the name associated with the service cannot be removed or changed until the IP interface name binding is removed. Also, the allow-ip-int-binding flag cannot be removed until the attached IP interface is unbound from the service name. Unbinding the service name from the IP interface causes the IP interface to detach from the VPLS service context. The IP interface may then be bound to another service name, or a SAP or SDP binding may be created for the interface using the SAP or spoke-SDP commands on the interface.
Specifies the service name that the system attempts to resolve to an allow-ip-int-binding enabled VPLS service associated with the name. This parameter is required when using the IP interface vpls command. The specified name is expressed as an ASCII string comprised of up to 32 characters. It does not need to already be associated with a service and the system does not check to ensure that multiple IP interfaces are not bound to the same name.
interface ip-int-name
no interface ip-int-name
config>service>ies
config>service>vprn
Supported on all 7210 SAS platforms as described in this document
This command configures a logical IP routing interface for a VPRN. When created, attributes such as an IP address and Service Access Point (SAP) can be associated with the IP interface.
The interface command, under the context of services, is used to create and maintain IP routing interfaces within VPRN service IDs. The interface command can be executed in the context of an IES service ID. The IP interface created is associated with the service core network routing instance and default routing.
Interface names are case sensitive and must be unique within the group of defined IP interfaces defined for config service vprn interface (that is, the network core router instance). Interface names must not be in the dotted decimal notation of an IP address. For example, the name ‟1.1.1.1” is not allowed but ‟int-1.1.1.1” is allowed. Show commands for router interfaces use either interface names or the IP addresses. Use unique IP address values and IP address names to maintain clarity. It could be unclear if the same IP address and IP address name values are used. Although not recommended, duplicate interface names can exist in different router instances.
When a new name is entered, a new logical router interface is created. When an existing interface name is entered, the user enters the router interface context for editing and configuration.
By default, there are no default IP interface names defined within the system. All VPRN IP interfaces must be explicitly defined. Interfaces are created in an enabled state.
The no form of this command removes the IP interface and all the associated configuration. The interface must be administratively shut down before issuing the no interface command.
For IES services, the IP interface must be shut down before the SAP on that interface may be removed.
Specifies the name of the IP interface. Interface names must be unique within the group of defined IP interfaces for config router interface and config service vprn interface commands. An interface name cannot be in the form of an IP address. Interface names can be from 1 to 32 alphanumeric characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
If ip-int-name already exists within the service ID, the context is changed to maintain that IP interface. If ip-int-name already exists within another service ID, an error occurs, and the context is not changed to that IP interface. If ip-int-name does not exist, the interface is created and context is changed to that interface for further command processing.
ingress
config>service>ies>if>vpls
config>service>vprn>if>vlps
Supported on all 7210 SAS platforms as described in this document
Commands in this context define the VPLS routed ip-filter-id optional filter overrides.
[no] enable-table-classification
config>service>vprn>if>vpls>ingress
7210 SAS-Mxp.
This command enables and disables the use of IP DSCP table-based classification to assign forwarding class (FC) and profile on a per-interface ingress basis.
The match-criteria configured in the service ingress policy, which require CAM resources, are ignored. Only meters from the service ingress policy are used (and the meters still require CAM resources). If an IP DSCP classification policy is configured in the VPLS SAP ingress policy, it is not used to assign FC and profile.
The no form of this command disables table-based classification. When disabled, the IP ingress packets within a VPLS service attached to the IP interface use the SAP ingress QoS policy applied to the virtual port used by the packets, when defined.
no enable-table-classification
routed-override-qos-policy policy-id
no routed-override-qos-policy
config>service>vprn>if>vpls>ingress
7210 SAS-Mxp.
This command configures an IP DSCP classification policy that is applied to all ingress packets entering the VPLS service. The DSCP classification policy overrides any existing SAP ingress QoS policy applied to SAPs for packets associated with the routing IP interface. The routed override QoS policy is optional, and when it is not defined or removed, the IP routed packets use the existing SAP ingress QoS policy configured on the VPLS virtual port.
The no form of this command removes the IP DSCP classification policy from the ingress IP interface. When removed, the IP ingress routed packets within a VPLS service attached to the IP interface use the SAP ingress QoS policy applied to the virtual port used by the packets, when defined.
no routed-override-qos-policy
Specifies the ID for the routed override QoS policy. Allowed values are an integer that corresponds to an IP DSCP classification policy previously created in the configure>qos>dscp-classification context.
v4-routed-override-filter ip-filter-id
no v4-routed-override-filter
config>service>ies>if>vpls>ingress
config>service>vprn>if>vpls>ingress
Supported on all 7210 SAS platforms as described in this document
This command specifies an IP filter ID that is applied to all ingress packets entering the VPLS service. The filter overrides any existing ingress IP filter applied to SAPs or SDP bindings for packets associated with the routing IP interface. The override filter is optional, and when it is not defined or is removed, the IP routed packets use the existing ingress IP filter on the VPLS virtual port.
The no form of this command is used to remove the IP routed override filter from the ingress IP interface. When removed, the IP ingress routed packets within a VPLS service attached to the IP interface use the IP ingress filter applied to the packets virtual port, when defined.
Specifies the ID for the IP filter policy. Allowed values are an integer that corresponds to an IP filter policy previously created in the configure>filter>ip-filter context.
igmp
config>service>vprn
7210 SAS-T (network operating mode), 7210 SAS-Mxp
Commands in this context configure IGMP parameters.
interface ip-int-name
no interface
config>service>vprn>igmp
7210 SAS-T, 7210 SAS-Mxp
This command configures IGMP interface parameters.
Specifies the name of the IP interface. Interface names can be from 1 to 32 alphanumeric characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
import policy-name
no import
config>service>vprn>igmp>if
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command imports a policy to filter IGMP packets.
The no form of this command removes the policy association from the IGMP instance.
no import
Specifies the import route policy name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
The specified names must already be defined.
disable-router-alert-check
no disable-router-alert-check
config>service>vprn>igmp>if
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command enables the IGMP router alert check option.
The no form of this command disables the router alert check.
max-sources sources
no max-sources
config>service>vprn>igmp>if
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command specifies the maximum number of sources for which IGMP can have local receiver information, based on received IGMP reports on this interface. When this configuration is changed dynamically to a value lower than the currently accepted number of sources, the sources that are already accepted are not deleted. Only new sources are not allowed.
Specifies the maximum number of sources for this interface.
max-groups value
no max-groups
config>service>vprn>igmp>if
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command specifies the maximum number of groups for which IGMP can have local receiver information based on received IGMP reports on this interface. When this configuration is changed dynamically to a value lower than the currently accepted number of groups, the groups that are already accepted are not deleted. Only new groups are not allowed. By default, there is no limit to the number of groups.
0
Specifies the maximum number of groups for this interface.
static
config>service>vprn>igmp>if
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command tests forwarding on an interface without a receiver host. When enabled, data is forwarded to an interface without receiving membership reports from host members.
[no] group grp-ip-address
config>service>vprn>igmp>if>static
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command adds a static multicast group either as a (*,G) or one or more (S,G) records. Use IGMP static group memberships to test multicast forwarding without a receiver host. When IGMP static groups are enabled, data is forwarded to an interface without receiving membership reports from host members.
When static IGMP group entries on point-to-point links that connect routers to a rendezvous point (RP) are configured, the static IGMP group entries do not generate join messages toward the RP.
Specifies an IGMP multicast group address that receives data on an interface. The IP address must be unique for each static group. The address must be in dotted decimal notation.
[no] source ip-address
config>service>vprn>igmp>if>static>group
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command specifies the source address of the multicast group, which is an IPv4 unicast address. By specifying the source address, a multicast receiver host signals to the router that the multicast group only receives multicast traffic from this specific source.
The source command and the specification of individual sources for the same group are mutually exclusive.
The source command, in combination with the group command, is used to create a specific (S,G) static group entry.
The no form of this command removes the source from the configuration.
Specifies the IPv4 unicast address.
[no] starg
config>service>vprn>igmp>if>static>group
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command adds a static (*,G) entry. This command can be enabled only if no existing source addresses for this group are specified.
The no form of this command removes the starg entry from the configuration.
[no] subnet-check
config>service>vprn>igmp>if
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command enables subnet checking for IGMP messages received on this interface. All IGMP packets with a source address that is not in the local subnet are dropped.
enabled
version version
no version
config>service>vprn>igmp>if
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command specifies the IGMP version. If routers run different versions of IGMP, they negotiate the lowest common version of IGMP that is supported by hosts on their subnet and operate in that version. For IGMP to function correctly, all routers on a LAN should be configured to run the same version of IGMP on that LAN.
For IGMPv3, a multicast router that is also a group member performs both parts of IGMPv3, receiving and responding to its own IGMP message transmissions as well as those of its neighbors.
3
Specifies the IGMP version number.
query-interval seconds
no query-interval
config>service>vprn>igmp
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command configures the frequency that the querier router transmits general host-query messages. The host-query messages solicit group membership information which are sent to the all-systems multicast group address, 224.0.0.1.
125
Specifies the time frequency, in seconds, that the router transmits general host-query messages.
query-last-member-interval seconds
config>service>vprn>igmp
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command configures the frequency at which the querier sends group-specific query messages, including messages sent in response to leave-group messages. The shorter the interval, the faster the detection of the loss of the last member of a group.
1
Specifies the frequency, in seconds, at which query messages are sent.
query-response-interval seconds
config>service>vprn>igmp
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command configures how long the querier router waits to receive a response to a host-query message from a host.
10
Specifies the length of time to wait to receive a response to the host-query message from the host.
robust-count robust-count
no robust-count
config>service>vprn>igmp
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command configures the robust count. The robust-count parameter allows adjusting for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count can be increased.
2
Specifies the robust count value.
igmp
config>service>vprn>igmp
config>service>vprn>igmp>if
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command configures group ranges that are translated to SSM (S,G) entries. If the static entry needs to be created, it must be translated from an IGMPv1 or IGMPv2 request to a Source Specific Multicast (SSM) join request. An SSM translate source can be added only when the starg command is not enabled. An error message is generated when attempting to configure the source command while starg command is enabled.
[no] grp-range start end
config>service>vprn>igmp>ssm-translate
config>service>vprn>igmp>if>ssm-translate
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command configures group ranges that are translated to SSM (S,G) entries.
Specifies an IP address for the start of the group range.
Specifies an IP address for the end of the group range. This value should always be greater than or equal to the value of the start value.
[no] source ip-address
config>service>vprn>igmp>ssm-translate
config>service>vprn>igmp>if>ssm-translate
7210 SAS-T (network operating mode), 7210 SAS-Mxp
This command specifies the source IP address for the group range. Whenever a (*,G) report is received in the range specified by grp-range start and end parameters, it is translated to an (S,G) report with the value of this object as the source address.
Specifies the IP address that is sending data.
maximum-ipv6-routes number [log-only] [threshold percent]
no maximum-ipv6-routes
config>service>vprn
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command configures the maximum number of remote IPv6 routes that can be held within a VRF context. Local, host, static, and aggregate routes are not counted.
The VPRN service ID must be in a shutdown state before the maximum-ipv6-routes command parameters can be modified.
If the log-only keyword is not specified, and the maximum-ipv6-routes value is set below the existing number of routes in a VRF, the offending RIP peer (if applicable) is brought down (but the VPRN instance remains up). BGP peering remains up, but the exceeding BGP routes are not added to the VRF.
The maximum route threshold can dynamically change to increase the number of supported routes, even when the maximum is already reached. Protocols resubmit the routes that were initially rejected.
The no form of this command disables any limit on the number of routes within a VRF context. Issue the no form of this command only when the VPRN instance is shut down.
0 or disabled
Specifies an integer that specifies the maximum number of routes to be held in a VRF context.
Specifies that if the maximum limit is reached, the event only is logged. The log-only keyword does not disable the learning of new routes.
Specifies the percentage at which a warning log message and SNMP trap should be set. There are two warning levels: mid-level and high-level. A mid-level warning occurs when the threshold percent value is reached, and a high-level warning occurs at the halfway level between the maximum number of IPv6 routes and the percent value ([max + mid] / 2).
maximum-routes number [log-only] [threshold percent]
no maximum-routes
config>service>vprn
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command configures the maximum number of remote routes that can be held within a VRF context. Local, host, static, and aggregate routes are not counted.
The VPRN service ID must be in a shutdown state before maximum-routes command parameters can be modified.
If the log-only parameter is not specified and the maximum-routes value is set below the existing number of routes in a VRF, the offending RIP peer (if applicable) is brought down (but the VPRN instance remains up). BGP peering remains up, but the exceeding BGP routes are not added to the VRF.
The maximum route threshold can dynamically change to increase the number of supported routes even when the maximum has already been reached. Protocols resubmit the routes that were initially rejected.
The no form of this command disables any limit on the number of routes within a VRF context. Issue the no form of this command only when the VPRN instance is shut down.
0 or disabled
Specifies the maximum number of routes to be held in a VRF context.
Specifies that if the maximum limit is reached, only log the event. The log-only keyword does not disable the learning of new routes.
Specifies the percentage at which a warning log message and SNMP trap should be set. There are two warning levels: mid-level and high-level. A mid-level warning occurs when the threshold percent value is reached, and a high-level warning occurs at the halfway level between the maximum number of routes and the percent value ([max + mid] / 2).
route-distinguisher [ip-address:number | asn:number]
no route-distinguisher
config>service>vprn
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command sets the identifier attached to routes the VPN belongs to. Each routing instance must have a unique route distinguisher (within the carrier domain) associated with it. A route distinguisher must be defined for a VPRN to be operationally active.
no route-distinguisher
Specifies the IP address in dotted decimal notation. The assigned number must not be greater than 65535.
Specifies the AS number 2-byte value less than or equal to 65535. The assigned number can be any 32-bit unsigned integer value.
router-id ip-address
no router-id
config>service>vprn
config>service>vprn>bgp
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command sets the router ID for a specific VPRN context.
If neither the router ID nor system interface are defined, the router ID from the base router context is inherited.
The no form of this command removes the router ID definition from the specific VPRN context.
no router-id
Specifies the IP address in dotted decimal notation.
service-name service-name
no service-name
config>service>vprn
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command configures an optional service name, up to 64 characters, which adds a name identifier to a specific service to use in configuration references and in show commands throughout the system. This helps the service provider/administrator to identify and manage services within the 7210 SAS platforms.
All services are required to assign a service ID to initially create a service. However, either the service ID or the service name can be used to identify and reference a specific service when it is initially created.
Specifies a unique service name to identify the service. Service names may not begin with an integer (0 to 9).
sgt-qos
config>service>vprn
7210 SAS-Mxp
Commands in this context configure DSCP/dot1p re-marking for select self-generated traffic.
application dscp-app-name dscp {dscp-value | dscp-name}
application dot1p-app-name dot1p dot1p-priority
no application {dscp-app-name | dot1p-app-name}
config>service>vprn>sgt-qos
7210 SAS-Mxp
This command configures DSCP/dot1p re-marking for self-generated application traffic. When an application is configured using this command, the specified DSCP name/value is used for all packets generated by this application within the router instance it is configured. The instances can be base router, VPRN service, or management.
Using the value configured in this command:
Sets the DSCP bits in the IP packet
Maps to the FC
Based on this FC, the egress QoS policy sets the Ethernet 802.1p and MPLS EXP bits. This includes ARP and IS-IS packets that, due to their nature, do not carry DSCP bits.
The DSCP value in the egress IP header is as configured in this command.
Only one DSCP name/value can be configured per application. If multiple entries are configured, the subsequent entry overrides the previously configured entry.
The no form of this command reverts to the default value.
Specifies the DSCP application name.
Specifies a value when this packet egresses the respective egress policy should provide the mapping for the DSCP value to either LSP-EXP bits or IEEE 802.1p (dot1p) bits as appropriate otherwise the default mapping applies.
Specifies the DSCP name.
Specifies the dot1p priority.
Specifies the dot1p application name.
dscp dscp-name fc fc-name
no dscp dscp-name
config>service>vprn>sgt-qos
7210 SAS-Mxp
This command creates a mapping between the DiffServ Code Point (DSCP) of the self-generated traffic and the forwarding class.
Self-generated traffic for configured applications that matches the specified DSCP are assigned to the corresponding forwarding class. Multiple commands can be entered to define the association of some or all 64 DSCPs to a forwarding class.
All DSCP names that define a DSCP value must be explicitly defined.
The no form of this command removes the DSCP-to-forwarding class association.
Specifies the name of the DSCP to be associated with the forwarding class. A DiffServ code point can only be specified by its name and only an existing DiffServ code point can be specified. The software provides names for the well known code points.
Specifies the forwarding class name. Applications and protocols that are configured under the dscp command use the configured IP DSCP value.
snmp-community community-name [version SNMP-version]
no snmp-community [community-name]
config>service>vprn
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command sets the SNMP community name to be used with the associated VPRN instance.
If an SNMP community name is not specified, SNMP access is not allowed.
The no form of this command removes the SNMP community name from the specific VPRN context.
Specifies one or more SNMP community names.
Specifies the SNMP version.
source-address
config>service>vprn
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Commands in this context specify the source address and application that should be used in all unsolicited packets.
application app [ip-int-name | ip-address]
no application app
config>service>vprn>source-address
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command specifies the source address and application.
Specifies the application name.
Specifies the name of the IP interface or IP address. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] {next-hop ip-int-name | ip-address | ipsec-tunnel ipsec-tunnel-name} [bfd-enable | {cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]}]
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] indirect ip-address [cpe-check cpe-ip-address [interval seconds][drop-count count] [log]]
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] black-hole
config>service>vprn
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command creates static route entries within the associated router instance. When configuring a static route, either next-hop, indirect or black-hole must be configured.
The no form of this command deletes the static route entry. If a static route needs to be removed when multiple static routes exist to the same destination, as many parameters to uniquely identify the static route must be entered.
If a CPE connectivity check target address is already being used as the target address in a different static route, cpe-check parameters must match. If they do not, the new configuration command are rejected.
If a static-route command is issued with no cpe-check target but the destination prefix/netmask and next-hop matches a static route that did have an associated cpe-check, the cpe-check test is removed from the associated static route.
Specifies the destination address of the aggregate route in dotted decimal notation.
Specifies the subnet mask in dotted decimal notation.
Specifies the name of the IP interface. Interface names must be unique within the group of defined IP interfaces for config router interface and config service ies interface commands. An interface name cannot be in the form of an IP address. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed with
Specifies the IP address of the IP interface. The ip-addr portion of the address command specifies the IP host address that is used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation.
Static routes can be administratively enabled or disabled. Use the enable parameter to re-enable a disabled static route. To enable a static route, it must be uniquely identified by the IP address, mask, and any other parameter that is required to identify the exact static route.
The administrative state is maintained in the configuration file.
Static routes can be administratively enabled or disabled. Use the disable parameter to disable a static route while maintaining the static route in the configuration. To enable a static route, it must be uniquely identified by the IP address, mask, and any other parameter that is required to identify the exact static route.
The administrative state is maintained in the configuration file.
Specifies the interval between ICMP pings to the target IP address.
Specifies the number of consecutive ping-replies that must be missed to declare the CPE down and to de-active the associated static route.
This optional parameter enables the ability to log transitions between active and in-active based on the CPE connectivity check. Events should be sent to the system log, syslog and SNMP traps.
Specifies the directly connected next hop IP address used to reach the destination. If the next hop is over an unnumbered interface, the ip-int-name of the unnumbered interface (on this node) can be configured.
The next-hop keyword and the indirect or black-hole keywords are mutually exclusive. If an identical command is entered (with the exception of either the indirect or black-hole parameters), this static route is replaced with the newly entered command, and unless specified, the respective defaults for preference and metric are applied.
The ip-addr configured here can be either on the network side or the access side on this node. This address must be associated with a network directly connected to a network configured on this node.
Specifies an IPSec tunnel name up to 32 characters.
Specifies that the route is indirect and specifies the next hop IP address used to reach the destination.
The configured ip-addr is not directly connected to a network configured on this node. The destination can be reachable via multiple paths. The static route remains valid as long as the address configured as the indirect address remains a valid entry in the routing table. Indirect static routes cannot use an ip-prefix/mask to another indirect static route.
The indirect keyword and the next-hop or black-hole keywords are mutually exclusive. If an identical command is entered (with the exception of either the next-hop or black-hole parameters), this static route is replaced with the newly entered command and unless specified the respective defaults for preference and metric are applied.
The ip-addr configured can be either on the network or the access side and is at least one hop away from this node.
Specifies a blackhole route, meaning that if the destination address on a packet matches this static route it is silently discarded.
The black-hole keyword is mutually exclusive with either the next-hop or indirect keywords. If an identical command is entered, with exception of either the next-hop or indirect parameters, the static route is replaced with the new command, and unless specified, the respective defaults for preference and metric are applied.
Specifies the preference of this static route (as opposed to the routes from different sources such as BGP or OSPF), expressed as a decimal integer. When modifying the preference value of an existing static route, unless specified, the metric does not change.
If multiple routes are learned with an identical preference using the same protocol, the lowest cost route is used. If multiple routes are learned with an identical preference using the same protocol and the costs (metrics) are equal, the decision of which route to use is determined by the configuration of the ECMP command.
Specifies the cost metric for the static route, expressed as a decimal integer. This value is used when importing this static route into other protocols such as OSPF. This value is also used to determine the static route to install in the forwarding table: When modifying the metrics of an existing static route, unless specified, the preference does not change.
If there are multiple static routes with the same preference but unequal metrics, the lower cost (metric) route is installed. If there are multiple static routes with equal preference and metrics, ECMP rules apply. If there are multiple routes with unequal preferences, the lower preference route is installed.
Adds a 32-bit integer tag to the static route. The tag is used in route policies to control distribution of the route into other protocols.
Associates the state of the static route to a BFD session between the local system and the configured nexthop. This keyword cannot be configured if the nexthop is indirect or a blackhole keywords are specified.
NOTE: For more information about the protocols and platforms that support BFD, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Router Configuration Guide.
Specifies the IP address of the target CPE device. ICMP pings are sent to this target IP address. This parameter must be configured to enable the CPE connectivity feature for the associated static route. The target-ip-address cannot be in the same subnet as the static route subnet to avoid possible circular references. This option is mutually exclusive with BFD support on a specific static route.
vrf-export policy [policy...]
no vrf-export
config>service>vprn
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command specifies the export policies to control routes exported from the local VPN routing/forwarding (VRF) to other VRFs on the same or remote PE routers (via MP-BGP).
The no form of this command removes all route policy names from the export list.
Specifies the route policy statement name.
vrf-import policy [policy...]
no vrf-import
config>service>vprn
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command sets the import policies to control routes imported to the local VPN routing/ forwarding (VRF) from other VRFs on the same or remote PE routers (via MP-BGP). BGP-VPN routes imported with a vrf-import policy use the BGP preference value of 170 when imported from remote PE routers, or retain the protocol preference value of the exported route when imported from other VRFs on the same router, unless the preference is changed by the policy.
The no form of this command removes all route policy names from the import list.
Specifies the route policy statement name.
vrf-target {ext-community | export ext-community | import ext-community}
no vrf-target
config>service>vprn
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command facilitates a simplified method to configure the route target to be added to advertised routes or compared against received routes from other VRFs on the same or remote PE routers (via MP-BGP).
BGP-VPN routes imported with a vrf-target statement use the BGP preference value of 170 when imported from remote PE routers, or retain the protocol preference value of the exported route when imported from other VRFs in the same router.
Specified vrf-import or vrf-export policies override the vrf-target policy.
The no form of this command removes the vrf-target.
no vrf-target
Specifies an extended BGP community in the type:x:y format. The value x can be an integer or IP address. The type can be the target or origin. x and y are 16-bit integers.
Specifies communities allowed to be accepted from remote PE neighbors.
Specifies communities allowed to be sent to remote PE neighbors.