Fabric OS Documentation Updates Supporting Fabric OS v7.0.x

52 Fabric OS Documentation Updates
53-1002165-10
Documentation updates for Fabric OS v7.0.0 and later
11
Under the heading “Validating IP connectivity” in Table 7, are the following changes:
• On page 40, there is a change to the arguments and percentage values for QoS Priority
Percentages. They should be as follows.
Short option: -q high, med, low
Long option: - -qos high, med, low or - -qos- high, - -qos-med, - -qos--low
Operands: Percentage. Whole values from 10-80 (total 100).
Under the heading “Validating IP connectivity” in Table 8, are the following changes:
• On page 42, there is a change to the argument for Committed rate. The short options should
be -b and -B.
• On page 42, there is a change to the description for Adaptive rate limiting (ARL) for short option
-b.
The valid ranges for -min-comm-rate are 10,000 Kbps through 10,000,000 Kbps for GbE ports
• On page 42, there is a change to the description for Adaptive rate limiting (ARL) for short option
-B.
The valid ranges for -max-comm-rate are 10,000 Kbps through 10,000,000 Kbps for GbE
ports.
• On page 43, there is a change to the description for Keep-alive timeout.
The range of valid values is 0.5 through 7,200 seconds.
• Under “Creating a multicircuit tunnel (example)” on page 46, the paragraph following Figure 13
should read as follows.
Although six circuits per tunnel are configured in the example and six circuits is the maximum
for the 7800 switch or ten FCIP circuits can be configured per 10 GbE port on a FX8-24 blade,
you can create less circuits if you desire. To create multiple tunnels, simply configure tunnels
and circuits for these tunnels. For details, refer to the following sections of this guide:
• Under “WAN performance analysis tools,” the command in the last bullet should be portShow
fcipTunnel - - perf.
Chapter 3, FCIP on the FR4-18i Blade
The following section is added under “Creating IP interfaces and routes.”
IP interface considerations
There may be an issue with a tunnel not initiating after creating new IP interfaces (IPIFs) for a
FR4-18i blade GbE interface when multiple IPIFs exist for the tunnel on the same GbE interface.
This occurs when the received destination IP address falsely appears to be a broadcast address
when compared to the first IPIF subnet mask. To avoid this problem, always define IPIFs in order,
with the most available host addresses defined first.
As an example, if IP subnet 1 has a mask of 255.255.255.0 and subnet 2 has a mask of
255.255.0.0, then the first IPIF defined on a GbE port should be the subnet 2 IPIF (as it is the least
restrictive address). This will avoid a false positive check for a broadcast address for any IP address
in subnet 1.