Anyone know where to download IP BootTest? 1

[Toni269]

None of the links for IP BootTest download are working.

I called Avaya Tier 3 and they have no clue what it is!

ipbootest@avaya.com emails are returned

Links on their website are blank...

http://support.avaya.com/japple/css/japple?PAGE=Product&temp.productID=141944

Thanks,

Toni

 

[ken07734]

Yes, I know what it is and I will look to see if I can find the link for it.

 

[ken07734]

Try this link all the way at the bottom of the page there is a link to the software. I would run it through your virus scan software before unzipping it to be sure it's safe.

 

[ken07734]

Sorry, forgot to post the link.

http://www.avayausers.com/showthread.php?p=56601

 

[Toni269]

Wow - GREAT Find, thank yo SO much, the link is good!
You Rock, a star for you!

 

[ken07734]

no problem....I was finally able to help someone!

 

[victor5908]

Forgive my ignorance but what is this used for?

 

[Toni269]

It's for testing if the DHCP and FTFP servers are setup correctly. Below is the readme/instruction file:

Avaya IP Boot Test


Avaya IP Boot Test User Instructions

Avaya IP Boot Test v1.3.2
October 23, 2002

1. Introduction


Avaya IP Boot Test is designed to test whether the DHCP and TFTP servers have been configured correctly to allow Avaya IP Phones to boot correctly. Avaya IP Boot Test provides information that can assist with the diagnosis of DHCP and TFTP configuration problems.

More specifically, Avaya IP Boot Test tests whether you have a DHCP and TFTP server set up according to the Avaya LAN Administrator v1.6 document. This document can be downloaded from the Avaya support website: go to

http://support.avaya.com

and search for "LAN Administrator"

You are welcome to send feedback or problem reports to ipboottest@avaya.com

Avaya IP Boot Test tests in two stages:

1. Avaya IP Boot Test makes DHCP requests for the number of endpoints specified with the options the IP Phone expects. Once it has been allocated the requested number of addresses, it then releases these addresses.

2. Avaya IP Boot Test tries to download the files "46xxupgrade.scr" and
"4630upgrade2.scr" as well as the files the SCR file references from the
specified TFTP server. To pass the test, these files need to be located on
the TFTP server as specified in the options provided by the DHCP server.

*WARNING*

Avaya IP Boot Test gets real IP addresses from your DHCP server. If other
applications are relying on the DHCP server to boot, and you exhaust the
available IP addresses using Avaya IP Boot Test, then these devices may
fail to boot. Read this file carefully before using Avaya IP Boot Test on
your network.

If Avaya IP Boot Test exits prematurely (e.g. the user ends the program before it has finished) some IP addresses may still be reserved by the DHCP server. Avaya IP Boot Test can be run with the -clean option to release these address reservations from the DHCP Server. The -clean option will read a temporary file created during normal execution that contains all the addresses that have been successfully allocated but are not yet released. When run with the -clean option Avaya IP Boot Test will send Release messages to the DHCP server, releasing any IP addresses that Avaya IP Boot Test knows it has allocated.

Because TFTP testing for the 4630 involves a large number of binary images, the run time for a complete TFTP download test may be unacceptably long. To speed up the TFTP testing, Avaya IP Boot Test will only get the first data block (512 bytes) of each binary image to verify its presence on the TFTP server and then terminate the download. After running TFTP testing, error messages may appear on the TFTP server log per file that Avaya IP Boot Test verifies. For instance on the Avaya TFTP server, the user will observe "Inconclusive System Error [From Remote]" for each image file. This error can be safely ignored when it relates to Avaya IP Boot Test operation.
2. Supported Platforms

Avaya IP BootTest will run on Microsoft Windows 98/ME/NT4/2000/XP. It requires a PC with at least a 400MHz Pentium II Processor and the minimum RAM required for the Operating System.
3. Suggested Usage

The suggested usage of the tool is to run it for a single endpoint in verbose mode. This will indicate whether the DHCP and TFTP servers are functioning properly. Once this has been verified the tool can be run with the -n option to check that there is sufficient capacity, i.e. that addresses for the number of endpoints for the particular installation can be successfully allocated.
4. Options

The program defaults to running both the DHCP test (for a single endpoint) and the TFTP test. All output defaults to standard out.

-i - Invoke interactive mode, user will be prompted for input.
-n [ number ] - Number of phones to be simulated (default = 1, max = 255).
-h - Print out the list of options.
-o [ Filename ] - Output to filename rather than standard out.
-tftp [ Address ] - Run only the TFTP test using the TFTP server supplied.
-tftpdir [ Path ] - TFTP path.
-dhcp - Run only the DHCP test.
-clean - Release the addresses stored in the temporary file.
-v - Verbose. Output additional run-time test information.

During execution a temporary file "allocatedaddresses" is created in the
working directory that stores the addresses that have been successfully leased from the DHCP server (this file is deleted once the addresses have been successfully released).

4.1 Interactive Mode

When Avaya IP Boot Test is invoked with the "-i" option, it will be launched in interactive mode. Users will be prompted to enter test settings on screen as follows:

Run DHCP Testing (y/n)? [y]

Simply press enter or type "y" if you wish to run DHCP testing. If you have
selected to run DHCP testing, Avaya IP Boot Test will then prompt you for the number of IP phones to simulate.

Enter the number of phones to be simulated. [Default = 1]

Simply pressing return will default testing to one endpoint, useful for sanity
testing of the DHCP configuration. If testing for a specific capacity, enter the number of IP phones to be installed on your network.

The program will next ask the user if TFTP testing is required:

Run TFTP Testing (y/n)? [y]

If TFTP testing is selected, the user will be asked to enter the TFTP server
addresses and directory to be tested against if DHCP testing has NOT been
selected. If DHCP testing is selected, the TFTP server and directory will
be obtained from DHCP options.

Please enter the TFTP server address(es), separated by commas (,).

Please enter the TFTP directory.

The program will next prompt for a file name if test output is to be saved to
a file on disk. If no file name is provided, test results will be displayed on
screen.

Output filename? [Press enter for output to screen.]

Finally, if additional run-time test information is required, the user can type "y" to:

Output additional run-time test information (y/n)? [n]

After all input settings have been gathered, the testing will begin.
5. Output

There are three types of messages provided by Avaya IP Boot Test. They are:

* PASS - a test passed. This is used to indicate that a configuration
checkpoint was correctly set up.

* FAIL - a test failed. This is used to indicate that a configuration
checkpoint was incorrectly set up.

* INFO - an informational message about some attribute of the test or
configuration of the DHCP/TFTP server.

Example output:

c:\> IPBootTest.exe
Avaya IP Boot Test (Version 1.3.2) copyright 2002 Avaya Inc.
Please send feedback or report problems to ipboottest@avaya.com.
INFO [12:51:50.99] Testing DHCP by simulating 1 endpoints
INFO [12:51:50.99] Simulating endpoint number: 1
INFO [12:51:54.09] DHCP server was found with IP address: 192.168.27.199 - PINKPANTHER-NT4
INFO [12:51:57.56] Valid Offer for endpoint 1 : allocated 192.168.27.111 successfully
PASS [12:51:58.16] DHCP test result: your DHCP server and network appear to be correctly configured.
INFO [12:51:58.16] TFTPSERVER set to: 192.168.27.199
INFO [12:51:58.16] TFTPPATH set to:
INFO [12:51:58.17] Testing TFTP...
INFO [12:51:58.17] Testing TFTP server: 192.168.27.199 (PINKPANTHER-NT4)
PASS [12:54:50.39] Available TFTP servers: 1

-------
TEST SUMMARY:
1 address(es) were requested and successfully obtained.
TFTP Server at 192.168.27.199 is available:
The 4630 model IP Phone is supported.
All other 4600 series IP Phones models are supported.

This is a default run of the program (it defaults to testing 1 endpoint)
output indicates that a DHCP server was found, it gave the appropriate address
allocation and the files were successfully downloaded from the TFTP server.

c:\> IPBootTest.exe -v
Avaya IP Boot Test (Version 1.3.2) copyright 2002 Avaya Inc.
Please send feedback or report problems to ipboottest@avaya.com.
INFO [12:56:13.45] Testing DHCP by simulating 1 endpoints
INFO [12:56:13.45] Simulating endpoint number: 1
INFO [12:56:13.45] Sent DISCOVER Packet
INFO [12:56:16.50] Received OFFER Packet
INFO [12:56:16.50] DHCP server was found with IP address: 192.168.27.199 - PINKPANTHER-NT4
INFO [12:56:16.50] Examining Offer from: 192.168.27.199
INFO [12:56:16.50] Check for option 51
INFO [12:56:16.50] Option 51: Offered an infinite lease
INFO [12:56:16.50] Check for option 176: mcipadd=1.2.3.4,tftpsrvr=192.168.27.199,tftpdir=
INFO [12:56:16.50] Using offer from 192.168.27.199
INFO [12:56:16.50] Sent REQUEST Packet
INFO [12:56:16.55] Received ACK Packet
INFO [12:56:16.55] Checking availability of: 192.168.27.111
INFO [12:56:19.94] Valid Offer for endpoint 1 : allocated 192.168.27.111 successfully
INFO [12:56:19.94] Attempt number 0 to send RELEASE Packet for: 192.168.27.111
INFO [12:56:20.14] Attempt number 1 to send RELEASE Packet for: 192.168.27.111
INFO [12:56:20.34] Attempt number 2 to send RELEASE Packet for: 192.168.27.111
PASS [12:56:20.54] DHCP test result: your DHCP server and network appear to be correctly configured.
INFO [12:56:20.54] TFTPSERVER set to: 192.168.27.199
INFO [12:56:20.54] TFTPPATH set to:
INFO [12:56:20.54] Testing TFTP...
INFO [12:56:20.54] Testing TFTP server: 192.168.27.199 (PINKPANTHER-NT4)
INFO [12:56:20.54] Successfully pinged server: 192.168.27.199
INFO [12:56:20.54] Testing for images for 46xx model phones...
INFO [12:56:20.56] Successfully downloaded "46XXUPGRADE.SCR" from 192.168.27.199
INFO [12:56:20.57] File "bb4602r1_6.bin" exists on server 192.168.27.199.
INFO [12:56:22.57] File "bbla20_0_14.bin" exists on server 192.168.27.199.
INFO [12:56:24.60] File "bbla0_59.bin" exists on server 192.168.27.199.
INFO [12:56:26.61] File "ap4602r1_6.bin" exists on server 192.168.27.199.
INFO [12:56:28.63] File "def06r1_70.bin" exists on server 192.168.27.199.
INFO [12:56:30.66] File "def20r1_71.bin" exists on server 192.168.27.199.
INFO [12:56:32.66] File "def24r1_70.bin" exists on server 192.168.27.199.
INFO [12:56:34.67] Testing for 4630 IP Phone image files...
INFO [12:56:34.72] Successfully downloaded "46xxsettings.scr" from 192.168.27.199
INFO [12:56:34.73] Successfully downloaded "4630UPGRADE2.SCR" from 192.168.27.199
INFO [12:56:34.76] Successfully downloaded "update1_751.sh" from 192.168.27.199
INFO [12:56:34.79] File "def30a1_751m.bin" exists on server 192.168.27.199.
INFO [12:56:36.82] File "def30s1_751.bin" exists on server 192.168.27.199.
INFO [12:56:38.82] File "btst30a1_751.bin" exists on server 192.168.27.199.
INFO [12:56:40.87] File "btst30s1_751.bin" exists on server 192.168.27.199.
INFO [12:56:42.87] File "avaya/lib/appletviewer.properites" exists on server 192.168.27.199.
.
.
.
INFO [12:58:50.14] File "avaya/archives/ipst_ipstjnetworkopt.jar" exists on server 192.168.27.199.
INFO [12:58:52.14] File "avaya/group1.txt" exists on server 192.168.27.199.
INFO [12:58:54.15] File "avaya/group2.txt" exists on server 192.168.27.199.
INFO [12:58:56.18] File "avaya/group3.txt" exists on server 192.168.27.199.
INFO [12:58:58.18] File "avaya/group4.txt" exists on server 192.168.27.199.
INFO [12:59:00.23] File "avaya/group5.txt" exists on server 192.168.27.199.
INFO [12:59:02.23] File "avaya/gbDetails.txt" exists on server 192.168.27.199.
INFO [12:59:04.27] File "avaya/opt.ini" exists on server 192.168.27.199.
INFO [12:59:06.27] File "avaya/log.config" exists on server 192.168.27.199.
INFO [12:59:08.31] File "avaya/props" exists on server 192.168.27.199.
PASS [12:59:10.32] Available TFTP servers: 1

-------
TEST SUMMARY:
1 address(es) were requested and successfully obtained.
TFTP Server at 192.168.27.199 is available:
The 4630 model IP Phone is supported.
All other 4600 series IP Phones models are supported.

The -v (verbose) option provides more details during the testing, including
things such as:

* Which DHCP Options are provided by the server
* Which files successfully/unsuccessfully download
6. Known issues:

* VLAN: Avaya IP Boot Test can not dynamically change the VLAN a PC is on. To work around this limitation, you may configure your network to put the PC into the VLAN that is to be tested for suitability for IP Phones. Avaya IP Boot Test will simply test with the VLAN that the PC is configured for (usually VLAN ID 0).

* When there is a lot of traffic on the LAN, Avaya IP Boot Test may fail. This is because DHCP protocol packets may be dropped under network load. Avaya IP Boot Test times out after 3 seconds without response when performing DHCP communication.

* Under Windows versions prior to Windows 2000 Avaya IP Boot Test will use Ping rather than ARP to detect the existence of a host with an IP Address. This means that Avaya IP Boot Test may not report allocation of an in-use IP address if that address is allocated to a machine that does not respond to pings.

* Avaya IP Boot Test currently examines DHCP Option 43. In v1.7 of the IP
Phone code use of this option may be deprecated, and hence this version of
Avaya IP Boot Test may give false positive results.

* We require a DNS server to be configured for the PC that Avaya IP Boot Test is run on to resolve hostnames/addresses. Avaya IP Boot Test does not currently use the DNS server specified by the DHCP server. It is unlikely, but DNS resolved names may not be consistent with those an IP phone will see.

* Avaya IP Boot Test acquires very long leases on IP addresses and may fail to clean up fully when network conditions cause packets to be lost. This
can result in IP addresses remaining allocated by the DHCP server. If you
suspect the network conditions are bad, then run Avaya IP Boot Test with
the -clean option again before running further Avaya IP Boot Test tests. If
you are still in doubt, use the management interface on your DHCP server to
verify the allocated IP addresses have been released.

* Avaya IP Boot Test cannot be run on a PC that is also running a DHCP server or DHCP relay. This is due to the fact that the network ports required for communication by Avaya IP Boot Test are in use by the servers. It can successfully be run on a PC that has a DHCP Client active.

 

[victor5908]

Thanks for all of the info!
I'll fool with that button thing today too-