Restrictions on a DvR Isolated Controller

The following list identifies restrictions of a DvR isolated Controller:

• A DvR isolated Controller does not connect to the DvR backbone and therefore does not share routes with other DvR domains.

• You cannot configure a shared subnet between two DvR domains that do not have a backbone connection.

• All DvR Controllers within the same domain must have the same role, either all conventional DvR Controllers or all isolated DvR Controllers.

• You cannot enable Multi-area SPB DvR backbone redistribution on a boundary node that operates as a DvR isolated Controller.

• Controllers in the same domain must be of the same type (isolated or regular).
  

  Note

  If you migrate from a conventional DvR deployment to an isolated DvR deployment, or vice versa, there can be a combination of controller types in the domain until the migration is complete.

• You can enable Multi-area SPB DvR backbone redistribution on a boundary node if the home area or remote area includes a DvR isolated Controller.

For more information about DvR Isolated Domains and Configure an Isolated Controller on a DvR Isolated Domain, see DvR Isolated Domains and Configure an Isolated Controller on a DvR Isolated Domain.