RFC1944 - Benchmarking Methodology for Network Interconnect(2)

时间:2005-02-15 来源: 作者: 点击:
lengths of longer than 50 seconds may require that the router be configured for an extended ARP timeout. +--------+ +------------+ | | | phantom |------ P LAN A IN A------| DUT |------------| |------
  
lengths of longer than 50 seconds may require that the router
be configured for an extended ARP timeout.

+--------+ +------------+
| | | phantom |------ P LAN
A
IN A------| DUT |------------| |------ P LAN
B
| | OUT A | router |------ P LAN
C
+--------+ +------------+

Figure 2

In the case where full routing is being used

C.2.4.2 Routing Update Frame
If the test does not involve adjacent net routing the tester
must supply proper routing information using a routing update.
A single routing update is used before each trial on each
"destination" port (see section C.24). This update includes
the network addresses that are reachable through a phantom
router on the network attached to the port. For a full mesh
test, one destination network address is present in the routing
update for each of the "input" ports. The test stream on each

"input" port consists of a repeating sequence of frames, one to
each of the "output" ports.

C.2.4.3 Management Query Frame
The management overhead test uses SNMP to query a set of
variables that should be present in all DUTs that support SNMP.
The variables for a single interface only are read by an NMS
at the appropriate intervals. The list of variables to
retrieve follow:

sysUpTime
ifInOctets
ifOutOctets
ifInUcastPkts
ifOutUcastPkts

C.2.4.4 Test Frames
The test frame is an UDP Echo Request with enough data to fill
out the required frame size. The data should not be all bits
off or all bits on since these patters can cause a "bit
stuffing" process to be used to maintain clock synchronization
on WAN links. This process will result in a longer frame than
was intended.

C.2.4.5 Frame Formats - TCP/IP on Ethernet
Each of the frames below are described for the 1st pair of DUT
ports, i.e. "input" port #1 and "output" port #1. Addresses
must be changed if the frame is to be used for other ports.

C.2.6.1 Learning Frame

ARP Request on Ethernet

-- DATAGRAM HEADER
offset data (hex) description
00 FF FF FF FF FF FF dest MAC address send to
broadcast address
06 xx xx xx xx xx xx set to source MAC address
12 08 06 ARP type
14 00 01 hardware type Ethernet = 1
16 08 00 protocol type IP = 800
18 06 hardware address length 48 bits
on Ethernet
19 04 protocol address length 4 octets
for IP
20 00 01 opcode request = 1
22 xx xx xx xx xx xx source MAC address
28 xx xx xx xx source IP address

32 FF FF FF FF FF FF requesting DUT's MAC address
38 xx xx xx xx DUT's IP address

C.2.6.2 Routing Update Frame

-- DATAGRAM HEADER
offset data (hex) description
00 FF FF FF FF FF FF dest MAC address is broadcast
06 xx xx xx xx xx xx source hardware address
12 08 00 type

-- IP HEADER
14 45 IP version - 4, header length (4
byte units) - 5
15 00 service field
16 00 EE total length
18 00 00 ID
20 40 00 flags (3 bits) 4 (do not
fragment),
fragment offset-0
22 0A TTL
23 11 protocol - 17 (UDP)
24 C4 8D header checksum
26 xx xx xx xx source IP address
30 xx xx xx destination IP address
33 FF host part = FF for broadcast

-- UDP HEADER
34 02 08 source port 208 = RIP
36 02 08 destination port 208 = RIP
38 00 DA UDP message length
40 00 00 UDP checksum

-- RIP packet
42 02 command = response
43 01 version = 1
44 00 00 0

-- net 1
46 00 02 family = IP
48 00 00 0
50 xx xx xx net 1 IP address
53 00 net not node
54 00 00 00 00 0
58 00 00 00 00 0
62 00 00 00 07 metric 7

-- net 2

66 00 02 family = IP
68 00 00 0
70 xx xx xx net 2 IP address
73 00 net not node
74 00 00 00 00 0
78 00 00 00 00 0
82 00 00 00 07 metric 7

-- net 3
86 00 02 family = IP
88 00 00 0
90 xx xx xx net 3 IP address
93 00 net not node
94 00 00 00 00 0
98 00 00 00 00 0
102 00 00 00 07 metric 7

-- net 4
106 00 02 family = IP
108 00 00 0
110 xx xx xx net 4 IP address
113 00 net not node
114 00 00 00 00 0
118 00 00 00 00 0
122 00 00 00 07 metric 7

-- net 5
126 00 02 family = IP
128 00 00 0
130 00 net 5 IP address
133 00 net not node
134 00 00 00 00 0
138 00 00 00 00 0
142 00 00 00 07 metric 7

-- net 6
146 00 02 family = IP
148 00 00 0
150 xx xx xx net 6 IP address
153 00 net not node
154 00 00 00 00 0
158 00 00 00 00 0
162 00 00 00 07 metric 7

C.2.4.6 Management Query Frame

To be defined.

C.2.6.4 Test Frames
UDP echo request on Ethernet

-- DATAGRAM HEADER
offset data (hex) description
00 xx xx xx xx xx xx set to dest MAC address
06 xx xx xx xx xx xx set to source MAC address
12 08 00 type

-- IP HEADER
14 45 IP version - 4 header length 5 4
byte units
15 00 TOS
16 00 2E total length*
18 00 00 ID
20 00 00 flags (3 bits) - 0 fragment
offset-0
22 0A TTL
23 11 protocol - 17 (UDP)
24 C4 8D header checksum*
26 xx xx xx xx set to source IP address**
30 xx xx xx xx set to destination IP address**

-- UDP HEADER
34 C0 20 source port
36 00 07 destination port 07 = Echo
38 00 1A UDP message length*
40 00 00 UDP checksum

-- UDP DATA
42 00 01 02 03 04 05 06 07 some data***
50 08 09 0A 0B 0C 0D 0E 0F

* - change for different length frames

** - change for different logical streams

*** - fill remainder of frame with incrementing octets,
repeated if required by frame length

Values to be used in Total Length and UDP message length fields:

frame size total length UDP message length
64 00 2E 00 1A
128 00 6E 00 5A
256 00 EE 00 9A
512 01 EE 01 9A
768 02 EE 02 9A
1024 03 EE 03 9A
1280 04 EE 04 9A
1518 05 DC 05 C8
------分隔线----------------------------
顶一下
(0)
0%
踩一下
(0)
0%
------分隔线----------------------------
最新评论 查看所有评论
发表评论 查看所有评论
请自觉遵守互联网相关的政策法规,严禁发布色情、暴力、反动的言论。
评价:
表情:
用户名: 密码: 验证码:
推荐内容