Service: Destination ( IP/protocol/port )
Tenant: Source ( Endpoint )
WayPoint = Public/WAN Interface IP@ + dual-NAT encapsulation
...
Documentation: https://docs.128technology.com/docs/intro_installation_aws
Basic Configuration: https://docs.128technology.com/docs/intro_basic_router_config/
128 Technology Conductor | https://aws.amazon.com/marketplace/seller-profile?id=9f7a8f2b-c239-4c66-b6a8-7f79e772f23c https://aws.amazon.com/marketplace/search/results?searchTerms=Juniper+Networks https://aws.amazon.com/marketplace/search?searchTerms=128+technology |
|---|
|  Image Removed
| 1. Press "Continue to Subscribe". then "Continue to Configuration" then "Continue to Launch"
2. The "Stack name" will be the name of the router in the configuration.
3. Select an existing VPC and EC2 KeyPair to allow SSH access.
4. This listing deploys a 128T Router with one interface in a public subnet and a second interface in a private subnet. In this step select existing public and private subnets.
5. Optionally, if using a 128T Conductor enter the primary node IP address, which appears as the "IPv4 Public IP" in the EC2 Dashboard. If the Conductor is HA, enter the secondary node IP address.
6. Select the instance type (c5.xlarge is selected by default), and select "Next".
7. In the "Configure stack options" step, none of the additional fields are required, so select "Next".
8. In the "Review" step, review the details, click acknowledgments, and select "Create stack".
9. During deployment the "Status" field starts with "CREATE_IN_PROGRESS" and after 1-2 minutes, the "Logical ID" with the stack name should have a status of "CREATE_COMPLETE".  Image Added |
| 1- With Cloud formation |
|
|---|
using the Cloudformation Template |  Image Added
|
|  Image Added
|
| |
|
|
>>> Then click LAUNCH |
 Image Added
|
|  Image Removed Image Added
|
| |
|  |
|  Image Added
|
| |
|
|
|---|
10. Go to the "Outputs" tab and copy the "InstanceIPAddress" and use it to access the Router GUI from Google Chrome with URL "https://xxx.xxx.xxx.xxx". 11. Because the certificate is self-signed, you will have to accept the certificate. With Google Chrome, type "thisisunsafe". 12. When the login screen for the 128T GUI appears the default username is "admin" and the default password is the Instance ID. |
|
Conductor Login:username: admin Password: instance ID: i-0489910xxxxxxxxx
or https://x.x.x.x/dashboard | |  Image Removed | 
Image Removed |
| If the password does not work | 1- log using SSH ( and the KeyPair ) 2- change the passwords with sudo passwd admin >> enter a new password |
| Upgrade |
|
|---|
| install the username / token | repo and issues install128t repo authenticate -u <user> -t <token> |
| 1-List repository: sudo install128t repo list 2- add beta repo: sudo install128t repo enable beta ( or alpha or both ) 3- add plugins: sudo install128t repo enable plugins-beta |
| Upgrade the installer ( if needed ) | 9.0 Upgrade Conductor and SSR sudo dnf upgrade 128T-installer |
|
| Code Block |
|---|
| [centos@ip-172-31-110-205 ~]$ sudo install128t repo list
Installer will run in non-interactive mode
Preferences are valid
Current Installer version: 3.1.2-1
Repository | ID | Enabled | Credentials Valid
---------------------+-------------------------------------+---------+-------------------
128tech-local-saved | 128tech-local-saved | True | N/A
app-data-release | 128t-authenticated-app-data-release | True | True
beta | 128t-authenticated-beta | True | True
legacy-certificate | 128tech-release | True | N/A
legacy-release | 128t-authenticated-legacy-release | True | True
plugins-beta | 128t-authenticated-plugins-beta | True | True
plugins-release | 128t-authenticated-plugins-release | True | True
release | 128t-authenticated-release | True | True
Installer complete
[centos@ip-172-31-110-205 ~]$
|
|
| Upgrade from the GUO ( or PCLI ) |
|
|
|
|---|
| Public IP address | Auto-assign Public IP: Enable |
| SG | Create a new security group: Enable HTTPS in the security group |
|
|
