96
Power on Wheels
Connecting to the customer network
The Power on Wheels “tower” contains a network switch that all the nodes and servers
connect into. The last gigabit ethernet port on the switch is defined for the admin network
(129.40.100.32/27). Customers who want to connect the tower into their internal network and
allow remote access, need to implement a gateway for this network and add the necessary
routing. Depending on restrictions as to what IP ranges are valid in the internal network,
NAT may be needed.
Gateway
The gateway IP for the tower admin network is 129.40.100.62. The servers have this IP
defined as their default route. A router or firewall device, managed by the customer, should
be configured with this IP.
Example for Cisco 6509 switch/router:
vlan 101
name pwr_n_whls_129.40.100.32/27
interface vlan 101
desc Power on Wheels gateway
ip address 129.40.100.62 255.255.255.224
no shut
Once the gateway is defined and the switch port connected, ping attempts from the gateway
to the nodes will help verify proper connectivity.
Routing
In order for the tower environment to be reachable outside the subnet, its network should be
advertised in the customer’s internal network. The details depend on how routing is set up; it
is possible that adding the gateway definition in the router automatically injects that network
into whatever routing protocol (RIP, OSPF, etc) is being used. However, if a firewall was
used to implement the gateway, then the router connecting to its inbound interface may need
a route manually defined.
Example for Cisco 6509, assuming next hop is a firewall that has an ‘inside’ address of
10.1.1.1 and an ‘outside’ address of 129.40.100.62 (the tower gateway):
ip route 129.40.100.32 255.255.255.224 10.1.1.1
Router vs. Firewall
If there are technical or policy reasons that prohibit 129.40.100.32/27 from being advertised
in the customer network, a method to hide the real addresses will need to be implemented. It
Komentarze do niniejszej Instrukcji