29. Layer 3 Switching
ROX™ v2.2 User Guide 292 RuggedBackbone™ RX5000
29.1.9. Sample Use Case
Consider the network illustrated below. The switch connecting all of these networks is a
RuggedBackbone™ Layer 3 switch.
Figure 29.2. Layer 3 Switch Use Case
Assume the following:
• VLAN 150 and VLAN 250 have approximately 200 devices each.
• VLAN 300 is a server farm with RuggedNMS and some other servers polling these devices on a
near-constant basis. The IP address for Server 1 is 172.30.30.10. The IP address for Server 2 is
172.30.30.20
• VLAN 400 connects the Layer 3 switch to an external network via a gateway with the IP address
172.30.40.2.
• Devices and servers in VLAN 150, 250 and 300 should only be able to reach 2 networks –
10.200.50.0/24 and 10.200.60.0/24 – for management purposes.
• The 400 devices in VLAN 150 and VLAN 250 receive IP multicast data from the external network
(VLAN 400) at the address 227.100.20.100.
• Servers in VLAN 300 receive IP multicast data from the external network (VLAN 400) at the address
227.100.250.250.
• No firewall is used in this use case.
Assume all Layer 2 switching-related configuration has been done; that is, the VLANs have been
created with proper port assignment. In this example, no specific Layer 3 switch configuration is explicitly
required. As long as a software router configuration is sufficient for the above requirements, the Layer
3 Switch will be able to function through auto-learning switching rules. However, the Layer 3 switching
configuration described in the following sections is recommended for better utilization of CPU and Layer
3 switching ASIC resources:
• Section 29.1.9.1, “Setting up Unicast Routes”
• Section 29.1.9.2, “Setting up Multicast Routing”
• Section 29.1.9.3, “Configuring Static Layer 3 Switching Rules for Servers”
• Section 29.1.9.4, “Configuring Static ARP Table Entries for Servers”
• Section 29.1.9.5, “Layer 3 Switching Rules for Devices in VLANs 150 and 250”
To Next Page
Loading...
Need help?
General
