Wireless Access

last person joined: 18 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Tunneling between controller....

This thread has been viewed 2 times
  • 1.  Tunneling between controller....

    Posted Jan 01, 2014 10:22 PM

    Hi all,

     

    I will deploy one new controller(controller B) in DR site for clients (vlan 100)..Now I have a controller(controller A) in my existing production network. And I want the vlan100 gateway is in the existing building. I have a idea that can I form a tunnel between two controllers in order that centralize all remote traffic(vlan 100) back to exsiting network? the tunnel should be layer 2 ,right?

     

    any one can help? or give me some reference/document?

     

    many thanks



  • 2.  RE: Tunneling between controller....



  • 3.  RE: Tunneling between controller....

    Posted Jan 02, 2014 04:18 PM

    Here's the config I'm using:

     

    Controller2 (users in the VLAN100 get tunnelled back to Controller 1)

    !
    interface vlan 100
    	ip address 192.168.0.249 255.255.255.0
    !
    interface tunnel 91
    	description "Guest Tunnel"
    	tunnel source 10.30.1.254
    	tunnel mode gre 0
    	tunnel destination 10.21.0.65
    	trusted
    	mtu 1500
    	tunnel vlan 100
    !

     

    Controller1 (head end, where layer-3 happens for VLAN100)

    !
    interface vlan 100
    	ip address 192.168.0.250 255.255.255.0
    !
    interface tunnel 91
    	description "Boise Guests"
    	tunnel source 10.21.0.65
    	tunnel mode gre 0
    	tunnel destination 10.30.1.254
    	tunnel vlan 100
    !

    I'm using this for guests, so I trust at the far end, and do-not-trust at the head, and they get dropped off on the portal.