Habr•October 30, 2026•🇷🇺Translated from Russian

Reviving Huawei SANEX9510: Expired Certificates, Zero-Byte Keystore and Lost '@' Symbol Fixed Without Database Restart

A telecom OSS platform based on Huawei SANEX9510 (version V200R003C10SPC110) was restored after ten months of downtime caused by a cascade of seven distinct failures across four independent TLS contours.

The system collects and analyzes signaling traffic (MAP, ISUP, SCCP, TCAP) on two main servers and four DSS collectors. Data flows through four separate encrypted paths: WAS-DAS over Thrift (port 29301), DAS-DSS over FTPS, WAS-DSS over SGDSS (port 6688), and Store-Sybase IQ (port 2988). Each contour uses its own keystore and truststore, producing generic error messages that masked the real causes.

Layer 1: DAS identity certificate replacement

The first certificates to expire belonged to the DAS FTPS identity (CN=GENEX CN Nastar, expired 2025-10-18). A new serverkeystore_das.p12 containing the chain mae.huawei.com → Huawei Wireless Network Product CA → Huawei Equipment CA was deployed to both nodes, allowing DAS to start.

Layer 2: Zero-byte WAS keystore

WAS still failed to start because its identity PKCS#12 file was exactly 0 bytes. The empty file produced only indirect TLS errors instead of a clear fatal message. A new keystore was built from server_final.pem and SI.cer, verified as a valid PrivateKeyEntry with CN=mae.huawei.com valid until 2030.

Layer 3: Single missing '@' in encrypted password

TrustStorePass in ThriftClient.properties had lost its leading '@' during copy-paste through a PTY session. Restoring the character allowed the encrypted password to decrypt correctly and the truststore to open.

Layer 4: Separate FTPS keystore

DAS uses serverkeystore_das.p12 for Thrift but serverkeystore.p12 for FTPS (configured in ftpsCer.properties). A mapping of all property files to their actual keystores prevented accidental breakage of the newly restored WAS-DAS link while the FTPS certificate was replaced.

Layer 5: DSS private-key format incompatibility

New certificates had been loaded on the server in May 2026 but not applied to the DSS collectors. After loading via OMU and LOD CERT, the FTP service still refused to start. The private key had been generated with modern OpenSSL using PBKDF2 with HMAC-SHA512, which the product's legacy OpenSSL (0.9.8/1.0.x) could not process. Re-encrypting the key with matching parameters on a current Ubuntu system resolved the issue.

Layer 6: WAS-DSS SGDSS contour on port 6688

After FTPS was fixed, the GUI still showed Connection Interrupted Between WAS and Device. Manual OpenSSL and Java TLS handshakes confirmed mutual authentication worked. Re-establishing the links between WAS and the DSS collectors brought all four DSS instances online without further configuration changes.

Layer 7: Store connection leak to Sybase IQ

Store reported login errors while Sybase IQ showed 204 established connections against a -gm 300 limit. Restarting only the Store process reduced connections to 113 and restored database writes. No password changes or ALTER USER commands were executed.

An unrelated month-old alarm (Failed to import DAS data to database, Alarm ID 20) was traced to a missing PB_DAS_DIRSIZE table. The table was created manually from the installation DDL; subsequent import cycles succeeded immediately.

Related articles

Habr•Other

Cloud4U Webinar Details Migration to On-Premises Microsoft Exchange Server Including Email, Calendars and Infrastructure Setup

Cloud4U is hosting a webinar on November 20 at 12:00 MSK focused on migrating corporate email systems to a self-hosted Microsoft Exchange server. The session covers end-to-end planning from initial preparation and pilot testing through full data transfer and final cutover. Participants will learn practical methods for moving messages and calendars while maintaining delivery reliability and avoiding spam folder placement. Specific tools such as imapsync and PST files are examined along with strategies for handling duplicate messages during repeated sync passes. The webinar also addresses why simply updating MX records is insufficient and explains the correct configuration of SPF, DKIM and DMARC records. Additional topics include calendar migration via ICS files, limitations with active meetings, and post-migration verification steps before decommissioning the legacy system.

AntiMalware•Other

MTS Expands Global Access Service to Most Tariffs for ChatGPT, Netflix and Other Foreign Platforms

MTS has broadened availability of its Global Access service, which enables subscribers to reach ChatGPT, Claude, Netflix, Spotify and similar overseas platforms without using a VPN. The option is now offered on the majority of current and archived tariff plans, with the exception of Membrana, MTS Junior and MTS Junior+. It remains incompatible with Membrana, Safe Childhood and Safe Internet add-ons. Global Access functions exclusively over the MTS mobile network and requires no additional applications. Supported platforms also include Strava and Ticketmaster. The service is positioned for resources unavailable in Russia but not blocked by Roskomnadzor. New users receive seven free days, after which the monthly fee is 249 rubles, while TOP and TOP+ tariffs include it at no extra cost.

AntiMalware•Other

Yandex Restores Access to 99.55% of Yandex Disk User Data After Service Disruption

Yandex has restored access to 99.55% of user data stored on Yandex Disk following a major service outage. Core functions including automatic photo uploads from smartphones, downloading files and folders as archives, and video playback have been returned to normal operation. The company stated that recovery work is still underway and that inaccessible files do not necessarily mean permanent data loss. Users experiencing issues with specific files are advised to contact Yandex Disk technical support. Yandex is also redistributing computing resources across additional locations in various Russian regions to improve stability and fault tolerance. The number of these locations continues to grow, although no timeline has been provided for full restoration of the remaining data.

AntiMalware•Other

Survey Shows 42% of Organizations Unify Multi-Vendor Security Tools into Single Protection Contour

A live AM Live broadcast on cybersecurity ecosystems revealed that 42% of participants have already combined solutions from multiple vendors into one unified security contour. Another 23% reported partial integration of tools, while 24% keep their protections operating independently and only 11% rely exclusively on a single vendor. Panelists emphasized the need for clear responsibility assignment, seamless data exchange, and formation of shared security context across products. Key selection criteria for ecosystems included breadth of product lines for 32% of viewers and discounts or bonuses for 28%. Experts advised practical testing of interoperability and evaluation of total cost of ownership before committing to any model. Service provider responsibilities for integration, SLA compliance, and outcomes must be defined in advance, according to CURATOR director Edgar Mikaelyan. After the session, 32% of attendees stated plans to launch or expand a security ecosystem project.