IP Router Configuration
Router Configuration Guide 145
never — When specified, no tunnels will be placed on blacklist under any circumstance. This
parameter will available to preserve backward compatibility.
max-list-length
Syntax max-list-length unlimited
max-list-length count
no max-list-length
Context configure>router>l2tp>tunnel-selection-blacklist
stop-ccn-other A tunnel will be forced to the blacklist in case that StopCCN
message with the following Result Codes is received:
(1) General request to clear control connection
(4) Requester is not authorized to establish a control channel
(5) Protocol version not supported
(6) Requester is being shutdown
Or in the case that the StopCCN with the following result codes is
transmitted:
(4) Requester is not authorized to establish a control channel.
(5) Protocol version not supported
The receipt of the following Result Codes will NEVER blacklist a
tunnel:
(0) Reserved
(3) Control channel already exist
(7) Finite state machine error
(8) Undefined
Transmission of the following Result Codes will NEVER blacklist
a tunnel:
(1) General request to clear control connection
(3) Control channel already exist
(6) Requester is being shutdown
(7) Finite state machine error
addr-change-timeout A timed-out tunnel for which the peer IP address has changed mid-
session (from the one that is provided initially during configuration)
will be forced to the blacklist. In absence of this configuration
option, only the configured peer for the tunnel will be blacklisted,
but not the tunnel itself which now has a different peer address than
the one initially configured.
Table 6: Return codes (Continued)
Return code Tunnels added to blacklist
To Next Page
Loading...
