4. vManage Dash Board Tour (Device
Pane
The Device pane (vSmart, vEdge,
vBond, and vManage status)
displays the up or down status of
the individual devices- First the
vSmart
Click on the number against the
vSmart icon
• Observe reachability ,
Hostname, system IP, Site ID,
Device and Model Type
• Click on the number against
the vEdge icon
• Observe reachability ,
Hostname, system IP, Site ID,
Device and Model Type. Choose
Dash Board
5. Device System Status
The System status provides very useful
information about a device • Click on
the following links and observe the
device characteristics.
• Control Connections
• System Status
• Events
• Troubleshooting
6. From vEdge (Branch 1) Can you
show me how to ping , traceroute
to DC1 and DC2 vEdges , also
check some other parameters.
7. vEdge Health,vEdge and Transport
Health , Top Application and
Application Aware Routing , These
Panes looking very cool to me ,
can you kindly elaborate more on
this .
8. Let’s do feature template for some
time Via vManage and understand
its concept .
9. Plan your Feature or CLI Template.
Before you jump to configuring the vEdge using Feature or CLI templates plan on
the following
1. Identify the device
2. Identify the number of interfaces active
3. Plan for an IP addressing scheme
4. Circuit (transport) connections
5. Serial number of the device
6. Site id
7. Hostname
12. OMP Routing Protocol
• Orchestration of overlay network communication, including connectivity among network
sites, service chaining, and VPN topologies
• Distribution of service-level routing information and related location mappings
• Distribution of data plane security parameters
• Central control and distribution of routing policy
(OMP also advertises policies configured on the vSmart controller that are executed on
vEdge routers, including application-routing policy, cflowd flow templates, and data policy )
13. OMP Route Advertisements
• OMP routes (also called vRoutes)—Prefixes that establish reachability between end points that
use the OMP orchestrated transport network. OMP routes can represent services in a central data
center, services at a branch office, or collections of hosts and other end points in any location of
the overlay network. OMP routes require and resolve into TLOCs for functional forwarding. In
comparison with BGP, an OMP route is the equivalent of a prefix carried in any of the BGP AFI/SAFI
fields.
• Transport locations (TLOCs)—Identifiers that tie an OMP route to a physical location. The TLOC is
the only entity of the OMP routing domain that is visible to the underlying network, and it must be
reachable via routing in the underlying network. A TLOC can be directly reachable via an entry in
the routing table of the physical network, or it must be represented by a prefix residing on the
outside of a NAT device and must be included in the routing table. In comparison with BGP, the
TLOC acts as the next hop for OMP routes.
• Service routes—Identifiers that tie an OMP route to a service in the network, specifying the
location of the service in the network. Services include firewalls, Intrusion Detection Systems (IDPs),
and load balancers. Service route information is carried in both service and OMP routes.
15. OMP Routes
Each vEdge router at a branch or local site advertises OMP routes to the vSmart controllers
in its domain. These routes contain routing information that the vEdge router has learned
from its site-local network.
A vEdge router can advertise one of the following types of site-local routes:
• Connected (also known as direct)
• Static
• BGP
• OSPF (inter-area, intra-area, and external)
16. OMP routes advertise the following
attributes:
• TLOC—Transport location identifier of the next hop for the vRoute. It is similar to the BGP
NEXT_HOP attribute.
• Origin—Source of the route, such as BGP, OSPF, connected, and static, and the metric
associated with the original route.
• Originator—OMP identifier of the originator of the route, which is the IP address from which the
route was learned.
• Preference—Degree of preference for an OMP route. A higher preference value is more
preferred.
• Service—Network service associated with the OMP route.
• Site ID—Identifier of a site within the Viptela overlay network domain to which the OMP route
belongs.
• Tag—Optional, transitive path attribute that an OMP speaker can use to control the routing
information it accepts, prefers, or redistributes.
• VPN—VPN or network segment to which the OMP route belongs.
17. Fun Stuff .. Can you login to all the
devices and show me OMP
Configuration
Please show me , omp peers
omp routes , omp summary …
18. Configure OMP Graceful Restart
Viptela(config-omp)# timers graceful-restart-timer seconds
Advertise Routes to OMP
To configure the routes that the vEdge router advertises to OMP for all VPNs configured on the
router:
vEdge(config-omp)# advertise (bgp | connected | ospf type | static)
To configure the routes that the vEdge router advertises to OMP for a specific VPN on the router:
vEdge(config-vpn-omp)# advertise (aggregate prefix [aggregate-only] | bgp | connected |
network prefix | ospf type | static)
Configure the Number of Advertised Routes
More to OMP ….
19. Configure the OMP Hold Time
Viptela(config-omp)# timers holdtime seconds
The hold time can be in the range 0 through 65535 seconds. The keepalive timer is one-third the
hold time and is not configurable. If the local device and the peer have different hold time
intervals, the higher value is used.
Viptela(config-omp)# send-path-limit number
Configure the Number of Installed OMP Paths
By default, vEdge routers and vSmart controllers advertises up to four equal-cost
route–TLOC tuples for the same route.
You can configure them to advertise from 1 to 16 route–TLOC tuples for the same route:
More to OMP ….
20. Configure the OMP Update Advertisement Interval By default, OMP sends Update
packets once per second. To modify this interval:
Viptela(config-omp)# timers advertisement-interval seconds
The interval can be in the range 0 through 65535 seconds.
Configure the End-of-RIB Timer After an OMP session goes down and then comes back up, an
end-of-RIB (EOR) marker is sent after 300 seconds (5 minutes).
After this maker is sent, any routes that were not refreshed after the OMP session came back up
are considered to be stale and are deleted from the route table. To modify the EOR timer:
Viptela(config-omp)# timers eor-timer seconds
The time can be in the range 1 through 3600 seconds (1 hour).
More to OMP ….
22. TLOC
• TLOC—Transport location identifier of the next hop for the vRoute. It is similar to the BGP
NEXT_HOP attribute.
A TLOC consists of three components:
◦ System IP address of the OMP speaker that originates the OMP route
◦ Color to identify the link type
◦ Encapsulation type on the transport tunnel
TLOC routes advertise the following attributes:
• TLOC private address—Private IP address of the interface associated with the TLOC.
• TLOC public address—NAT-translated address of the TLOC.
• Carrier—An identifier of the carrier type, which is generally used to indicate whether the
transport is public or private.
• Color—Identifies the link type.
23. Continue …
• Encapsulation type—Tunnel encapsulation type.
• Preference—Degree of preference that is used to differentiate between TLOCs that
advertise the same OMP route
• Site ID—Identifier of a site within the Viptela overlay network domain to which the TLOC
belongs.
• Tag—Optional, transitive path attribute that an OMP speaker can use to control the flow
of routing information toward a TLOC. When an OMP route is advertised along with its TLOC,
both or either can be distributed with a community TAG, to be used to decide how send
traffic to or receive traffic from a group of TLOCs.
• Weight—Value that is used to discriminate among multiple entry points if an OMP route is
reachable through two or more TLOCs.
![Configure OMP Graceful Restart
Viptela(config-omp)# timers graceful-restart-timer seconds
Advertise Routes to OMP
To configure the routes that the vEdge router advertises to OMP for all VPNs configured on the
router:
vEdge(config-omp)# advertise (bgp | connected | ospf type | static)
To configure the routes that the vEdge router advertises to OMP for a specific VPN on the router:
vEdge(config-vpn-omp)# advertise (aggregate prefix [aggregate-only] | bgp | connected |
network prefix | ospf type | static)
Configure the Number of Advertised Routes
More to OMP ….](https://image.slidesharecdn.com/vdc-250410061307-63743eeb/85/Virtual-Domain-vipsol2-Technology-with-SDWAN-OMP-Viptela-18-320.jpg)
