@an0nymous 

Which device is offering IP's on the 192.168.68.0/24 network?

Have you rebooted or power-cycled the router since the 10.10.40.0/24 network was created and assigned?  (If not, the old address stick around)

  @an0nymous 

Ok, a few things then:

1. Internet Capacity (Gateway)...you have to manually edit this to your 'purchased speed package'.  It doesn't report the speedtest capacities like the older Controllers did.

2. I am assuming your VM_LAN is defined on your controller, is untagged, and has the 192.168.68.0/24 subnet

3. I assume you did not define a Management VLAN on either the Router or the Controller (this is different from defining a 'Management' VLAN in the controller)

I am going out on a bit of limb here, but what if the router gets its IP from the lowest applicable VLAN or the first defined LAN network?  And does it matter?  The router should respond equally well to a ping to 192.168.68.1 as it does to 10.10.40.1 as technically those are all valid IP's for the router.  You can likely validate this in your client's ARP table after pinging a number of those IPs.

The OC200 will get its IP from the first DHCP response packet it gets, unless you have defined a management VLAN and are tagging those packets on the OC200 port.  You should (IMHO) always assign a Reserved IP to your controller, and I would imagine that if you did map the controller MAC address to say 10.10.40.2 and restarted the controller, it would come back up with that IP.