Specifications
192 Implementing IBM System Networking 10Gb Ethernet Switches
Run [no] ip route healthcheck to enable or disable static route health checks. The
default setting is disabled.
3. Verify the ECMP static routes operation.
Run show ip route static to display the static routes information. You can see the
difference between simple static routes and ECMP static routes in Example 5-41.
Example 5-41 ECMP static routes verification
Simple static route
ACC-1#sh ip route static
Current static routes:
Destination Mask Gateway If ECMP BGP
--------------- --------------- --------------- ---- ------ ------
10.0.0.0 255.255.0.0 10.0.101.2
ECMP health-check ping interval: 1
ECMP health-check retries number: 3
ECMP Hash Mechanism: sip dip tcpl4 udpl4 sport dport
Gateway healthcheck: disabled
ACC-1#
ECMP static route
ACC-1#show ip route static
Current static routes:
Destination Mask Gateway If ECMP BGP
--------------- --------------- --------------- ---- ------ ------
10.0.0.0 255.255.0.0 10.0.101.2 *
10.0.102.2 *
ECMP health-check ping interval: 1
ECMP health-check retries number: 3
ECMP Hash Mechanism: sip dip protocol tcpl4 udpl4 sport dport
Gateway healthcheck: enabled
ACC-1#
5.3.2 Basic IPv6 configuration
This section describes basic IPv6 implementation on the same network infrastructure as
IPv4, with minimal configuration changes.
The goal is to provide a starting point for a seamless IPv4 to IPv6 migration and to show how
IPv6 and IPv4 can coexist in the same network, by using the same hardware and software
resources, with no additional investment and without interfering each other.
The IPv6 implementation for the reference architecture uses the same layout as IPv4.
Both protocols run on identical Layer 1 and Layer 2 layers. IPv6 uses a different set of IP
interfaces, but has the same VLANs and STP configuration as IPv4. All the equipment is dual
stacked and run IPv6 and IPv4 simultaneously (both the switches and the hosts). Servers are
connected to switches using untagged ports, carrying IPv4 and IPv6 on the same VLAN.
The configuration is intended to be similar for both protocols, but some features are not
available in the IBM Networking OS implementation of IPv6.
Important: Carrying the IPv4 and the IPv6 traffic on the same VLAN facilitates an easy
migration with minimal configuration changes on the network infrastructure.