Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsVpnIkePhase1LifeTime",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Enter the duration, in fsVpnIkePhase1LifeTimeType, of the IKE security association (SA), after which the IKE SA expires and is re-negotiated. if you wish to save setup time for new IPsec SAs, configure a longer IKE SA lifetime. However, shorter lifetimes provide more secure IKE negotiations because the SA between the tunnel endpoints must be successfully renegotiated more frequently. NOTE in case of IKEv1: If the IKEv1 lifetimes on two peers are not the same (equal in duration), the IKE policy lifetime of the initiating peer must be shorter than the lifetime of the responding peer, and the shorter lifetime will be used in IKE negotiations between the devices. \"",
"DEFVAL",
"{",
"2400",
"}",
"::=",
"{",
"fsVpnEntry",
"34",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Enter the duration, in fsVpnIkePhase1LifeTimeType, of the IKE security association (SA), after which the IKE SA expires and is re-negotiated. if you wish to save setup time for new IPsec SAs, configure a longer IKE SA lifetime. However, shorter lifetimes provide more secure IKE negotiations because the SA between the tunnel endpoints must be successfully renegotiated more frequently. NOTE in case of IKEv1: If the IKEv1 lifetimes on two peers are not the same (equal in duration), the IKE policy lifetime of the initiating peer must be shorter than the lifetime of the responding peer, and the shorter lifetime will be used in IKE negotiations between the devices."
],
null,
null,
null,
[
"DEFVAL",
2400
]
]
}