Personal Identity Network
Feature Overview
The PIN solution involves creating Personal Area Networks (PAN) for each unit in a Multi-Dwelling Unit (MDU) or dorm room in a university campus, using a shared network (access points, switches, and internet gateway).
The following devices are involved in the PIN service:
- RUCKUS Edge - Provides Internet Gateway functionality for each PAN.
- Distribution Switch (DS) - Acts as an aggregation point for all the access layer switches.
- Access Switch (AS) - Facilitates the connection of end-node devices, such as access points, to the network.
- Access Point (AP) - Facilitates the connection of end-user devices, such as smartphones and tablets, to the network.
RUCKUS Edge currently utilizes the WAN Link IP address for NAT with APs and switches. However, to manage more than 64K NAT sessions, which is often required in high-density environments, RUCKUS Edge employs multiple NAT IP addresses on the WAN interface. This approach ensures sufficient capacity and performance for extensive network traffic.
Requirements
To complete the LAG/Port & Virtual IP settings in the cluster configuration wizard, the user must create at least one physical LAN.
Limitations
Note the following limitations regarding this feature:
- Ensure that the firmware version is at least 2.3.0.1181 to support this feature
- Only Active-Standby High Availability (HA) support is available.
- SD-LAN and Personal Identity Network are mutually exclusive features. If RUCKUS Edge or Network is chosen for one service, it cannot be utilized for the other service.
- Only DPSK networks are supported, and the DPSK service must remain consistent within the Identity Group.
- The venue must have an Edge cluster and must enable Property Management within the Identity Group.
- Once a PIN has been created, the cluster, DHCP service, and DHCP pool cannot be modified in the profile.
- The tunnel profile is restricted to using only the VNI type within the PIN.
- Only physical ports and LAGs can be configured as cluster interfaces.
- The maximum number of NAT IP addresses supported per Edge device is 128.
- Each NAT IP can support up to 64,000 sessions per destination IP or port.
- Only RUCKUS Edge clusters in active/standby mode support multiple NAT IP addresses.
Considerations
Consider the following when configuring and using this feature:
- A maximum of 16 sub-interfaces is supported per physical port or LAG.
- Both NAT pool addresses and the WAN interface address will be used for NAT.
- The NAT pool addresses must reside within the same subnet as the WAN interface address to ensure proper network configuration and functionality.
- The Multiple Public NAT IP Address Support enhancement works independently, including when using dual-WAN link and even when the Edge device connection to RUCKUS One is down.
Best Practices
This feature has no special recommendations for feature enablement or usage.
Prerequisites
The following list outlines the prerequisites for building a PIN service. The RUCKUS One wizard will guide you through the steps to complete the entire PIN service setup.