description description-string
no description
config>service>vprn>bgp
config>service>vprn
config>service>vprn>if
config>service>vprn>if>sap
config>service>vprn>if>ipv6 (only supported on the 7210 SAS-Mxp)
config>service>vprn>if>ipv6>dhcp6-relay (only supported on the 7210 SAS-Mxp)
config>service>vprn>bgp
config>service>vprn>bgp>group
config>service>vprn>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command creates a text description stored in the configuration file for a configuration context.
The no form of this command removes the string from the configuration.
Specifies the description character string. Allowed values are any string up to 80 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.
[no] shutdown
config>service>vprn
config>service>vprn>if
config>service>vprn>if>sap
config>service>vprn>if>ipv6 (only supported on the 7210 SAS-Mxp)
config>service>vprn>if>ipv6>dhcp6-relay (only supported on the 7210 SAS-Mxp)
config>service>vprn>bgp
config>service>vprn>bgp>group
config>service>vprn>bgp>group>neighbor
config>service>vprn>spoke-sdp
config>service>vprn>if>vrrp
config>service>vprn>if>ipv6>vrrp
config>service>vprn>if>dhcp
config>service>vprn>if>ipv6>dhcp
config>service>vprn>if>ipv6>ospf
config>service>vprn>if>ipv6>pim
config>service>vprn>if>ipv6>igmp
Supported on all 7210 SAS platforms as described in this document
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.
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 AS number was previously changed, the BGP AS number inherits the new value.
Bindings to an SDP within the service are put into the out-of-service state when the service is shut down. While the service is shut down, all customer packets are dropped and counted as discards for billing and debugging purposes.
A service is regarded as operational providing that one IP Interface SAP and one SDP is operational.
Disables the BGP instance on the specific IP interface. Routes learned from a neighbor that is shut down are immediately removed from the BGP database and RTM. If BGP is globally shut down, all group and neighbor interfaces are operationally shut down. If a BGP group is shut down, all member neighbor interfaces are shutdown operationally. If a BGP neighbor is shut down, only that neighbor interface is operationally shutdown.
On all 7210 SAS platforms, VRRP is created in the no shutdown state.
On the 7210 SAS-Mxp, the protocol is handled as follows.
The configure service vprn if vrrp command instantiates the protocol in the no shutdown state, and resources are allocated to enable the node to process the protocol.
To deallocate resources, you must issue the configure service vprn if vrrp shutdown and configure service vprn if no vrrp commands to allow the node to start up correctly after the reboot. It is not sufficient to only issue a configure service vprn if vrrp shutdown command.
Resources for VRRP are allocated when the VRRP context is enabled, either in the base routing instance or the VPRN service instance. Resources are deallocated when the configuration of the last VRRP context under either base routing instances or VPRN service is removed or shutdown.
On all 7210 SAS platforms, VRRPv3 is created in the no shutdown state.
On the 7210 SAS-Mxp, the protocol is handled as follows.
The configure service vprn if ipv6 vrrp command instantiates the protocol in the no shutdown state, and resources are allocated to enable the node to process the protocol.
To deallocate resources, you must issue the configure service vprn if ipv6 vrrp shutdown and configure service vprn if ipv6 no vrrp commands to allow the node to start up correctly after the reboot. It is not sufficient to only issue the configure service vprn if ipv6 vrrp shutdown command.
The resources for VRRPv3 are allocated when the VRRPv3 context is enabled either in the base routing instance or the VPRN service instance. Resources are deallocated when the configuration of the last VRRPv3 context under either base routing instances or VPRN service is removed or shutdown.
On all 7210 SAS platforms, BGP is created in the no shutdown state.
On the 7210 SAS-Mxp, the protocol is handled as follows.
The configure service vprn bgp command instantiates the protocol in the no shutdown state, and resources are allocated to enable the node to process the protocol.
To deallocate resources, you must issue the configure service vprn bgp shutdown and configure service vprn no bgp commands to allow the node to start up correctly after the reboot. It is not sufficient to only issue a configure service vprn bgp shutdown command.
Resources for BGP are allocated when the BGP context is enabled either in the base routing instance or the VPRN service. Resources are deallocated when the configuration of the last BGP context under either the base routing instance or VPRN service instance is removed and shutdown.
On all 7210 SAS platforms, IGMP is created in the no shutdown state.
On the 7210 SAS-Mxp, the protocol is handled as follows.
The configure service vprn igmp command instantiates the protocol in the no shutdown state, and resources are allocated to enable the node to process the protocol.
To deallocate resources, you must issue the configure service vprn igmp shutdown and configure service vprn no igmp commands to allow the node to start up correctly after the reboot. It is not sufficient to issue only the configure service vprn igmp shutdown command.
Resources for IGMP are allocated when the IGMP protocol is enabled, either in the base routing instance or the VPRN service instance. Resources are deallocated when the configuration of the last IGMP context under either base routing instances or VPRN service is removed or shutdown.
On all 7210 SAS platforms, PIM is created in the no shutdown state.
On the 7210 SAS-Mxp, the protocol is handled as follows.
The configure service vprn pim command instantiates the protocol in the no shutdown state and resources are allocated to enable the node to process the protocol.
To deallocate resources, you must issue the configure service vprn pim shutdown and configure service vprn no pim commands to allow the node to start up correctly after the reboot. It is not sufficient to issue only the configure service vprn pim shutdown command.
Resources for PIM are allocated when the PIM protocol is enabled, either in the base routing instance or the VPRN service instance. Resources are deallocated when the configuration of the last PIM context under either base routing instances or VPRN service is removed or shutdown.
On all 7210 SAS platforms, OSPFv2 is created in the no shutdown state.
On the 7210 SAS-Mxp, the protocol is handled as follows.
The configure service vprn ospf command instantiates the protocol in the no shutdown state, and resources are allocated to enable the node to process the protocol.
To deallocate resource, you must issue the configure service vprn ospf shutdown and configure service vprn no ospf commands to allow the node to start up correctly after the reboot. It is not sufficient to issue only the configure service vprn ospf shutdown command.
Resources for OSPF are allocated when the OSPF protocol is enabled, either in the base routing instance or the VPRN service instance. Resources are deallocated when the configuration of the last OSPF context under either base routing instances or VPRN service is removed or shutdown
When the no shutdown command is issued in the configure>service>vprn>if>dhcp context under the first IPv4 interface configured, in either the base routing instance or VPRN service instance, resources are allocated to enable the node to process the protocol.
The resources are deallocated when you issue the configure service vprn if dhcp shutdown command for the last IPv4 interface configured, in either the base routing instance or VPRN service instance enabled to use DHCP relay (IPv4).
When the no shutdown command is issued in the configure>service>vprn>if>ipv6>dhcp6-relay context under the first IPv6 interface configured in any VPRN service, resources are allocated to enable processing of the protocol by the node.
The resources are deallocated when you issue the configure service vprn if ipv6 dhcp6-relay shutdown command for the last IPv6 interface configured in either the base routing instance or VPRN service instance enabled to use DHCP6 relay.