Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

PowerScale OneFS 9.8.0.0 Web Administration Guide

PDF

Source-based routing

Source-based routing (SBR) selects which gateway to direct outgoing client traffic through based on the source IP address in each packet header.

When enabled, source-based routing automatically scans your network configuration to create client traffic rules. If you modify your network configuration, for example, changing the IP address of a gateway server, source-based routing adjusts the rules. Source-based routing is applied across the entire cluster.

In OneFS 9.8 and later, the IPv6 protocol is supported and source-based routing is enabled by default. Enabling or disabling source-based routing goes into effect immediately. Packets in transit continue on their original courses, and subsequent traffic is routed based on the status change. If the status of source-based routing changes during transmission, transactions that are composed of multiple packets might be disrupted or delayed.

In the event where there is more than one matching route, rules that are made from static routes are evaluated first. If a static route matches, static routes are prioritized over source-based rules. When a static route is added, the matching static route is found first and takes precedence over source-based routing routes. If both source-based routing and static routes are configured, the static routes always take priority for traffic that matches the static routes.

Source-based routing should be enabled if you have a large network with a complex topology. For example, if your network is a multitenant environment with several gateways, traffic is more efficiently distributed with source-based routing.

Examples

In the following example, source-based routing is enabled on a PowerScale cluster that is connected to SubnetA and SubnetB. Each subnet is configured with a SmartConnect zone and a gateway, also labeled A and B. When a client on SubnetA makes a request to SmartConnect ZoneB, the response originates from ZoneB. The result is a ZoneB address as the source IP in the packet header, and the response is routed through GatewayB. Without source-based routing, the default route is destination-based, so the response is routed through GatewayA.

In another example, a client on SubnetC, which is not connected to the PowerScale cluster, makes a request to SmartConnect ZoneA and ZoneB. The response from ZoneA is routed through GatewayA, and the response from ZoneB is routed through GatewayB. In other words, the traffic is split between gateways. Without source-based routing, both responses are routed through the same gateway.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\