The network administrator can create a template that will be applied when the system goes into maintenance mode. This allows
the administrator to isolate specific protocols. All instances that need to be isolated must be explicitly specified.
The admin can create multiple templates with different configurations. However, only a single template will be applied to
the maintenance mode CLI. Once applied, the template cannot be updated. If the template needs to be updated, then you must
remove it, make the changes, and then re-apply.
Starting from Cisco IOS XE Fuji 16.9.1 release, support has been added to service protocols belonging to one class within a template in parallel. The priority order
of the protocols will be the same as that of the default template. To configure this feature, enter the maintenance mode using
the system mode maintenance command and enable the functionality using the templatetemplate-namecalss command.
For example if the custom template has the following protocols:
Maintenance-template foo
router isis 100
hsrp Et0/1 1
hsrp Et0/1 2
router isis 200
Maintenance-template foo class
router isis 100
hsrp Et0/1 1
hsrp Et0/1 2
router isis 200
In the above example, since isis belongs to CLASS_IGP, router isis 100 & router isis 200 will be serviced in parallel. Once
acks are received for both these protocols belonging to IGP class, FHRP_CLASS clients, hsrp Et0/1 and hsrp Et0/1 2 will be
serviced in parallel.
When the template-class feature is configured, the protocols follow an order based on the class they belong to when entering
maintenance mode. The protocols follow the opposite order when returning to normal mode.