Cisco Cisco Packet Data Gateway (PDG)
AAA Changes in Release 17
AAA Enhancements for 17.3 ▀
Release Change Reference, StarOS Release 17 ▄
43
CSCut26850 - Enhance multiple diameter peers to use same Host-name
Applicable Products: ePDG, GGSN, HA, HeNBGW, HNBGW, HSGW, IPSG, MME, PDSN, P-GW, SGSN,
SAEGW, SaMOG, S-GW
SAEGW, SaMOG, S-GW
Feature Changes
Provision for Multiple SCTP Associations towards Same Diameter Peer
The current endpoint configuration allows each SCTP association to be uniquely identified by a Diameter peer name.
But there was a requirement where two SCTP associations are identified with the same peer name. This kind of reused
peer-name was used by HSS peers which act as Active and Standby HSS nodes. The SCTP associations in HSS behave
in a manner such that one association is always SCTP active (for the active HSS) while the other SCTP association with
the standby HSS would be closed and would keep flapping. In order to allow configuring multiple SCTP associations
with same peer-name, a new optional keyword “
But there was a requirement where two SCTP associations are identified with the same peer name. This kind of reused
peer-name was used by HSS peers which act as Active and Standby HSS nodes. The SCTP associations in HSS behave
in a manner such that one association is always SCTP active (for the active HSS) while the other SCTP association with
the standby HSS would be closed and would keep flapping. In order to allow configuring multiple SCTP associations
with same peer-name, a new optional keyword “
destination-host-name
” has been introduced in the
peer
CLI
command that is available as part of the Endpoint configuration.
Important:
This enhancement is applicable to 17.2.2 and later releases.
This additional configuration option will allow multiple unique peers (Diameter HSS servers) to be configured with the
same host name. With this enhancement, MME will be capable of provisioning multiple Diameter SCTP associations to
reach the same HSS peer name. This configuration will also ensure that all the Diameter messages are exchanged
properly with the configured destination host.
same host name. With this enhancement, MME will be capable of provisioning multiple Diameter SCTP associations to
reach the same HSS peer name. This configuration will also ensure that all the Diameter messages are exchanged
properly with the configured destination host.
Internally the peers are identified with unique peer-name. But the Origin-host AVP provided by the server (in
CER/CEA/App-msgs) is validated against both peer-name and destination-host-name provided in the CLI. Even if
multiple peers are responding with same Origin-Host, this can be validated and accepted based on the CLI
configuration.
CER/CEA/App-msgs) is validated against both peer-name and destination-host-name provided in the CLI. Even if
multiple peers are responding with same Origin-Host, this can be validated and accepted based on the CLI
configuration.
Previous Behavior: Current Diameter endpoint implementation does not provide the flexibility to configure two
Diameter peers (servers) with the same host name.
Diameter peers (servers) with the same host name.
New Behavior: The existing endpoint peer CLI command has been enhanced to include optional Destination Host
Name information to address the customer’s requirement.
Name information to address the customer’s requirement.
If a peer is selected by Diameter base protocol to forward an application request, then the host name specified through
the “
the “
destination-host-name
” option will be used to encode the Destination-Host AVP.
This keyword “
destination-host-name
” is made optional for backward compatibility. That means, if the
destination-host-name is not specified in the CLI, the peer name itself is copied to the destination-host-name for
backward compatibility.
backward compatibility.
Command Changes
peer
A new optional keyword “
destination-host-name
” has been added as part of the
peer
CLI command in Diameter
endpoint configuration to allow configuring multiple unique peers with the same host name.
configure
context context_name