Alcatel-Lucent 8950 AAA User Manual page 74

Table of Contents

Advertisement

Managing 8950 AAA Servers
............................................................................................................................................................................................................................................................
Table 4-11
Table 4-11 Diameter Properties panel–Properties
Configurable Properties
Diameter Address
Origin Realm
Origin Host
Peer Socket Timeout
Peer Idle Timeout
Peer Idle Holdoff
............................................................................................................................................................................................................................................................
4 - 18
lists the configurable entities of this panel.
Description
Sets the listen addresses for diameter requests. This
value is a comma separated list of address:port values. If
address is omitted, it is assumed to be *. If the port is
omitted, it defaults to 3868. Default value is *:3868. If
this property is not defined or set to zero (0) diameter
requests will not be processed.
Specifies the origin realm.
Specifies the origin host. Useful when testing diameter
when no outside network connection is available.
Specifies the amount of time (in milliseconds) allowed
before generating a peer state machine 'Timeout' event
as defined in RFC-3588, paragraph 5.6, during
connection establishment with a remote peer. As an
example, when an initiating peer attempts to connect to
a remote peer in the Closed state, it starts a timer
simultaneously with the connection request being sent.
Then, in 'Wait-Conn-Ack', the state that follows Closed,
a Timeout event is generated if no other event intervenes
and the connection state is brought back to Closed while
noting the peer as unavailable.
Specifies the time in milliseconds the peer is timed out if
idle.
Specifies the time in milliseconds before a peer is failed
back after being suspended (if it was failed over at the
time of suspension). Peers are getting suspended as a
result of an idle-timeout, either on the local side or by
the remote server requesting a connection shut down.
Without this time-out and no extended requests,
suspended peers would be kept in the failed over state
indefinitely if they were failed over when asked to
suspend.
Policy Server tab
365-360-001R6.0
Issue 1, December 2008

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents