![]() In this example of a broken connection, the initiator is not registered on the storage controller. Ping must work before the initiator can attach to a target.Ĭheck the Target State. If the ping status fails, check your network configuration and IP settings. Initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR This is an example of a successful connection: F340-31-13-FI-1-A# connect adapter 1/1/1 If the blade fails to attach the LUN after service profile association, connect to the UCS Manager (UCSM) command-line interface (CLI). If the service profile fails to associate to the blade, and if you receive this error message, check the overlay vNIC native vLAN configuration to verify that the correct vLAN is selected. This section provides information you can use to troubleshoot your configuration. There is currently no verification procedure available for this configuration. Use the configured IQN and IP information for LUN masking on the storage controller.Ĭlick the plus ( +) sign in order to add storage target information:Įnter the iSCSI target IQN name in the iSCSI Target Name field.Įnter the IP Address of the target iSCSI portal in the IPv4 Address field.Īssociate the service profile with the server. If the storage controller is on same subnet, you do not need to define a Default Gateway or any Domain Name System (DNS) servers. An example is 124.Įnter the IPv4 Address and the Subnet Mask for the initiator. Set the Initiator Name Assignment to Manual, then enter the Initiator Name in IQN or extended universal identified (EUI) format. The VLAN is the one defined as native in Step 1.Įxpand iSCSI vNICs and double-click the appropriate iSCSI vNIC in order to add it to device list. Modify the iSCSI Adapter Policy only if it is necessary. The Overlay vNICs should be the ones with native VLAN configured in Step 1. This is not an actual vNIC it is an iSCSI boot firmware table (iBFT) configuration placeholder for iSCSI boot configuration. ![]() Select the iSCSI VLAN to be a Native VLAN on the last vNIC use the last vNIC to avoid issues with ESXi 5.0 installations.Ĭreate a virtual iSCSI vNIC in order to serve as an iSCSI configuration placeholder. This procedure describes how to configure the service profile for iSCSI boot. Refer to the Cisco Technical Tips Conventions for more information on document conventions. If your network is live, make sure that you understand the potential impact of any command. ![]() All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. This document is not restricted to specific software and hardware versions. The boot logical unit number (LUN) ID is available. The iSCSI qualified name (IQN) and IP address of the storage system iSCSI target portal is available. The VIC adapter can be a M81KR, a VIC1240, or a VIC1280. The Cisco virtual interface card (VIC) adapter is used. The service profile is set up with the correct VLANs on the virtual network interface cards (vNICs). The blades and storage both have Layer 2 (L2) connectivity. Prerequisites RequirementsĮnsure that you meet these requirements before you attempt this configuration: The target audience is UCS administrators who have a basic understanding of UCS functions. This document describes how to boot from the Internet Small Computer System Interface (iSCSI) on the Cisco Unified Computing System (UCS) platform and how to perform basic troubleshooting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |