Skip to end of metadata
Go to start of metadata

This procedure describes how to add or modify a Loopback Address.

Modifying, Enabling and Disabling a Loopback Interface

Note: The functionality of enabling and disabling logical interfaces is available on the Ribbon SBC 2000 only.

Figure : Loopback Interface

 

 

To modify a Loopback Interface:

  1. Click the expand () Icon next to the entry you wish to modify.
  2. Edit the entry properties as required.

To enable a Loopback Interface:

  1. Select the check box next to the entry you wish to enable.
  2. Click the Enable () icon at the top of the table. 

To disable a Loopback Interface:

 

  1. Select the check box next to the entry you wish to disable.
  2. Click the Disable () icon at the top of the table. 

Configuring Loopback Interfaces

Before you configure a loopback interface, make sure that static and/or dynamic routing has been correctly configured to handle aRibbon SBC 1000/2000 with a loopback interface.
Example:

SBC 1000/2000

Loopback IP: 172.16.40/24

App-IP: 138.51.200.220/24

Cisco Router

Eth4/0: 138.51.200.220/24

 

In this example the Cisco device can ping 138.51.200.220. But, by default, it is unable ping 172.16.40.1. So a static route must be established on the Cisco device before it can reach 172.16.40.0/24 through 138.51.200.220.

Note that both 172.16.40.1 and 138.51.200.220 identify the same Ribbon SBC 1000/2000.

The advantage of using a loopback interface is that SIP may use 172.16.40.1 in its configuration, and the interface IP addresses may be changed without impacting current calls in progress or SG configurations. When interface IP addresses are changed, it may affect RTP/RTCP packets using that interface, as would any network-level change. Calls in progress or SG configurations on the Ribbon SBC 1000/2000and other SIP-layer peers of Ribbon will not have to be suspended, re-configured, torn-down, or re-established in any way. The applications use IP addresses completely isolated from the IP addresses that are used on the links/networks.

Identification/Status - Field Definitions

The Identification/Status Panel controls the network identity of the port and its administrative state (Up or Down). It also provides the port's current service status and when that status last changed.

Port Alias

Specifies an alias for the port. This text is configured by the operator for exclusive use by SNMP-based element and network management systems to assign a key to the port or interface, that is unique across the managed network. Examples would be "Node10Port5" and "VerizonPort5"

Admin State

Specifies the administrative state of the port. Valid entries: Enabled or Disabled.

Networking - Field Definitions

Primary/Secondary Address

Specifies the Primary or Secondary IP Address of this loopback interface.

Primary/Secondary Netmask

Specifies the network mask applied to either the Primary or Secondary IP Address.

Configure Secondary Interface

Specifies whether or not a secondary IP address is configured for this loopback interface.

ACL Out

Specifies the Access Control List to be used on this interface when filtering outgoing packets. Select from the drop down list (populated from the Access Control List table). For more information about Access Control Lists, see Managing Access Control Lists.