★ ⭐AP can not come online Cloudnet troubleshooting steps

2023-12-29 15:18:40 Published
  • 0 Followed
  • 0Collected ,2704Browsed

Network Topology

Traditional topology


Problem Description

AP can not come online Cloudnet


Process Analysis

1. Checking the AP"s address allocation

Command: display interface brief
  • Whether the AP obtains an IP address through DHCP 
  • Whether the VLAN where the IP address is obtained is VLAN1 

Note:

  • AP generally uses DHCP to get VLAN 1 address, if using other VLAN as management VLAN needs to be added under Cloudnet VLAN settings.

PathSettings>Cloud APs>VLAN Settings



2. Confirm the device"s connectivity to the Internet

Command: ping -c 10 -a Management IP address of the device 8.8.8.8

Example:

[WA6630]dis int b 
*down: administratively down 
(s): spoofing (l): loopback 
Interface   Physical Protocol  IP Address   Description 
Vlan1             up          up      192.168.1.5         -- 
ping -c 10 -a 192.168.1.5 8.8.8.8 
Ping 8.8.8.8 (8.8.8.8) from 192.168.1.5: 56 data bytes, press CTRL_C to break 
56 bytes from 8.8.8.8: icmp_seq=0 ttl=113 time=5.268 ms
56 bytes from 8.8.8.8: icmp_seq=1 ttl=113 time=3.962 ms


3. Confirm whether the device can resolve Cloudnet"s domain name.

Command: ping oasiscloud.h3c.com / ping cloudnet.h3c.com


4. Confirm firewall port and address clearance, Cloudnet Platform needs to use the following IP addresses and ports.

IP address

Protocol

Source port

Destination port

Description

52.163.242.100

TCP

any

80/443

WEB GUI management

52.187.3.51

TCP

any

19443

Cloudnet connect

13.76.182.179

TCP

any

80/443

Cloudnet authentication

13.76.252.214

TCP

any

5555/28443

License Server

52.187.0.95

TCP

any

80/443

apikong GW

40.73.23.215(This is just an example. The actual NTP Server address is subject to the resolution.)

UDP

any

123

NTP Server


5. If the device still does not come online after checking the above steps, please collect the following information

  • Collect the command result
display cloud-management state
sys
[H3C]probe
[H3C-probe]display system internal cloud-management state

  • Collect online debugging
debugging cloud-management all
t m
t d
After collecting 3-4 min, please undo this debugging
undo debugging cloud-management all
u t m
u t d

  • Collect the offline AP diag-info
The method of collecting diagnostic information is as follows:
(Method A)
Save the operation record, record the displayed information through the terminal to save the session (there is a lot of information, it takes a little time)
[H3C] display diagnostic-information
Save or display diagnostic information (Y = save, N = display)? [Y / N]: n
 
(Method B)
Save to device storage, ftp export to device
[H3C] dis diagnostic-information
Save or display diagnostic information (Y = save, N = display)? [Y / N]: y
Please input the file name (*. Diag) [cfa0: /default.diag]:
Diagnostic information is outputting to cfa0: /default.diag.
Please wait ...
Save successfully.
 
Export the file in the path.
 
This is an example for exporting diag-info:
https://knowledge.h3c.com/Theme/details/113271




Solution

Troubleshooting feedback based on the above steps


Total score:   
Please rate this case:   
0 Comments

No Comments

Add Comments: