FYI: Cable break in JHB

thanks ocleroux, I did see the thread and posted on it. I started this thread with a more descriptive subject. I was hoping for more info as it seems surprising a cable break can cause a nationwide outage as being reported in the following threads:

http://mybroadband.co.za/vb/showthread.php/336116-FYI-Cable-break-in-JHB
http://mybroadband.co.za/vb/showthr...lse-got-data-connection-problems-in-Cape-Town
http://mybroadband.co.za/vb/showthread.php/336130-No-Vodacom-signal-in-Midrand

I cannot believe that single cable break can cause a problem as widespread as this.
 
Network still fidgety on my side.

I have full HSPDA access for 5 minutes and then all of a sudden no connection at all. Still struggling to make calls with me cellphone though.
 
Electron1 said:
thanks ocleroux, I did see the thread and posted on it. I started this thread with a more descriptive subject. I was hoping for more info as it seems surprising a cable break can cause a nationwide outage as being reported in the following threads:

http://mybroadband.co.za/vb/showthread.php/336116-FYI-Cable-break-in-JHB
http://mybroadband.co.za/vb/showthr...lse-got-data-connection-problems-in-Cape-Town
http://mybroadband.co.za/vb/showthread.php/336130-No-Vodacom-signal-in-Midrand

I cannot believe that single cable break can cause a problem as widespread as this.
Click to expand...

Was not the cable-break per se that caused the problems, but it triggered a snow-ball effect and then helped to compound the issues.
 
Still having network issues - have full signal and can message on BIS but SMS's to Vodacom numbers fail and when I try to call out it just says "Call failed" - guess they're still busy with it...
 
jannievanzyl said:
Was not the cable-break per se that caused the problems, but it triggered a snow-ball effect and then helped to compound the issues.
Click to expand...

I would be fasinated to know techincally what happened today. Seems like it affected smartie phones more than other phones, 3G maybe?
in Durban I had no connection from maybe 6am. till I rebooted my phone at 10am then all was good but then SMSs were a complete balls up to put it politely, duplicates and late, very late delivery.

Amazing how we rely on such a service and so when it breaks our little worlds crumble :)

Any explainations for it?
 
skydog said:
I would be fasinated to know techincally what happened today. Seems like it affected smartie phones more than other phones, 3G maybe?
in Durban I had no connection from maybe 6am. till I rebooted my phone at 10am then all was good but then SMSs were a complete balls up to put it politely, duplicates and late, very late delivery.

Amazing how we rely on such a service and so when it breaks our little worlds crumble :)

Any explainations for it?
Click to expand...
http://mybroadband.co.za/vb/showthr...20-May-2011)?p=6162952&viewfull=1#post6162952

http://en.wikipedia.org/wiki/Spanning_Tree_Protocol
 
Last edited:
MickeyD said:
http://mybroadband.co.za/vb/showthr...20-May-2011)?p=6162952&viewfull=1#post6162952

http://en.wikipedia.org/wiki/Spanning_Tree_Protocol
Click to expand...

No, spanning tree is a layer 2 protocol used in enterprise networks and hopefully not in big red's network.

STP refers to http://en.wikipedia.org/wiki/Signal_Transfer_Point

I posted a theory here: http://mybroadband.co.za/vb/showthr...20-May-2011)?p=6164452&viewfull=1#post6164452 but there has been no response.

Since it was a fibre break the assumption is that there has been some engineering to encapsulate the TDM network over IP. This implies that the network is based on a legacy 2G set of protocols.

I haven't a clue who is the STP vendor involved but since Huawei is used over at the big red I searched for information on their STP which directed me to this link http://www.huawei.com/publications/view.do?id=1780&cid=3982&pid=61
It says file not found but luckily Google has a cached copy (as late as 4th May) http://webcache.googleusercontent.c...l=za&client=firefox-a&source=www.google.co.za

Now the interesting bit from this url:
Five essues on IP-based signaling

It is acknowledged industry-wide that the following issues require carriers' attention prior to constructing IP-based signaling networks:

Independent signaling network

In a way that is unrelated to circuit connections, MAP and CAP signaling dominate mobile networks and the two are generally employed for mobile user location updates, route queries and intelligent network service operations. In terms of protocol stacks, whether MAP and CAP signaling is carried via TDM, ATM or IP protocol, the SCCP layer is always necessary. That is, MAP signaling and CAP signaling need the transmission function of the SCCP layer to transmit messages to destinations. In each 2G network, a major function of STP in the signaling network is GT translation and message transfer. In each 3GPP R4 network, the SCCP-based addressing mode remains unchanged, so the GT translation and message transfer functions remain essential.

Large-scale R4 networks demand independent STP equipment for MAP/CAP signaling bearing and transfer so as to reduce the number of signaling link sets and SCTP associations in the MSC/MSC Server. Future value-added services can therefore be flexibly supported. Multiple network elements are directly connected to a pair of STPs with large capacity, high performance in order to reduce transmission links, simplify network structure, reduce OPEX and ensure network expandability. Consequently, the hierarchical architecture is applicable to TDM, TDM-to-IP evolution and IP-based signaling networks. Carriers can choose to adopt a two or three-layered hierarchical architecture according to actual network condition.

Link-based protocols

SIGTRAN protocol stack includes the M3UA, M2PA, M2UA, SUA, and SCTP protocols. Different protocols can be selected according to link types when IP bearing is adopted to facilitate smooth upgrades for signaling networks.

M3UA is a 3GPP recommended SIGTRAN protocol that is adopted between terminal offices and the STP. It supports all existing mobile network protocols including BICC, ISUP, MAP and CAP, but it describes an implementation protocol mainly designed for SG applications. It is limited to being a one-hop signaling transfer or as an IP SP edge access protocol.

M2PA-based IP signaling links provide link-based signaling network management functions via MTP3. M2PA can be used as the SIGTRAN protocol between STPs that supports signaling link fault switching and enables competent network management and security.

Reliability processing

If either IP or TDM are used to bear signaling, then only the bearer layer and application protocols can be changed. Most signaling networks currently adopt dual-plane networking, and the same layer equipment is interconnected by at least two links. This reliability processing mechanism plays an important networking function, and the reliability of each signaling network can be further heightened by employing IP bearer network and SIGTRAN protocol stack features.

The IP bearer network adopts some redundancy design features such as dual uplinks and planes. VRRP, VGMP and HRP technologies can be employed to execute switching redundant structure switching, and APDP/BFD technologies can be utilized for fault detection.

In view of equipments, SCTP's multi-home feature can be used to improve reliability. This feature means for the same association, multiple IP addresses may be adopted at both the local and peer ends and guarantees layer-2 transmission reliability. Based on this feature, paths can be configured in different physical network segments, thus ensuring the reliability of IP bearer network links.

Solving error codes

Due to the characteristics of the IP bearer network and signaling services' transmission requirements, QoS remains an important factor underpinning SS7 signaling networks. In the TDM-based bearing mode, signaling messages are transmitted via dedicated networks. Therefore, the element affecting the bearer network QoS is error codes. An error code detection mechanism is defined into the MTP2 layer that can quickly detect error codes and implement message re-transmission and link switching to minimize losses. However, as the IP bearer network is a best-effort network, it is incapable of collecting delay, packet loss and jitter data. The SCTP protocol cannot, therefore, define physical layer requirements or quickly realize message retransmission and link switching. For each signaling network, high QoS must be guaranteed to offer users a holistic, high-grade service experience.

Similar as the above analysis, the QoS of SS7 signaling network can be guaranteed from the network aspect and the equipment aspect. Each bearer network must enable dedicated usage, light bearing and quality guarantee. Via quality guarantee in the IP bearer network, QoS needed in the service layer can be enabled. For example, MPLS VPN or light-bearing IP dedicated network can be used to avoid network congestions.

As equipments at both ends of IP links are on the transmission layer, the SCTP protocol can be used to improve QoS. The connection-oriented SCTP can ensure security and correctness in message transmission; it can also well control packet losses. The SCTP protocol can control and measure channel delays, which can meet the requirements for delay on the application layer. Equipment QoS can be improved via the flow control function on the service layer.

MSC server can analyze signaling messages according to service types and customer types. When it detects poor IP link quality, it preferentially guarantees the transmission of signaling messages of important services from important customers. The STP equipment in the signaling network can preferentially transmit important signaling messages according to carriers' requirements and message contents, including origination signaling point code, destination signaling point code, and message types.

In addition to QoS guarantees, the equipment lends itself to quantifying QoS, allowing carriers instant problem detection and an immediate awareness of signaling bearer quality. Just as the SCTP ensures reliable message transmission, the signaling transmission status of the SCTP can be used to judge the IP bearer network's QoS. An inferior QoS can increase SCTP message acknowledgement delays and the need for message retransmissions. By analyzing the two parameters - SCTP message acknowledgement delays and the number of message retransmission - the IP bearer network's QoS can be judged.

Ensuring broadband link performance

TDM-based SS7 signaling links are restricted by physical transmission rates. An ordinary link is 64Kbit/s, or 56Kbit/s in some networks, while high-speed rates are 2Mbit/s. When an IP-based SIGTRAN link is adopted, the theoretical bandwidth between the two ends can reach hundreds or thousands of megabits. However, given that the IP network is a best-effort network and that the bearer layer shares its bandwidth, the basis for ensuring broadband link performance rests with guaranteeing sufficient signaling message QoS. In this context, broadband link reference loads define another networking precondition.
Click to expand...

So I would conclude that my theory about insufficient QoS on the big red's network might have some merit?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X