Scribd
Upload
2 views

Template and policy

The document outlines the steps for implementing a hub and spoke topology with a focus on routing and Quality of Service (QoS) policies. It details the creation of a default null0 route in the HUB site to ensure reachability to spoke sites, as well as the configuration of traffic rules and QoS maps. Additionally, it emphasizes the importance of applying these configurations through device templates for effective management.

Uploaded by

rajputarvindkumar64
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views

Template and policy

The document outlines the steps for implementing a hub and spoke topology with a focus on routing and Quality of Service (QoS) policies. It details the creation of a default null0 route in the HUB site to ensure reachability to spoke sites, as well as the configuration of traffic rules and QoS maps. Additionally, it emphasizes the importance of applying these configurations through device templates for effective management.

Uploaded by

rajputarvindkumar64
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 16

Hub and scope topology

Group of interest

Select hub and spoke topology below


No need for any traffic rule now

After that also put one default null0 route into HUB site vpn10 so that this will propagate to spoke site
vpn10 and we have reachability after this change to all spoke site via hub site

We can perfrom hub and spoke via Route basis:- to block route in between spoke sites

Group of interest are same as below

After this select custom Route


Then select sequence type route

In Sequence rule we have lots match condition and action we have to set accordingly our requirement
Select spoke site and action is rejected

Default action accepted


After that leave any traffic rule

Now at last we have to select the site list for which sites we need to apply and direction

All control policy Always apply from vsmart out towards other vEdge route
QOS

First we have to create localized policy in which we are creating class map in group of interest
Now add Qos Map
Just click next and next at the end save the policy by name

Now we have to apply shapping rate into the egress interface via centralized feature template
So we have to push qos map via template…go to the device template in additional template
Now configuration in the device put the same configuration into the interface

Configuration have been pushed into the interface via device template

AS per lab guide

You might also like