RepNet Table

The Secure Edge Portal includes a RepNet table where you can view a consolidated list of all Representational Network NATs applied within your environment. The RepNet table provides information about the Network Address Translation (NAT), and includes a calculator to help convert native IPs to RepNet IPs (and vice versa).

You can access the table from the RepNet Table menu item, under Networks in the portal’s left menu.

The RepNet Table contains three tabs: From Edge, From Virtual, and Edge Static Routes.

• From Edge: The Representational Network, when applied on the Edge iNode, provides NAT on remote networks connected upstream of Virtual iNodes, i.e., the subnet supporting the cloud infrastructure behind the Virtual iNode. This is to mitigate IP conflicts that could arise when a single Edge Network (TAN) is connected to two or more cloud destinations, each with their own Virtual iNode, that utilize the same subnet. When a device downstream of an Edge iNode must communicate to two isolated cloud applications, each app behind a dedicated Virtual iNode having the same subnet assigned behind both Virtual iNodes, then static routes will get added to the device using the RepNet associated with each Virtual iNode.
  
  Example: Access Control panel connected behind Edge iNode has two tunnels connected to it: (a) for Remote Access portal via Virtual iNode 1, and (b) for Data Pipeline to centralized ACS server behind Virtual iNode 2. Both subnets behind Virtual iNode 1 and Virtual iNode 2 are 10.0.10.0/23. To avoid routing conflicts from the ACS panel to either cloud destination, we configure two RepNets on the Edge iNode: (a) 172.20.1.0/23 for Virtual iNode 1, and (b) 172.20.3.0/23 for Virtual iNode 2. This ensures remote access traffic flows through Virtual iNode 1 while data traffic to the ACS server flows through Virtual iNode 2.

• From Virtual: The Representational Network, when applied on the Virtual iNode, provides NAT on remote networks connected downstream of Edge iNodes. This is to mitigate IP conflicts that could arise when the same subnet is utilized across sites that are connected to the same Virtual iNode. When referencing any edge device from cloud infrastructure that sits behind a Virtual iNode, users will reference devices by their RepNet IP instead of their native IP.
  
  Example: Site A and Site B both have their BMS networks utilizing 192.168.1.0/24 and both Edge iNodes at each site are connected to the same Virtual iNode. Two RepNets will be assigned on the Virtual iNode: (a) 172.10.1.0/24 for Site A, and (b) 172.10.2.0/24 for Site B. For any cloud application that sits behind the Virtual iNode, users shall reference devices at Site A using 172.10.1.x and devices at Site B using 172.10.2.y.

• Edge Static Routes: This is an extension of Representational Network when applied on the Virtual iNode. However, this provides NAT for segmented networks configured as static routes on a given Edge Network (TAN). The difference being that RepNet for segmented networks is applied at the Edge iNode when configuring a static route. When referencing any segmented device from cloud infrastructure that sits behind a Virtual iNode, users will reference these segmented devices by the RepNet IP configured in the static route settings instead of their native IP.
  
  Example: BMS network is connected to Edge iNode. The BMS subnet has a segmented chiller network connected downstream. This segmented chiller subnet is not directly connected to the Edge iNode but has devices that need to be attached to a cloud hosted BMS application. A static route for the chiller subnet is added to the BMS TAN configuration and assigned an appropriate RepNet. When attaching chiller devices to the cloud hosted BMS application, users will configure them utilizing the associated RepNet IP instead of their native IP.

When you select a row entry in the RepNet table, more tools will become available. The pop-up displays a portion of the NAT Table with the option to export (as a .csv) the full list. At the top of the pop-up display is a calculator tool to translate between Native IP and RepNet IP (or vise versa).