Questions[aruba](server)

I have a problem with bonding mode 802.3ad between Ubuntu 20.04.3 and switch aruba 6300m.

Any problems :

The bonding work fine but after a reboot i need to shut / no shut my lag on 6300M switch for "actualize" the bonding. After that it's work fine. (Only mode 802.3ad have this problem).

sudo netplan apply does not work. I need to reboot my server for apply configuration

Netplan conf :

network:
version: 2
renderer: networkd
ethernets:
  ens3f0np0:
    dhcp4: false
  eno5np0:
    dhcp4: false
bonds:
  bond0:
    interfaces: [ens3f0np0,eno5np0]
    addresses: [MyIP]
    gateway4: MyGateway
    nameservers:
      addresses: [MyDNS]
    parameters:
      mode: 802.3ad
      lacp-rate: fast
      mii-monitor-interval: 100

Conf LAG Aruba 6300M when it's works :

 Aggregated-interfaces       : 1/1/20 2/1/20
 Aggregation-key             : 25
 Aggregate mode              : active
 Hash                        : l3-src-dst
 LACP rate                   : fast
 Speed                       : 20000 Mb/s
 Mode                        : access

Conf LAG Aruba 6300M When ubuntu was reboot :

State information : Disabled by LACP or LAG
 Type                        : normal
 Aggregated-interfaces       : 1/1/20 2/1/20
 Aggregation-key             : 25
 Aggregate mode              : active
 Hash                        : l3-src-dst
 LACP rate                   : fast
 Speed                       : 0 Mb/s
 Mode                        : access

if I shut / no shut lag or make aggregate mode passive to active it's works.

can you help me please, i think i have a problem with my netplan configuration

Sudo netplan try :

bond0: reverting custom parameters for bridges and bonds is not supported

Please carefully review the configuration and use 'netplan apply' directly.

I am trying to configure Radius authentification using NPS backend. I have configured both ends but it does not seem to work.I am not sure if this is even correct. Kindly help.

NPS Config:

I have added my switch info under Radius Clients by giving the ip-address and shared secret key. Under Connection request policy I have specified the ip-address of the switch as condition. Under Network Policy I have specified the Active directory user groups and service-type is set to administrative.

Aruba 2930f switch config:

radius-server host key aaa authentication ssh login radius local aaa authentication ssh enable radius local

I can ping Radius server and the switch. I can only login as a local user and not as AD user

Okay so I'm a little new to VLANS, so forgive me if this is a silly question. I have a firewall set up with a few VLANS:

ID 1: This is the primary, and set to untagged. This will be used as a management VLAN ID 30: 'Guest' for the less trusted devices ID 40: 'iot' for our it devices. I wan them segregated for QOS and security reasons ID 50: 'Trusted' for staff to access specific resources on the LAN.

My question is this. The majority of devices connecting to VLAN 30 and 50 will be standard workstations, with NICs that don't understand VLAN tagging. If I set port-based VLAN, I still have to have it as a tagged VLAN, as that's how it's set on the firewall (The firewall is running a 'bridge' port to pipe all 4 VLANS over to the layer 2 switch), and of course, will only allow one of those VLANS to come back untagged. If I set it as a tagged VLAN, the workstation doesn't understand it and gives a 169 IP. if I set it to an untagged, same deal - I assume as the firewall is only expecting tagged traffic from those VLANS. What am I missing here?

Context: My firewall is a Watchguard, my switch is an HP Aruba

I have deployed 11 Aruba AP 92 without controller, selecting the correct boot mode at the beginning of the configuration process. The 11 AP were separately configured with IP address, SSID and channel selection. When I connect AP on the LAN, 3 of them are visible trough the lan but are not working on the radio interface, "11gn" led is solid red, SSID not visible and there is no radio signal... I use to deploy Cisco AP and I am fairly new to Aruba, any help would be appreciated.

We have an Aruba wireless system with five current access points and a virtual controller. I have just purchased another (Aruba 92) access point and can't get the controller to recognize it. The power LED is blinking green, the Enet LED is blinking amber. The access point is plugged into our HP PoE switch that the other ones are plugged into, but it is not getting an IP from the DHCP server.

The virtual controller version is 5.0.3

I am fairly new to Aruba and any help would be appreciated.