In this section:

Use this example configuration to configure your SLB-SBC setup on OpenStack.

Note

Use the same configuration on all SBCs which communicate to a particular SLB.

Procedure

License Requirements

The following licenses are required to perform this procedure:

  • LB-INSTANCE on SLB (on/off)
  • SBC-LB on SBC (count based) 

Configure SLB on OpenStack

# Configuration of ipInterfaceGroup : ( Here 3 interfaceGroups are configured, out of which 2(i.e., LIG1 and LIG2) are used for calls and 1 (i.e., LIG3) dedicated for SBC-SLB interface) :

set addressContext default ipInterfaceGroup LIG1 ipInterface LIF1 ceName vsbcSystem portName pkt0 ipVarV4 IF2.IPV4 prefixVarV4 IF2.PrefixV4 vlanTagVar IF2.VlanId ipVarV6 IF2.IPV6 prefixVarV6 IF2.PrefixV6
commit
set addressContext default ipInterfaceGroup LIG1 ipInterface LIF1 mode inService state enable
commit
set addressContext default ipInterfaceGroup LIG2 ipInterface LIF2 ceName vsbcSystem portName pkt1 ipVarV4 IF3.IPV4 prefixVarV4 IF3.PrefixV4 vlanTagVar IF3.VlanId ipVarV6 IF3.IPV6 prefixVarV6 IF3.PrefixV6
commit
set addressContext default ipInterfaceGroup LIG2 ipInterface LIF2 mode inService state enabled
commit
set addressContext default ipInterfaceGroup LIG3 ipInterface LIF3 ceName vsbcSystem portName pkt0 ipVarV4 IF4.IPV4 prefixVarV4 IF4.PrefixV4 vlanTagVar IF4.VlanId ipVarV6 IF4.IPV6 prefixVarV6 IF4.PrefixV6
commit
set addressContext default ipInterfaceGroup LIG3 ipInterface LIF3 mode inService state enabled
commit


# Configuration of static route :

set addressContext default staticRoute :: 0 fd00:10:6b50:6280::1 LIG1 LIF1 preference 100
commit
set addressContext default staticRoute :: 0 fd00:10:6b50:6290::1 LIG2 LIF2 preference 100
commit
set addressContext default staticRoute 0.0.0.0 0 10.52.36.1 LIG1 LIF1 preference 100
commit
set addressContext default staticRoute 0.0.0.0 0 10.52.38.1 LIG2 LIF2 preference 100
commit

set addressContext default staticRoute :: 0 fd00:10:6b50:6290::1 LIG3 LIF3 preference 100
commit
set addressContext default staticRoute 0.0.0.0 0 10.52.37.1 LIG3 LIF3 preference 100
commit


# Configuration of 2 zones ( ZONE_IAD is INGRESS and ZONE_AS is EGRESS zone)

set addressContext default zone ZONE55555_AS id 3
commit

set addressContext default zone ZONE55555_IAD id 2
commit


# Configuration of Ingress & Egress SipSigPorts :

Note :  sipSigIDs of both Ingress & Egress should be same as configured in SBC . Here ids are 2 , 3 for ingress & egress sipSigPorts respectively, so the same 2,3 should be configured in SBC as well

set addressContext default zone ZONE55555_IAD id 2 sipSigPort 2 ipInterfaceGroupName LIG1 ipVarV6 IF2.IPV6 ipVarV4 IF2.IPV4 portNumber 5060 state enabled transportProtocolsAllowed sip-tls-tcp,sip-tcp,sip-udp
commit

set addressContext default zone ZONE55555_AS id 3 sipSigPort 3 ipInterfaceGroupName LIG2 ipVarV6 IF3.IPV6 ipVarV4 IF3.IPV4 portNumber 5060 state enabled transportProtocolsAllowed sip-udp,sip-tcp,sip-tls-tcp
commit


# Configuration of common interface which is to be used for SLB-SBC communication :
set system slb commInterface addressContext default ipInterfaceGroup LIG3 pktIpVar IF4.IPV4
commit

Configure ACLs on SLB


Note

The Bucket Size value is insignificant if the Fill Rate value is unlimited.

  • The Fill Rate is the maximum rate you expect for the traffic to pass the policer.
  • The Bucket Size is the number of additional packets allowed to pass in a given period if available packets are in the bucket. The credit balance is consumed before the packets are discarded.

If the ACL rules with action = discard, the Fill Rate and the Bucket Size values are irrelevant, and the packets are dropped based on the Type, IP address, or Port.

The Fill Rate and the Bucket Size parameters do not play any role since the policer portion of an ACL is only applicable for the "accept" action and is ignored with the "discard" action since all the packets are already discarded by the criteria.

# Configuration of ipAccessControlList :

set addressContext default ipAccessControlList rule 1 state enabled fillRate unlimited bucketSize unlimited destIpAddress 10.52.36.152 precedence 1 destIpAddressPrefixLength 32
commit

set addressContext default ipAccessControlList rule 2 state enabled fillRate unlimited bucketSize unlimited destIpAddress 10.52.38.152 precedence 2 destIpAddressPrefixLength 32
commit

set addressContext default ipAccessControlList rule 3 state enabled fillRate unlimited bucketSize unlimited destIpAddress 10.52.37.152 precedence 3 destIpAddressPrefixLength 32
commit

# Note: 10.52.37.152 is the IF4.IPV4 IPAddress of the SLB.

set addressContext default operatorAggregatePolicer bucketSize unlimited fillRate unlimited
commit

ACCESS Support Configuration in SLB

Access support configuration is not needed for PEERING CALL.

# Here ZONE_IAD is INGRESS and ZONE_AS is EGRESS zone:

set addressContext default zone ZONE55555_IAD remoteDeviceType accessDevice
commit

set addressContext default zone ZONE55555_AS remoteDeviceType appServer
commit

SLB-specific Configuration in SBC/OAM

Note

Apart from the following configuration, you must configure whatever configuration is required for a basic call on the SBC/OAM.  For example, TrunkGroup, static routes, and so on.


# Configuration to enable SLB in SBC :

set system slb usage enable
commit


# Configuration of common interface which is to be used for SBC-SLB communication :

set system slb commInterface addressContext default ipInterfaceGroup LIG3 pktIpVar IF4.IPV4 
commit


# Configuration of SLB IP Address which is to be used for SBC-SLB communication :

set system slb slbAddress SLBATP ipAddress 10.52.37.152
commit
# Note: 10.52.37.152 is the IF4.IPV4 IPAddress of the SLB.

# Configuration to enable SLB Name in sipSigPort of SBC :

Note : sipSigPort IDs of SBC and SLB should be same . Here sipSigport IDs are 2 ,3 for INGRESS & EGRESS respectively. Same IDs were used in SLB sipSigPort as well

set addressContext default zone ZONE55555_IAD id 2 sipSigPort 2 slbName SLBATP
commit

set addressContext default zone ZONE55555_AS id 3 sipSigPort 3 slbName SLBATP
commit


# Command in OAM to push configuration to SBCs  : ( Only for OAM enabled SBCs)

request system admin vsbcSystem saveAndActivate