Advertisment: Broadband via satellite
Advertisment: Worldwide satellite services from Ground Control Company

www.satsig.net

Satellite Internet Forum.

Welcome, Guest.        Forum rules.
      Home            Login            Register          
Pages: 1

Re: VSAT troubleshooting/Bandwidth utilization iss

(Read 2974 times)
imepals
Member
★★
Offline



Posts: 30
May 22nd, 2007 at 11:17am  
Thanks for all your response to this post. Maxim Usatov pls do send me the PEP trial. I have also considered your suggestions and but would like to know how to calculate the capacity if satellite you need for a given number of PCs. Over here like i stated before we have about 70pcs, 50 of which can be online simultaneously.

Another problem i have ji=ust noticed is the high latency on my network. a roundtrip delay returns at >3000ms sometimes 4000ms.

An investigation revealed that a ping from my fast-ethernet port to the serial port of my boarder router returns at >1000ms! These 2 interfaces are on the same router (cisco 3745 router).

Also in the past week i have observed from my Cacti software (a bandwidth utilization monitoring tool) that i am transmitting at over 307kpbs (i have not upgraded to this service rate) whereas i am subscribed for a bandwidth of 256/256kpbs. I have reported this to the service provider but nothing has been done about it and besides the latency is still high.

On the DVB, is there a way i can determine the overbooking or oversubscription rate from the DVB box or is it only the provider that has access to such information? And what’s the main difference between DVB/SCPC and SCPC/SCPC?

Pinging yahoo.com [216.109.112.135] with 32 bytes of data

Reply from 216.109.112.135: bytes=32 time=3989ms TTL=53
Reply from 216.109.112.135: bytes=32 time=3960ms TTL=53
Reply from 216.109.112.135: bytes=32 time=4049ms TTL=53
Reply from 216.109.112.135: bytes=32 time=4288ms TTL=53
Request timed out.
Reply from 216.109.112.135: bytes=32 time=4332ms TTL=54
Request timed out.
Reply from 216.109.112.135: bytes=32 time=4274ms TTL=53
Request timed out.
Reply from 216.109.112.135: bytes=32 time=4094ms TTL=54
Reply from 216.109.112.135: bytes=32 time=3859ms TTL=54
Reply from 216.109.112.135: bytes=32 time=3658ms TTL=54
Reply from 216.109.112.135: bytes=32 time=3837ms TTL=53
Reply from 216.109.112.135: bytes=32 time=3771ms TTL=53
Reply from 216.109.112.135: bytes=32 time=4057ms TTL=53
Reply from 216.109.112.135: bytes=32 time=4157ms TTL=53
Reply from 216.109.112.135: bytes=32 time=3816ms TTL=54
Reply from 216.109.112.135: bytes=32 time=4015ms TTL=54
Request timed out.
Reply from 216.109.112.135: bytes=32 time=4127ms TTL=53

Ping statistics for 216.109.112.135:
    Packets: Sent = 20, Received = 16, Lost = 4 (20% loss
Approximate round trip times in milli-seconds:
    Minimum = 3658ms, Maximum = 4332ms, Average = 4017ms

Expecting your professional advise as usual.
Back to top
 
 
IP Logged
 
Maxim Usatov
Senior Member
★★★
Offline



Posts: 116
Czech Republic
Reply #1 - May 23rd, 2007 at 8:27am  
I will send you an e-mail with the way to get PEP implemented. For a network with 50 simultaneously online PCs I would recommend no less than 512/128 or 512/256 CIR, if all bandwidth is dedicated. Of course I don't know what applications you use there. If I'd knew that probably I'd recommend some burstable quota as SCPC/SCPC or DVB/SCPC could be really expensive and inefficient in some cases.

I will provide you with more information by e-mail along with the PEP trial.
Back to top
 
WWW  
IP Logged
 
Pages: 1