The following are the limitations of the configuration rollback feature for the 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp:
Resource profile policy changes cannot be rolled back. That is, if there is a change in resource policy/parameters between active configuration and checkpoint, rollback will not proceed.
PTP is not supported.
For SAP ingress QoS, due to the slice information available in the .sdx file, whenever there is a change in ingress QoS policy attached to a SAP, or if there are any additional SAPs in the checkpoint file, all SAPs are torn down and rebuilt. The user will be prompted before this occurs.
A SAP that has a change in egress QoS policy will be shut down and will do a no shutdown after a delay.
During rollback, all ports and SAPs are shut down and brought back up again. This brings down traffic and control protocols that have been initiated or are transitioning through the node during rollback.
Rollback is not permitted when there is a change to port-scheduler-mode.
Back-to-back rollbacks, particularly scaled ones, are not recommended. Users must allow sufficient time for the system to process the current rollback before initiating a new one.
On the 7210 SAS-R6 and 7210 SAS-R12, if there are additional differences in resource profile templates between two rollback points, the rollback procedure does not roll back any changes. An error message is displayed asking the user to undo these resource profile template changes manually.
Rollback is not allowed between two rollback points if there are changes in the slice allocation in the same resource profile template. On the 7210 SAS-R6 and 7210 SAS-R12, the restriction also applies for a template that is not associated with any card.
On the 7210 SAS-R6 and 7210 SAS-R12, if the resource profile templates are the same across two different rollback points but the attachment to the card is different, it may result in resource allocation failures in scaling scenarios.