extreme wireless Identify v2110 problem with access on port 5825

[MarekorMark]

Hi
I have problem with access on my controller on port 5825.
That problem appeared after netsight migration and upgrading from v6.3.0.184 to 186
wireless controller (WC) is in my managment vlan as the FW interface is and on FW interface a can connect and WC interface on port 5825 is unreachable but I can ping WC.
Also i can "ask" if 5825 port on WC is reachable and i have an answer from that port.
WC is a part of netsight and nacgateway infrastructure

What and where i should check to do the right troubleshooting of that problem

[MarekorMark]

This is what ive got with wireshark... WC is sending RESET FLAG

Transmission Control Protocol, Src Port: 56554 (56554), Dst Port: 5825 (5825), Seq: 201, Ack: 1, Len: 0
Source Port: 56554 (56554)
Destination Port: 5825 (5825)


[Stream index: 5]
[TCP Segment Len: 0]
Sequence number: 201 (relative sequence number)
Acknowledgment number: 1 (relative ack number)
Header Length: 20 bytes
Flags: 0x014 (RST, ACK)
000. .... .... = Reserved: Not set
...0 .... .... = Nonce: Not set
.... 0... .... = Congestion Window Reduced (CWR): Not set
.... .0.. .... = ECN-Echo: Not set
.... ..0. .... = Urgent: Not set
.... ...1 .... = Acknowledgment: Set
.... .... 0... = Push: Not set
.... .... .1.. = Reset: Set
[Expert Info (Warning/Sequence): Connection reset (RST)]
[Connection reset (RST)]
< connection="" reset="">
[Severity level: Warning]
[Group: Sequence]
.... .... ..0. = Syn: Not set
.... .... ...0 = Fin: Not set
[TCP Flags: ·······A·R··]
Window size value: 0
[Calculated window size: 0]
[Window size scaling factor: 256]
Checksum: 0xc5f1 [unverified]
[Checksum Status: Unverified]
Urgent pointer: 0

[MarekorMark]

APs topology has no default GW ip only controller has its own IP, AP topology is separatet from others

IMHO the problem is with the GUI configuration ... for example SSH (22) port is working fine

[Ronald_Dvorak]

What about the topology that is used to connect the APs ?

Is there a default gw set in the > controller > administration > host attributes > default gw IP ?

[MarekorMark]

every topology is Bridged at AP and i cant add IP address to it.

[Ronald_Dvorak]

You shouldn't use the Admin interface during normal operation as it could result in different data paths.

Could you try to enable mgmt on another topology and test whether you'd access the controller via VLAN#20 on that IP.