Cisco Network Boot Installation and Configuration Guide, Release 2.1
Chapter 4 - Troubleshooting
Downloads: This chapterpdf (PDF - 229.0KB) The complete bookPDF (PDF - 1.2MB) | Feedback

Maintenance and Troubleshooting

Table Of Contents

Maintenance and Troubleshooting

Maintenance

Replacing a Host

Changing the Network Drivers

Troubleshooting

General Information

Example Displays for Cisco Network Boot

Error Messages

Cisco Network Boot and Host Errors

Network Errors

DHCP iSCSI Option Format Errors

Login Errors

iSCSI Target Errors

Replication Errors


Maintenance and Troubleshooting


This chapter explains how to perform maintenance and how to troubleshoot if Cisco Network Boot does not work as it should. The troubleshooting section includes a normal display on Cisco Network Boot and error messages you might encounter when installing and configuring Cisco Network Boot. It also includes explanations of the error messages and actions you can take to resolve the messages.


Note If you need to call Cisco TAC, they may ask you to produce a log file. Log files are created for each replication. The file name is ciscoopX.log (where X is the volume letter of the replication destination). This log file provides insight on the failure and is created in the install directory of the Network Boot Management utility.


This chapter contains the following topics:

Maintenance

Troubleshooting

Maintenance

Maintenance consists of tasks for replacing a host and changing the network.

Replacing a Host


Note The replacement host must have the same NIC and interface number as the original host. If it does not, the boot will fail.


To replace a host, perform the following steps:


Step 1 Record the Ethernet MAC address of the NIC to be used for storage access.

Step 2 Modify the reservation in the DCHP server with the MAC address.

Step 3 Boot the host.

Changing the Network Drivers

You may need to change the network drivers if the NIC vendor has a new version of their driver or if you install a service pack with driver updates.

To change the network drivers, perform the following steps:


Step 1 Go to Control Panel > iSCSI Config.

Step 2 Click the Normal Boot button.

The boot type changes to Normal.

Step 3 Make the network driver changes.

Step 4 Click the Early Boot button.

The boot type changes back to Early.


Troubleshooting

Troubleshooting consists of general information, normal displays for Cisco Network Boot, and error messages.

General Information

Rather than using a repair diskette or CD ROM for troubleshooting, iSCSI volumes should be mounted on a working system and repaired from there.

Example Displays for Cisco Network Boot

During the boot process each system, such as Intel Eclipse, Compaq, and Dell, displays its own PXE-specific information. Following are examples of a normal Cisco Network Boot display and additional system-specific displays that need to appear before Cisco Network Boot can run.

Example 4-1 Normal Cisco Network Boot Display

Cisco Network Boot netboot-2.1.1 19-Aug-2002.04:46:21
PXE Version: 02.01
Client Name: squall1               MAC: 67:22:95:88:01:54
  Client IP: 10.2.50.10        DHCP IP: 10.2.50.18     
 Gateway IP: 10.2.50.1         Netmask: 255.255.255.0  
   iSCSI IP: 10.2.50.102 	 				 TCP Port: 3260
  Initiator:  
iqn.1987-05.com.cisco:00.04aeccb6d6099d06325595df2480730ocmasterbootdisk
     Target: 
iqn.1987-05.com.cisco.00..bootdisk-01
   Boot LUN: 0000
  iSCSI MAC: 43:87:18:44:23:22 Alias: bootdisk-01

  iSCSI LUN: 0000    3.75GB  SEAGATE  ST318452  002EV08074
  iSCSI LUN: 0001    7.85GB  SEAGATE  ST318452  002EV08075

Disk  Type   Cylinders  Heads  Sectors   Max C: Size
  00  iSCSI     0x03ff   0xfe     0x3f        7.8 GB
  01  iSCSI     0x03ff   0xfe     0x3f        7.8 GB
  02   BIOS     0x03ff   0xfe     0x20        3.8 GB

Booting from......

If the display differs significantly from what is shown, check the connection to the DHCP server or to the Cisco SN 5400 Series system.

Example 4-2 Intel Eclipse Display

Intel UNDI, PXE-2.0 (build xxx)
Copyright...

Client MAC Addr: xx xx xx xx xx xx  GUID: 
Client IP: nn.nn.nn.nn  Mask: nn.nn.nn.nn  DHCP IP: nn.nn.nn.nn
Gateway IP: nn.nn.nn.nn

Example 4-3 Compaq Booting from an Onboard Intel NIC

Prolient DL380
Initializing Intel 9R) boot agent version 4.017
PXE 2.0 build 083 (WFM 2.0)
Intel (R) boot agent version 4.0.17
Copyright
Client MAC Addr: xx xx xx xx xx xx  GUID: 
Client IP: nn.nn.nn.nn  Mask: nn.nn.nn.nn  DHCP IP: nn.nn.nn.nn
Gateway IP: nn.nn.nn.nn

Example 4-4 Dell Booting from an Onboard Intel NIC

PowEdge 1650
Initializing Intel 9R) boot agent version 4.017
PXE 2.0 build 083 (WFM 2.0)
Intel (R) boot agent version 4.0.17
Copyright
Client MAC Addr: xx xx xx xx xx xx  GUID: 
Client IP: nn.nn.nn.nn  Mask: nn.nn.nn.nn  DHCP IP: nn.nn.nn.nn
Gateway IP: nn.nn.nn.nn

Error Messages

Following are error messages for the following categories:

Cisco Network Boot and Host Errors

Network Errors

DHCP iSCSI Option Format Errors

Login Errors

iSCSI Target Errors

Replication Errors

Cisco Network Boot and Host Errors

Error Message    PXE not found

Explanation    The host does not support PXE.

Recommended Action    Add an Intel Pro/1000 XT server adapter NIC.

Error Message    Not enough conventional memory. The Cisco Network Boot segment at 
0xnnnn is below 512k (0x8000)

Explanation    . The PXE implementation does not leave enough memory for Cisco Network Boot to run. Cisco Network Boot won't run at all on the host in this configuration.

Recommended Action    Install and configure a PXE-supported 10/100 or Gigabit Ethernet NIC, such as the Intel Pro/1000 XT server. For more information, boot using the pxecheck utility instead of inbp.com.

Error Message    System boots up to the Windows splash screen; a blue screen displays 
the message, "BOOT DEVICE NOT AVAILABLE."

Explanation    The iSCSI driver was not set to use Early boot order during installation.

Recommended Action    Boot the internal hard drive, set the boot type to the Early setting (not to the Normal setting), and copy the image to the iSCSI target again.

Network Errors

Error Message    No ARP response from target IP address

Explanation    The network could not find the hardware address (MAC address) of the iSCSI target.

Recommended Action    Make sure that the iSCSI target is online. Make sure that the IP address in the root path option is correct. Also, make sure that the default gateway (if needed) is the first one in the router list (option 3) and that the subnet mask is correct.

Error Message    Unable to find boot drive on iSCSI target

Explanation    No internal or iSCSI targets found.

Recommended Action    Make sure that the iSCSI target has a valid copy of the BIOS on the boot image.

Error Message    No BIOS or iSCSI hard disks

Explanation    No internal or iSCSI targets found.

Recommended Action    Make sure that the iSCSI target has a valid copy of the BIOS on the boot image.

Error Message    No boot disk, insert disk and press Ctrl+Alt+Del

Explanation    No device that was found was bootable.

Recommended Action    Insert a bootable diskette or install an operating system or replicate an existing iSCSI boot disk.

Error Message    No ARP response yet, please wait or use control-alt-delete to reboot

Explanation    The iSCSI target IP address is incorrect, or the iSCSI target is not operational, or the network is down between the host and the iSCSI target. inbp.com will retry the ARP request every five seconds for 15 or 20 minutes. This may also happen under very heavy network traffic with high packet loss.

Recommended Action    If the target address is incorrect, fix the iSCSI boot string in the DHCP reservation, and use control-alt-delete to reboot. If the target address is correct, wait for the iSCSI target to become operational (this may happen if both the host and the target are powered on at the same time), or correct the network problem.

Error Message    No DHCP response yet, please wait or use control-alt-delete to reboot

Explanation    The DHCP server may have gone down, or is being restarted, or network problems may have occurred between the host and the DHCP server. This could also happen under very heavy network traffic with high packet loss. inbp.com will retry the DHCP request every five seconds for about 10 minutes.

Recommended Action    Start up the DHCP server if it is stopped, correct the network problem, or wait for the retries to work.

DHCP iSCSI Option Format Errors

Error Message    DHCP iSCSI option format error - option must start with iscsi

Explanation    The DHCP iSCSI option is not formatted correctly.

Recommended Action    Begin the option with iscsi...; see the example in "Setting Up the DHCP/TFTP Server" in "Installing and Configuring for Cisco Network Boot Operation."

Error Message    DHCP iSCSI option format error - non-dotted decimal character in IP 
address

Explanation    The DHCP iSCSI option, IP address field, is not formatted correctly.

Recommended Action    Use only a dotted-decimal IP address in the IP address field.

Error Message    DHCP iSCSI option format error - transport protocol field must be tcp 
or blank

Explanation    The DHCP iSCSI option is not formatted correctly.

Recommended Action    Enter tcp in the transport protocol field or leave the field blank.

Error Message    DHCP iSCSI option format error - non-decimal character in TCP port 
number field

Explanation    The DHCP iSCSI option is not formatted correctly.

Recommended Action    Enter the decimal TCP port number used by the iSCSI target in the TCP port field. If not specified, the default is 3260.

Error Message    DHCP iSCSI option format error - non-hexadecimal character in LUN field

Explanation    The DHCP iSCSI option is not formatted correctly.

Recommended Action    The LUN field must be in hexadecimal. Only the first four characters are used. (This should be zero.)

Error Message    DHCP iSCSI option format error - iSCSI Target option not returned by 
DHCP

Explanation    The DHCP iSCSI option, root path, was not configured correctly in the DHCP server.

Recommended Action    Add the root path option to the DHCP reservation.

Error Message    DHCP iSCSI option format error - target not specified

Explanation    The DHCP iSCSI option does not include the iSCSI target name.

Recommended Action    Add the iSCSI target name to the end of the DHCP ISCSI option.

Login Errors

Error Message    target not found

Explanation    The iSCSI target does not exist at the specified IP address.

Recommended Action    Correct the iSCSI target name in the root path DHCP option, or correct the IP address.

Error Message    initiator was not successfully authenticated by target

Explanation    The connection failed due to an authentication error.

Recommended Action    Check authentication keys.

Error Message    initiator not authorized to access target

Explanation    The connection failed due to an authorization error.

Recommended Action    Make sure that the access lists on the Cisco 5400 Series system allow the host to access the iSCSI target.

Error Message    unexpected initiator error

Explanation    The connection failed due to an unexpected initiator problem.

Recommended Action    Report the error to Cisco TAC.

Error Message    unexpected target error

Explanation    The connection failed due to an unexpected target error.

Recommended Action    Make sure that the Cisco 5400 Series system is running and available. If the error persists, report it to Cisco TAC.

Error Message    iSCSI login status Ox

Explanation    The connection failed.

Recommended Action    Check login errors in the Cisco SN 5400 Series system documentation.

Error Message    Unsupported iSCSI target

Explanation    This error means that the iSCSI target is not a Cisco target or that it is a Cisco target running an older firmware release.

Recommended Action    Install a Cisco iSCSI product, or upgrade the firmware as specified in "Before Installing Cisco Network Boot."

iSCSI Target Errors

Error Message    iSCSI initialization failed

Explanation    The iSCSI driver initialization failed.

Recommended Action    This should not happen. Report this error to Cisco TAC.

Error Message    iSCSI test unit ready failed 

A display such as the following is also shown.

SCSI Command returned status 0x02
Check condition; sense key 0x05, ASC/Q0x2500
LUN Not Supported
	Exp. The LUN does not exist on the iSCSI target.
	Action: Add the LUN or fix the boot string.

Explanation    The iSCSI test unit failed.

Recommended Action    Check that the fibre channel device behind the Cisco 5400 Series system is powered up and ready, and that the specified LUN exists.

Error Message    iSCSI read failed

A display such as the following is also shown.

SCSI Command returned status 0x02
Check condition; sense key 0x05, ASC/Q0x2500
	LBA Out of Range

Explanation    The iSCSI read failed.

Recommended Action    Make sure that the LUN is mapped to a valid iSCSI target.

Error Message    iSCSI get capacity failed

A display such as the following is also shown.

SCSI Command returned status 0x02
Check condition; sense key 0x05, ASC/Q0x2500
LUN Not Supported
	Exp. The LUN does not exist on the iSCSI target.
	Action: Add the LUN or fix the boot string.

Explanation    The iSCSI get capacity failed.

Recommended Action    Make sure that the LUN is mapped to a valid iSCSI target.

Error Message    iSCSI device block size not 512 bytes

Explanation    The block size of the physical device is not 512 bytes.

Recommended Action    Access the fibre channel device and reconfigure it to use a 512-byte block size.

Error Message    iSCSI inquiry failed

A display such as the following is also shown.

SCSI Command returned status 0x02
Check condition; sense key 0x05, ASC/Q0x2500
LUN Not Supported
	Exp. The LUN does not exist on the iSCSI target.
	Action: Add the LUN or fix the boot string.

Explanation    The iSCSI inquiry failed.

Recommended Action    Check that the fibre channel device behind the Cisco 5400 Series system is powered up and ready, and that the specified LUN exists

Replication Errors

Error Message    Can't find iSCSI driver or is not set to Early Boot

Explanation    The iSCSI driver has not been installed or is not set to Early Boot.

Recommended Action    Check to make sure you have the iSCSI driver installed and the Early Boot set.

Error Message    Could not validate source IP address or could not find iSCSI driver 
registry entries

Explanation    The wrong source IP address was set for the NIC with PXE enabled or the Local Area Connection was not configured with the static IP address matching the DHCP reservation.

Recommended Action    Check to make sure you have put in the correct address. This IP address is the static IP address of the master boot host.

Error Message    Couldn't find physical device for source

Explanation    The wrong device was selected.

Recommended Action    Quit and restart the utility. Ensure the correct device is selected.

Error Message    Couldn't find physical device for destination

Explanation    The wrong device was selected.

Recommended Action    Quit and restart the utility. Ensure the correct device is selected.

Error Message    Invalid copy source

Explanation    Selecting the copy source was not done correctly. No boot partition was found.

Recommended Action    Ensure the source has an Active Partition.

Error Message    Invalid copy destination

Explanation    Selecting the copy destination was not done correctly. No boot partition was found.

Recommended Action    Ensure that you checked Mark Active Partition when you have finished creating the partition.

Error Message    Not a bootable NTFS partition

Explanation    The volume is not formatted with NTFS or is not set to Healthy - Active.

Recommended Action    Check the device selection. ensure that the volume is formatted with NTFS and is set to Healthy - Active.

Error Message    Failure trying to get source and destination free and used space sizes.

Explanation    The Microsoft API failed.

Recommended Action    Quit and start Cisco Network Boot again.

Error Message    Destination is too small to hold source.

Explanation    The size of the destination volume is not large enough to contain the source volume.

Recommended Action    The size of the destination volume should be 10% more than the size of the used space on the source volume. Make a new partition of the required size. Format and set active. Go through the replication process again.

Error Message    Invalid copy destination, invalid BPB (BIOS parameter block) or not 
formatted for NTFS

Explanation    The volume is not formatted with NTFS or you did not select the correct volume.

Recommended Action    Check to make sure the volume format is NTFS. Verify the correct volume selection.

Error Message    Invalid copy destination, invalid bytes per sector

Explanation    The number of bytes per sector is not correct.

Recommended Action    Check the format of the storage device. Be sure that the volume disks have 512 bytes per sector. (This is independent of the cluster size.)

Error Message    I/0 Failure for the current destination

Explanation    The current destination cannot be verified. This is a Microsoft API failure.

Recommended Action    Go through the replication process again.

Error Message    Is a systemroot and can't be a replication destination.

Explanation    The destination copy can't be where the operating system is currently active.

Recommended Action    Check the volume selection.