Release Notes for CCII END GE Driver ------------------------------------- Version : 1.2 Release date : 2007-10-05 1. Getting Started --------------- 1.1. Boot vxWorks and load the ccGeEndxxx.a lib with 'ld < ccGeEndxxx'. Where xxx=X86 for X86 HCC xxx=18x for SVME/DMV-181/182/183 HCC xxx=Mv5100 for Motorola MVME-5100 HCC 1.2. Type 'muxDevStart ( muxDevLoad ( 0 , geLoad,"",0,0 ))' to start the driver. 1.3. Type 'ipAttach ( 0, "ccge" ) to attach the driver to TCP/IP. Verify that the ccge0 device exists by typing 'ifShow'. 1.4. Set the IP address using ifAddrSet. 1.5. Confirm the GE connection using ping. An example is shown below (NOTE: This example assumes there is already another NIC on the GE LAN which has been set up with an IP address of 10.0.0.1): -> muxDevStart ( muxDevLoad ( 0 , geLoad,"",0,0 )) value = 0 = 0x0 -> ifShow lo (unit number 0): Flags: (0x69) UP LOOPBACK ARP RUNNING Internet address: 127.0.0.1 Netmask 0xff000000 Subnetmask 0xff000000 Metric is 0 Maximum Transfer Unit size is 32758 0 packets received; 0 packets sent 0 input errors; 0 output errors 0 collisions ccge (unit number 0): Flags: (0x63) UP BROADCAST ARP RUNNING Netmask 0xffffffff Subnetmask 0xffffffff Ethernet address is 00:00:5a:45:f0:46 Metric is 0 Maximum Transfer Unit size is 1560 18 packets received; 0 packets sent 0 input errors; 0 output errors 0 collisions value = 18 = 0x12 -> ipAttach 0, "ccge0" value = 0 = 0x0 -> ifAddrSet "ccge0","10.0.0.4" value = 0 = 0x0 -> ping "10.0.0.1" PING 10.0.0.1: 56 data bytes 64 bytes from 10.0.0.1: icmp_seq=1. time=0. ms 64 bytes from 10.0.0.1: icmp_seq=2. time=0. ms 64 bytes from 10.0.0.1: icmp_seq=3. time=0. ms 64 bytes from 10.0.0.1: icmp_seq=4. time=0. ms 64 bytes from 10.0.0.1: icmp_seq=5. time=0. ms ccgeStats can be used to get some statistics from the driver. 1.6 Using the supplied TCP/UDP Blaster test software The TCP/UDP Blaster application transmits packets of data from one host to another as fast as possible using BSD sockets. Two versions of the Blaster application is provided, vxBlaster (for general TCP/UDP throughput testing) and vxMCBlaster (for testing the driver's newly added multicast functionality) The application consists of two components. The server component (“Blastee”) is initiated on one of the hosts, then the client component (“Blaster”) is initiated on the other. The Blastee, which receives data from the Blaster, reports the amount of data received at regular intervals (nominally every one second). It also reports the number of packets received against the number of packets lost. The application has the following parameters which are configured from the command line : server_ip_address: IP address of the server host multicast_ip_address: shared multicast IP address port: TCP or UDP port number dotcp: 0 used for UDP test; 1 used for TCP test size: size of the data packet in bytes buffer_length: size of the TCP or UDP buffer length in bytes delay: delay between data packets or bursts in milliseconds; 0 used for no delay burst: number of packets sent every delay milliseconds; only required if delay > 0; default value is 1 id: 0 can be used for testing. 1.6.1 vxBlaster usage in VxWorks Note: in this example the client host (Blaster) ip address is "10.0.0.1" and the server host (Blastee) ip address is "10.0.0.2" Load the Blaster application on each host as follows : ld < vxBlaster_x86_55.o (x86 PC hosts) ld < vxBlaster_ppc_55.o (CWV-183, DMV-182 and DMV-181 hosts) ld < vxBlaster_5100_55.o (MVME-5100 hosts) The command line parameters are : blaster (server_ip_address, port, dotcp, size, buffer_length, delay, burst) blastee (port, dotcp, size, buffer_length, id) Start Blastee on the server host as follows : sp blastee, 7000, 0, 1000, 32000, 0 (for UDP test) sp blastee, 7000, 1, 1000, 32000, 0 (for TCP test) Start Blaster on the client host as follows : sp blaster, “10.0.0.2", 7000, 0, 1000, 32000, 0 (for UDP test) sp blaster, “10.0.0.2", 7000, 1, 1000, 32000, 0 (for TCP test) The Blaster and Blastee can be terminated using the following commands : blasterStop = 1 blasteeStop = 1 1.6.2 vxMCBlaster usage in VxWorks Note: in this example the client host (mcBlaster) ip address is "10.0.0.1" and the server host (mcBlastee) ip address is "10.0.0.2" Load the multicast Blaster application on each host as follows : ld < vxMCBlaster_x86_55.o (x86 PC hosts) ld < vxMCBlaster_ppc_55.o (CWV-183, DMV-182 and DMV-181 hosts) ld < vxMCBlaster_5100_55.o (MVME-5100 hosts) The command line parameters are : mcBlaster (interface_ip_address, multicast_ip_address, port, size, buffer_length, delay, burst) mcBlastee (interface_ip_address, multicast_ip_address, port, size, buffer_length) Start Blastee on the server host as follows : sp mcBlastee, "10.0.0.2", "224.1.0.1", 7777, 1000, 16000 Start Blaster on the client host as follows : sp mcBlaster, “10.0.0.1", "224.1.0.1", 7777, 1000, 16000, 1000 The Blaster and Blastee can be terminated using the following commands : blasterStop = 1 blasteeStop = 1 1.6 See vxWorks documentation for building driver into kernel. 2. Known Issues with the Current Release ------------------------------------- (* = outstanding issue) 2.1 *Support for one card only at this stage. 2.2 *No support for END polled mode transmit and receive. 3. Revision History ---------------- 0.1 - 2005-10-03 - GJK First release. 0.2 - 2006-04-28 - GJK Added RLMT modes 0.3 - 2006-12-04 - ARK Resolved RLMT problems and optimised switchover times. Implemented scatter/gather. Implemented interrupt moderation. Added Motorola MVME-5100 support. 0.4 - 2006-12-12 - ARK Some performance optimisation. Implemented WRS TechTip 325. 0.5 - 2007-01-22 - ARK Driver now stable on CWV-183. Driver supports VxWorks 6.x (qualified on VxWorks 6.2). 1.0 - 2007-04-12 - ARK Driver now implements hardware checksum. Command line parameters now supported. 1.1 - 2007-08-19 - ARK Multicast support added. 1.2 - 2007-10-05 - ARK / OVS VxWorks 6.x support restored Readme.txt updated to include procedure for reconfiguring VxWorks to allow large UDP packet transmission