Getting Started
Important Moderation Notice
This community is currently under full moderation, meaning all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you will receive an email outlining the reason(s). We have implemented full moderation to control spam. Thank you for your patience and participation.
Top Liked Posts
-
By Vee4By Siva4By Vee2By fun4net1By Maksym1
Versa Branch reports IKE failed error
Hi Experts,
I am new to versa and have automated most of the deployment, The headend nodes are up and I see Controller connected, I have had to make updates manually to director to connect the analytics so I can see the data in analytics.
I've got a branch node that I have provisioned but it fails on IKE , The activation logs have the following output, Please can you provide any steps to debug this issue. Thanks you
****** Versa Logging started ******
main-layout-controller with path =
/home
, token =
undefined
, passcode =
undefined
set branch ports success
getDeviceStatus - success
getProviderOrg success - response
getTunnelStatusForVPN success - response
getDirectorStatus - success
get life cycles - success
Share :
Comments
-
could you look at IKE status, from CLI you could use this command to find what is the status of IKE
show orgs org-services "orgname" ipsec vpn profile "profile name"ike history- this should show you the reason. also make sure the network reachability is fine between branch and the controllers.
/* */
