The steps going forward will need to be executed through the Bastion server deployed in this lab. Please see Connect to the Bastion Server to access the lab for information on how to connect to the Bastion server..
Open Charon Manager from the Bastion desktop.
Obtain the Emulator Host IP Address and Password for Emulator Server from the Event Engine dashboard.
If you need assistance obtaining information from the Event Engine dashboard, please see the Getting Started: Login section of this lab.
The Charon Manager console will display the environments managed by the Charon emulator as shown below. We will be configuring the Target environment. This is where we will be migrating our Solaris environment from the on-premise datacenter.
Select eth2 from the list and copy its MAC address. eth2 is the adapter of the target system being managed by Charon manager.
It is mandatory that the emulator (or any other client) uses the MAC address assigned to the instance by AWS. This applies to all incoming and outgoing packets.
IP setting information for eth2 (target environment) will be empty, that is because the network configuration will need to be done on the Solaris operating system. These steps will be covered in the upcoming sections.
Charon SSP is emulating a HME adapter, which is a SPARC hardware network interface.
In this configuration, the target environment is being allocated 1GB of emulated RAM and an additional 1GB of DIT acceleration (cache). This means that our target system could consume up to 2GB of RAM.