Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
AUTH1UserResourceIdentifier{userKey=2c909b309109945b01912fd89e540006, userName='null'}
JIRAIDAUTHSBX-134997
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c86a86c5bc016a96dce2140009, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cbfd06fb, userName='null'}

Overview

An SBC SWe deployment requires a VPC with sufficient IP space to support four or five IPv4 subnets:

...

  1. Navigate to the VPC Dashboard: https://console.aws.amazon.com/vpc/


  2. Select Your VPCs on the left taskbar to see the list of available VPCs available.


  3. Select Subnets on the left taskbar.
  4. ClickSelect Create subnet to create a subnet for MGT0 using a CIDR block. For example, x.x.0.0/20.

    Info
    titleNote

    The SBC uses the MGT0 interface for resolving communications with the AWS REST API endpoints. Because none of the SBC's subnets may overlap with VPC's default DNS IP, use the default route of MGT0 interface for communicating with the VPC's DNS server IP.

    To avoid routing conflicts, ensure the default DNS server IP of the AWS VPC network where the SBC is deployed either overlaps with the SBC's MGT0 subnet or none of the SBC's subnets. 

  5. Select
    Click Create subnet to create a subnet for HA0 using an IPv4 CIDR block, for example, x.x.16.0/20.
  6. Click Select Create subnet to create a subnet for PKT0 using an using an IPv4 CIDR block, for example, x.x.32.0/20.
  7. Click Select Create subnet to create a subnet for PKT1 using an IPv4 CIDR block, for example,  x.x.48.0/20.


  8. If deploying a High-Availability Forwarded Engine instance with the SBC, use a public-facing subnet. You can re-use an existing public-facing subnet.
    If not available, click select Create subnet to create a subnet for HFE Public-facing using an IPv4 CIDR block, for example, x.x.64.0/20

...