📘

This is only needed if location does not have internet access with DHCP, such as all static WAN

👍

Request WAN circuits with DHCP setup (Bridge mode for static)

Having at least one DHCP WAN circuit at every spoke is recommended, even if it is only a backup LTE

This should connect to WAN0/1 for reachability.

1. EC Devices are set for DHCP on WAN0/1/2 and MGMT0 out of the box,
2. Plugging into any connection that gives DHCP IP address and has 443 access to the internet will allow the device to check into your Orch.
3. Cases where only static IP exists you can login locally to the device to set the IP.

Local Access MGMT1/LAN

1. Plug into mgmt1 directly, open browser and navigate to https://169.254.0.1
   1. EC 10104 – Does not have MGMT ports, use LAN0 and navigate to https://169.254.0.1
2. If local LAN internet access exists with DHCP: Plug WAN0/1/2 into LAN, device will check into ORCH in a few minutes.
   1. Option 2: MGMT0 into local network with DHCP and HTTPS: to the ip address. This option is prefered for onboarding or setting up a replacement EC as you can do all the config without risk of affecting prod traffic, however it does not test the tunnel forming side of things.
3. Both options above may need added to any NAC type security controls and/or enterprise firewall rules.

❗️

MGMT1 traffic will not route, strictly direct access only.

1. Log in using the appliance's default credentials. They are not published here —
   they ship with the appliance, and your HPE SE can confirm them if you do not
   have them on hand.
   1. Navigate to Configuration > deployment
   2. Enter your IP address and default gateway on WAN0/1 and save/apply

   3. 📘

      Pro tip – Configure LAN1 static IP – plug into local LAN – can now access remotely (assuming no firewall or NAC prevent access)

Physical MGMT0 port

🚀

Best Practice: Should only be used for onboarding/initial config.

Unplug cable or shut down the interface once appliance is in orch.

❗️

MGMT0 - This interface should not be plugged into a direct internet connection, plug into a network behind Firewall or Temporarily LTE/Cable modem is fine for onboarding a device.

1. Plug in MGMT0 to:
   1. LTE/cable modem with DHCP
   2. Local LAN with DHCP
2. Once EC checks into Orch:
   1. Configure WAN0/1 with IP address as required
   2. Configure LAN0/1 as required
      1. NOTE: can put any address here to save the config, can config LAN later once on site if preferred.

🚧

🚀 Best Practice: Only use MGMT0/1 for onboarding.

By default the MGMT Services template has all services set to "any" which will result in mgmt0 being used if it's connected. Only by changing the defaults can you override the use of mgmt0 for those services.

Caution should be used with DHCP relay as changing from "any" will force all DHCP requests to source from that single interface which might cause issues. The EC can be configured to use Option82 to mitigate the issue but you must ensure your DHCP server supports Option82 and has the source IP whitelisted.

❗️

With MGMT0 connected or DHCP Relay MGMT Service set to a specific interface, DHCP will source from only one interface forcing the need to use Option82 and configure your DHCP server correctly to support this.

🚧

Tunnels will NOT build on MGMT0/1