Versions Compared

Old Version 2

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
UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}UserResourceIdentifier{userKey=8a00a0c85c46b657015d4f57d577001c, userName='null'}UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHCHOR-4523 6900
REV5
REV6
REV3
REV1

Panel

In this section:

Table of Contents
maxLevel2

...

Info

By default, Azure designates the VM’s first network's Interface as the primary network interface. Only the primary network interface receives a network default gateway and routes via DHCP. The first network interface on the SWe Lite is recommended to be used only for management. Media traffic routed to this interface will not be processed. To avoid this problem, you must either:

  • Create a Static Route(s) on the SWe Lite to route signaling/media traffic to the Media (non admin) interface(s).
  • Create a Static Route(s) on the SWe Lite to route all traffic to the Media (non admin) interface(s). When you do this, you must configure all Logical Interfaces with the DHCP Options to Use field set to IP Address (refer to Configuring and Modifying Logical Interfaces).
 

  • Change the primary network interface assignment from the Management interface to the Media interface. Refer to Change Azure Default Route.

Step 8: License Installation

...