Thanks. It looks like it all checks out on my end. We have a cluster but only one MD is up at the moment due to another issue:
(ArubaMM) [mynode] #configure t
Enter Configuration commands, one per line. End with CNTL/Z
(ArubaMM) [mynode] (config) #show openflow-controller
Openflow-controller
-------------------
Parameter Value
--------- -----
ofc state Enabled
ofc host-ageout-time 3600 sec
ofc mode passive
ofc certificate-file none
ofc key-file none
ofc ca-certificate-file none
ofc tls Disabled
ofc port 6633
ofc topology-discovery Disabled
ofc auxiliary-channel-port 6633
(ArubaMM) [mynode] (config) #show openflow-controller switches
Switches
--------
Dpid IP Version Status Auxiliary-Status/Id Capabilities Description
---- -- ------- ------ ------------------- ------------ -----------
00:00:00:1a:1e:07:6a:d0 10.0.0.111:44435 v1.3 Up Down/0 Flow stats, Table stats, Port stats, Queue Stats Aruba Networks, Inc. Aruba7210 ArubaOS, 8.7.1.4 SEM-MD02 TV0002322
Total number of switches: 1
(ArubaMM) [mynode] (config) #show openflow-controller flow-table app-name AirGroup
Flow-table
----------
Dpid In Port Src Mac Dst Mac Ether Src IP Dst IP Proto Src Port Dst Port App Name Actions
---- ------- ------- ------- ----- ------ ------ ----- -------- -------- -------- -------
00:00:00:1a:1e:07:6a:d0 * * * 0x86dd * * 17 * 1900 AirGroup output=
00:00:00:1a:1e:07:6a:d0 * * * 0x800 * * 17 * 5353 AirGroup output=controller
00:00:00:1a:1e:07:6a:d0 * * * 0x86dd * * 17 * 5353 AirGroup output=
00:00:00:1a:1e:07:6a:d0 * * * 0x800 10.0.0.111 222.173.190.239 17 60001 60001 AirGroup output=controller
00:00:00:1a:1e:07:6a:d0 * * * 0x800 * * 17 * 1900 AirGroup output=controller
Total number of flows: 5
(ArubaMM) [mynode] (config) #
------------------------------
Nathan Kuhl
------------------------------
Original Message:
Sent: Sep 24, 2021 02:36 PM
From: Christopher Wickline
Subject: Wired MDNS traffic
If you run these commands on the MM,
show openflow-controller
show openflow-controller switches
show openflow-controller flow-table app-name AirGroup (AirGroup is case sensitive)
The first one should show ofc enabled
the second one should show all your MDs as up, with 4 capabilities (Flow, Table, Port and Queue)
The third one, at least for me, shows multiple sessions within.
Just a forewarning, I'm just comparing what I have in these settings and what works for my environment. I'm not saying these are best practice/how it should be.
------------------------------
Chris Wickline | ACCA |
Original Message:
Sent: Sep 24, 2021 02:17 PM
From: Nathan Kuhl
Subject: Wired MDNS traffic
Openflow was something that TAC was looking at and felt like something was off here. If I run that command on the MM, I get this:
(ArubaMM) [mynode] #show openflow-profile
show openflow-profile is not supported on this model!
(SEM-MD02) #show openflow-profile
Openflow-profile "default"
--------------------------
Parameter Value
--------- -----
controller-ip masterip:6633
State Enabled
Openflow mode passive
Openflow version v1.3
Auxiliary State Disabled
Auxiliary Channel Port 6633
VLAN ID or range(s) of VLAN IDs 1-4094
custom-cert-file none
custom-key-file none
ca-certificate-file none
openflow tls Disabled
custom cert Disabled
(SEM-MD02) #
------------------------------
Nathan Kuhl
Original Message:
Sent: Sep 24, 2021 02:10 PM
From: Christopher Wickline
Subject: Wired MDNS traffic
I must have imagined the untrusted VLAN. Not sure where I got that.
That being said, I trunked a trusted VLAN to test and devices in that VLAN started showing up in our list of Airgroup servers, so what you are trying to do should work. We are on 8.7.1.4 as well.
Just for sanity, do you have the VLANs enabled in the openflow profile? (MD: show openflow-profile)
The trunked VLANs need to be added to that profile on the MDs for the MM to process them, since you are running in centralized mode.
If not, I can share a sanitized version of our config and maybe that'll point something out that maybe you are missing.
------------------------------
Chris Wickline | ACCA |
Original Message:
Sent: Sep 24, 2021 01:25 PM
From: Nathan Kuhl
Subject: Wired MDNS traffic
Just an update on this. TAC escalated me to the next tier. This tech support agent deals mostly with AirGroup. He's unable to determine why we're not seeing any mDNS traffic from wired clients. He said that trusted ports should still be forwarding traffic from wired clients and that making it untrusted is not necessary. We never had untrusted ports before on our controllers running AOS 6.5 in the past so that would seem to be true.
We're currently running AOS 8.7.1.4. He believes that there could be a bug in this version and advised us to upgrade to 8.7.1.5. I'll update this thread with the results when we can do this.
BTW, we're only on 8.7 because we plan on installing an AP-575 outdoors shortly. Otherwise, we'd be on the most stable version of 8.6.
------------------------------
Nathan Kuhl
Original Message:
Sent: Sep 19, 2021 05:14 PM
From: Nathan Kuhl
Subject: Wired MDNS traffic
Hello everyone,
We upgraded from ArubaOS 6.5 (Master-local) to ArubaOS 8.7.1.4 (MM-MD01-MD02) a month ago. Ever since then, wireless users can not see wired MDNS/AirGroup servers. All of our VLANS exist on the controllers. We ported over the settings from the old config including BCMC opt ON for all VLANS. I know this setting being on can affect wired MDNS traffic but it was on before and it worked.
TAC has no idea after multiple calls. Can anyone point us in the right direction?
------------------------------
Nathan Kuhl
------------------------------