> For the complete documentation index, see [llms.txt](https://docs.gxc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gxc.io/docs/network-configuration-and-operations-guides/4g-onyx-edge-on-premises-4.x-installation-and-operations/installation-requirements.md). # Installation Requirements This section describes the hardware, software, and other requirements for Onyx Edge On-Premises AGWs. ## Hardware Specifications The GXC-supplied Onyx-ES hardware comes pre-installed with Onyx Edge software for Onyx Edge On-Premises deployments. For information regarding available Onyx-ES hardware options and specifications, please contact GXC Technical Support. ## Software Requirements The GXC-supplied Onyx Edge ISO image includes all required software components for fresh Onyx Edge software installations. ## Network Interfaces The Onyx-ES hardware has two network interfaces―eth0 and eth1. * eth0 can get its IP address over DHCP (default) or can have its IP address statically configured. Internet access is required over this interface. * eth1, is statically assigned 10.0.2.1/24. During a fresh installation, it is important that this interface is not connected to anything until the installation completes to avoid confusion on which is the first/Internet interface. This interface can later be connected to the switch to the radio network (or directly to an AP). {% hint style="info" %} **NOTE:** The Onyx Edge will start a DHCP service on the eth1 interface. Care should be taken to not have other equipment on this network segment that might be affected by this DHCP service. {% endhint %} {% hint style="info" %} **NOTE:** There is no specific requirement on which physical port is designated as eth0 (Internet) and which as eth1 (radio). However, the same interface connection must be maintained right from ISO installation to deployment. {% endhint %} ### eth1 Configuration Constraints {% hint style="info" %} **NOTE:** Do not configure eth1 statically. Either set it to DHCP (recommended) or disable it. {% endhint %} {% hint style="info" %} **NOTE:** When configuring VLAN on eth0, disable the native/untagged eth0 interface. eth1 must be set to DHCP (recommended) or disabled. {% endhint %} ### Identifying eth0 and eth1 Interfaces GXC supplies Onyx-ES hardware with physical ports clearly labeled eth0 and eth1 on the chassis. If, for any reason, you have to verify which physical port is eth0 and which eth1, use one of the following methods: {% stepper %} {% step %} Cable connection test: * Plug a cable into one port at a time and check the link status: ``` ip link show eth0 | grep "state UP" ip link show eth1 | grep "state UP" ``` * Or monitor in real time: ``` watch -n 1 'ip link show | grep -E "eth[0-1]"' ``` {% endstep %} {% step %} Use ethtool to identify ports by blinking LEDs. * To make the LED blink on eth0 for 30 seconds: ``` ethtool --identify eth0 30 ``` * To make the LED blink on eth1 for 30 seconds: ``` ethtool --identify eth1 30 ``` Watch the physical ports to see which one blinks. {% endstep %} {% step %} Check MAC address mapping: * To view network interfaces and their MAC addresses: ``` ip link show ``` * Or, use ifconfig: ``` ifconfig -a ``` * Compare with the MAC addresses printed on the physical port labels. Most Dell servers have MAC address stickers near the Ethernet ports. {% endstep %} {% step %} Check interface naming and Bus information: * To view detailed interface information including PCI bus location: ``` ip link show eth0 ip link show eth1 ``` * Or, use lshw: ``` lshw -class network -short ``` {% endstep %} {% endstepper %} ## User Accounts and Access Credentials This section provides information related to the onyxedge and agw\_user accounts. ### onyxedge User {% hint style="info" %} **NOTE:** onyxedge user credentials are available only to GXC personnel. {% endhint %} onyxedge user is the super user on the Onyx-ES with full sudo privileges. onyxedge user credentials to log on to any Onyx-ES: * Host name: onyxedge-agw * Username: onyxedge * Password to log on via the terminal is available only to GXC personnel. ### agw\_user {% hint style="info" %} **NOTE:** agw\_user credentials are available only to GXC Partner and Customer Administrators. {% endhint %} agw\_user is a second user on the Onyx-ES with the privileges to gather basic debug information, restart Onyx Edge services, and reset Onyx Edge back to factory settings. agw\_user credentials to log on to Onyx-ES: * IP address of the Onyx Edge. * Username: agw\_user * Password to log on via the Onyx-ES terminal. GXC Partner Administrators and Customer Super Administrators can change this password. * SSH key to log on remotely. GXC Partner Administrators and Customer Super Administrators can add SSH keys in the Onyx Portal. To SSH into an Onyx Edge as agw\_user, run the following command: ``` ssh agw_user@ ``` For information on the CLI commands available to agw\_user, see Run Commands on Onyx Edge as agw\_user. For information on configuring the agw\_user account, see the *4G Onyx Portal Operations Guide > Configure Onyx Edge agw\_user Account*. {% hint style="info" %} **NOTE:** If you do not have management access to the Onyx-ES, work with your GXC Technical Support representative. {% endhint %} ## Network Connectivity and Enterprise Firewall Configuration The Onyx Edge requires network connectivity to communicate with the Orchestrator and other GXC cloud services to operate correctly. Ensure that enterprise firewalls and network Access Control Lists (ACLs) are configured to allow the required traffic flows. For detailed information on the required ports, protocols, and destination URLs/IPs that must be allowed through enterprise firewalls, refer to the *Onyx 4G & 5G Firewall Configuration for Onyx Networks Application Note*. This document provides the firewall rules for the Onyx Edge (eth0 and eth1 interfaces), APs, and Mesh Nodes to ensure proper communication with GXC cloud services. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.gxc.io/docs/network-configuration-and-operations-guides/4g-onyx-edge-on-premises-4.x-installation-and-operations/installation-requirements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.