Kepler Server Power & Display Connections
Plug a standard C13 power cable into any of power supply inlets (left or right) at the rear.
If you have redundant or independent power circuits available (outlets on different breakers or separate uninterruptible power supplies), plug the 2nd power supply into the 2nd (separate) source.
Press the power button on the front of the server to turn the server on.
NOTE: Once power is connected, you may hear the cooling fans turn on. This does NOT mean the server itself is on. Always check the illumination of the front power button to confirm if the server itself is on.
Optionally, you may connect a VGA monitor to any of the VGA/D-Sub ports (one port is at the front and the other is at the rear). This will allow you to monitor the boot-up sequence of the server.
As these servers are meant to run 24/7, when cold booted from off or restarted, they take approximately 4-5 minutes to complete their boot-up sequence, load the operating system, and finally initialize all the Kepler software. You will not be able to access the web management portal until the system has completed booting.
If a monitor is connected, once you see the following text, the server has completed its boot-up sequence.
While the server is booting (~4 to 5 minutes), you can move onto connecting the network connections.
Kepler Server Network Setup
The server supports two mutually exclusive methods of addressing to connect to your network:
- static IP (manually set)
- dynamic IP (via a dynamic host configuration protocol [DHCP] server on your network)
Your network administrator should have details on which method to utilize and what values to set for the various network parameters.
Out of the box, the Kepler server defaults to using DHCP (dynamic host configuration protocol) and will attempt to lease an IP address from your network’s DHCP server, if available.
To begin, plug an Ethernet cable between your network and Port 1 on the Kepler server.
Method 1: Dynamic Network Address (DHCP) Procedure
If your network uses DHCP (dynamic host configuration protocol) to automatically assign IP addresses, the Kepler server will receive one from your network.
Using another computer connected on the same network/subnet, open a command prompt or terminal and execute the following command: ping kepler-user-terminal
If your network supports it, it will respond with the IP address assigned to the Kepler server by your network’s DHCP server.
If the above was successful, make a note of the IP address and move onto the “Web Management Portal” section further down.
If the ping command returns an error or does not provide the IP address of the Kepler server, move onto the next section to either obtain the address or set a static address.
Method 2: Find your DHCP-Assigned IP Address
Using a computer with administrator-level privileges, configure your system’s network settings as follows:
Subnet mask: 255.255.255.0
Default gateway: [blank]
Once those parameters have been successfully set, connect your computer and Port 2 of the Kepler server together (either directly with a cable or via a network switch: one network cable from your computer to the switch and another from Port 2 of the Kepler server to the same switch).
Port 2’s lights and your computer’s network status icon should indicate an active connection.
Open a command prompt or terminal and execute the following command to verify connectivity:
If you cannot ping the Kepler server, please verify your settings & physical connectivity.
Contact your IT/network administrator or Kepler for further assistance.