This guide is relevant if your core is on premise. After receiving the VeloCloud SD-WAN Device in the mail, follow the instructions below to install the device.
VeloCloud model numbers:
Velocloud 510 - GE4 is the WAN interface and GE1 is the LAN interface.
Velocloud 640- GE6 is the WAN interface and GE1 is the LAN interface.
Additional Notes:
Velocloud units can sit on a standard 19” 2u rackmount shelf.
The cables output is 100v - 240v and the power cable included is rated up to 300v.
Plug in process:
Prepare your WAN network
Review this sample network diagram that describes the connection. Feel free to ask any questions.
Ensure the network is open to the internet
Ensure needed ports are open to the internet and back to the Janusea orchestrator
Plug in device
Consider enabling a network log to observe tunnel formation for troubleshooting purposes
Plug in GE4/6 to the WAN port and GE1 to the LAN interface
If network is configured correctly, you will see a green light in 3-4 minutes. If not or you will see a red light, power-down before 5 minutes. Otherwise, the device will revert to prior DHCP configuration.
After a green light Janusea will confirm the connection as well.
Janusea Velocloud – we NAT traffic from 172.29.100.177 Janusea IP address to the core IP address that the CU provides
LAN connectivity
Prerequisite: FI networking is in place to route to the core and back
When ready Janusea will run a telnet test
Success will confirm networking to the core and back to the Velocloud device.
Good response from core API
Additional tests will be run to confirm a good response from the core api
Additional information may be needed here (e.g. Core api certificate)
Excerpt from provided network sample diagram:
This is a sample configuration for the Janusea Edge Device configured for an internal IP to access the Internet:
The Janusea Edge Device has a Private IP and exists entirely on the internal side of the client network. The GE4 (WAN) interface IP address must NAT out to the Internet with a public IP, allowing UDP ports 53 and 2426 and TCP ports 123 and 443. An inbound NAT
with the same public IP must allow UDP port 2426.
In the example diagram below, the internal IP of the WAN interface is 10.90.0.5. The GE1 (LAN) interface must communicate with the client firewall. The firewall must allow traffic from the LAN interface to source from the NAT address of 172.29.100.41 with a destination of the client core IP 192.168.1.10 using whatever ports are needed for the allowed communication. All routing devices between the Janusea Edge Device and the core must be able to route back to 172.29.100.40/29.
Please re-verify that port 2426 is open for both inbound and outbound traffic from the Velocloud.
Note: The GE4/6 (WAN) interface IP address must NAT out to the Internet with a public IP, allowing UDP ports 53 and 2426 and TCP ports 123 and 443. An inbound NAT
with the same public IP must allow UDP port 2426.
Notes for VeloCloud Rules:
UDP port 2426 and outbound | Inbound
|
TCP port 443 | Outbound |
TCP port 123 | Outbound |
UDP port 53 | Outbound |