1aoe-sancheck(8)             System Manager's Manual            aoe-sancheck(8)
2
3
4

NAME

6       aoe-sancheck - verify storage network capabilities
7

SYNOPSIS

9       aoe-sancheck [-v]
10

DESCRIPTION

12       The  aoe-sancheck  command  collects information about the local inter‐
13       faces and probes the network for ATA over Ethernet devices,  validating
14       the  paths  for  each device. It does not use the aoe kernel module but
15       rather the bpf interface to evaluate the network.   As  such,  the  aoe
16       module does not need to be loaded to perform the test.
17
18       The  output  of  the  command is divided into two sections: information
19       about the local interfaces followed by a list of detected AoE  devices.
20       The first section displays the local interfaces, if the interface is up
21       or down, its configured MTU, and the PCI ID for the interface.
22
23       The second section lists detected AoE devices, one per line,  with  the
24       following information:
25
26       Device The device name of the form eX.Y where X is the AoE device shelf
27              address, and Y is the AoE device slot address.
28
29       Macs   The number of mac addresses detected for this device.
30
31       Payload
32              The number of bytes of data the device can handle  in  a  single
33              AoE request. This number does not represent the total frame size
34              as it does not include bytes from ethernet or AoE headers.
35
36       Local Interfaces
37              The list of local interfaces from which the device is visible.
38
39   Options
40       -v     Prints out additional raw information.
41

DIAGNOSIS

43       For each device, aoe-sancheck may print out additional lines of sugges‐
44       tions or warnings.  The following checks are made:
45
46       The  MTU  of  the local interfaces is set high enough to handle the AoE
47       device's reported payload.
48              Depending on the host NIC's  capabilities  and  storage  network
49              switch's  capabilities,  best performance may or may not be with
50              local interface MTU set higher than a device's payload size.
51
52       The number of local interfaces matches the number of interfaces on  the
53       device.
54              Best performance comes from having a host and device with compa‐
55              rable bandwidth. Aoe-sancheck simply counts the number of inter‐
56              faces involved and does not figure link bandwidth in its compar‐
57              ison.
58
59       All local interfaces for an AoE device have the same MTU.
60              If one interface for a device has a smaller MTU than the others,
61              the  AoE driver must use the smaller payload size for all inter‐
62              faces.
63
64       Each path to the device is capable of the configured payload size.
65              This check detects the situation where a local interface is con‐
66              figured  for jumbo frames and the AoE device is capable of jumbo
67              frames, but some aspect of the network is incapable  of  passing
68              frames  that  size,  for  example, a misconfigured switch.  Aoe-
69              sancheck reports the maximum payload size the path is capable of
70              if less than the configured payload size.
71

BUGS

73       The  program  may  sometimes  display inconsistent results between runs
74       showing that a path is capable of a smaller frame size than it actually
75       is.   If  you  see  this behavior, please email one of the authors with
76       your verbose output.
77

SEE ALSO

79       aoeping(8), aoetools(8)
80

AUTHORS

82       Justin Sanders (justin@coraid.com), Sam Hopkins (sah@coraid.com)
83
84
85
86                                                               aoe-sancheck(8)
Impressum