In this section:
You can access the SP2000 remotely using the
Transaction Language 1 (TL1) port and TL1 commands
EMS access is not supported on the SP2000 and vSP2000.
Remote access to the SP2000 is only possible after you have executed the initial configuration process and configured the IP addresses on the Management and Routing CPUs/VMs. For more information about the initial configuration process and system access, refer to the appropriate document in the Installation Guides.
Access to the Web UI to configure and provision the SP2000 is limited to a Web browser using the Hypertext Transfer Protocol over Secure Socket Layer (HTTPS). If you attempt to use HTTP for system access, you are redirected to use HTTPS. Using HTTPS for system access provides protection from eavesdroppers and man-in-the-middle attacks. Before you can log onto the system, a Certificate of Authority (CA) notification is displayed to ensure that you are, indeed, logging onto the SP2000 (refer to Configuring Signed Certificates from a Certificate Authority).
For information about logging onto the system using the TL1 port and TL1 commands, refer to the appropriate section in the TL1 Reference Guide.
SP2000 Operation, Administration, and Maintenance configuration is largely agnostic of the chassis where the carrier card that hosts the Advanced Mezzanine Cards (AMCs) resides. The Web UI displays the dual carrier card set-up that is present on the chassis.
Access to the carrier cards is through the CPU bond0 and bond0.1 Ethernet interfaces (see the following table).
No physical cabling connections are required to the CPUs.
Carrier Cards Ethernet Configuration
System Card | Slot Number | Subnet | Interface (to be configured byuser) |
---|---|---|---|
CPU | 14 | Management traffic and SIGTRAN or SS7 Traffic on SEPARATE SUBNETS | bond0 |
CPU | 24 | bond0.1 |
The IEMS/GVM user interfaces are used to connect to the carrier cards through the Operation and Administration high-availability IP (OAM HA IP) address. The carrier cards function in an active/standby mode. When the high-availability IP address is invoked, the customer is seamlessly connected to the active carrier card (see the following figure).
As indicated in the following figure, typically, the carrier cards’ IP addresses and the OAM HA IP address are sequential.
System Access Web Interface (Example)
Networking information is defined during the initial configuration process and should only be changed during a maintenance window with Customer Support approval. For more information, contact Customer Support.
Start
The SP2000 supports a customized Linux-based operating system. The following UIs are supported:
For more information about the Web UI or Menu UI, refer to the appropriate sections in the Web UI and Menu UI Guide.
This release supports the following Web browsers:
The following browser versions were used for testing Release 24.0
Microsoft Edge Version: 121.0.2277.128
Firefox Version: 122.0.1
Google Chrome Version: 121.0.6167.185
To log onto the DSC-SP2000, use the shared IP interfaces (for more information about the system IP configuration, refer to the SP2000 Networking Configuration).
The Web UI supports the HTTPS protocol for securedWeb access. If you enter HTTP in the Web browser URL address when logging onto the system (see the procedure To log onto the Web UI (using IE), you are automatically redirected to HTTPS.
Microsoft Internet Explorer is the supported Web browser for the SS7 Database Application (SDA) on SP2000. You cannot access the SDA System Manager GUI using an unsupported Web browser.
Before you can start the Web UI, make sure that you
have installed the SP2000 (refer to appropriate chapter in the Installation Guides)
have connected the local console (refer to appropriate chapter in the Installation Guides understand the SP2000 IP networking configuration (refer to SP2000 Networking Configuration)
are familiar with the SP2000 Web UI (refer to Web UI and Menu UI Guide)
are familiar with the User Profiles and Privileges feature (refer to SP2000 User Profiles and Privileges)
are familiar with SP2000 password management (refer to DSC Password Management)
have the required password
For information about logging on as a tl1 user, refer to the appropriate section in the TL1 Reference Guide.
After you can access the Web UI, using the Custom Application you can create a redirect button to access any Web-enabled application, such as Google as shown in the following procedure.
Enter the required information in the text boxes (in this example, the information for Google and the required Link Address).
Click Save. The Google button appears under the Application Menu.
Click Google.
To prevent unauthorized access, you must click Logout to log off the Web UI.
From any screen in the Web UI click Logout.
Before you can start the Menu UI, make sure that you
have installed the SP2000
have connected the local console
understand the SP2000 IP networking configuration
For more information about the preceding items, refer to the appropriate sections in the Installation Guides
are familiar with the SP2000 Menu UI
For more information about the SP2000 Menu UI, refer to the appropriate sections in the Web UI and Menu UI Guide
completed the procedures in the DSC Password Management section using the Web UI
# startmenu
The SP2000 is equipped with a Simple Network Management Protocol (SNMP) agent that can connect with up to ten SNMP managers, or network management systems.
SNMP is part of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite. The SNMP is an application layer protocol that defines how management information between network devices is exchanged. The SNMP provides a means to monitor and control network devices.
An SNMP-managed network consists of the following three key components:
An SNMPManagercan manage and monitor a network device using
The SP2000 agents support Management Information Bases (MIBs) for monitoring various SP2000 devices, entities, and alarms, and includes a circular buffer to record (up to 2048) instances of the alarms. The default value is 1000. To set this value as required, refer to Configuring the Trap Log. The MIB contains the performance and alarm data collected from the SS7 network.
The Alarm Dashboard only displays alarms that are currently uncleared by the system. Alarms that are raised and quickly cleared by the system may be overlooked by the operator. Theptisyslogfile should be periodically reviewed for a historical list of all events and alarms that have been raised by the system.
For more information about SNMP, refer to Configuring SNMP.
Transaction Language 1 (TL1) is a Man-Machine Language (MML) widely used in the telecommunications industry for the management of network elements. A computer terminal configured with any operating system capable of establishing a Telnet session is used to communicate with a network element using TL1 commands. TL1 commands are ASCII-based instructions that are entered by an operator at a computer terminal and sent to a network element. The network element sends back a response based on the instructions.
The SP2000 supports a customized Linux-based operating system and TL1 command capabilities. The TL1 commands are used to manage software application elements and parameters for this product.
For more information about TL1, refer to the appropriate chapter in the TL1 Reference Guide.