Hi,,

I guess I would have to check with the telco and whether the link supplied
is 128k full duplex or 64k full duplex. Thanx for the info.

Regards
Naveen
-----Original Message-----
From: Lindahl, Carl [mailto:[EMAIL PROTECTED]
Sent: 10 February 2003 04:37
To: 'Naveen Sivenandan'; [EMAIL PROTECTED]
Subject: RE: [mrtg] Bandwidth Monitoring Total


What type of connection is this 128k connection? Most likely this is a full
duplex connection where you have 128k of bandwidth in each direction. So out
of 128k inbound you are using 100k. Outbound you have another 128k but only
using 40k of it.

Inbound, you are close to the link's max of 128k. I would personally
consider a link upgrade, but that is outside the scope of this, i.e. budget,
equipment, local loop installs, etc.

Carl




-----Original Message-----
From: Naveen Sivenandan [mailto:[EMAIL PROTECTED]
Sent: Monday, February 10, 2003 9:16 AM
To: [EMAIL PROTECTED]
Subject: [mrtg] Bandwidth Monitoring Total


Hi,,
 
I have a scenario wrt bandwidth monitoring and mrtg. I have the following
stats represented on MRTG based on 5 minute polling.
 
128K Diginet Link
1 hour interval stats represent ( 100k inbound and 40k outbound )
 
My total demand for bandwidth should indicate 140k. Does this mean that my
link is busy and would need to be upgraded. MRTG does not represent the
total line utilisation as compared to say Packeteer device. Hence my
question is what portion of the 128k link is busy.
 
Is it over utilised by using 140k (100+40) or the fact that 100 is inbound
and 40 is outbound, means I still have more space on the 128K pipe.
 
Your suggestions please.
Naveen

 

 


--
Unsubscribe mailto:[EMAIL PROTECTED]
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi

--
Unsubscribe mailto:[EMAIL PROTECTED]
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi

Reply via email to