Configuring GTPC Path Failure Customization
To configure the GTPC path failure customization, use the following configuration:
config
policy path-failure-detection policy_name
max-remote-rc-change maximum_remote
ignore echo-rc-change
ignore control-rc-change
ignore echo-failure
exit
exit
instance instance-id instance_id
endpoint gtp
replicas replica_count
vip-ip ipv4_address vip-port ipv4_port_number
vip-ipv6 ipv6_address vip-ipv6-port ipv6_port_number
dual-stack-transport { true | false }
path-failure detection-policy policy
interface [ s11 | s5e ]
end
NOTES:
-
When GTPC path failure detection policy isn’t configured at interface-level, endpoint-level path failure detection policy is applicable.
-
The max-remote-rc-change configuration specifies the counter change after which the S11 or S5 detects a peer restart. A peer restart is detected only if the absolute difference between the new and old restart counter is less than the value configured. For example, if the max-remote-rc-change is 10 and current peer restart counter is 251, then eGTP detects a peer restart only if the new restart counter is 252 through 255 or 0 through 5. Similarly, if the stored restart counter is 1, eGTP detects a peer restart only if the new restart counter is 2 through 11.
-
Valid settings are from 1 to 255. The recommended setting is 32.