cc/td/doc/product/rtrmgmt/sgm/sgm40
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Release Notes for Cisco
Signaling Gateway Manager
Release 4.0

Contents

Introduction

Hardware Requirements

Solaris Hardware Requirements

Linux Hardware Requirements

Windows Hardware Requirements

Caveats and Known Bugs for SGM Release 4.0

Windows 2000 hangs when Windows SGM client exits

Windows SGM client fails to launch due to permissions settings on Java preferences in the Windows registry

Loading address tables from an ITP fails or does not show all existing address tables

Content in the GTT Statistics tab is not updated

SMPP and UCP statistics show incorrect values

SMPP and UCP session changes are not reflected in the Events window

Related Documentation

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Cisco
Signaling Gateway Manager
Release 4.0

July 6, 2005

These release notes describe the caveats for Cisco Signaling Gateway Manager (SGM) Release 4.0. These release notes accompany the Cisco Signaling Gateway Manager User Guide, Release 4.0 and the Cisco Signaling Gateway Manager Installation Guide, Release 4.0.

Note You can access the most current Cisco documentation, including these release notes, online:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/sgm/index.htm

Contents

These release notes contain the following major sections:

• Introduction

• Hardware Requirements

• Caveats and Known Bugs for SGM Release 4.0

• Related Documentation

• Obtaining Documentation

• Documentation Feedback

• Obtaining Technical Assistance

• Obtaining Additional Publications and Information

Introduction

These release notes describe caveats, known bugs, and other important information for installing and using Cisco Signaling Gateway Manager (SGM) Software Release 4.0.

Hardware Requirements

Note For a complete listing of hardware and software requirements, see the Cisco Signaling Gateway Manager Installation Guide, Release 4.0.

This section details hardware requirements that must be met before installing SGM:

• Solaris Hardware Requirements

• Linux Hardware Requirements

• Windows Hardware Requirements

Solaris Hardware Requirements

Your system must meet the following hardware requirements to run SGM:

System Hardware

For server software only, or for server and client software running together on the same device:

•If your system does not comply with Network Equipment Building Standards (NEBS), use a SunFire V120 or greater with a 500 Mhz processor or greater.

•If your system is NEBS-compliant, use a Netra 120 or greater with a 500 Mhz processor or greater.

•You can use a Netra T1 or greater, with a 440 Mhz processor or greater, if absolutely necessary, but these devices are not recommended.

•If your network contains more than 50 nodes or 100 links, or if your system uses more than one SGM client, a more powerful CPU is strongly recommended.

•For medium-size networks, a SunFire V210, SunFire V240, or Netra 20 is recommended.

•For larger networks, a SunFire V240, Netra 20, or Sun 280R with maximum CPU and memory is recommended.

•For medium-size and larger networks, you can use a Sun Netra 1400 or greater, if absolutely necessary, but this device is not recommended.

For client software only:

•Sun SunBlade 100 with a 500 Mhz processor or greater.

To install software, a CD-ROM drive on the server or on a remote host system that can be accessed by the Network File System (NFS).

A color monitor is required if you will run the SGM client on the host system.

A PostScript-compatible printer is required for printing graphs and charts.

Memory (RAM)

For server software only, or for server and client software running together on the same device:

•512 MB RAM is required (768 MB strongly recommended).

•If you are running more than one SGM client on the same device, an additional 256 MB RAM is required for each additional client.

•If your network contains more than 50 nodes or 100 links, 1024 MB RAM is required.

•If your system uses more than one SGM client, 768 MB RAM is required.

•If you are running the server and client software on the same device, and you intend to use the client to configure Global Title Translation (GTT) tables, Multi-Layer Routing (MLR) address tables, or Distributed Short Message Routing (DSMR) address tables, up to 512 MB of additional RAM is required.

For example, a client used to configure 500,000-line GTT tables (the largest supported size) requires at least 512 MB of additional RAM, for a total of at least 1024 MB RAM on the device.

For client software only:

•512 MB RAM or greater is required (512 MB recommended).

•If you are running more than one SGM client on the same device, an additional 256 MB RAM is required for each additional client.

•Larger networks require more RAM to maintain performance.

•If you intend to use the client to configure GTT tables, up to 512 MB of additional RAM is required. For example, a client used to configure 500,000-line GTT tables (the largest supported size) requires at least 512 MB of additional RAM, for a total of at least 1024 MB RAM on the client.

Hard Disk Space

For server software only, or for server and client software running together on the same device, 500 MB is required.

For client software only, 75 MB is required (150 MB if installing the client from the SGM Web Server).

SGM statistics reporting requires approximately 1 MB of hard disk space for every 10 links in your network.

By default, the SGM event database can hold a maximum of 5000 events. If you change the default SGM settings to significantly increase the size of the message archive, or if you increase the default aging intervals for reports, additional hard disk space might be required, and the performance of the SGM server and clients is impacted.

Swap Space

Swap space of 1024 MB or greater is required (swap space twice the size of RAM is recommended). Swap space is in addition to the recommended hard disk space.

CiscoWorks2000 and HP OpenView

SGM does not require either CiscoWorks2000 or HP OpenView, but SGM does integrate with those products to provide added value. The above hardware requirements assume that you are not installing SGM on the same device as CiscoWorks2000 or HP OpenView. If you want to install and operate SGM, CiscoWorks2000, and HP OpenView on the same device at the same time, you need a a SunFire V240, Netra 20, or Sun 280R or greater, with enough memory and disk space to support the requirements of each product, as specified in its system requirements section.

Linux Hardware Requirements

Your system must meet the following hardware requirements to run SGM:

System Hardware

For SGM and CDM server software use a SunFire V20z with one or two AMD Opteron 200 series processors.

To install software, a CD-ROM drive on the server or on a remote host system that can be accessed by the Network File System (NFS).

Memory (RAM)

For SGM server software only:

•512 MB RAM is required (768  MB strongly recommended).

•If your network contains more than 50 nodes or 100 links, 1024 MB RAM is required.

For CDM server software only:

•1 GB RAM and 1 73 GB HDD are required.

For SGM and CDM server software:

•If CDM will be running concurrently with SGM then a minimum of 2 GB RAM is required.

Hard Disk Space

For SGM server software only, 500 MB is required.

SGM statistics reporting requires approximately 1 MB of hard disk space for every 10 links in your network.

By default, the SGM event database can hold a maximum of 5000 events. If you change the default SGM settings to significantly increase the size of the message archive, or if you increase the default aging intervals for reports, additional hard disk space might be required, and the performance of the SGM server is impacted.

For SGM and CDM server software on the same device:

•For CDM server software only, 256 MB is required. For CDM call detail record (CDR) storage, a minimum of 1 GB is required. Additional disk space may be required, depending upon the rate at which CDRs are generated, and the frequency at which CDR datastore files are removed.

Swap Space

Swap space of 1024 MB or greater is required (swap space twice the size of RAM is recommended). Swap space is in addition to the recommended hard disk space.

Windows Hardware Requirements

Your system must meet the following hardware requirements to run the SGM client:

System Hardware

An IBM PC-compatible computer is required, with the following specifications:

•A 500 Mhz or faster Pentium III processor or later.

•A color monitor.

•A CD-ROM drive (ISO 9660-compliant) on the host system, or access to the SGM Web Server.

A PostScript-compatible printer is required for printing graphs and charts.

Memory (RAM)

256 MB minimum is required.

If you intend to use the client to configure GTT tables, MLR address tables, or DSMR address tables, between 256 MB and 1 GB of additional RAM is required. For example, a client used to configure 500,000-line GTT tables (the largest supported size) requires at least 1 GB of additional RAM on the client.

Hard Disk Space

100 MB minimum on the drive where you install the SGM client is required (200 MB if installing the client from the SGM Web Server, plus 20 MB minimum on the drive on which you save the downloaded client package).

30 MB minimum on the drive that contains the TEMP directory is required (for InstallShield's temporary files).

20 MB minimum on the drive that contains the Program Files directory is required (for the uninstall files).

Caveats and Known Bugs for SGM Release 4.0

• Windows 2000 hangs when Windows SGM client exits

• Windows SGM client fails to launch due to permissions settings on Java preferences in the Windows registry

• Loading address tables from an ITP fails or does not show all existing address tables

• Content in the GTT Statistics tab is not updated

• SMPP and UCP statistics show incorrect values

• SMPP and UCP session changes are not reflected in the Events window

Windows 2000 hangs when Windows SGM client exits

When you exit the SGM client for Windows 2000 Professional, you might be unable to move the cursor, cursor movement might be very sluggish, or there might be no response to mouse clicks. This is a known Java bug.

Workaround: To correct this problem if it occurs, power-down the Windows device and reboot. To prevent this problem, update to the latest display driver for your video board.

[CSCea10113]

Windows SGM client fails to launch due to permissions settings on Java preferences in the Windows registry

The SGM Windows client may fail to launch because of permissions settings on Java preferences in the Windows registry.

Users who are running the SGM client on Windows with a non-administrative user account may be affected if they meet the following conditions:

•The Windows user ID under which the SGM client is launched is a restricted user.

•The system on which the SGM 4.0 client is running had a pre-1.4.2 version of the Java Virtual Machine (JVM) installed on it at some point (SGM version 3.x used JVM version 1.4.1).

Workaround: Launch the SGM client under an administrative account.

Alternatively, make the following changes to the Windows registry to allow SGM to run under a non-administrative account:

Step 1 Log in as the administrator.

Step 2 Launch regedt32 and give full permissions for the group to which the non-admin account exists (such as "Users" group) for the following registry key:

•HKEY_LOCAL_MACHINE/SOFTWARE/JavaSoft

On Windows XP, right click on the node and select permissions. On Windows 2000, select the node and click the security menu.

[CSCeh92286]

Loading address tables from an ITP fails or does not show all existing address tables

Note This bug is linked to IOS version 12.2(25)SW3, and will be fixed in the next version of IOS.

The Address Table Configurator/Editor option to load address table files from an ITP may not reflect all DSMR or MLR address tables on a signaling point, or the loading process may complete with the following error: "No address table exists" for a specified DSMR or MLR address table, even though the table does actually exist on the ITP.

Workaround: If the router is rebooted, the data will be updated. However, this is a temporary fix, as the problem will reappear over time.

[CSCsb18093]

Content in the GTT Statistics tab is not updated

Note This bug is linked to IOS version 12.2(25)SW3, and will be fixed in the next version of IOS.

Within a signaling point, on the GTT Statistics tab, the data under the General Information section may not be updated.

Workaround: If the router is rebooted, the data will be updated. However, this is a temporary fix, as the problem will reappear over time.

[CSCsb05110]

SMPP and UCP statistics show incorrect values

From the SGM Server Home Page, under the DSMR Daily link, when you click on the SMPP and UCP links, the following fields may return an incorrect value of zero:

•Request Sent Dest

•Request Received Dest

•Response Sent Dest

•Response Received Dest

[CSCsb20624]

SMPP and UCP session changes are not reflected in the Events window

For nodes that have SMPP and/or UCP configured, SMPP and UCP session changes (such as Active, Open, and Inactive) do not generate events in the SGM Events GUI and on the SGM Server Home Page, under the Status and SNMP Trap Messages link.

[CSCei27173]

Related Documentation

Use this document in conjunction with the following documents:

•Cisco Signaling Gateway Manager Installation Guide, Software Release 4.0

•Cisco Signaling Gateway Manager User Guide, Software Release 4.0

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).

Documentation Feedback

You can send comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do

Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

•Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

•The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

•World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

Copyright © 2005 Cisco Systems, Inc. All rights reserved.

hometocprevnextglossaryfeedbacksearchhelp

Posted: Wed Jul 6 08:07:10 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.