Cisco Cisco Packet Data Gateway (PDG)
HeNBGW Changes in Release 17
▀ HeNBGW Enhancements for 17.2
▄ Release Change Reference, StarOS Release 17
216
HeNBGW Enhancements for 17.2
This section identifies all of the HeNBGW enhancements included in this release:
Feature Changes - new or modified features or behavior changes. For details, refer to the HeNBGW Administration
Guide for this release.
Guide for this release.
Command Changes - changes to any of the CLI command syntax. For details, refer to the Command Line Interface
Reference for this release.
Reference for this release.
Performance Indicator Changes - new, modified, and deprecated bulk statistics, disconnect reasons, counters and/or
fields in new or modified schema and/or show command output. For details, refer to the Statistics and Counters
Reference for this release.
fields in new or modified schema and/or show command output. For details, refer to the Statistics and Counters
Reference for this release.
Important:
This release includes enhancements that are applicable to multiple products. The following lists the
various multi-product enhancements sections, some of which might include content applicable to your HeNBGW.
AAA Enhancements
CF Enhancements
ECS Enhancements
Firewall Enhancements
GTPP Enhancements
Lawful Intercept Enhancements
MVG Enhancements
NAT Enhancements
SNMP MIB Enhancements
System and Platform Enhancements
CSCuq12965 - DHCPv4 Proxy support for HeNBGW with IPSec
Feature Changes
DHCP support
The DHCPv4 proxy functionality on the SeGW integrated with HeNBGW is to update the DHCP messages with the
HeNB Id in DHCP Option 61 (Client ID) and forward the DHCP messages to an external DHCP server.
HeNB Id in DHCP Option 61 (Client ID) and forward the DHCP messages to an external DHCP server.
1. The SeGW forwards DHCP requests from a LTE FAP to an external DHCP server during IPSec Setup.
2. The SeGW adds LTE FAP Id in the Client Identifier (CID) of the DHCP messages.
3. The PNR then receives these DHCP requests maintains a mapping between the LTE FAP ID and the assigned
2. The SeGW adds LTE FAP Id in the Client Identifier (CID) of the DHCP messages.
3. The PNR then receives these DHCP requests maintains a mapping between the LTE FAP ID and the assigned
"Inner" IP Address
4. The RMS queries the PNR to get the LTE FAP inner IP Address, to use this inner IP Address to send TR-069
Connection Requests to the LTE FAP.