DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
In this section:
This object specifies the gateway to which you wish to direct traffic from your Packet, Management, or Link Interface. In effect, this object allows you to add, change, and delete gateways (next Hops) to these interfaces. Interface and static routes combine to form the IP routing table for your network.
This table must ultimately provide a route to each potential call destination IP address. The static route is used to add static IP routes for the IP interfaces. A static route indicates the nextHop gateway and IP interface that should be used for a particular peer network IP prefix.
Each signaling port within an Address Context must use a unique IP address and port number combination.
The SBC 5210 and SBC 7000 systems support creating IP Interface Groups containing sets of IP interfaces that are not "processor friendly" (i.e. carried on physical Ethernet ports served by separate processors). However, restrictions exist regarding the usage of such Interface Groups.
(This ability does not apply to the SBC 5110 and 5400 systems which have only two physical media ports. IP interfaces from the two physical ports may be configured within the same IP Interface Groups without restrictions.)
For complete details, refer to Configuring IP Interface Groups and Interfaces.
On SBC main screen, navigate to Configuration > System Provisioning > Category: Base Provisioning > Static Route.
The Static Route window is displayed.
The Static Route can be checked for each Address Context or for all the Address Contexts created. Use the drop-down box to select the desired Address Context.
To edit any of the Static Routes in the list, click the radio button next to the specific Static Route name.
The Edit Selected Static Route window is displayed below.
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.
The SBC does not allow to edit the Condition
for a Static Route
. To change the configuration of Condition
, delete the Static Route
and reconfigure it.
To create a new Static Route, click New Static Route tab on the Static Route List panel. The Create New Static Route window is displayed.
The following fields are displayed:
For a High Availability (HA) pair configuration, the SBC allows configuring a Static Route
for a specific host or CE Name
among the active and standby hosts of a HA pair configuration using the Condition
element. The Condition
element store the conditions on the basis of which routes are added to a SBC pair with HA configuration. Currently, the Condition
element only supports the CE Name
element.
Before configuring the Condition
using a specific CE Name
, ensure that IP Interface Group Name
and IP Interface Name
are configured. These three elements cannot be configured and saved simultaneously. For further details, refer to System Provisioning - IP Interface Group and IP Interface Group - IP Interface.
Static Routes
with specific CE Name
can be added only for packet interfaces.
To copy any of the created Static Route and to make any minor changes, click the radio button next to the specific Static Route to highlight the row.
Click Copy Static Route tab on the Static Route List panel. The Copy Selected Static Route window is displayed along with the field details which can be edited.
Make the required changes to the required fields and click Save to save the changes. The copied Static Route is displayed at the bottom of the original Static Route in the Static Route List panel.
To delete any of the created Static Route, click the radio button next to the specific Static Route which you want to delete.
Click the Delete symbol at the end of the highlighted row. A delete confirmation message appears seeking your decision.
Click Yes to remove the specific Static Route from the list.
CE Name
separately.Static Route
is deleted only from the instance in which it is configured, and not from both active and standby instances of a HA pair SBC configuration.