Hosting
Introduction
This getting started guide serves as the basis for establishing the first connection to your hosting system and BMC access. If you have already established the connection to the firewall, you can continue here.
Connection to firewall
Private Cloud Strategy
Basically, every private cloud package from the TERRA CLOUD is delivered with a virtual Securepoint UTM appliance.
This starter guide serves as the basis for setting up a VPN tunnel and accessing the firewall's web interface.
Requirements for access
OpenVPN Client:
- Securepoint VPN Client - Download Link
- other OpenVPN client
- OpenVPN Client for MacOS - click here
VPN configuration file:
The VPN data for administrator access can be found in the Cloud Center below the respective order within the service information, see also Service-Information.
The point "to the download area" takes you to a central share in Terra Drive, where all your VPN data for the booked virtual environments in the Terra Cloud is located. The prerequisite for this is the access data for your Drive NFR account.
Please note that the central share only contains the VPN data of the environments that you have booked in the Terra Cloud Center.
VLAN Requirements
Every virtual SecurePoint UTM has 2x virtual network interfaces.
One of them communicates with the Internet, the other communicates with the systems in the package.
Since a Hyper-V VM can have a maximum of 8x network cards attached, we can provide a maximum of 6x additional VLANs.
Connect to the firewall
An existing VPN tunnel is required for the connection to the firewall.
Before establishing the connection, please check whether the standard port 1194 is enabled for VPN connections on your local firewall.
If port 1194 is blocked, establishing the VPN tunnel will fail.
Initial setup of the VPN connection in the Securepoint VPN Client
- Install the respective VPN client, in this example we are assuming the Securepoint VPN client.
- Open the VPN client and click the gear at the bottom right to open the settings menu..
- In the context menu under Source file, click on the three dots to select the source file that was previously downloaded from the Cloud Portal.
- Select the opvn file from the previously extracted zip file and click “Import”.
- Optionally, the configuration can be assigned a name under “Import as:” under which the configuration will later be visible in the VPN client.
- Use the arrow button to start establishing the VPN connection
The required initial access data is:
User: ssluser-admin
Password: ChanTroFar93!
Connection to the firewall web interface
After the VPN connection has been successfully established, access the following address in any browser:
https://<firewall IP address>:11115
The IP address of the firewall was assigned by you when ordering the environment and can be accessed subsequently in the Cloud Center
can be viewed below the respective order within the service information, see also Service Information.
The required initial access data is:
User: fwadmin
Password: Terra001
Initial access to the firewall web interface
Note:
The WebGUI has changed visually since firmware version 12.6.2.
However, with a few exceptions, all points are still called the same, so you can continue to follow all the steps using the following instructions.
The first time you open the firewall web interface, a few things need to be done:
Assign firewall name
Please enter a firewall name, which must correspond to an FQDN, e.g. myfirewall.local.
The firewall name must not contain any umlauts, special characters or capital letters.
Then click on the Complete button.
Firmware Update
Depending on the preinstalled firmware version, you will receive a message that a newer firmware is available.
In this example we assume that version 11.8.9 is preinstalled.
This query should be answered with Yes when the environment is commissioned for the first time.
You will then receive a view of the available new firmware, which will be imported using the “Start test run” button.
In order to use the new firmware, several license agreements must be checked and accepted.
Finally, a restart must be carried out. This can take up to 5 minutes.
You can follow the restart via the console connection via the Technical Center (https://manage.terracloud.de).
After the firewall has successfully restarted and you have logged in again, the new firmware must be confirmed as the new standard firmware.
Confirm virus scanner message
If you have booked the firewall with only one vCore, you will receive a message that the number of virus scanners on the firewall has been reduced for stability and performance reasons.
This message is normal and needs to be confirmed.
Set cloud backup password
Please enter a password to back up your firewall configuration in the Securepoint cloud.
This gives you the opportunity to import the firewall configuration from the Securepoint Cloud after reinstalling the firewall.
Your firewall will then be completely set up.
Change of initial passwords
We recommend changing the initial passwords after handover.
- In the firewall interface, open the Authentication --> Users menu item
- Click on the configuration symbol (wrench) behind the respective user and enter the new password in the Password and Confirm Password fields.
- Finally click Save.
The user "admin" cannot be customized by you.
This is an administrative account that is only used in the background for the firewall services.
Instructions and information on configuring the firewall can be found at:
http://wiki.securepoint.de/index.php/Howtos-V11
Email protection: spam filter with anti-virus package (optional)
Protection is implemented directly on the firewall included in the cloud environment.
The following options can be set:
- https://wiki.securepoint.de/UTM/APP/Mailfilter
- https://wiki.securepoint.de/UTM/APP/Mailrelay-Best_Practice
Internet protection: Content filter with anti-virus package (optional)
Internet protection is implemented on the cloud firewall in your cloud environment. The following options can be set:
UMA mail archiving
Log in to Securepoint UMA
If mail archiving has been booked, a Securepoint UMA is available to you in your package.
The web interface for configuration can be accessed via the following address:
The prerequisite for this is a VPN tunnel that has been set up or access via a VM within the network.
The access data for this is “admin” and the password you have assigned.
Further information on configuring and commissioning the Securepoint UMA can be found at the following link:
https://wiki.terracloud.de/index.php/UMA
Connection to server
Windows Server
Establish RDP session
Open a remote desktop client and enter the IP address you assigned and connect to the server.
The default IP address of the first server, unless you specify otherwise in the ordering process, is:
192.168.143.1
The required access data is:
- User: Administrator
- Password: Terra001!
Please confirm any message regarding missing certificates that may occur. Certification is pending.
BMC - Access
Open the following address in your browser:
https://XXX.XXX.XXX.201 (Please replace the first three octets with the network specified in the order)
The default IP address, unless otherwise specified, is:
https://192.168.143.201
The required access data is:
- User: Administrator
- Password: Terra001!
We recommend changing the password after the first access. To do this, please go to the Configuration/Users menu item.
Highlight the user “Administrator” and click “Modify User” at the bottom of the list.
Enter a new password and confirmation, save the new password with “Modify”.
VMware ESX Server
After you have set up a VPN tunnel to your environment, open a browser and access the IP address of your server.
The default IP address of the first server, unless you specify otherwise in the ordering process, is:
http://192.168.143.1
You will then be connected to the VMware ESXi page, from here you can directly select the link and download the client
The required access data for server access in the vSphere Client is:
User: root
Password: Terra001!
Troubleshooting
BMC not reachable
Solution:
Download the following tool:
https://sourceforge.net/projects/ipmitool/
Please then enter the following command in the console:
"ipmitool reset bmc cold -I lan -H 10.0.0.1 -U admin -P password".
Explanation of the command:
ipmitool [ <options> ] <command> [ <sub-commands and sub-options> ]
reset bmc cold => immediate hard reset of the BMC module
-I lan => Use of the LAN interface
-H address-U admin -P password => H <hostname> [-U <username>] [-P <password>]
Read hardware log files
Please provide us with the following information:
- Windows Event Logs of the affected system:
- System log
- Application log
- SEL log from the remote management module:
