If the Status attribute shows UP, deactivate this Transport Server before proceeding to the next step.
Do the following:
Set the ADN Protocol to XML.
Activate the Transport Server
The Status should indicate UP before you can proceed with further provisioning
...
Cloak
id
@configADN
From the Main Menu, click DSC.
Click DSC Nodes.
Click the required DSC Node.
Click Adjacent Diameter Nodes.
Click Create.
Do the following:
Set the Type to UA XML.
Configure the other attributes as required.
If the General Configuration page does not appear, do the following:
Navigate to the Adjacent Diameter Node Selection screen
Click the ADN you created (as Type UA XML).
Configure the required attributes.
Click Continue.
Tip
The Status attribute shows DOWN until the ADN connection is established.
When creating an ADN, you are redirected to the General Configuration page where you may select options for the ADN. The 'Activate' checkbox is selected by default. Simply click 'Continue' to enable the new ADN Connection.
To configure an ADN Connection for a UA XML Session
...
Cloak
id
@configUA
From the Main Menu, click DSC.
Click DSC Nodes.
Click the required DSC Node.
Click Adjacent Diameter Nodes.
Click the required ADN.
Do one of the following:
If required, click Create to create an ADN Connection. Go to step 7.
Click the required ADN Connection. Go to step 10.
Enter the Process Instance.
Navigate to the ADN Connection Selection.
Click the ADN Connection that you just created.
Do the following:
Tip
The Status Attribute may show DOWN by default. However, if this is an already established connection, this attribute may show UP.
When creating a new ADN Connection, the 'Activate' checkbox is selected by default. Click 'Continue' to enable the new ADN Connection. For an existing ADN Connection, you must select the 'Activate' checkbox and then click 'Continue'. You may have to click 'Deactivate' first before enabling an existing ADN Connection that has been modified.
Using the Transport Type drop-down list, select SERVER ONLY.
Configure the other attributes as required.
Click ACTIVATE.
...
Cloak
id
@fire
Click Firewall.
Select the required CPU from the drop-down menu to view the firewall status.
Click Update.
Verify the VM virtaul slot status is set to DISABLED.
Click STOP FIREWALL if the VM virtual slot status is set to ENABLED.
Note
The global control enables or disables the Firewall on all Routing and Management and Routing VMs by selecting Enable Firewall or Disable Firewall. The Global Status of the Firewall must be Enabled before you can start or stop the Firewall on individual VMs).
Anchor
Creating Firewall
Creating Firewall
Creating a Firewall Module File
Noprint
Click to read more...
Toggle Cloak
id
@createfire
Cloak
id
@createfire
padding-left:3%;indent
To establish an XML session with a remote agent when the firewall is enabled on the companyseries4, you must manually create an IP filter module to allow a connection on remote ports.
The IP filter module is a text file that you create and should be stored in the /opt/cpu_ss7gw/current/data/firewall/modules directory using the following naming convention:
‘<file-name>.conn’ (for example, ssh-in.conn)
Within this file, you must specify the UNIX port number for the service type that you want to enable.
Note
Unless specified in the IP filter module, the companyseries4uses the default range of internal port numbers between 1,024 and 65,535. The remote system negotiates with the series4to establish the first available port number within the range specified.
Example:
Enable IMF traffic (file “imf.conn”):
MESSAGE=”IMF Traffic”
REMOTE_PORTS=”8901”
VALID_HOSTS=”192.168.10.2”
PROTOCOL:”tcp”
or, for multiple ports:
REMOTE_PORTS=”8901 8904 8909”
or for a range of ports:
REMOTE_PORTS=”8901:8909”
or for multiple hosts:
VALID_HOSTS=”192.168.10.2 192.168.20.2”
After you have created this text file, you must copy the file to all CPUs (Management, Routing, and Application CPUs) and restart the Firewall.
For more information on configuring the Firewall and other security services, refer to the .