appropriate service levels

15 pts.
Okay, here is a 4 part question I have. I thought I would include all 4 in one so I would not have to come back and ask again in case I was wrong in my understanding..... How can appropriate service levels be established for a network in the areas of: a. Availability b. Reliability c. Response time d. Throughput I do understand what they all are but I need to understand how to apply them: Availability is defined as the amount of time a computer or telephone system is available for processing transactions or telephone calls. Reliability is a measure of how dependable a system is once you actually use it. Reliability accounts for the time that it will take the component, part or system to fail while it is operating. It does not reflect how long it will take to get the unit under repair back into working condition. Response time is the time it takes a system to react to a given input. In voice recognition, response time typically refers to the amount of time required for a word to be recognized once the end of the word is detected. Throughput is the actual amount of useful and non-redundant information which is transmitted or processed. Throughput is the end result of a data call. The amount of data moved successfully from one place to another in a given period. Thanks again in advance......

Answer Wiki

Thanks. We'll let you know when a new response is added.

Nice question..
I havn’t sufficient time now to explain in details, little bit busy in It budget.

Let me know you are a experience man or fresher, If u r experience and spl. in industrial area and in networking then i think you definatly know 50% of your questions answer. I will explain it one by one..

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Khilving
    The first step is determining what is manageable. Network means different things to different people, so keep any SLA limited to what is under your control. Next is defining what is measurable. An SLA becomes an ongoing requirement, so you need to have the tools in place to obtain and report the metrics. Once you know what, baseline the performance. This is done to establish what is attainable. Finally, make the SLA relevant to the customer. This means putting the SLA in the context and terminology of the customer's business objectives. Keep in mind that most users still consider network as everything that happens once an enter key is pressed. It is often useful to report on the status of things outside of your control.
    0 pointsBadges:
  • Sswar111
    Hi there, I think this book might help, it was a very helpful learning aid for me.. Data Communication and Networking, BY: Forouzan
    0 pointsBadges:
  • Paul144hart
    Since you are looking for numbers, you need to get the information on the individual components and calculate availablility and reliability. Availability will depend more on your redundancy scheme, going from N+0 (none) to N+2 for multiple servers (you question related to computers/server, not just networks). Response time with the example of voice recognition doesn't apply to networks (I have the last five years with large telephony systems and ASR, and response is usually from the user's point of view when they stop, but vendors go from end of energy detection). Throughput can be estimated, but look for the weakest link, as that will be your limitation. Never use the stated speed (i.e. 100mb won't give you 100mb). A good rule of thumb is leave out 15%. Testing will be real way to find out. A good source on info is the O-Reilly book on large network design. Since you mentioned telephony, go to and look for reliability info as pertain to your SLA. There is always bellcore too. -Paul
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: