Versions Compared

Key

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

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHCHOR-5993
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd0, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c86a61778d016a7d0876df0017, userName='null'}


Panel

In this section:

Table of Contents
maxLevel3



Info
iconfalse

Related articles:

Children Display





The Logical Interfaces section configures IP addresses (both IPv4 and IPv6) for the Ethernet ports and VLANs. Detailed description of the IP addresses for each of the

Spacevars
0longproduct
 platforms is given below. To configure the physical layer settings and VLANs for the Ethernet ports, go to Ports.

About Logical Interfaces -
Spacevars
0company
SBC 1000

The 

Spacevars
0series
 supports three system created logical interfaces (known as Ethernet 1 IP,   Ethernet 2 IP, and Ethernet 3 IP) used to hold the IP addresses of the Ethernet ports 1, 2, and 3 respectively. In addition to the system created logical interfaces, the
Spacevars
0series
also supports user created VLAN logical interfaces. VLAN logical interfaces are created each time a VLAN is added to the system. See About Logical Interfaces - VLAN Interfaces.

Info

The third Ethernet port on the SBC 1000 is available only if running selected SBC 1000 hardware and SBC Release 6.0.0 or later. For hardware details, see Ribbon SBC 1000 Hardware Specifications.

Ethernet IP

When delivered from the factory, Ethernet 1 IP is enabled with DHCP by default, and an IPv4 address is acquired via a connected DHCP server. This IP address is used for performing Initial Setup on the SBC 1000. See Running Initial Setup for more information.

The default IP address for the logical interface named Ethernet 2 IP is 192.168.129.2. After initial configuration, you may configure this logical interface using Settings or Tasks tabs in the WebUI.

After initial configuration, a third logical interface named Ethernet 3 IP can be configured via Settings or Tasks tabs in the WebUI.

The IP addresses configured on the three logical interfaces and the VLAN interfaces are used for transporting all the VOIP media packets (e.g., RTP, SRTP) and all protocol packets (e.g., SIP, RTCP, TLS). DNS servers of the customer's network should map the

Spacevars
0series
system hostname to the configured IP addresses. The hostname or these IP addresses may be used by UC-enabling systems such as SIP-phones, IP-PBX and Microsoft Skype Servers and for accessing
Spacevars
0series
WebUI.

Info

Typical Skype for Business deployment where all three Ethernet ports are used:

  • Ethernet Port 1 to LAN
  • Ethernet Port 2 to WAN network 1 (primary)
  • Ethernet Port 3 to WAN network 2 (backup)

 About Logical Interfaces -
Spacevars
0company
SBC 2000

The

Spacevars
0series2
supports five system created logical interfaces (known as Administrative IP, Ethernet 1 IP, Ethernet 2 IP, Ethernet 3 IP, and Ethernet 4 IP) used to hold the IP addresses of the Admin port and each of the four Ethernet ports (see SBC 2000 Front Panel). In addition to the system created logical interfaces, the
Spacevars
0company
SBC 2000 also supports user-created VLAN logical interfaces. VLAN logical interfaces are created each time a VLAN is added to the system, and are further described in About Logical Interfaces - VLAN interfaces.

Administrative IP

The 

Spacevars
0series2
system defines a logical interface called the Admin IP (Administrative IP, also known as the Management IP). This logical interface is used to hold the IP address of the Admin Ethernet port . A secondary IP address may be configured for this logical interface. The primary IP address is a factory-default IP address of 192.168.128.2/24 and it is used for running Initial Setup of the 
Spacevars
0series2
system.

Include Page
_Sonus SBC 2000_Admin_Port_Warning
_Sonus SBC 2000_Admin_Port_Warning
nopaneltrue

Ethernet IP

The 

Spacevars
0series2
system has one predefined logical interface for each of the four Ethernet ports. In most deployments, one of these logical interfaces (typically Ethernet 1 IP) and its assigned IP address is used for transporting all the VOIP media packets (e.g., RTP, SRTP) and all protocol packets (e.g., SIP, RTCP, TLS). DNS servers of the customer's network should map the 
Spacevars
0series2
system hostname to this IP address. The hostname or these IP addresses may be used by UC-enabling systems such as SIP-phones, IP-PBX and Microsoft Skype Servers and for accessing the
Spacevars
0series2
WebUI.

By default, each of the four Ethernet ports is set up to use its matching logical interface (e.g. Port Ethernet X uses Ethernet X IP) for IP layer communication, but this can be changed by configuring the VLAN settings on the Ethernet port.

When delivered from the factory, Ethernet 1 IP is enabled with DHCP by default, and an IPv4 IP address is acquired via a connected DHCP server. This IP address is used for performing Initial Setup on the

Spacevars
0series2
. See Running Initial Setup more information. The default IP address for the logical interface named Ethernet 2 IP is 192.168.129.2. After initial configuration, you may configure this logical interface using Settings or Tasks tabs in the WebUI.

About Logical Interfaces -
Spacevars
0company
Spacevars
0series3

The

Spacevars
0series3
supports five system created logical interfaces (known as Administrative IP, Ethernet 1 IP, Ethernet 2 IP, Ethernet 3 IP, and Ethernet 4 IP). In addition to the system created logical interfaces, the
Spacevars
0company
 

Spacevars
0series3
 supports user-created VLAN logical sub-interfaces.

Administrative IP

The 

Spacevars
0series3
system supports a logical interface called the Admin IP (Administrative IP, also known as the Management IP). A Static IP or DHCP is used for running Initial Setup of the 
Spacevars
0series3
system.

Warning

The Administrative IP interface should be used for Running Initial Setup, as well as all management related functionality from the web browser.

Ethernet IP

The 

Spacevars
0series3
system has four logical interfaces. In most deployments, one of these logical interfaces (typically Ethernet 1 IP) is assigned an IP address used for transporting all the VOIP media packets (e.g., RTP, SRTP) and all protocol packets (e.g., SIP, RTCP, TLS). DNS servers of the customer's network should map the 
Spacevars
0series3
system hostname to this IP address. The hostname or these IP addresses may be used by UC-enabling systems such as SIP-phones, IP-PBX and Microsoft Skype Servers and for accessing the
Spacevars
0series3
WebUI.

In the default software, Ethernet 1 IP is enabled and an IPv4 IP address is acquired via a connected DHCP server. This IP address is used for performing Initial Setup on the

Spacevars
0series3
. See Running Initial Setup for more information. The default IP address for the logical interface named Ethernet 2 IP is 192.168.129.2. After initial configuration, you may configure this logical interface using Settings or Tasks tabs in the WebUI.

About Logical Interfaces - VLAN interfaces

SBC Edge 1000-2000

As described in the Managing VLANs - SBC 1000-2000 section, each time a VLAN is created, a matching Logical Interface is also automatically created. This Logical Interface allows you to configure an IP address and have IP layer access for this VLAN. The configured IP address can be accessed through any Ethernet port that is associated with the given VLAN. VLAN Logical Interfaces behave the same as any other Logical Interface, and can be used for transporting VOIP media packets (e.g. RTP, SRTP), protocol packets (e.g. SIP, RTCP, TLS), and/or dynamic routing.

Note

When a VLAN Logical Interface is first created, it will be disabled by default.

SBC SWe Edge

VLAN sub-interfaces allow the separation of either management traffic between the service provider and the customer, or to keep media traffic from multiple sources separate (that need to exist on the same SWe Edge instance). For example, a service provider could use a VLAN to manage a SWe Edge at a customer premise, while also having a management interface for the customer; the service provider and the customer would be on the same physical network, but have separate logical interfaces.

When a VLAN sub-interface is configured, any IP traffic that uses that sub-interface will be VLAN tagged with the configured value.

VLAN sub-interfaces behave the same as any other Logical Interface, and are used for transporting VOIP media packets (e.g. RTP, SRTP), protocol packets (e.g. SIP, RTCP, TLS), and/or dynamic routing.

Configuration for each VLAN sub-interface is identical to the main interfaces (except the VLAN value is used to specify the interface as a sub-interface).

For configuring VLAN sub-interfaces, refer to Managing VLANs - SBC SWe Edge

About Logical Interfaces - IPv4 and IPv6 Support

Logical interfaces support three modes of addressing: IPv4, IPv6, and Both (IPv4/IPv6). By default, Logical Interfaces are in IPv4 mode. When the Logical Interface is set for IPv4 mode, a Primary and Secondary IP address can be created. For IPv6, one primary IP Address can be statically configured.

For specific IPv4 and IPv6 configuration, see Configuring and Modifying Logical Interfaces.

IPv6 to IPv4 - Example

In this example, the LAN uses IPv6, and the WAN uses IPv4. The

Spacevars
0longproduct
is responsible for interworking SIP calls between the two networks. The DNS server is provided by the ISP and the NETP server is provided locally.

Image Modified


IPv6 to IPv6 - Example

In this example, both the LAN and the WAN use IPv6. The SBC is responsible for serving as a back-to-back user agent between the two call legs. The DNS server and NTP server are both on the WAN.

Image Modified


IPv4 to IPv6 - Example

In this example, the LAN uses IPv4 and the WAN uses IPv6. Just as in the IPv6-to-IPv4 case, the SBC is responsible for protocol interworking between the two call legs. The DNS server and the NTP server are both on the LAN.

Image Modified


Managing Logical Interfaces

Excerpt


Info

The example below is shown for SBC 2000.

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Node Interfaces > Logical Interfaces (Networking Interfaces > Logical Interfaces for SWe Edge)

    Image Modified


To view an interface's properties:

Include Page
_View_Entry_Values
_View_Entry_Values
nopaneltrue
Include Page
_Delete_Entry_Procedure
_Delete_Entry_Procedure
nopaneltrue

...


Anchor
logicalinterfacechange
logicalinterfacechange

Logical Interfaces and Redundant Ethernet Pairs

If the logical interface is part of a redundant Ethernet pair, several of the options on the secondary logical interface will become read-only.