When a user VR is created, no resources are allocated for routing protocols. You must add the routing protocols needed for your VR before you attempt to configure them. The maximum number of protocols supported is 64.
This provides for the following protocols:
- The basic seven protocols on VR-Default (RIP, OSPF, BGP, PIM, ISIS, OSPFv3, and R.png)
- 1 MPLS protocol instance on any VR (only on platforms that support MPLS)
- 56 additional protocols for user VRs. Any combination of the 7 protocols supported on user VRs (RIP, OSPF, BGP, PIM, ISIS, OSPFv3, and R.png) can be assigned to user VRs, up to a maximum number of 56.
When you add a protocol to a user VR, the software starts a process to support the protocol, but it does not enable that protocol. After you add a protocol to a user VR, you must specifically enable and configure that protocol before it starts.
When you add a protocol to a VRF, a protocol process is started in the parent VR (if it is not already started) and a protocol instance is created inside that process for this VRF.
You must add, configure, and enable a protocol for a VR before you start unicast or multicast forwarding on the VR and before you configure any features (such as VLANs) to use the VR.
- To add a protocol to a VR, use the command:configure vr vr_name [add | delete] protocol [ospf | ospf3 | rip | r.png | bgp | isis | pim]
If you add more than the maximum number of protocols, the following message appears:Error: Maximum number of Protocols that can be started in the system is 64
- To remove a protocol from a VR, use the command:configure vr vr-name delete protocol protocol-name