Skip Navigation Links | |
Exit Print View | |
Managing Oracle Solaris 11.1 Network Performance Oracle Solaris 11.1 Information Library |
1. Introduction to Network Performance Management
4. Administering Bridged Networks (Tasks)
How to Configure an IPMP Group That Uses DHCP
How to Manually Configure an Active-Active IPMP Group
How to Manually Configure an Active-Standby IPMP Group
How to Add an Interface to an IPMP Group
How to Remove an Interface From an IPMP Group
How to Move an Interface From One IPMP Group to Another IPMP Group
Configuring Probe-Based Failure Detection
Requirements for Choosing Targets for Probe-based Failure Detection
Configuring Probe-Based Failure Detection (Task Map)
How to Select Which Failure Detection Method to Use
How to Manually Specify Target Systems for Probe-Based Failure Detection
How to Configure the Behavior of the IPMP Daemon
Customizing the Output of the ipmpstat Command
Using the ipmpstat Command in Scripts
7. Exchanging Network Connectivity Information With LLDP
8. Working With Data Center Bridging Features in Oracle Solaris
9. Edge Virtual Bridging in Oracle Solaris
10. Integrated Load Balancer (Overview)
11. Configuring Integrated Load Balancer
12. Managing Integrated Load Balancer
13. Virtual Router Redundancy Protocol (Overview)
A. Link Aggregation Types: Feature Comparison
When you configure an IPMP group, the IPMP interface inherits the IP addresses of its underlying interfaces to use them as data addresses. The underlying interfaces then receive the IP address 0.0.0.0. Consequently, routes that are defined using specific IP interfaces become lost if these interfaces are subsequently added to an IPMP group.
Loss of routing when configuring IPMP commonly involves the default route and occurs in association with an Oracle Solaris installation. During installation, you are required to define a default route, for which you use an interface in the system, such as the primary interface. Subsequently, you configure an IPMP group by using the same interface on which you defined the default route. After the IPMP configuration, the system can no longer route network packets because the interface's address has been transferred to the IPMP interface.
To ensure that the default route is preserved while you use IPMP, the route must be defined without specifying the interface. In this manner, any interface, including the IPMP interface, can be used for routing. Thus the system can continue to route traffic.
Note - This section uses the primary interface as an example on which the default route is defined. However, the routing loss case applies to any interface that is used for routing and which later becomes part of an IPMP group.
The following procedure explains how to preserve the default route when you configure IPMP.
You must use the console to perform this procedure. If you use the ssh or telnet command to log in, the connection will be lost when you perform the subsequent steps.
# netstat -nr
# route -p delete default gateway-address -ifp interface
# route -p add default gateway-address
# netstat -nr
# svcadm restart routing-setup
Example 6-1 Defining Routes for IPMP
This example assumes that the default route was defined for net0 during the installation.
# netstat -nr Routing Table: IPv4 Destination Gateway Flags Ref Use Interface ------------- ------------ -------- ----- ----------- -------- default 10.153.125.1 UG 107 176682262 net0 10.153.125.0 10.153.125.222 U 22 137738792 net0 # route -p delete default 10.153.125.1 -ifp net0 # route -p add default 10.153.125.1 # netstat -nr Routing Table: IPv4 Destination Gateway Flags Ref Use Interface ------------- ------------ -------- ----- ----------- -------- default 10.153.125.1 UG 107 176682262 10.153.125.0 10.153.125.222 U 22 137738792 net0