Re: RFC 4666 on Signaling System 7(SS7)Message TransferPart 3 (MTP3) - User Adaptation Layer (M3UA)

"Brian F. G. Bidulock" <[email protected]>
Newsgroups gmane.ietf.sigtran
Organization http://www.openss7.org/
Message-ID <[email protected]>
Lincoln,

My ISP powers their DSLAMs off of commercial power.  (And they
are also the incumbent phone company.)

There are in fact many maintenance reasons for withdrawing traffic
from a node (e.g. SGP).  Maintenance.  Software upgrade.  Network
reconfiguration.  SS7 handles these through the management and
inhibition of signalling links using the same set of procedures 
that are used for failure.  The management reasons do not include
failure.

In the draft, I highlight the race condition between two SGP when
traffic is switched between them.  Without these procedures it is
unlikely that one could switch traffic on, say, an high capacity
HLR, without risking either message missequencing from prematurely
divering traffic to the alternate SGP, or risking widespread
transaction failure by delaying the traffic too long.  A protocol
approach can switch traffic almost instantaneously, and with little
risk.

Just taking one ASP in the pool down for software upgraed on a big
HLR could cause havoc in the network.  As things stand, you better
do it at 3:00 am.

--brian

-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.