Smooth integration of SteelConnect into existing networks

Solution Number:
S28029
Last Modified:
2020-05-16
Issue

In order to set up SteelConnect appliances for demos, lab, evaluation or testing purposes, it is often needed to smoothly integrate them into an existing network infrastructure, without the need to completely change the network cabling, routing or IP addressing schemes. This HOW TO gives some configuration hints about the needed steps to set up the network components (SteelConnect and non-SteelConnect). Please be aware that, due to security and routing considerations, we do not recommend to have this setup be a permanent configuration, consider this as a suggestion of a temporary special integration.

In this HOW TO, you see that two network cable connections are plugged into the same switch and network (the green and the orange cable), which might look unusual. The reason for this is that one cable (the green one) is used as the uplink connection for the gateway, whereas the orange cable is used as the LAN connection which serves for the existing (wired) clients as routing destination. Be aware that in this special configuration the SteelConnect Gateway needs two IP addresses out of the existing IP network pool – in our example it´s 192.168.0.254 (for the LAN-connection) and 192.168.0.2 (for the Uplink connection).

Solution

Example 1: No change to existing clients, new IP network for wireless clients
Example 2: SteelConnect Gateway as new default Gateway, new IP network for wireless clients
Example 3: SteelConnect Gateway as new default Gateway, existing IP network enhanced

No change to existing clients, new IP network for wireless clients

In this example we want to integrate SteelConnect products into an existing network environment.
SteelConnect’s Default HQ Zone has IP range 172.16.0.0/24 and we want to connect it with the existing network 192.168.0.0./24
The default gateway and DHCP Server for the existing network is a Router with the IP Address 192.168.0.1
We used the IP 192.168.0.254 of the existing network. Please make sure that this IP is not in the range of the DHCP Server and not used for a static IP assignment.

In addition to an unchanged HQ default configuration the following steps are necessary to implement the network scheme:

  1. Add a Zone into Site HQ for 192.168.0.0/24 via SteelConnect Manager > Network Design > Zones > New Zone
    1. select Site HQ
    2. Enter a name for the Zone (e.g. ExistingNetwork)
  2. Once the Zone is created edit the configuration
    1. Select Zone ExistingNetwork
    2. Navigate to Tab Gateways and select Manual
    3. Delete the Gateway assignment
    4. Add a new assignment with the following settings:
      • Gateway appliance: select the G50
      • Gateway type: Member
      • IP assignment: Manual (It’s also possible the obtain an IP address from the DHCP Server of the Router)
      • IPv4 Address: 192.168.0.254
      • DHCP/RA Server: Off
      • Inbound NAT: Off (Enable inbound NAT if you can’t create the route on your router. Point 7)
      • Skip outbound NAT: Off
      • navigate to Tab IP and change IPv4 Network to 192.168.0.0/24 and Gateway to 192.168.0.1
  3. Navigate to Ports section to configure one of the LAN ports of the SteelConnect Gateway into the Zone ExistingNetwork
    1. select port LAN1
    2. navigate to Tab Settings and select Zone ExistingNetwork
  4. Plug a cable into port LAN1 and connect it via the Switch to the 192.168.0.0/24 network
  5. Plug a cable into port WAN1 and connect it via the Switch to the Router 192.168.0.1
  6. Connect the SteelConnect Access Point (Ocedo Access Point) to port LAN2
  7. To get traffic flow between both networks add a route to the Router for 172.16.0.0/24 via 192.168.0.254

    Please note that Uplink Traffic from Clients in the existing Network won’t be reported in SteelConnect’s Traffic Timeline since the default gateway is the Router and not the SteelConnect Gateway.

    Make sure If autotrunking is active for the port LAN2 and on the AP if you want to broadcast the existing network with the SteelConnect Access Point.
     

SteelConnect Gateway as new default Gateway, new IP network for wireless clients

 

In this example the SteelConnect Gateway will become the new Default Gateway for the existing network 192.168.0.0/24 in the Headquarter and serves IP addresses for 192.168.0.0/24 and the new SteelConnect (Ocedo) network 172.16.0.0/24.
We used the IP 192.168.0.2 of the existing network. Please make sure that this IP is not in the range of the DHCP Server and not used for a static IP assignment.

In addition to an unchanged HQ default configuration the following steps are necessary to implement the network scheme:

  1. Add a Zone to Site HQ for network 192.168.0.0/24 via SteelConnect Manager > Network Design > Zones > New Zone
    1. Select Site HQ
    2. Enter a name for the Zone (e.g. ExistingNetwork)
  2. Once the Zone is created edit the configuration
    1. Select Zone ExistingNetwork
    2. Navigate to Tab IP and change IPv4 Network to 192.168.0.0/24 and Gateway to 192.168.0.254
  3. Change the existing Headquarter Uplink from DHCP to Static via SteelConnect Manager > Network Design > Uplinks
    1. Select HQ Uplink
    2. Navigate to Tab Settings and switch to Static IPv4 Type
      • Address: 192.168.0.2
      • Gateway: 192.168.0.1
  4. Navigate to Ports section to configure one of the LAN ports of the SteelConnect Gateway into Zone ExistingNetwork
    1. Select port LAN1
    2. Navigate to Tab Settings and select Zone ExistingNetwork
  5. Plug a cable into port LAN1 and connect it via the Switch to the 192.168.0.0/24 network
  6. Plug a cable into port WAN1 and connect it via the Switch to the Router 192.168.0.1
  7. Connect the SteelConnect Access Point to port LAN2
  8. Disable DHCP Server functionality on the Router for 192.168.0.0/24

Make sure If autotrunking is active for the port LAN2 and on the AP if you want to broadcast the existing network with the SteelConnect Access Point.
 

SteelConnect Gateway as new default Gateway, existing IP network enhanced

 

In this example the SteelConnect Gateway will become the new Default Gateway and DHCP Server for the existing network 192.168.0.0/24 in the Headquarter.

The SteelConnect Gateway is connected with two ports to the existing network. One cable is connected to the Uplink WAN Port and the other one to LAN Port.
We used the IP 192.168.0.2 of the existing network. Please make sure that this IP is not in the range of the DHCP Server and not used for a static IP assignment.

In addition to an unchanged HQ default configuration the following steps are necessary to implement the network scheme:

  1. Edit the HQ Zone configuration via Connect Controller > Network Design > Zones
    1. Select the HQ Zone
    2. Navigate to Tab IP and change IPv4 Network to 192.168.0.0/24 and Gateway to 192.168.0.254
  2. Change the existing Headquarter Uplink from DHCP to Static via SteelConnect Manager > Network Design > Uplinks
    1. Select the HQ Uplink
    2. Navigate to Tab Settings and switch to Static IPv4 Type
      • Address: 192.168.0.2
      • Gateway: 192.168.0.1
  3. Plug a cable into port LAN1 and connect it via the Switch to the 192.168.0.0/24 network
  4. Plug a cable into port WAN1 and connect it via the Switch to the Router 192.168.0.1
  5. Connect the SteelConnect Access Point to LAN2 Port
  6. Disable DHCP Server functionality on the Router for network 192.168.0.0/24
Environment

SteelConnect Gateway
SteelConnect Access Point
SteelConnect Manager

Attachments
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Can't find an answer? Create a case