Secure Socket Layer (Ssl); Secure Xml Api - Nomadix Access Gateways User Manual

A G
CCESS ATEWAY
example, WLAN Access Points and 802.3 switches) on private subnets on the subscriber side
of the Nomadix gateway. See also,
Two subsequent events drive the secure management function of the Nomadix gateway and the
devices behind it:
Establishing an IPSec tunnel to a centralized IPSec termination server (for example,
1.
Nortel Contivity). As part of the session establishment process, key tunnel parameters are
exchanged (for example, Hash Algorithm, Security Association Lifetimes, etc.).
2. The exchange of management traffic, either originating at the NOC or from the edge
device through the IPSec tunnel. Alternatively, AAA data such as RADIUS
Authentication and Accounting traffic can be sent through the IPSec tunnel. See also,
"RADIUS-driven Auto Configuration" on page
The advantage of using IPSec is that all types of management traffic are supported, including
the following typical examples:
ICMP - PING from NOC to edge devices

Telnet - Telnet from NOC to edge devices

Web Management - HTTP access from NOC to edge devices

SNMP





Secure Socket Layer (SSL)

This feature allows for the creation of an end-to-end encrypted link between your NSE-
powered product and wireless clients by enabling the Internal Web Server (IWS) to display
pages under a secure link—important when transmitting AAA information in a wireless
network when using RADIUS.
SSL requires service providers to obtain digital certificates to create HTTPS pages.
Instructions for obtaining certificates are provided by Nomadix.

Secure XML API

XML (eXtensible Markup Language) is used by the subscriber management module for user
administration. The XML interface allows the NSE to accept and process XML commands
from an external source. XML commands are sent over the network to your NSE-powered
product which executes the commands, and returns data to the system that initiated the
Introduction
"Defining IPSec Tunnel Settings" on page
SNMP GET from NOC to subscriber-side device (for example, AP)
SNMP SET from NOC to subscriber-side device (for example, AP)
SNMP Trap from subscriber-side device (for example, AP) to NOC
15.
139.
17