User`s manual

NIOC - Network I/O Control
3-148
3
Examples
Example 1: Initialize (type 0) the device/channel/node.
PPC1-Bug>NIOC <Return>
Controller LUN =00? <Return>
Device LUN =00? <Return>
Packet Address =00006454? <Return>
00006454 0000 0000 0000 0000 0000 0000 0000 0000 ................
00006464 0000 0000 ....
Send Packet (Y/N) =N? Y <Return>
PPC1-Bug>
Example 2: Retrieve the hardware address of the specified network
interface (type 1). Note that the transfer byte count is set to zero; this
specifies all possible data associated with the address retrieval. This
also holds true for the reception of data packets.
PPC1-Bug>NIOC <Return>
Controller LUN =00? <Return>
Device LUN =00? <Return>
Packet Address =00006454? <Return>
00006454 0000 0000 0000 0001 0000 E000 0000 0000 ................
00006464 0000 0000 ....
Send Packet (Y/N) =N? Y <Return>
PPC1-Bug>
View the address data retrieval.
PPC1-Bug>MD E000:6;B <Return>
0000E000 08 00 3E 21 0F CC ..>!..
PPC1-Bug>
Example 3: View the packet to transmit, ARP Request.
This example illustrates the transmission (type 2) of a packet (ARP
Request). The transfer byte count specifies how many bytes are to
be transmitted. If the transfer byte count is below the minimum
transmit byte count for the specified interface, the driver rounds to
the minimum and places it into your packet. However, the specified
network interface driver does not round down to the maximum if
the transfer byte count exceeds the maximum. You must ensure
packet integrity (e.g., source and destination addresses) for the
specified network interface; the driver does not insert any data.