Re: # of Signalling Processes
"Lee Dryburgh" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <[email protected]> |
Quick questions - have you read about n+k redundancy in the specs? Are you familiar with processes (in the UNIX sense, child processes, daemon Etc.)? I have no idea why you think the RFCs should be stating limits on the number of software processes that you spawn. Regards Lee On 09/05/07, Ilie Glib <[email protected]> wrote: > Hello Folks, > > SIGTRAN protocols provide support for systems redundancy and scalability by implementing the concept of signalling processes (SGP, ASP, IPSP) and TMT. > > Could you please share your view on the minimum number of signalling processes per logical entity (AS or SG) that the SIGTRAN signalling processes MUST support. > > I am after answers to very simple questions like > > 1. How many SGPs shall a standard ASP support per SG? > 2. How many SGs shall a standard ASP support per SS7 destination? > 3. How many ASPs shall an SGP/SG support per AS? > 4. How many remote signaling processes per logical entity (SG/AS) have to be supported to comply with SIGTRAN RFCs? > > I would expect that SIGTRAN RFCs provide answers to the questions above. However, to my knowledge, none of the RFCs puts any limit on the number of redundant signalling processes. In my view this may result in interoperability problems and traffic disturbances. > > 5. What are the corresponding capabilities of products from main market players? > > These questions make sense almost for all user adaptation layers and traffic mode types. > > > Thank you in advance for your help > > -- > Ilie > > > _______________________________________________ > Sigtran mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/sigtran > >