Diameter, Configure Peer Node and Connections

1 Description

This instruction describes how to configure one or more Diameter connections from the own node to a peer node.

2 Procedure

Prerequisites

No documents are required.
No tools are required.
The following conditions must apply:
- The unique node identifier, formatted as a case-insensitive, and extended Fully Qualified Domain Name (FQDN). The identifier is composed of the unique node identifier of the peer node to connect to, and the Diameter stack identifier assigned to the own node.
- The unique identifier of the Diameter connection to configure between the own node and the peer node.

2.1 Configure Peer Node and Connections Using CLI

Prerequisites

An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

Steps

Navigate to the DIA-CFG-PeerNodeContainer Managed Object (MO), for example:
>dn ManagedElement=NODE06ST,XyzFunction=xyz,DIA-CFG-Application=DIA,DIA-CFG-StackContainer=abc,DIA-CFG-PeerNodeContainer=abc
Enter Config mode:
(DIA-CFG-PeerNodeContainer=abc)>configure
Create the DIA-CFG-NeighbourNode MO, for example:
(config-DIA-CFG-PeerNodeContainer=abc)>DIA-CFG-NeighbourNode=node12.ericsson.com\23abc

Note:
A first connection conn1 is created automatically with the DIA-CFG-NeighbourNode MO.
Set the transportLayerType and ipAddressesList attributes of the DIA-CFG-NeigbourNode MO, for example.
(config-DIA-CFG-NeighbourNode=node12.ericsson.com\23abc)>transportLayerType=1

(config-DIA-CFG-NeighbourNode=node12.ericsson.com\23abc>ipAddressesList="0:10.1.137.2"

(config-DIA-CFG-NeighbourNode=node12.ericsson.com\23abc>ipAddressesList="1:2dea::66:2"
Set any other relevant optional attributes for the DIA-CFG-NeighbourNode MO.
Enable the DIA-CFG-NeighbourNode MO:
(config-DIA-CFG-NeighbourNode=node12.ericsson.com\23abc)>enabled=true
Commit the settings:
(config-DIA-CFG-NeighbourNode=node12.ericsson.com\23abc)>commit -s

Verify the peer node configuration result:

(config-DIA-CFG-NeighbourNode=node12.ericsson.com\23abc)>show

The following is an example output:

DIA-CFG-NeighbourNode=node12.ericsson.com\23abc
   connIds
      "0:abc#23node12.ericsson.com#23conn1"
   diaVendorId="0"
   firmwareRevision="0"
   isDynamic=false
   ipAddressesList
      "0:10.1.137.2"
      "1:2dea::66:2"
   productName=""
   realm=""
   transportLayerType="1"
   DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1

Navigate to the DIA-CFG-Conn MO for the connection conn1, for example:
(config-DIA-CFG-NeighbourNode=node12.ericsson.com\23abc)>DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1
Set any other relevant optional attributes for the connection for the DIA-CFG-Conn MO.
Enable the DIA-CFG-Conn MO for the connection:
(config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>enabled=true
Commit the settings:
(config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>commit -s
Verify the connection configuration result:
(config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>show

The following is an example output:
DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1 blockReason="Own Node or Peer Node disabled" enabled=true linkStatus="Initial"
Are more connections needed?
Yes: Continue with the next step.

No: Proceed with Step 22.
Navigate to the DIA-CFG-NeighbourNode MO:
>up
Create the DIA-CFG-Conn MO for one more connection, for example:
(config-DIA-CFG-NeighbourNode=node12.ericsson.com\23abc)>DIA-CFG-Conn=abc\23node12.ericsson.com\23conn2
Set any other relevant optional attributes for the connection for the DIA-CFG-Conn MO.
Enable the DIA-CFG-Conn MO for the connection:
(config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn2)>enabled=true
Commit the settings:
(config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn2)>commit -s
Verify the connection configuration result:
(config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn2)>show

The following is an example output:
DIA-CFG-Conn=abc\23node12.ericsson.com\23conn2 blockReason="Own Node or Peer Node disabled" enabled=true linkStatus="Initial"
Proceed with Step 14.
Return to Exec mode:
(config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn2)>end

2.2 Configure Peer Node and Connections Using NETCONF

Steps

Prepare an XML file according to the following template to add Peer Node:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
      <XYZFunctionBranch>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId><applStackId></stackContainerId>
           <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId><applStackId></peerNodeContainerId>
             <DIA-CFG-NeighbourNode operation="create">
              <nodeId><applNodeId></nodeId>
              <transportLayerType><transportLayerType></transportLayerType>
              <ipAddressesList><ipAddress></ipAddressesList>
              <sctpAddressesList><sctpAddress></sctpAddressesList>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
         </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
    </XYZFunctionBranch>
   </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]> 
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

Note:: The XYZFunctionBranch part can be composed of many elements depending on where the Diameter subtree is connected in the managed element structure. In the example below, we assume that the parent MOs are created and the XYZFunctionBranch is empty.

Example to add Peer Node using NETCONF:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId>TST_SRV</stackContainerId>
           <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId>TST_SRV</peerNodeContainerId>
             <DIA-CFG-NeighbourNode operation="create">
              <nodeId>server.ericsson.com\23TST_SRV</nodeId>
              <transportLayerType>1</transportLayerType>
              <ipAddressesList>0:10.1.137.2</ipAddressesList>
              <ipAddressesList>1:2dea::66:2</ipAddressesList>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
         </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
   </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]>
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

Pass the prepared XML file to shell:
ssh -p 830 <user_name>@<node_vip_address> -s -t ⇒ netconf < <xml_file>

<xml_file> refers to the XML file name.

Prepare an XML file according to the following template to modifying the Peer Node attributes:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
      <XYZFunctionBranch>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId><applStackId></stackContainerId>
           <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId><applStackId></peerNodeContainerId>
             <DIA-CFG-NeighbourNode operation="replace">
              <nodeId><applNodeId></nodeId>
              <attribute1>value1</attribute1>
              ...
              <attributeN>valueN</attributeN>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
         </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
     </XYZFunctionBranch>
    </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]> 
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

Note:: The XYZFunctionBranch part can be composed of many elements depending on where the Diameter subtree is connected in the managed element structure. In the example below, we assume that the parent MOs are created and the XYZFunctionBranch is empty.

Example to modify Peer Node attributes using NETCONF:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId>TST_SRV</stackContainerId>
           <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId>TST_SRV</peerNodeContainerId>
             <DIA-CFG-NeighbourNode operation="replace">
              <nodeId>server.ericsson.com\23TST_SRV</nodeId>
              <enabled>true</enabled>
              <initiateConnection>false</initiateConnection>
              <ipAddressesList>2:10.1.137.2</ipAddressesList>
              <ipAddressesList>3:2dea::66:2</ipAddressesList>
              <sctpAddressesList>0:10.1.137.4</sctpAddressesList>
              <portNr>40000</portNr>
              <isIPv6Supported>true</isIPv6Supported>
              <transportLayerType>3</transportLayerType>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
         </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
    </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]> 
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

Pass the prepared XML file to shell:
ssh -p 830 <user_name>@<node_vip_address> -s -t ⇒ netconf < <xml_file>

<xml_file> refers to the XML file name.

Prepare an XML file according to the following template to enable Peer Node:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
      <XYZFunctionBranch>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId><applStackId></stackContainerId>
            <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId><applStackId></peerNodeContainerId>
             <DIA-CFG-NeighbourNode operation="replace">
              <nodeId><applNodeId></nodeId>
              <enabled>true</enabled>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
        </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
    </XYZFunctionBranch>
   </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]>
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

Note:: The XYZFunctionBranch part can be composed of many elements depending on where the Diameter subtree is connected in the managed element structure. In the example below, we assume that the parent MOs are created and the XYZFunctionBranch is empty.

Example to enable Peer Node using NETCONF:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId>TST_SRV</stackContainerId>
           <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId>TST_SRV</peerNodeContainerId>
             <DIA-CFG-NeighbourNode operation="replace">
              <nodeId>server.ericsson.com\23TST_SRV</nodeId>
              <enabled>true</enabled>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
         </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
   </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]>
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

To disable Peer Node, set enabled to false in the provided example.

Pass the prepared XML file to shell:
ssh -p 830 <user_name>@<node_vip_address> -s -t ⇒ netconf < <xml_file>

<xml_file> refers to the XML file name.

Prepare an XML file according to the following template to delete Peer Node:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
      <XYZFunctionBranch>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId><applStackId></stackContainerId>
            <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId><applStackId></peerNodeContainerId>
             <DIA-CFG-NeighbourNode operation="delete">
              <nodeId><applNodeId></nodeId>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
        </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
    </XYZFunctionBranch>
   </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]>
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

Note:: The XYZFunctionBranch part can be composed of many elements depending on where the Diameter subtree is connected in the managed element structure. In the example below, we assume that the parent MOs are created and the XYZFunctionBranch is empty.

Example to delete Peer Node using NETCONF:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId>TST_SRV</stackContainerId>
           <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId>TST_SRV</peerNodeContainerId>
             <DIA-CFG-NeighbourNode operation="delete">
              <nodeId>server.ericsson.com\23TST_SRV</nodeId>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
         </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
   </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]>
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

Pass the prepared XML file to shell:
ssh -p 830 <user_name>@<node_vip_address> -s -t ⇒ netconf < <xml_file>

<xml_file> refers to the XML file name.

Prepare an XML file according to the following template to add a Connection:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
      <XYZFunctionBranch>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId><applStackId></stackContainerId>
           <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId><applStackId></peerNodeContainerId>
             <DIA-CFG-NeighbourNode>
              <nodeId><applNodeId></nodeId>
               <DIA-CFG-Conn operation="create">
                <connId><applConnId></connId>
               </DIA-CFG-Conn>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
         </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
    </XYZFunctionBranch>
   </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]>
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

Note:: The XYZFunctionBranch part can be composed of many elements depending on where the Diameter subtree is connected in the managed element structure. In the example below, we assume that the parent MOs are created and the XYZFunctionBranch is empty.

Example to add a Connection using NETCONF:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId>TST_SRV</stackContainerId>
           <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId>TST_SRV</peerNodeContainerId>
             <DIA-CFG-NeighbourNode>
              <nodeId>server.ericsson.com\23TST_SRV</nodeId>
               <DIA-CFG-Conn operation="create">
                <connId>TST_SRV\23server.ericsson.com\23conn2</connId>
               </DIA-CFG-Conn>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
         </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
   </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]>
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

Pass the prepared XML file to shell:
ssh -p 830 <user_name>@<node_vip_address> -s -t ⇒ netconf < <xml_file>

<xml_file> refers to the XML file name.

Prepare an XML file according to the following template to enable a Connection:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
      <XYZFunctionBranch>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId><applStackId></stackContainerId>
            <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId><applStackId></peerNodeContainerId>
             <DIA-CFG-NeighbourNode>
              <nodeId><applNodeId></nodeId>
               <DIA-CFG-Conn operation="replace">
                <connId><applConnId></connId>
                <enabled>true</enabled>
               </DIA-CFG-Conn>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
        </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
    </XYZFunctionBranch>
   </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]>
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

Note:: The XYZFunctionBranch part can be composed of many elements depending on where the Diameter subtree is connected in the managed element structure. In the example below, we assume that the parent MOs are created and the XYZFunctionBranch is empty.

Example to enable a Connection using NETCONF:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId>TST_SRV1</stackContainerId>
           <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId>TST_SRV1</peerNodeContainerId>
             <DIA-CFG-NeighbourNode>
              <nodeId>coloc.realmColoc.com\23TST_SRV1</nodeId>
               <DIA-CFG-Conn operation="replace">
                <connId>TST_SRV1\23coloc.realmColoc.com\23conn1</connId>
                <enabled>true</enabled>
               </DIA-CFG-Conn>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
         </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
   </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]>
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

To disable the Connection, set enabled to false in the provided example.

Pass the prepared XML file to shell:
ssh -p 830 <user_name>@<node_vip_address> -s -t ⇒ netconf < <xml_file>

<xml_file> refers to the XML file name.

Prepare an XML file according to the following template to delete a Connection:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
      <XYZFunctionBranch>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId><applStackId></stackContainerId>
            <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId><applStackId></peerNodeContainerId>
             <DIA-CFG-NeighbourNode>
              <nodeId><applNodeId></nodeId>
               <DIA-CFG-Conn operation="delete">
                <connId><applConnId></connId>
               </DIA-CFG-Conn>
             </DIA-CFG-NeighbourNode>
          </DIA-CFG-PeerNodeContainer>
        </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
    </XYZFunctionBranch>
   </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]>
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

Note:: The XYZFunctionBranch part can be composed of many elements depending on where the Diameter subtree is connected in the managed element structure. In the example below, we assume that the parent MOs are created and the XYZFunctionBranch is empty.

Example to delete a Connection using NETCONF:

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
  </capabilities>
</hello>]]>]]>
<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
  <target><running/></target>
   <config>
     <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
     <managedElementId>1</managedElementId>
       <DIA-CFG-Application xmlns="urn:com:ericsson:ecim:dia_mim">
        <applicationName>DIA</applicationName>
         <DIA-CFG-StackContainer>
          <stackContainerId>TST_SRV</stackContainerId>
           <DIA-CFG-PeerNodeContainer>
            <peerNodeContainerId>TST_SRV</peerNodeContainerId>
             <DIA-CFG-NeighbourNode>
              <nodeId>server.ericsson.com\23TST_SRV</nodeId>
               <DIA-CFG-Conn operation="delete">
                <connId>TST_SRV\23server.ericsson.com\23conn2</connId>
               </DIA-CFG-Conn>
             </DIA-CFG-NeighbourNode>
           </DIA-CFG-PeerNodeContainer>
         </DIA-CFG-StackContainer>
       </DIA-CFG-Application>
   </ManagedElement>
  </config>
</edit-config>
</rpc>]]>]]>
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>]]>]]>

Pass the prepared XML file to shell:
ssh -p 830 <user_name>@<node_vip_address> -s -t ⇒ netconf < <xml_file>

<xml_file> refers to the XML file name.

1	Description
2	Procedure
2.1	Configure Peer Node and Connections Using CLI
2.2	Configure Peer Node and Connections Using NETCONF