8.4. VPRN Services Command Reference for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C

This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.

The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.

Services are created in the administratively down (shutdown) state. When a no shutdown command is entered, the service becomes administratively up and then tries to enter the operationally up state. Default administrative states for services and service entities is described as follows in Special Cases.

The no form of this command places the entity into an administratively enabled state.

If the ASN was previously changed, the BGP ASN inherits the new value.

This command creates a text description stored in the configuration file for a configuration context.

The description command associates a text string with a configuration context to help identify the content in the configuration file.

The no form of this command removes the string from the configuration.

This command enables ECMP only for VPN-IPv4 routes learned through MP-BGP (not PE-CE VPN routes) and configures the number of routes for path sharing; for example, the value 2 means two equal-cost routes are used for cost sharing.

ECMP can be used only for routes learned with the same preference and the same protocol. When more ECMP routes are available at the best preference than configured using the max-ecmp-routes value, the following route selection criteria apply for VPN-IPv4 routes.

The no form of this command disables ECMP path sharing. If ECMP is disabled, and multiple routes are available at the best preference and equal cost, the VPN-IPv4 route selection is based on the following criteria.

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 belongs to the same customer.

By default, no VPRN services instances exist until they are explicitly created.

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.

This command configures an aggregate route.

This command automatically installs an aggregate in the routing table when there are one or more component routes. A component route is any route used for forwarding that is a more specific match to the aggregate.

The use of aggregate routes can reduce the number of routes that need to be advertised to neighbor routers, leading to smaller routing table sizes.

Overlapping aggregate routes may be configured; in this case a route becomes a component of only the one aggregate route with the longest prefix match; for example, if one aggregate is configured as 10.0.0.0/16 and another as 10.0.0.0/24, route 10.0.128/17 would be aggregated into 10.0.0.0/16, and route 10.0.0.128/25 would be aggregated into 10.0.0.0/24. If multiple entries are made with the same prefix and the same mask the previous entry is overwritten.

A standard 4-byte BGP community may be associated with an aggregate route to facilitate route policy matching.

The no form of this command removes the aggregate.

This command enables IP interface binding.

The no form of this command disables IP interface binding.

This command enables the context to configure automatic binding of a VPRN service using tunnels to MP-BGP peers.

The auto-bind-tunnel context configures the binding of VPRN routes to tunnels. 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 command is set to any, any supported tunnel type in the 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 will be 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 (in the configure>service>vprn>spoke-sdp context), 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.

This command configures the resolution mode in the automatic binding of a VPRN service to tunnels to MP-BGP peers.

This command enables the context to 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.

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 the ldp command 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.

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.

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 sr-isis 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.

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.

This command defines the autonomous system (AS) to be used by this VPN routing/forwarding (VRF). This command defines the autonomous system to be used by this VPN routing.

The no form of this command removes the defined AS from this VPRN context.

This command specifies the maximum number of remote routes that can be held within a VPN VRF context. Local, host, static and aggregate routes are not counted.

The VPRN service ID must be in a shutdown state to modify the maximum-routes command parameters.

If the log-only keyword 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 their 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 shutdown.

This command sets the identifier attached to routes the VPN belongs to. Each routing instance must have a unique (within the carrier domain) route distinguisher associated with it. A route distinguisher must be defined for a VPRN to be operationally active.

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.

This command configures an optional service name that adds a name identifier to a specific service to then use that service name in configuration references as well as display and use service names in show commands throughout the system. This helps the service provider or 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.

This command enables the context to configure SNMP parameters for this VPRN.

This command configures the SNMP community names to be used with the associated VPRN instance. These VPRN community names associate SNMP v1/v2c requests with a particular VPRN context and to return a reply that contains VPRN-specific data or limit SNMP access to data in a specific VPRN instance.

VPRN SNMP communities configured with an access permission of “r” are automatically associated with the default access group "snmp-vprn-ro” and the “vprn-view” view (read only). VPRN SNMP communities configured with an access permission of “rw” are automatically associated with the default access group "snmp-vprn” and the “vprn-view” view (read/write).

The community in an SNMP v1/v2 request determines the SNMP context (the VPRN number for accessing SNMP tables) and not the VPRN of the incoming interface on which the request is received. When an SNMP request arrives on VPRN 5 interface “ringo” with a destination IP address equal to the “ringo” interface, but the community in the SNMP request is the community configured against VPRN 101, the SNMP request will be processed using the VPRN 101 context (the response will contain information about VPRN 101). Nokia recommends to avoid using a simple series of vprn snmp-community values that are similar to each other (for example, avoid my-vprncomm-1, my-vprn-comm-2, and so on).

By default, the SNMP community must be explicitly specified.

The no form of this command removes the SNMP community name from the specific VPRN context.

This command enables the context to specify the source address and application that should be used in all unsolicited packets.

This command specifies the source address and application.

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.

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 is 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 will be removed from the associated static route.

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 as are required to uniquely identify the static route must be entered.

This command specifies the export policies to control routes exported from the local VPN VRF to other VRFs on the same or remote PE routers (via MP-BGP).

By default, no routes are exported from the VRF.

The no form of this command removes all route policy names from the export list.

This command sets the import policies to control routes imported to the local VPN 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.

By default, no routes are accepted into the VRF.

The no form of this command removes all route policy names from the import list.

This command enables the context to configure DHCP parameters.

This command instantiates a local DHCP server. A local DHCP server can serve multiple interfaces but is limited to the routing context in was which it was created.

Note: The DHCP server is supported only for craft access for local management of the node. It must not be used as a general purpose DHCP server.

This command enables the sending of “forcerenew” messages.

The no form of this command disables the sending of “forcerenew” messages.

This command configures a DHCP address pool on the router.

This command configures the maximum amount of time that a client can lease the IP address.

The no form of this command reverts to the default value.

This command configures the minimum amount of time that a client can lease the IP address.

The no form of this command reverts to the default value.

This command specifies the desired minimum number of free addresses in this pool.

The no form of this command reverts to the default value.

This command configures the local DHCPv4 server handling of an Option 50 request. Option 50 indicates a client request for a previously allocated message, as described in section 3.2 of RFC 2131, Dynamic Host Configuration Protocol.

When this command is enabled, the address allocation algorithm uses a pool to search for the address specified in Option 10. If the address is not found in the pool, the system returns a DHCP NAK message. If the message is found, the system drops the DHCP packet.

This command configures the offer time.

The no form of this command reverts to the default value.

This command enables the context to configure pool options. The options defined in this context can be overruled if the same option is defined in the local user database.

This command configures specific DHCP options. The option defined in this context can be overruled if the same option is defined in the local user database.

The no form of the removes the option from the configuration.

This command configures the IP address of the DNS server.

This command configures the default domain for a DHCP client that the router uses to complete unqualified hostnames (without a dotted-decimal domain name).

The no form of this command removes the name from the configuration.

This command configures the time the client transitions to a rebinding state.

The no form of this command removes the time from the configuration.

This command configures the time the client transitions to a renew state.

The no form of this command removes the time from the configuration.

This command configures the amount of time that the DHCP server grants to the DHCP client to use a particular IP address.

The no form of this command removes the lease time parameters from the configuration.

This command configures a subnet of IP addresses to be served from the pool. The subnet cannot include any addresses that were assigned to subscribers without those addresses specifically excluded. When the subnet is created, no IP addresses are made available until a range is defined.

This command configures a range of IP addresses to be served from the pool. All IP addresses between the start and end IP addresses are included (other than specific excluded addresses).

This command specifies a range of IP addresses that are excluded from the pool of IP addresses in this subnet.

This command configures the maximum number of declined addresses allowed.

This command configures the minimum number of free addresses in this subnet. If the actual number of free addresses in this subnet falls below this configured minimum, a notification is generated.

This command configures the IP address of the default router for a DHCP client. Up to four IP addresses can be specified.

The no form of this command removes the addresses from the configuration.

This command specifies the subnet-mask option to the client. The mask can either be defined (for supernetting) or taken from the pool address.

The no form of this command removes the address from the configuration.

This command enables the use of gateway IP address (GIADDR) matching. If the gi-address flag is enabled, a pool can be used even if a subnet is not found. If the local-user-db-name is not used, the gi-address flag is used and addresses are handed out by GI only. If a user must be blocked from getting an address, the server maps to a local user database and configures the user with no address.

A pool can include multiple subnets. Because the GIADDR is shared by multiple subnets in a subscriber-interface, the pool may provide IP addresses from any of the subnets included when the GIADDR is matched to any of its subnets. This allows a pool to be created that represents a subnet.

This command configures a local user database for authentication.

This command specifies the route target to be added to the advertised routes or compared against the received routes from other VRFs on the same or remote PE routers. Specified vrf-import or vrf-export policies override the vrf-target policy.

The no form of this command removes the vrf-target.

This command enables the context to configure subscriber management entities. A subscriber is uniquely identified by a subscriber identification string. Each subscriber can have one DHCP session active at any time. Each session is referred to as a subscriber host and is identified by its IP address and MAC address.

Note: On 7210 SAS-K 2F6C4T, the 7x50 subscriber management CLI is inherited to allow users to configure a DHCP address for specific hosts when using DHCP server for local craft access. 7210 SAS platforms do not support subscriber management. In all the commands under this section, in the context of 7210 SAS usage, DHCP subscriber refers to an IP host requesting an IP address.

This command enables the context to configure a local user database.

This command configures IPoE host parameters.

This command configures the mask.

This command defines a DHCP subscriber.

This command configures the IP address definition for the host.

When the user database is from a local DHCP server, this command defines the IP address the server “offers” to the DHCP-client.

When the user database is used for PPPoE authentication, the gi-address parameter cannot be used. A fixed IP address then causes PPPoE to use this IP address. If no IP address is specified, the PPPoE looks for an IP address by other means (in this case, DHCP). If a pool name is specified, this pool is sent in the DHCP request so that it can be used by the DHCP server to determine which address to give to the host.

The no form of this command causes no IP address to be assigned to this host. In a user database referred to from a local DHCP server, creating a host without address information causes the matching client to never receive an IP address.

The no form of this command reverts to the default.

This command configures the selection of GI addresses based on the host entry in local use database.

The gi-address must be a valid address (associated with an interface) within the routing context that received the DHCP message on the access side.

This command specifies the domain name that is appended to a user name in RADIUS-authentication-request messages for the specific host.

This command enables the context to configure host identification parameters.

This command configures the IP address of the DHCP server to which to relay.

The no form of this command removes the DHCP server IP address from the configuration.

The configured DHCP server IP address must reference one of the addresses configured under the DHCP CLI context of an IES or VPRN subscriber.

This command specifies the circuit ID to match.

This command configures a range of encapsulation tags as the host identifications. The encapsulation tag is dot1q or qinq on an Ethernet port.

For dot1q, the start and end tag is single number, ranging from 0 ti 4094; for QinQ, the start and end tag format is x.y, x or y could be “*”, which indicates to ignore the inner or outer tag.

This command can be used only when encap-tag-range is configured as one of the match-list parameters.

The no form of this command removes the values from the configuration.

This command specifies the MAC address to match.

This command specifies the Vendor-Identifying Vendor Option to match. Option 60 is encoded as Type-Length-Value (TLV). The hex-string portion of Option 60 in the received DHCP request is used for matching. Only the first 32 bytes can be defined using this command. If Option 60 included in the message is longer, those bytes are ignored.

The no form of this command reverts to the default.

This command specifies the remote ID of the host.

The no form of this command reverts to the default value.

This command specifies the SAP ID from the Nokia vendor-specific suboption in Option 82 to match.

This command specifies an existing service ID from the Nokia vendor-specific suboption in Option 82 to match.

This command specifies the string from the Nokia vendor-specific suboption in Option 82 to match.

This command specifies the system ID from the Nokia vendor-specific suboption in Option 82 to match.

This command enables the context to configure pool options. The options defined at the host level are overruled if the same option is defined at the local user database level.

This command configures specific DHCP options. The options defined at the host level are overruled if the same option is defined at the local user database level.

The no form of this command removes the option from the configuration.

This command configures the IP address of the default router for a DHCP client. Up to four IP addresses can be specified.

The no form of this command removes the addresses from the configuration.

This command configures the IP address of the DNS server.

This command configures the default domain for a DHCP client that the router uses to complete unqualified host names (without a dotted-decimal domain name).

The no form of this command removes the name from the configuration.

This command configures the time the client transitions to a rebinding state.

The no form of this command removes the time from the configuration.

This command configures the time the client transitions to a renew state.

The no form of this command removes the time from the configuration.

This command configures the amount of time that the DHCP server grants to the DHCP client to use a particular IP address.

The no form of this command removes the lease time parameters from the configuration.

This command specifies the subnet-mask option to the client. The mask can either be defined (for supernetting) or taken from the pool address.

The no form of this command removes the address from the configuration.

This command configures the mask.

This command specifies the type of matching done to identify a host.

This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.

The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.

The no form of this command places the entity into an administratively enabled state.

This command binds a service to an existing Service Distribution Point (SDP). The SDP defines the transport tunnel to which this VPRN service is bound.

The SDP has an operational state that determines the operational state of the SDP within the service; for example, if the SDP is administratively or operationally down, the SDP for the service is down.

The SDP must exist in the config>service>sdp context before it can be associated with a VPRN service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id exists, a binding between the specific sdp-id and service is created.

SDPs must be explicitly associated and bound to a service to allow far-end routers to participate in the service. Alternatively, auto-bind can be used. With auto-bind, no VPRN spoke-SDP configuration is required. When both auto-bind and spoke-sdp are configured, spoke-sdp takes precedence. The spoke-sdp configuration must be undone for auto-bind to take effect.

The no form of this command removes the SDP binding from the service; the SDP configuration is not affected. When the SDP binding is removed, no packets are forwarded to the far-end router.

This command creates a logical IP routing interface for a Virtual Private Routed Network (VPRN). When created, attributes like an IP address and 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 VPRN service ID. The IP interface created is associated with the service core network routing instance and default routing table. The typical use for IP interfaces created in this manner is for subscriber Internet access.

Interface names are case-sensitive and must be unique within the group of IP interfaces defined for config router interface and config service vprn interface. 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 IP addresses. Use unique IP address values and IP address names to maintain clarity. It could be unclear to the user if the same IP address and IP address name values are used. Although not recommended, duplicate interface names can exist in different router instances.

The available IP address space for local subnets and routes is controlled with the config router service-prefix command. The service-prefix command administers the allowed subnets that can be defined on service IP interfaces. It also controls the prefixes that may be learned or statically defined with the service IP interface as the egress interface. This allows segmenting the IP address space into config router and config service domains.

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 IP the interface and all the associated configuration. The interface must be administratively shut down before issuing the no interface command.

For VPRN services, the IP interface must be shut down before the SAP on that interface may be removed. VPRN services do not have the shutdown command in the SAP CLI context. VPRN service SAPs rely on the interface status to enable and disable them.

This command assigns an IP address, IP subnet, and broadcast address format to a VPRN IP router interface. Only one IP address can be associated with an IP interface.

An IP address must be assigned to each VPRN IP interface. An IP address and a mask are used together to create a local IP prefix. The defined IP prefix must be unique within the context of the routing instance. It cannot overlap with other existing IP prefixes defined as local subnets on other IP interfaces in the same routing context within the 7210 SAS.

The local subnet that the address command defines must be part of the services address space within the routing context using the config router service-prefix command. The default is to disallow the complete address space to services. When a portion of the address space is allocated as a service prefix, that portion can be made unavailable for IP interfaces defined within the config>router>interface context for network core connectivity with the exclude option in the config router service-prefix command.

The IP address for the interface can be entered in either CIDR (Classless Inter-Domain Routing) or traditional dotted decimal notation. The show commands display CIDR notation and are stored in configuration files.

By default, no IP address or subnet association exists on an IP interface until it is explicitly created.

Use the no form of this command to remove the IP address assignment from the IP interface. When the no address command is entered, the interface becomes operationally down.

The operational state is a read-only variable and the only controlling variables are the address and admin states. The address and admin states are independent and can be set independently. If an interface is in an administratively up state and an address is assigned, it becomes operationally up and the protocol interfaces and the MPLS LSPs associated with that IP interface are reinitialized.

This command configures the forwarding of directed broadcasts out of the IP interface.

A directed broadcast is a packet received on a local router interface destined for the subnet broadcast address on another IP interface. The allow-directed-broadcasts command on an IP interface enables or disables the transmission of packets destined to the subnet broadcast address of the egress IP interface.

When enabled, a frame destined to the local subnet on this IP interface will be sent as a subnet broadcast out this interface. Care should be exercised when allowing directed broadcasts because it is a well-known mechanism used for denial-of-service attacks.

When disabled, directed broadcast packets discarded at this egress IP interface will be counted in the normal discard counters for the egress SAP.

By default, directed broadcasts are not allowed and will be discarded at this egress IP interface.

The no form of this command disables the forwarding of directed broadcasts out of the IP interface.

This command configures the IP maximum transmit unit (packet) for this interface.

The no form of this command reverts to the default value.

This command configures the associated interface as a loopback interface that has no associated physical interface. As a result, the associated interface cannot be bound to a SAP.

When using mtrace/mstat in a Layer 3 VPN context, the configuration for the VPRN should have a loopback address configured that has the same address as the core instance system address (BGP next hop).

This command enables local proxy ARP. When local proxy ARP is enabled on an IP interface, the system responds to all ARP requests for IP addresses belonging to the subnet with its own MAC address, and therefore becomes the forwarding point for all traffic between hosts in that subnet. When the local-proxy-arp command is enabled, ICMP redirects on the ports associated with the service are automatically blocked.

This command assigns a specific MAC address to a VPRN IP interface. The default is the physical MAC address associated with the Ethernet interface on which the SAP is configured.

The no form of this command reverts the MAC address of the IP interface to the default value.

This command enables proxy ARP on the interface.

This command enables a proxy ARP policy for the interface.

The no form of this command disables the proxy ARP capability.

This command enables remote proxy ARP on the interface.

Remote proxy ARP is similar to proxy ARP. It allows the router to answer an ARP request on an interface for a subnet that is not provisioned on that interface. This allows the router to forward to the other subnet on behalf of the requester. To distinguish remote proxy ARP from local proxy ARP, local proxy ARP performs a similar function but only when the requested IP is on the receiving interface.

This command configures a static address resolution protocol (ARP) entry associating an IP address or an unnumbered address with a MAC address for the core router instance. This static ARP appears in the core routing ARP table. A static ARP can be configured only if it exists on the network attached to the IP interface.

If an entry for a particular IP address or unnumbered address already exists and a new MAC address is configured for the IP address, the existing MAC address will be replaced with the new MAC address.

The no form of this command removes a static ARP entry.

This command sets an IP interface as an unnumbered interface and specifies the IP address to be used for the interface.

To conserve IP addresses, unnumbered interfaces can be configured. The address used when generating packets on this interface is the ip-address parameter configured.

An error message is generated when an unnumbered interface is configured and an IP address already exists on this interface

The no form of this command removes the IP address from the interface, effectively removing the unnumbered property. The interface must be shut down before the no unnumbered command is issued to delete the IP address from the interface or an error message is generated.

This command enables the context to configure IPv6 for an VPRN interface.

The no form of this command disables IPv6.

This command assigns an address to the IPv6 interface.

The no form of this command deletes the specified IPv6 address.

This command configures ICMPv6 parameters for the interface.

This command specifies whether, and how often, ICMPv6 “packet-too-big” messages should be sent. When enabled, ICMPv6 “packet-too-big” messages are generated by this interface.

The no form of this command disables the sending of ICMPv6 “packet-too-big” messages.

This command specifies whether, and how often, ICMPv6 “parameter-problem” messages should be sent. When enabled, ICMPv6 “parameter-problem” messages are generated by this interface.

The no form of this command disables the sending of ICMPv6 “parameter-problem” messages.

This command configures ICMPv6 “redirect” messages. When enabled, ICMPv6 redirects are generated when routes are not optimal on this router, and another router on the same subnetwork has a better route to alert that node that a better route is available should be sent.

The no form of this command disables the sending of ICMPv6 redirect messages.

This command configures the rate for ICMPv6 “time-exceeded” messages.

The no form of this command disables the sending of ICMPv6 “time-exceeded” messages.

This command enables and configures the rate for ICMPv6 host and network destination “unreachables” messages issued on the router interface.

The no form of this command disables the generation of ICMPv6 destination “unreachables” messages on the router interface.

This command assigns the IPv6 link local address to the interface.

This command enables local proxy neighbor discovery on the interface.

The no form of this command disables local proxy neighbor discovery.

This command configures IPv6-to-MAC address mapping on the interface.

The no form of this command deletes IPv6-to-MAC address mapping for the specified IPv6 address.

This command applies a proxy neighbor discovery policy for the interface.

The no form of this command disables the proxy neighbor discovery policy application.

This command enables unicast RPF (uRPF) check on this interface.

The no form of this command disables unicast RPF (uRPF) check on this interface.

This command configures the uRPF check feature (if enabled) to ignore default routes for purposes of determining the validity of incoming packets.

The no form of this command considers the default route to be eligible when performing a uRPF check.