Package com.ibm.cloud.is.vpc.v1.model
Class VPNGatewayConnectionStaticRouteModeTunnel
- java.lang.Object
-
- com.ibm.cloud.sdk.core.service.model.GenericModel
-
- com.ibm.cloud.is.vpc.v1.model.VPNGatewayConnectionStaticRouteModeTunnel
-
- All Implemented Interfaces:
com.ibm.cloud.sdk.core.service.model.ObjectModel
public class VPNGatewayConnectionStaticRouteModeTunnel extends com.ibm.cloud.sdk.core.service.model.GenericModel
VPNGatewayConnectionStaticRouteModeTunnel.
-
-
Nested Class Summary
Nested Classes Modifier and Type Class Description static interface
VPNGatewayConnectionStaticRouteModeTunnel.Status
The status of the VPN Tunnel.
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description IP
getPublicIp()
Gets the publicIp.String
getStatus()
Gets the status.List<VPNGatewayConnectionTunnelStatusReason>
getStatusReasons()
Gets the statusReasons.
-
-
-
Method Detail
-
getPublicIp
public IP getPublicIp()
Gets the publicIp. The IP address of the VPN gateway member in which the tunnel resides.- Returns:
- the publicIp
-
getStatus
public String getStatus()
Gets the status. The status of the VPN Tunnel.- Returns:
- the status
-
getStatusReasons
public List<VPNGatewayConnectionTunnelStatusReason> getStatusReasons()
Gets the statusReasons. The reasons for the current VPN gateway connection tunnels status (if any): - `cannot_authenticate_connection`: Failed to authenticate a connection because of mismatched IKE ID and PSK (check IKE ID and PSK in peer VPN configuration) - `internal_error`: Internal error (contact IBM support) - `ike_policy_mismatch`: None of the proposed IKE crypto suites was acceptable (check the IKE policies on both sides of the VPN) - `ike_v1_id_local_remote_cidr_mismatch`: Invalid IKE ID or mismatched local CIDRs and remote CIDRs in IKE V1 (check the IKE ID or the local CIDRs and remote CIDRs in IKE V1 configuration) - `ike_v2_local_remote_cidr_mismatch`: Mismatched local CIDRs and remote CIDRs in IKE V2 (check the local CIDRs and remote CIDRs in IKE V2 configuration) - `ipsec_policy_mismatch`: None of the proposed IPsec crypto suites was acceptable (check the IPsec policies on both sides of the VPN) - `peer_not_responding`: No response from peer (check network ACL configuration, peer availability, and on-premise firewall configuration) The enumerated reason code values for this property will expand in the future. When processing this property, check for and log unknown values. Optionally halt processing and surface the error, or bypass the resource on which the unexpected reason code was encountered.- Returns:
- the statusReasons
-
-