Versions Compared

Old Version 7

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.
CSS Stylesheet
img.confluence-embedded-image { display: inline-block !important; }

SBC 1000

The

Spacevars
0series
has three Ethernet ports used for communicating with the IP network. All SIP traffic is carried on these two ports. Unlike the SBC 2000, this model has no dedicated Management Port.

Info

The third Ethernet port on the SBC 1000 is available only if running SBC 1000 v2 hardware. For hardware details, see Ribbon SBC 1000 Hardware Specifications.

SBC 2000

The

Spacevars
0series2
has four Ethernet ports and one Ethernet Management port. By default, each of the four non-management ports are in their own system created VLAN, and are isolated from one another.

ASM

If the unit is equipped with a built-in ASM, all ASM traffic is carried uniquely through this Ethernet port.

Info
iconfalse

For communication between the

Spacevars
0longproduct
and the ASM to work properly, the ASM port's Default Untagged VLAN must be set to a VLAN whose logical IP address is in the same subnet as the ASM's IP address. For example, if the ASM port's default VLAN is set to Ethernet 1 VLAN, then the logical interface Ethernet 1 IP must have its IP address in the same subnet as the ASM IP.

Working with Ethernet Ports:

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to Node Interfaces > Ports. See below for examples.

SBC 1000 - Ports

Panel
borderStylenone
Caption
0Figure
1Ethernet Ports - SBC 1000 Example

Image RemovedImage Added

SBC 2000 - Ports

Panel
borderStylenone
Caption
0Figure
1Ethernet Ports - SBC 2000 Example

Image RemovedImage Added

Ethernet Redundancy for Failover

Ethernet redundancy on the SBC 1000/2000 supports continued operation of the SBC if failures occur regarding the underlying Ethernet service, such as:

  • Ethernet switch malfunction
  • Ethernet port malfunction

By offering a standby Ethernet port to an active port, the 

Spacevars
0longproduct
allows SBC traffic to be re-directed from a primary Ethernet switch to an alternate Ethernet switch (within the same subnet) that is pre-configured (by the enterprise) with the same network connections as the primary Ethernet switch. The alternate switch is assumed capable of recognizing the introduction of live traffic to/from the SBC (over the standby Ethernet port) and to recover the outbound/inbound connections to the rest of the network.

Ethernet redundancy includes:

  • A provisioning construct called Ethernet Redundancy Pair
    Only one instance of pair will be supported by the SBC 1000 at any given time;
    A maximum of two instances of pair will be supported by the SBC 2000 at any given time;
  • Any pair must be associated with two physically distinct Ethernet ports; on the SBC 2000, all Ethernet ports associated with one or two pair(s) must be unique;
  • One port within the pair is selected as primary (carries all Tx and Rx to a primary Ethernet switch); the other is provisioned as the standby and is connected to an alternate Ethernet switch in the same subnet;
  • The SBC will offer the provisioning of a single IP address to the pair, to "hide" from upper SBC application layers the Ethernet redundancy feature (i.e. only a single IP address may be assigned to the pair).

 

Info

The Ethernet redundancy featuredoes not support load balancing, and does not guarantee SBC availability.

 

To configure Ethernet Port Redundancy, refer to the following pages for details:

 

To view a Ethernet Port's properties:

Include Page
_View_Entry_Values
_View_Entry_Values
nopaneltrue
Include Page
_Delete_Entry_Procedure
_Delete_Entry_Procedure
nopaneltrue

See also, Viewing Port Counters and Channel Details,

Children Display
depth3
styleh5