0% found this document useful (0 votes)
17 views5 pages

Orchestrator Overview

Navigating the VCO- Velocloud Orchestrator

Uploaded by

mwilson
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
0% found this document useful (0 votes)
17 views5 pages

Orchestrator Overview

Navigating the VCO- Velocloud Orchestrator

Uploaded by

mwilson
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/ 5

Navigating the VCO- Velocloud Orchestrator

Monitoring your Velocloud Appliances:

Monitor Tabs

 Network Overview
o Here, you can view the status of all sites. For more detail, click on one and see below:
 Edge Overview
o This tab is where you will be able to see what WAN connections are connected and their
status, online (green), offline(red), degraded(yellow), standby(grey) or unknown status
o On the right, you will be able to see the bandwidth that the router is either auto-
detecting or is hard coded to provide for a tunnel; up and down arrows show which is
upload and which is download.
o Further right, you can enable of disable alerts for a particular connection.
 QoE
o This tab is where you’ll be able to see the quality of the connections on each line. Green
is good, yellow means trouble or minor degradation and red is trouble; any connection
in standby-only mode will show as red or white. You can hover over the line to show the
cause of the trouble, latency, jitter or packet loss.
o Toggling between Voice, Video and Transactional traffic types may show different
results; issues on one and not the other, etc.
 Transport
o This tab is where you can see the amount of traffic being put through any connection at
any given time, the time ranges are also customizable. You can also select to Start Live
Monitoring to see the traffic flow in real-time. The page will default to bytes
received/sent, but you can change this drop down to however you prefer to view the
data, such as Average Throughput.
 Applications
o This is where you can view the “top talkers” for applications, websites and other
destinations of traffic such as Cloud backups and data transfers. You can expand the
drop down at the bottom to view more of the list or all of the list, to see more detail of
the traffic and how much bandwidth it has used over a customizable period of time.
 Sources
o This is where you’ll be able to see the source of traffic, however if traffic is behind a
device with security enabled such as a Firewall, you may only see the MAC/IP of the
Firewall or other device, versus individual devices. This will also show voice traffic, up to
and including individual phones on the network.
 Destinations
o This is where you will be able to view the “top talkers” in IP/Domain format, versus just
an application or traffic tyle
 Business Priority
o This is where you can view the traffic based on it’s priority classification (from Business
Policies)
 System
o Here, you can view system stats and health, such as CPU Percentage, Flow counts,
Memory Usage and more.

Network Services

 Here, you will be able to see any Cloud VPN tunnels to non-Velocloud sites, BGP Stats and VNFs.
 Routing
o Here, you can view and manage multi-cast settings.
 Alerts
o This is where you will be able to view the logs of any alerts that were generated and
emailed out.
 Events
o This is where you will see all events, such as link drops and restorations, logins from
users, changes that were made and by whom, updates and devices re-registering on the
network.
 Reports
o This is where you can generate reports, however it is a new feature with limited
capability at this time.

Making Changes:

Configure

 Here you will select which Device you would like to change or view the configuration.

For changes to more than one device at a time, please select Profiles instead of Edges

 Edge Overview
o Here, you can set the name of the device, enable or disable alerting for a device, select
what profile it’s associated with, if there’s more than one in production, as well as
generate re-activation keys if necessary and when provisioning.
 TPx standard naming conventions are the prefix XO or XC (Optimum or Core
contract level) followed by the install order number and the street address or
city. These can be customized to customer preference, though TPx prefers to
have the prefix and order number left intact for easier reference into the
ticketing systems etc.
 Device
o Here, we can view and create configurations on the device level. Options involve Cloud
VPN, Static Routes, ICMP, BGP, SNMP, VLANs, Sub interfaces and WAN connections as
well as port associations and segmentation. To add/remove, view or edit MAC
reservations, select to Edit the VLAN.
 NOTE: The Management IP is used for remote and local access into the device,
this needs to be set, however it CAN be changed to align with a subnet in use on
the LAN, if needed.
 NOTE: The Wi-Fi Radio function does work, however is not considered a
supported feature at this time.
 Business Policy
o This is where we can view and create traffic shapers and custom policies. Here, we can
link steer traffic, prioritize, or throttle specific traffic and more.
 During provisioning, TPx will prioritize voice traffic by default and potentially put
in rules to further prioritize/link steer remote access.

You cannot edit the Rules From Profile* section on this page and will need to do so from
the Profile level, by going to Configure, Profiles, then selecting the profile and the
Business Policy tab there.

 Firewall
o This is where we can configure more specific rules for blocking/allowing traffic as well as
managing Port Forwards and 1:1 NATs. TPx will configure forwards during provisioning
for access to the voice equipment and TPx managed Firewalls, if necessary.

Profiles

 Overview
o This is where you can see the segments assigned to a profile as well as the device
models that are selected to be enabled to use the profile.
 Device
o This is similar to the device tab on the device level, however the options are fewer, as
many require being tailored to the individual device.
 Business Policy
o Here we can edit the policies, as stated in the Device section, that are set on the profile
and create new policies that will apply to all devices using a profile, versus creating them
on individual edges.
 Firewall
o Here we can edit the Firewall Rules to allow or drop tagged traffic, but other changes
such as port forwards and 1:1 NATs need to be completed at the device level.
Segments

 Here we manage segmentation for the LAN, if necessary. All sites by default will receive
a Voice and Global Segment when provisioned. Public, Internet and Custom Segments
can be added at any time.
o Note: If a multi-site build has subnets on different segments such as one on the
Global segment only and one on the Internet segment only, site to site
connectivity will not work and testing on the Remote Diagnostics page will cause
an error saying that Branch-to-Branch VPN is Disabled.

Overlay Flow Control

 Here we can view subnets, static routes and learned routing. This is a great location to
find what location a subnet lives at, in a multi-site setup, versus going site by site
through device configurations.

Network Services

 Here you can view and configure Edge Clusters, Non-Velocloud sites (tunnel
connections), VNFs, DNS services (not the DNS settings for the individual subnets) and
more

Alerts and Notifications

 This is where we select the alerting thresholds, what events will trigger an alert and the
recipients list. TPx will input [email protected] and [email protected] or
[email protected] when setting up alerting, to verify alerts will reach the
repair teams. Time thresholds are currently defaulted to 3 minutes for link disconnects,
device disconnects, and VPN tunnel disconnects. High Availability customers will also
have Edge HA Failover selected. These alerts can be customized to a customer’s
preference; however they are at the profile level and cannot be individualized per
device.

Customer

 This is where we can enable segmentation, NFV’s, update Firmware and the Partner
Handoff/Gateway pools. Most options on this page require engaging TPx Engineers.

Test and Troubleshoot

Remote Diagnostics

 To access the diagnostic tools for each site, select the individual router you would like
from the list.

The diagnostics page will take up to a minute or two to load.


o This is where we can view the ARP table, by clicking the Dump ARP button after
toggling the drop down to select the maximum number of entries you’d like to
view. 100, 500 or 1000.
o You can Clear the ARP Cache for individual VLANs and WAN interfaces by
selecting the interface from the drop-down and clicking the button that says
Run.
o You can do a DNS lookup on a hostname, restart DNS/DHCP services if a subnet
that manages DHCP/DNS is not properly updating or needs a change pushed
o Flushing flows can be done without selecting a particular source/destination IP
to flush all flows and force it to re-establish and re-classify, and can be used to
re-establish VPN tunnels after an outage or force Business Policies to apply after
creation and more. NOTE: This may cause a brief blip in service and could
potentially cause a VPN to need to be reconnected, or a phone call to drop.
o You can flush the NAT table, view the Interface Status for both switched and
routed interfaces (True for a device is connected and False for an unused port;
an SFP module installed will show as True, even if a cable is not connected to
the module)
o We can also ping test from the VLANs to verify connectivity as well as perform
traceroutes and view system health.
o This is also where we can test if the CloudVPN tunnels are connected and view
the latency between sites.
o After changing bandwidth or adding/removing circuits, you can also retest WAN
Bandwidth on this page for circuits set to auto-detect bandwidth, to re-read the
bandwidth allocation from the hand-off.
 Remote Actions
o Here we can select to reboot devices, restart the TPx service (shorter than
reboot, but will trigger an HA Failover event), Identify, Shutdown or Deactivate.
All actions will request confirmation.
 Diagnostic Bundles
o Here we are able to request PCAPs(Packet Captures) and Diagnostic Bundles to
be locally downloaded and analyzed (recommend using Wireshark for opening
the files). They are typically saved for up to six months but can manually
remove if needed or adjust the retention time.

Administration

 The options in this section are managed by TPx – up to and including managing
customer users and authentication

TPx also provides this Portal Guide to assist with learning to Navigate the Platform:

tpx.com/support/sd-wan-training-guide-for-velocloud/

You might also like