VLANS on trunk interface with DHCP

Hello,

Just purchased RB1100ahx2 (awesome), replacing cisco ISR1921. Trying to get the configuration of VLAN's and DHCP server running on this device. Having some confusion with configuration, its fustrating.

Bonded two(2) ethernet ports; eth5 &eth6 to create a trunk interface.

assigned vlan1, vlan20, vlan30, vlan88 to TRUNK_interface

created IP Pool, address list, and DHCP server. DHCP server will not assign properly and not working. What am I missing?

/ip address print
Flags: X - disabled, I - invalid, D - dynamic

ADDRESS NETWORK INTERFACE

0 ;;; default configuration
192.168.88.1/24 192.168.88.0 TRNK_LAN
1 192.168.0.1/24 192.168.0.0 TRNK_LAN
2 192.168.20.1/24 192.168.20.0 TRNK_LAN
3 192.168.130.1/24 192.168.130.0 TRNK_LAN

\

/interface vlan print
Flags: X - disabled, R - running, S - slave

NAME MTU ARP VLAN-ID INTERFACE

0 R vlan1 1500 enabled 1 TRNK_LAN
1 R vlan20 1500 enabled 20 TRNK_LAN
2 R vlan30 1500 enabled 30 TRNK_LAN
3 R vlan88 1500 enabled 88 TRNK_LAN

Ok - I found the error on my own and corrected it. DHCP servers are assigned to the VLAN’s now with address pools.

However the DCHP server(s) are NOT providing the default gateway. Computers receive IP and mask, but no default gateway; why!!?

Furthermore, Have VOIP phone (VLAN20 - 192.168.20.0) - using torch shows that when phone plugged into a tagged port - it does not show up handing out an IP address.

You dont need to bound to make a trunk Interface. Just add vlan’s to a Ethernet.

Bound make more speed, failover etc. Trunk (in cisco world) is just tagged vlan to a port.

Access is the vlan’s from the trunk as Access ports. MT dont use the same “terminology” together With other Suppliers (like Nortel etc)

The IP adresses, should be assigned to its vlan Interface. If you want to bridge the vlan (to be one big l2), put all vlans to a bridge ((but would not the vlan stuff then be to no use? and all untagged would be better))

You need to apply the IP addresses / netmasks to the VLAN interfaces not the TRNK_LAN interface.

The DHCP servers are showing invalid status because you have them bound to interfaces which have no IP/netmasks.