Wireless Access

last person joined: 15 hours ago 

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

Management of Series 6000 Chassis with M3 Controllers

This thread has been viewed 0 times

  • 1.  Management of Series 6000 Chassis with M3 Controllers

    Posted Jan 16, 2012 01:14 PM

    Re:  Series 6000 Chassis with four M3 Controllers:

     

    Can I manage all four M3 Controllers from any one of the M3 Controller Management Ports?

    Perhaps only the one slot 0 must be used?

    Is the entire chassis managed as one system with one GUI or do I need to log into a GUI for each M3 Controller?

     

    Thanks



  • 2.  RE: Management of Series 6000 Chassis with M3 Controllers
    Best Answer

    Posted Jan 16, 2012 01:20 PM

    Each M3 is independent.  You will have to manage each one as a separate card (login to each GUI or CLI).  Each M3 will also need network connectivity, so you really can't use only one mgmt port.

     

    Think of the chasis as a power supply and rack mount kit for up to 4 separate controllers.

     



  • 3.  RE: Management of Series 6000 Chassis with M3 Controllers
    Best Answer

    Posted Jan 16, 2012 01:24 PM

    Each M3 in a chassis is logically separate from a management and a networking perspective.  You will need to network each into the environment as if they were separate units and manage the "local" config (VLAN info, IP info, Net Management Info, phyical ports, etc) separately.  If you like, you can set these up as master/local where one is master and the other 3 are local so that the "global" config (all AP-Group related config, policies, aaa, etc) and monitoring is managed from one spot.  You can pick which one you want to be the master, really doesn't matter.  This would be the same if they were separate controllers.  Please be sure to follow master/local design guidelines in the VRDs however.