PIN Service
Feature Overview
The PIN solution involves creating Personal Area Networks (PAN) for each user (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 participate in the PIN service:
- RUCKUS Edge: Provides Internet Gateway functionality for each PAN.
- Access Point (AP): Connects Wi-Fi devices such as laptops, smartphones, and tablets to the network.
- Distribution Switch (DS): Aggregates all access layer switches connecting wired client devices.
- Access Switch (AS): Connects wired client devices to the network.
Multiple Public NAT IP Address Support
RUCKUS Edge uses the WAN link IP address for NAT with APs, switches, and client devices. To manage more than 64K NAT sessions, often required in high-density environments, RUCKUS Edge employs multiple NAT IP addresses on the WAN interface. This ensures sufficient capacity and performance for extensive network traffic.
Requirements
To complete the LAG/Port and Virtual IP settings in the cluster configuration wizard, the user must create at least one physical LAN.
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.
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 (PIN) 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 Edge cluster, APs, distribution switches, and access switches must be in same venue.
-
The venue must have an Edge cluster and must enable the property management feature 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.
-
Edge device supports up to 128 NAT IP addresses on the WAN interface.
-
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.
Best Practices
This feature has no special recommendations for feature enablement or usage.
Prerequisites
Before creating and activating a Personal Identity Network (PIN) service in RUCKUS One, the following prerequisites must be met. These requirements ensure that the RUCKUS One wizard can guide you through a smooth and successful PIN configuration process.
-
Configure DHCP Pools (for Internal DHCP): When using the internal DHCP on the Edge cluster, configure at least one DHCP pool for PAN. Add an infrastructure network/management pool for APs and switches. This is optional if a third-party DHCP server on the segment provides IP addresses.
-
- Create and Activate DPSK networks
- DPSK Wi‑Fi networks must be active at the venue.
- Match DPSK service to identity group
- DPSK networks must use the same DPSK service associated with the venue’s identity group in property management.
- Ensure APs are ready.
- APs at the venue must be onboarded and operational.
- APs must already have Identity and DPSK settings properly configured.