topic The ap's ip address is incorrect on adoption status result. in ExtremeWireless (WiNG)

The ap's ip address is incorrect on adoption status result.

zlinuxboy — Sun, 29 Aug 2021 14:43:47 GMT

I deploy 3 AP7522s, one of them is VC. here is the context of profile ap7522 default-ap7522

profile ap7522 default-ap7522
 use enterprise-ui
 ip name-server 221.176.88.95
 ip default-gateway 192.168.9.254
 autoinstall configuration
 autoinstall firmware
 use radius-server-policy WERSP
 crypto ikev1 policy ikev1-default
  isakmp-proposal default encryption aes-256 group 2 hash sha
 crypto ikev2 policy ikev2-default
  isakmp-proposal default encryption aes-256 group 2 hash sha
 crypto ipsec transform-set default esp-aes-256 esp-sha-hmac
 crypto ikev1 remote-vpn
 crypto ikev2 remote-vpn
 crypto auto-ipsec-secure
 crypto load-management
 crypto remote-vpn-client
 interface radio1
  data-rates gn
  wlan wing-hkxd bss 1 primary
 interface radio2
  wlan wing-hkxd bss 1 primary
 interface ge1
  switchport mode trunk
  switchport trunk allowed vlan 7-10
  switchport trunk native vlan 9
 interface vlan1
  ip address dhcp
  ip address zeroconf secondary
  ip dhcp client request options all
 interface pppoe1
 use firewall-policy default
 ntp server 0.pool.ntp.org
 use client-identity-group default
 virtual-controller auto
 virtual-controller management-interface ip address 192.168.9.140/24
 virtual-controller management-interface vlan 9
 rf-domain-manager capable
 logging on
 service pm sys-restart
 router ospf
 adoption-mode controller
!
rf-domain default
 timezone Asia/Shanghai
 country-code cn
 use smart-rf-policy hkxd
 use nsight-policy default
!
ap7522 74-67-F7-04-31-5C
 use profile default-ap7522
 use rf-domain default
 hostname ap7522-04315C
 interface vlan9
  ip address 192.168.9.143/24
!
ap7522 74-67-F7-04-4F-A8
 use profile default-ap7522
 use rf-domain default
 hostname cz3-ap46
!
ap7522 74-67-F7-04-4F-C4
 use profile default-ap7522
 use rf-domain default
 hostname ap7522-044FC4
!
ap7522 74-67-F7-04-53-20
 use profile default-ap7522
 use rf-domain default
 hostname ap7522-045320
 interface vlan9
  ip address 192.168.9.144/24
!
ap7522 74-67-F7-A1-AE-58
 use profile default-ap7522
 use rf-domain default
 hostname ap7522-A1AE58
 interface vlan9
  ip address 192.168.9.142/24
!
ap7522 74-67-F7-A2-DA-54
 use profile default-ap7522
 use rf-domain default
 hostname ap7522-A2DA54
 interface vlan9
  ip address 192.168.9.141/24
 no adoption-mode

the VC’s IP is 192.168.9.140

the 3 AP’s mac and IP are:

74-67-F7-04-31-5C : 192.168.9.143

74-67-F7-04-53-20 : 192.168.9.144

74-67-F7-A2-DA-54 : 192.168.9.141

but when `show adoption status` on vc

ap7522-04315C> show adoption status
Adoption Mode: CONTROLLER
--------------------------------------------------------------------------------------------------------------------------------
DEVICE-NAME       VERSION         CFG-STAT         MSGS ADOPTED-BY        LAST-ADOPTION                  UPTIME     IPv4-ADDRESS
--------------------------------------------------------------------------------------------------------------------------------
ap7522-045320     5.9.8.4-002R    configured       No   ap7522-04315C       0 days 00:18:52     0 days 00:21:01    192.168.9.140
ap7522-A2DA54     5.9.8.4-002R    configured       No   ap7522-04315C       0 days 00:30:23     0 days 15:23:04    192.168.9.141
---------------------------------------------------------------------------------------------------------------------------------

The ap7522-045320’s IP was change from 9.144 to 9.140(VC), what is wrong?

Question2:

I serial console to ap7522-045320, the hostname have a suffix ‘*’:

ap7522-045320*#

what does it mean?

Re: The ap's ip address is incorrect on adoption status result.

arichter — Sun, 29 Aug 2021 16:18:03 GMT

Hello ,

in regards to Q2 , the “*” means, that there is a crash file on the given device.

That can be cleared by changing into the crashfile directory.

on CLI : dir , then cd Crash…, in there del *.* and confirm with “Y”.

On the other topic, AP changing IP, this might be something on the election process of the VC / RFDM and might be something on Mint ID. This is only an assumption, as I do not have further informations at this point.

I think, a “show global domain-managers” could help, to see, which AP was elected RFDM.

Re: The ap's ip address is incorrect on adoption status result.

zlinuxboy — Sun, 29 Aug 2021 17:06:07 GMT

@arichter

here are the relative cli result on vc:

Yes, you are right, after delete the crashinfo, the hostname’s suffix * disappear.

Re: The ap's ip address is incorrect on adoption status result.

RobertZ — Mon, 30 Aug 2021 00:16:57 GMT

You can also do that with one cli command:
directly on device “ service clear crash-info “
from wlc “service clear crash-info on <device_name> “

Re: The ap's ip address is incorrect on adoption status result.

RobertZ — Mon, 30 Aug 2021 00:20:52 GMT

Seams that is the VC, you have configured with the below:

 virtual-controller auto
 virtual-controller management-interface ip address 192.168.9.140/24
 virtual-controller management-interface vlan 9

Re: The ap's ip address is incorrect on adoption status result.

ckelly — Mon, 30 Aug 2021 00:24:29 GMT

Here’s what I see from your postings:

This AP has an override IP address for .144

ap7522 74-67-F7-04-53-20
 use profile default-ap7522
 use rf-domain default
 hostname ap7522-045320
 interface vlan9
  ip address 192.168.9.144/24

You say that the the VC’s IP is 192.168.9.140, but I don’t see any of the APs assigned a .140 address anywhere in the posted config.

And then you say, “but when `show adoption status` on vc”, it outputs information for AP

ap7522-04315C

which has a static IP address of .143 in the posted config.

So I’m having a hard time determining which MAC address is supposed to be the VC in this setup.

Re: The ap's ip address is incorrect on adoption status result.

zlinuxboy — Mon, 30 Aug 2021 08:24:33 GMT

@Chris Kelly

well, here are the logic
1. Through the profile config, they will elect a vc, and then assign 9.140 to the vc as secondary ip.
2. The device override config will assign static to the ap.
3. ap7522-04315c was elected as vc, it's secondary ip is 9.140, the primary ip is 9.143
4. ap7522-045320's ip is 9.144, ap7522-a2da54's ip is 9.141

so, I think the result of `show adoption status` on vc(ap7522-4315c) should be as this:

```

ap7522-04315C> show adoption status
Adoption Mode: CONTROLLER
--------------------------------------------------------------------------------------------------------------------------------
DEVICE-NAME VERSION CFG-STAT MSGS ADOPTED-BY LAST-ADOPTION UPTIME IPv4-ADDRESS
--------------------------------------------------------------------------------------------------------------------------------
ap7522-045320 5.9.8.4-002R configured No ap7522-04315C 0 days 00:18:52 0 days 00:21:01 192.168.9.144
ap7522-A2DA54 5.9.8.4-002R configured No ap7522-04315C 0 days 00:30:23 0 days 15:23:04 192.168.9.141
---------------------------------------------------------------------------------------------------------------------------------

```

but it's weird, the actrual result is:

```

ap7522-04315C> show adoption status
Adoption Mode: CONTROLLER
--------------------------------------------------------------------------------------------------------------------------------
DEVICE-NAME VERSION CFG-STAT MSGS ADOPTED-BY LAST-ADOPTION UPTIME IPv4-ADDRESS
--------------------------------------------------------------------------------------------------------------------------------
ap7522-045320 5.9.8.4-002R configured No ap7522-04315C 0 days 00:18:52 0 days 00:21:01 192.168.9.140
ap7522-A2DA54 5.9.8.4-002R configured No ap7522-04315C 0 days 00:30:23 0 days 15:23:04 192.168.9.141
---------------------------------------------------------------------------------------------------------------------------------

```

that make me confused.

by the way, that will be convenient if the forum support markdown.

Re: The ap's ip address is incorrect on adoption status result.

ckelly — Mon, 30 Aug 2021 20:49:20 GMT

@zlinuxboy I see what you are referring to now and your confusion.

I’m not sure why this is happening right now though.

With these all being the same AP model and ap7522-04315C having the lowest MiNT-ID, it’s correct that ap7522-04315C should be elected as the VC and therefore be assigned and be reachable via the .9.140 address.

What is odd is that ‘show adoption status’ output correctly indicates that ap7522-045320 is adopted by ap7522-04315C, which is expected, but that ap7522-045320 has the .9.140 address, instead of its statically assigned .9.144 address.

I would SSH into ap7522-045320 directly and look at its interface address status.

Once logged in, run:

show int vlan 1

show int vlan 9

show adoption status

Re: The ap's ip address is incorrect on adoption status result.

zlinuxboy — Tue, 31 Aug 2021 23:43:39 GMT

ap7522-045320>show int vlan 1
Interface vlan1 is UP
  Hardware-type: vlan, Mode: Layer 3, Address: 74-67-F7-04-53-20
  Index: 5, Metric: 1, MTU: 1500
  IP-Address: 169.254.83.32/16(ZEROCONF) secondary
    input packets 0, bytes 0, dropped 0, multicast packets 0
    input errors 0, length 0, overrun 0, CRC 0, frame 0, fifo 0, missed 0
    output packets 18, bytes 7844, dropped 0
    output errors 0, aborted 0, carrier 0, fifo 0, heartbeat 0, window 0
    collisions 0
  IPv6 mode is disabled

ap7522-045320>show int vlan 9
Interface vlan9 is UP
  Hardware-type: vlan, Mode: Layer 3, Address: 74-67-F7-04-53-20
  Index: 6, Metric: 1, MTU: 1500
  IP-Address: 192.168.9.144/24
    input packets 1966, bytes 246009, dropped 0, multicast packets 0
    input errors 0, length 0, overrun 0, CRC 0, frame 0, fifo 0, missed 0
    output packets 544, bytes 50475, dropped 0
    output errors 0, aborted 0, carrier 0, fifo 0, heartbeat 0, window 0
    collisions 0
  IPv6 mode is disabled

ap7522-045320>show adoption status
Adoption Mode: CONTROLLER
Adopted by:
Type          : ap7522
System Name   : ap7522-04315C
MAC address   : 74-67-F7-04-31-5C
MiNT address  : 75.04.31.5C
Time          :   0 days 00:10:23 ago

nothing abnormal.

@Chris Kelly

Re: The ap's ip address is incorrect on adoption status result.

ckelly — Thu, 02 Sep 2021 20:09:29 GMT

Based on that output, it does appear that ap7522-045320 is getting assigned the static address of .9.144 like it’s supposed to:

ap7522 74-67-F7-A1-AE-58
 use profile default-ap7522
 use rf-domain default
 hostname ap7522-A1AE58
 interface vlan9
  ip address 192.168.9.142/24

So the only thing that is not normal is the .9.140 address connecting you into this same AP (should be connecting you to ap7522-04315C instead.

Can you post the full config listing from ap7522-045320 ?

Re: The ap's ip address is incorrect on adoption status result.

zlinuxboy — Thu, 02 Sep 2021 21:46:35 GMT

I have been reset them all and created config from scratch, everything is fine now, thanks any way. @Chris Kelly there are two more questions about mint:

ap7522-045320>show mint known-adopters
75.04.31.5C
ap7522-045320>show mint links details
1 mint links on 75.04.53.20:
link vlan-9 at level 1, 2 adjacencies, DIS 75.04.53.20 (self):
  cost 10, hello-interval 4, adj-hold-time 13
  created: by auto VC
  adjacency with 75.04.31.5C, state UP (2 hours), last hello 1 seconds ago
  adjacency with 75.A2.DA.54, state UP (2 hours), last hello 3 seconds ago
ap7522-045320>show mint lsp
id 75.04.53.20, level 1, 2 adjacencies, 0 extended-vlans
seqnum 319627, expires in 28 minutes, republish in 1147 seconds
90 bytes, can-adopt: False, adopted-by: 75.04.31.5C, dis-priority 90, Level-2-gateway: False
hostname "ap7522-045320"
rf-domain "hkxd", priority vector: 0xc05a0000
adjacent to 75.A2.DA.54, cost 10
adjacent to 75.04.31.5C, cost 10

I have 3 AP7522 and deploy as dynamic VC scene.

1. what does DIS mean on `show mint link`;
2. why there are only 1 mint links to 75.04.53.20. According to the extreme's KB, level1 mint links is point to multipoint, so isn't it should form 2 mint links to 75.04.31.5C and 75.A2.DA.54?

Re: The ap's ip address is incorrect on adoption status result.

ckelly — Thu, 02 Sep 2021 22:20:11 GMT

In your output, are all 6 APs hooked up? Based on the output, that doesn’t appear to be the case.

DIS applies to tunneled mint traffic. This doesn’t apply in your case. The traffic is locally bridged.
MiNT links are point to point but an AP or controller can have multiple MiNT links to other MiNT devices (both level-1 and level-2 links at the same time). In your setup, each of the 7522’s should form a level-1 MiNT link with each other. So if there are 6 APs, each AP should show MiNT links with the other 5 APs. (and will also list a level-1 MiNT link with its own MiNT ID).

On one of the APs, run the command:

show mint neighbors

Re: The ap's ip address is incorrect on adoption status result.

zlinuxboy — Thu, 02 Sep 2021 22:42:22 GMT

Sorry, I have cut down the APs number from 6 to 3 , I should put the sentence ”I have 3 AP7522 and deploy as dynamic VC scene ” at first of the last post.

here is the result of `show mint neighbors` on vc:

ap7522-04315C>show mint neighbors
2 mint neighbors of 75.04.31.5C:
75.04.53.20 (ap7522-045320) at level 1, best adjacency vlan-9
75.A2.DA.54 (ap7522-A2DA54) at level 1, best adjacency vlan-9

does this links number correct? It’s only 1 link to neighbors

ap7522-04315C>show mint links
1 mint links on 75.04.31.5C:
link vlan-9 at level 1, 2 adjacencies, DIS 75.04.53.20

based on you comment, isn’t it should be 2 links to the other neighbors?

Re: The ap's ip address is incorrect on adoption status result.

ckelly — Thu, 02 Sep 2021 22:45:11 GMT

Okay, that makes more sense then.

So in the neighbor output from 04315C, we can see its two neighbors.

So 04315C has a level-1 MINT link to each of these APs, as expected.

This is what I would expect to see.

Re: The ap's ip address is incorrect on adoption status result.

zlinuxboy — Thu, 02 Sep 2021 22:47:51 GMT

@Chris Kelly hold on man, I just update the last comment, pls check it out again.

Re: The ap's ip address is incorrect on adoption status result.

ckelly — Thu, 02 Sep 2021 22:52:48 GMT

Okay...so the output from the VC, as you did, should look like your original posting - with the two APs listed.

Try running the neighbor command on each AP. Each one should list the other 2 APs.