03-29-2017 11:13 AM
03-31-2017 04:06 AM
10-17-2021 08:03 PM
@martin_martin hey Martin.
on the output, it displays this:
------ TUNNELMGR Information ------
tunnelmgr Service:Enabled
Tunnel Establishment: Disabled
Tunnel IPSec: Disabled
Tunnel Authentication:Enabled
Tunnel Cipher:Disabled
Tunnel Cipher Key Len: 128
Tunnel Forward Bcast: Disabled
PMTU: Auto
PMTU Discovery: Enabled
Node Affinity:Disabled
Force Fragmentation:Disabled
Offload:Disabled
Tunnel Type: Ruckus-GRE
SCG-D IP List:
SCG-D Subject List:
Internal Subnet:10.255.0.0
No GRE over UDP
Keep Alive Interval/Retry-limit: 10/6
Keep Alive Interval2: N/A
Keep Alive Count: N/A
Force Primary Interval: N/A
------- Run Time Status (Debug) -------
Current tunnel ID: N/A
Current failover mode: 0
Current connected SCG-D: N/A
Current connected SCG-D subject: N/A
Current connected SCG-D serial: N/A
Current Session UpTime: N/A
Current Keep Alive retry count: N/A
Number of tunnel (re)establishment: 0
FIPS mode: Disable
Reason on last re-establishment:
Suggested action:
Ipsec state : IPSEC_BEGIN
Ping default gateway from last disconnection: N/A
------ Logging parameters ------
Log Console:Disable
Log Level:3
----------- gre1 status -----------
gre1: RX packets N/A errors:N/A dropped:N/A
gre1: TX packets N/A errors:N/A dropped:N/A
OK
This is connected and pointing to the vSZ/D
10-19-2021 03:07 AM
Hi,
As mentioned if you want user traffic tunneled the AP needs to know what the IP address of the vSZ-D is. In the above list I see no IP address of the vSZ-D.
Also in the above output I see no tunnel up:
Current tunnel ID: N/A
Current failover mode: 0
Current connected SCG-D: N/A
Current connected SCG-D subject: N/A
Current connected SCG-D serial: N/A
Current Session UpTime: N/A
Regards
Martin