Versions Compared

Old Version 4

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
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}
JIRAIDAUTHSBX-129908
REV5UserResourceIdentifier{userKey=8a00a0c87e188912017e4c24a00e0016, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9450244, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9450244, userName='null'}


Include Page
_CNe only
_CNe only


Panel

In this section:

Table of Contents
maxLevel2



Info
iconfalse

Related articles:



After the OAM dashboard service activates, network operators must manually populate the Network Segment Table with IP address details. The Network Segment (NS) then retrieves the information from the Network Segment table (NST) through the config-agent.

The NS maintains the IP association details in a table termed Network Service Association table (NSAT), which is used during the switchover, or when the pod re-requests for an IP address using the same name.

Command Syntax

The available command syntax is based on the chosen networkSegmentType. 

Code Block
titleOAM
collapsetrue
% set system networkSegmentTable <table name> 
  ipNameV4 <IPv4 list>
    ipList <IP Address>
    ipRangeEnd <IP address>
    ipRangeStart <IP address>
  ipNameV6 <IPv6 list>
  networkInterfaceName <name>
  networkName <name> -- for OAM networkSegmentType only
  networkSegmentType <OAM | PFE | SC | SG | SLB>
  prefixV4 <prefix>
  prefixV6  <prefix>
  vlanId <ID>


Code Block
titlePacket Front-End (PFE) Pods
collapsetrue
% set system networkSegmentTable <table name> 
  ipNameV4 <IPv4 list>
    ipList <IP Address>
    ipRangeEnd <IP address>
    ipRangeStart <IP address>
  ipNameV6 <IPv6 list>
  networkInterfaceName <name>
  networkSegmentType <OAM | PFE | SC | SG | SLB >
  pfeID <ID> -- for PFE networkSegmentType only
  portRanges -- for PFE networkSegmentType only 
  prefixV4 <prefix>
  prefixV6  <prefix>
  state <disabled | enabled> -- for PFE networkSegmentType only 
  vlanId <ID>


Code Block
titleBack-end Pods (SC, SG, SLB)
collapsetrue
% set system networkSegmentTable <table name> 
  ipNameV4 <IPv4 list>
    ipList <IP Address>
    ipRangeEnd <IP address>
    ipRangeStart <IP address>
  ipNameV6 <IPv6 list>
  networkInterfaceName <name>  
  networkSegmentType <OAM | PFE | SC | SG | SLB >   
  prefixV4 <prefix>
  prefixV6  <prefix>
  vlanId <ID>


Command Parameters


Multiexcerpt
MultiExcerptNameNetwork Segment All Types

General Parameters (All Network Segment Types)

ParameterLength/RangeDescription

networkSegmentTable

1-23<Name> – The Network Segment Table name for the system.

ipNameV4

1-23

<IPv4 list name> – The list of IPv4 names containing the IP addresses and 'Start' and 'End' IP addresses. 

  • ipList <IP Address> – Enter the list of IP addresses in space-separated format.
  • ipRangeEnd <Ending IP address>
  • ipRangeStart <Beginning IP address>

ipNameV6

N/A

The list of IPv6 names.

networkInterfaceName

N/A

The name of the network interface.

  • mgt0
  • pkt0
  • pkt1

networkSegmentType

N/A

The network segment type for this configuration.

  • OAM  – distributes configuration information to relevant pod instances
  • PFE – When configured, enables Packet Front-End functionality.
  • SC – All types of Media (RTP and X3) land on SC directly
  • SG – When configured, enables the interfacing for non SIP signaling communication. 
  • SLB – Acts as the single entry/exit point for all SIP Signaling to the SBC CNe.

Available_since
Release12.1.2

prefixV4

0 - 32<V4 prefix> – The IPv4 prefix for this Network Segment Table.

prefixV6

0 -128<V6 prefix> – The IPv6 prefix for this Network Segment Table.

vlanId

2 - 4094<TAG> – The VLAN TAG assigned to this Network Segment Table.


OAM-specific Parameter

ParameterLength/RangeDescription

networkName

0-255

Specify the primary and secondary (as applicable) network name.

  • primary – Enter the name of primary network. 
  • secondary – Enter the name of secondary (port-redundancy case) network. 

PFE-specific Parameters

ParameterLength/RangeDescription

pfeID 

N/ASpecify a PFE ID.

portRanges

1-23

<Name> – Enter a unique Port Range name, and then specify its parameters.

  • applicationType – Specify the application type for this Network Segment Table.
    • media
    • signaling
    • signalingGateway
  • rangeStart – Port range start value. Length: 1-65535
  • rangeEnd – Port range end value. Length: 1-65535
  • transport – The protocol type for this Port Range:
    • tcp
    • udp

state

N/A

The Administrative state of the Network Segment Table. You can only change the Network Segment Table when it is disabled, and your changes only take effect once the state changes back to "enabled."

  • disabled (default)
  • enabled



Configuration Examples

IP Range

Code Block

admin@sbc set system networkSegmentTable nst1 prefixV4 24 vlanId 20 networkInterfaceName pkt0 networkSegmentType SC ipNameV4 range1 ipRangeStart 10.NN.NN.N ipRangeEnd 10.NN.NN.N
[ok][2021-05-25 08:35:05] 
[edit]
admin@sbc commit
Commit complete.
[ok][2021-05-25 08:35:07]
[edit]
admin@sbc

IP List

Code Block

admin@sbc set system networkSegmentTable nst1 prefixV4 24 vlanId 20 networkInterfaceName pkt0 networkSegmentType SC ipNameV4 list ipList [ NN.NN.NN.NN NN.NN.NN.NN NN.NN.NN.NN NN.NN.NN.NN ]
[ok][2021-05-25 08:39:07] 
[edit]
admin@sbc commit
Commit complete.
[ok][2021-05-25 08:39:09]
[edit]
admin@sbc

Packet Front-End for Cloud Native SBC (CNe)

Users can configure the networkSegment type "PFE" to set up the Packet Front-End for SBC CNe. Only the PFE and OAM network segment types are allowed in the PFE-based SBC CNe solution.

The following parameters are added to the network segment table to support SBC CNe:

  • PFE ID
  • applicationType
  • rangeStart
  • rangeEnd
  • transport
  • state

For more information on PFE for CNe, refer to: Packet Front-End for Cloud Native SBC.

Command Syntax

Code Block
titleExample
% set system networkSegmentTable pfe-pkt0 networkSegmentType PFE pfeID <1-15> networkInterfaceName <pkt0 | pkt1> prefixV4 <0-32> vlanId <0-4095> ipNameV4 <name> ipList <IP Address> portRanges <range name> rangeStart <1-65535> rangeEnd <1-65535> applicationType <signaling | media | signalingGateway> transport <udp | tcp> state <enabled | disabled>

Command Parameters

Parameter

Length/Range

Description

M/O

pfeID

1-15

Packet Frontend ID to which the network segment is anchored.

M
applicationTypeN/A

Application type used for Port Range signaling, Media, and Signaling Gateway.

  • media
  • signaling
  • signalingGateway
M
rangeStart1-65535Port range start value.M
rangeEnd1-65535Port range end value.M
transportN/A

Layer 4 protocol.

  • tcp
  • udp
M
stateN/A

State of the network segment table.

  • disabled (Default)
  • enabled
M

Configuration Examples

Code Block
set system networkSegmentTable pfe-pkt0 networkSegmentType PFE pfeID 1 networkInterfaceName pkt0 prefixV4 23 vlanId 485
set system networkSegmentTable pfe-pkt0 ipNameV4 PFE_PKT0 ipList [ 10.161.116.50 ]
set system networkSegmentTable pfe-pkt0 portRanges range1 rangeStart 4096 rangeEnd 4607 applicationType signaling transport udp
set system networkSegmentTable pfe-pkt0 portRanges range2 rangeStart 4608 rangeEnd 6143 applicationType media transport udp
set system networkSegmentTable pfe-pkt0 portRanges range3 rangeStart 6144 rangeEnd 6655 applicationType signalingGateway transport udp
set system networkSegmentTable pfe-pkt0 state enabled
commit