Wireless: SonicPoints does not come up however console logs Shows "timeout in SSPP provision!, SDP Session Closed, SDP Provisioning Failed"
03/26/2020 5 6028
Senario : - SonicPoints does not come up however console logs Shows "timeout in sspp provision!, SDP Session Closed, SDP Provisioning Failed"
Sonicpoint Wave unit and is directly connected to the Sonicwall interface X3. The SP’s goes on continuous rebooting mode. From the console logs we see SDP Provision fail and timeout in SSPP provision.
We tried replacing both the units still the issue remains same. Attached is the SP logs and TSR. The SonicWave is connected directly to the SonicWALL using POE injector.
We have tried updating the SonicWave firmware in standalone mode and connecting it to the SonicWALL, but still the sonic wave exhibits the same behavior.
Initializing SonicWall Simple Provision Protocol (SSPP)
Copyright (c) 2017 SonicWall, Inc. ,b1PP|`
Product Model: SonicWave 432e
Product Code: 5430
Firmware Version: 184.108.40.206_6
Serial Number: 18:B1:69:8D:9B:90
IP address: 10.40.51.239
ID: Domestic 802.11ac wave2 Radio
Ethernet LAN: 1000 Mbps Full-duplex
WLAN Radio 0: 5 GHz 802.11ac/n/a Mixed
WLAN Radio 1: 2.4 GHz 802.11n/g/b Mixed
Build Time: Oct 26 2017 19:46:41
br0: port 1(eth0) entered forwarding state
No lease, forking to background
Successfully connected to GatewayReceived SDP Configuration Update
Using existing certificate
timeout in sspp provision!
SDP Session Closed
SDP Provisioning Failed
file_storage: all files have been saved!
Provision failure is mainly caused by wrong routing configurations and usually with Wrong VPN Policies.
Please check route policy and vpn rules which may affect packet route.
Please check if the Access Points are getting adequate Power via POE adaptor as per SonicPoints and SonicWaves specification.
SonicPoint provision include 2 private protocols. One is SDP, another SSPP.
SDP is layer2 protocol which doesn’t depend on TCP/IP stack. So it won’t lookup NAT policies.
But, SSPP protocol is TCP based application protocol. Each provision is trigged by SDP at first, then do SSPP.
In order to do SSPP provision successfully, sonicpoint needs to establish TCP session with WLAN interface IP.
RMA the SonicPoints is not necessary.