Diameter Node - CLI

Use the Diameter Node object to define the parameters for the SBC side of a Diameter interface.

The SBC Core uses a connection over a Diameter interface for both quality of service (QoS) resource reservation requests and for transmitting lawful intercept (LI) information to mediation servers in deployments that follow the PacketCable 2.0 LI model. Within SBC configuration there is a single Diameter node object that is shared for both use cases. 

In the first use case, the Rx interface pertains to QoS resource reservation for reserving bandwidth in an IP access network. The Rx interface is used to exchange application-level session information between a Policy and Charging Rules Function (PCRF) element and the P-CSCF. The SBC, acting as a P-CSCF, creates a TCP connection with the configured PCRF. For this case, you use the Diameter Node object to configure the Diameter realm for sending external QoS requests on a per-IP-trunk-group basis.

In the second case, the SBC uses a Diameter-based interface (X2 interface) over TCP transport to send intercepted call data and associated call events from the SBC to an LI mediation server. In general, LI configuration must be completed by a user with specific LI privileges (the calea user). However because the Diameter node object is also used for a non-LI purpose, the node name (<diameterNode_name>) must be assigned, as described on this page, by a user with admin privileges. You then include the Diameter node name in the LI call data channel (CDC) configuration. However, the remaining Diameter configuration required to support PC 2.0 LI (Diameter peers and Diameter realm routes), must be completed by the calea user within CDC configuration. Refer to PacketCable 2.0 LI Configuration for information and procedures for configuring Diameter parameters for PC 2.0 LI deployments. 

Command Syntax

% set addressContext <addressContext_name> diamNode <diameterNode_name>
	dumpPdu <disabled | enabled>
	ipInterfaceGroupName <IPIG_name> 
	ipV4Address <IPv4 address towards peer> 
	ipV6Address <IPv6 address towards peer> 
	originRealm <origin realm name> 
	peer <peer_name>
		deviceWatchdogTimer <0-100000 ms>
		deviceWatchdogTimerAnswerTimeout <1000-500000 ms>
		fqdn <1-256 characters> 
		ipAddress <IP address>
		sessionDistribution <honor-reply-order | round-robin>
		state <disabled | enabled> 
		tcpPort <#> 
	primaryOriginHost <primary host name> 
	realmRoute <realmRoute_name> 
		appId <e2 | rf | rx> 
		peer <name> 
		priority <0-100> 
		realm <name> 
		state <disabled | enabled> 
	secondaryOriginHost <secondary host name> 
	state <disabled | enabled> 
	transactionTimeout <500-6000 milliseconds>

% set addressContext default diamNode <node name>
    originRealm <realm name>
    primaryOriginHost <Host name>
    secondaryOriginHost <Secondary host>
    state <disabled | enabled>
    ipInterfaceGroupName <IG Name>
    networkSegmentName <Network Segment name>
    ipNameV4 <IPv4 address>
    ipNameV6 <IPv6 address>
    peer <peer name>
        state <disabled | enabled>        
        ipAddress <IPv4 address>
        fqdn <FQDN>
        tcpPort <port>
        deviceWatchdogTimer <timer value>
        deviceWatchdogTimerAnswerTimeout <timeout value>
    realmRoute <Realm Route name>
        peer <Peer name>
        realm <Realm>
        appId rx
        state <disabled | enabled>

Command Parameters

Diameter Node Parameters

Command Example (P-CSCF/PCRF Use Case)

Example Diameter Node configuration:

% set addressContext ADDR_CONTEXT_1 diamNode diam ipInterfaceGroupName LIG1 ipV4Address 10.54.154.89 ipV6Address fe80::210:6bff:fe03:231 originRealm pcscf-open-ims.test primaryOriginHost katie secondaryOriginHost eleanor transactionTimeout 1500

Mandatory parameters:

1. At least one IP address is required (ipV4Address or ipV6Address)
2. diamNode name
3. primaryOriginHost name
4. ipInterfaceGroupName
5. originRealm name

Default Values:

• state = disabled
• transactionTimeout = 1000 ms

Example Diameter Node Configuration for SBC CNe

set addressContext default diamNode Diam originRealm pcscf-rf-ims.test primaryOriginHost pcrf1 secondaryOriginHost pcrf2 networkSegmentName sg-default-pkt0 ipNameV4 SGPKT0 ipInterfaceGroupName LIGSG state enabled

Mandatory Parameters

1. At least one IP address is required (ipV4Address or ipV6Address)
2. diamNode name
3. primaryOriginHost name
4. ipInterfaceGroupName
5. originRealm name
6. networkSegmentName and either ipNameV4 or ipNameV6.

Default Values:

• state = disabled
• transactionTimeout = 1000 ms

Requirements:

• You cannot modify the ipNameV4/ipNameV6 unless the diamNode is in disabled state.
• The ipAddress (networkSegmentName) assigned for the diamNode is from the new Network Segment Table NsTableType="NS_SG".
• The  ipInterfaceGroup associated with the diamNode contains at least one ipInterface of type NS_SG.
• All the fields related to ipAddress/ipMetaVar are hidden for CNF.
• You cannot modify the network segment table if the ipName is in use by the diamNode.

Example Peer Configuration:

% set addressContext ADDR_CONTEXT_1 diamNode diam peer camiant.nj.sonusnet.com ipAddress 1.2.3.4 fqdn camiant.nj.sonusnet.com tcpPort 4868

Mandatory parameters:

1. fqdn
2. ipAddress
3. peer name

Default values:

• state = disabled
• tcpPort = 3868

Example Realm Route Configuration:

% set addressContext ADDR_CONTEXT_1 diamNode diam realmRoute camiant.nj.sonusnet.com realm camiant.nj.sonusnet.com peer camiant.nj.sonusnet.com appId rx priority 1

Mandatory parameters:

1. peer name
2. realm
3. realmRoute name

Default values:

• appId = rx (for PCRF interface)
• state = disabled
• priority = 0