Table of Contents
Advertisement
There are two routes.
sending packet using route No. 1
ml ip address structure, starting:
ml flag (ml interface up or down) = 0x00000000
ml tick = 0
ml ip address = 0xc0a80203, 192.168.2.3
There are two preferred route pairs:
from local if 0 to remote if 0
from local if 1 to remote if 1
There are two actual routes (two preferred).
---------------------------------------
from local if 0 to remote if 0
destination ip address structure:
if flag (up or down) = 0x000000c1
if tick = 0
ipaddr = 0xc0a80003, 192.168.0.3
---------------------------------------
from local if 1 to remote if 1
destination ip address structure:
if flag (up or down) = 0x000000c1
if tick = 0
ipaddr = 0xc0a80103, 192.168.1.3
5.12.3 Packets dropped because of a hardware problem on an
endpoint
To check for dropped packets at the HMC, check /var/adm/sni/sni_errpt_capture. Each
hardware event has an entry. If you don't have the register mappings for error bits, check whether
the errors are recoverable (non-MP-Fatal) or MP-Fatal. (MP-Fatal errors take longer to recover
from and could be associated with more drops.)
The following is an example of Recoverable/Non Mp Fatal entry in
/var/adm/sni/sni_errpt_capture:
Current time is:
Mon Oct 4 05:08:51 2004
Errpt Sequence num is: 3229
Errpt Timestamp is:
Mon Oct 4 05:08:51 2004
Event TOD is:
2004160209010410
Event TOD date:
Oct 04 09:02:16 2004
Not MP Fatal
DSS Log count = 07
1st Attn type = Recoverable
2nd Attn type = Recoverable
1st Alert type = Alert 02 - SMA Detected Error FNM handles callout
SMA chip (GFW #)
SMA location
SMA logically defined in this LPAR
Failure Signature
pshpstuningguidewp040105.doc
3
U1.28-P1-H1/Q1
sni1
8073D001
Page 27
Advertisement
Table of Contents
