> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/2pxe-server/4.0/reference/ipxe-console-commands.md).

# iPXE Console Commands

During the iPXE initialization phase, pressing the **C** key interrupts the automated network boot process and opens the interactive iPXE command-line interface. This provides direct administrative access to the current boot session, allowing manual execution of network operations for troubleshooting and validation purposes.

Entering the iPXE command line does not modify firmware, server configuration, or DHCP settings, and any actions performed are limited to the current boot session only. This feature is intended for diagnostic and advanced troubleshooting scenarios and should not be used during standard production boot workflows unless investigation is required.

### **Boot commands**

**autoboot** - Boot system from network interface

### Network interface commands

**ifstat** - Display interfaces\
**ifopen** - Open interfaces\
**ifclose** - Close interfaces\
**ifconf** or **dhcp** - Automatically configure interfaces\
**route** - Display routing table\
**nstat** - Display neighbor table\
**ipstat** - Display IP statistics\
**vcreate** - Create VLAN\
**vdestroy** - Destroy VLAN

### **Image management commands**

**imgstat** - Display images\
**chain** or **imgexec** or **boot** - Download and boot an executable image\
**imgfetch** or **module** or **initrd** - Download an image\
**kernel** or **imgselect** or **imgload** - Download and select an executable image\
**imgfree** - Discard images\
**imgargs** - Set image command-line arguments\
**imgtrust** - Set image trust requirement\
**imgverify** - Verify an image as trusted

### **SAN commands**

**sanhook** - Attach SAN device\
**sanboot** - Boot from SAN device\
**sanunhook** - Detach SAN device\
**fcstat** - Display Fibre Channel ports\
**fcels** - Issue Fibre Channel ELS request

### **Configuration setting commands**

**config** - Start interactive configuration tool\
**show** - Display configuration setting\
**set** - Set configuration setting\
**clear** - Delete configuration setting\
**read** - Prompt user to enter configuration setting\
**inc** - Increment numeric value of configuration setting\
**login** - Prompt user to enter user name and password

### Flow control commands

**isset** - Test for existence\
**iseq** - Test for equality\
**goto** - Jump to script label\
**exit** - Exit current shell or script

### Menu commands

**menu** - Create menu\
**item** - Add menu item\
**choose** - Choose menu item

### Console management commands

**console** - Configure console\
**colour** - Define colour\
**cpair** - Define colour pair

### Form parameter commands

**params** - Create form parameter list\
**param** - Add form parameter

### Miscellaneous commands

**echo** - Print text to console\
**prompt** - Prompt user to press key\
**shell** - Start new interactive shell\
**help** - Display list of available commands\
**sleep** - Delay for fixed period of time\
**reboot** - Reboot system\
**poweroff** - Power off system\
**cpuid** - Check x86 CPU feature\
**sync** - Wait for background operations to complete\
**nslookup** - Resolve host name to network address\
**ping** - Check network connectivity\
**pciscan** - Scan for PCI devices

### Misc commands

**lotest** - Perform loopback testing\
**pxebs** - Perform PXE boot server discovery\
**time** - Measure time taken to execute command\
**gdbstub** - Start remote debugging\
**profstat** - Display profiling statistics


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.2pintsoftware.com/2pxe-server/4.0/reference/ipxe-console-commands.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.