Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

mynameisjuan

Member
  • Content Count

    3,969
  • Joined

  • Last visited

Awards

This user doesn't have any awards

About mynameisjuan

  • Title
    Veteran

Profile Information

  • Interests
    ISP Network Engineer
  • Occupation
    ISP Network Engineer

Recent Profile Visitors

2,299 profile views
  1.  Im not trying to bother you or spam my thread, but you haven't replied to my latency spikes thread after i provided a reply and the things you asked from me, im really desperate for help. thank you.

  2. 1. Many people here are posting their latency but its dependent on the location of the endpoint and distance to it. 30ms on average for sites or gaming is not bad, 30ms to your ISPs gateway, then its on the higher side. But it varies based on where you are connecting to. 2. DSL (ADSL/VDSL) actually has lower latency then fiber. Signal propagates faster through copper then it does fiber and ATM cells lacking inter-frame gaps means less latency. This of course is minimal, especially in the real world. The problem is since copper is trash, means DSL and COAX to an extent require inter
  3. 1 - What are your speeds? 2 - Are the spikes consistent? across games or just a single one time between spikes time of day another device is streaming, uploading photos (cell), etc. Port forwarding has no effect on latency and I would undo those rules added. The 4011 can basically handle anything you throw at it so at this time that can be taken out of the equation. Mikrotik will give you all the information you might need to troubleshoot. Login to the web interface, since you did the quick setup its 192.168.88.1 and do the following:
  4. If they are connected via a 10g switch which is left defaulted, they would be in the same L2 domain so they can communicate directly with each other. Else, If the PCs are directly connected and their second ports are connected to the 1gig switch you need to configure a separate subnet in order for Windows to know which interface to send traffic out. Also in your first post, the "LAN" ports on consumer routers are bound to a switch chip which means as long as long as the devices are within the same subnet, it will have no performance hit on the router as the router's CPU is not hand
  5. Might seem arbitrary but it should include CPU. Unlike enterprise gear, consumer routers typically have a basic switch chip (ASIC) and do all routing, firewall, services, etc. in software only achieving better performance using kernel level routing such as fasttrack. So technically there is really no router/firewall per say in consumer equipment as its just handled by software. Far from dumb. What separated a hub from a switch was its smarts in learning and forwarding traffic. Its all done at the ASIC level but what might seem dumb is actually not. Its referred to
  6. Its confusing because RouterOS allows you low level configuration, no different than any other enterprise CLI hierarchy and if you could see under the hood for Meraki and Unify, the configuration would look similar. Its just all hidden to you and automatically checks the hidden boxes that make it a smoother experience. For me, I rather know what my hardware is exactly doing but that doesn't mean it cannot be a pain point. Also a controller is not necessary. Most issues almost always revolve around Country band being incorrect, example, if you are in the US, its need to be set to un
  7. Past and current work place (both ISPs) have gone all SM. Price difference of SFPs and fiber has gotten so close, the cost of mismanaged inventory; extra spares to cover both MM/SM SFPs and fiber patches; labor cost due to time by techs grabbing the wrong optic or fiber or re-running from MM to SM; multiple inter-bay panels; etc, it basically equals out or is cheaper in the long run.
  8. I don't think you realize how malleable fiber is and its casing. It can stretch and retract up to a point but that is smaller than the dia of a pencil. Stretching is how fiber is made. Again arcs are not the problem, bends are and wrapping it around a dia equivalent to a pencil does not introduce a bend. If you are worried about the plastic cracking, unless you are dealing with un-shielded fiber that has been baking in the sun for some time, not going to happen without some serious pulling or fast kinks. Goes with the former above. Best practices are not always based on hard limits
  9. That is just best practice. SM can easily be wrapped around a pencil without issues. Its done in the field by techs when working with live fiber in the many instances of lack of labeling, documentation or poorly managed. Every two wraps tend to give -2db of loss so you can monitor ports on the blade for loss without disrupting customer traffic and common. MM is about the same. It does not damage the fiber, just introducing reflection. Bends, not arcs, are more of a concern
  10. Multigig is the standard now for most deployments. The extra cost for 10g switches/routers as well as NICs is not worth it, with multigig trickling in to the built in NICs now. Also the cost to re-run the cabling if Cat5e (which can do 10g up to 30m) is not cheap depending on the building layout or not allowed to depending on the lease. Unless you can see regular saturation at a gig, its a waste to upgrade for "future proofing" or why not. LTT is the definition of the type of customer that needs high throughput to the host. Businesses even today barely use more than a few megs and
  11. This is the reasoning behind my point of why SM is becoming the primary and only option for many enterprises. Even inter-rack connections, the less cabling that needs to be replaced and instead can just need optics swapped eases migration especially at scale. When it comes to intra-rack connections this becomes especially important to not have to re-run fiber. There are many reasons where moving to SM only from a management, cost and inventory perspective make much more sense regardless of if MM/DAC just work. - Inventory: the need to have extra spares from SM/MM patches of mu
  12. Strain is due to cable stiffness and weight. Neither of which apply to fiber patches and most the time is due to person doing the cabling Pads? You mean attenuators? You do know you can run 20km and some 40km optics with 1ft patches right? SM 10km optics are no problem for short runs. Like it or not but the enterprise view on MM is shifting. Old and doing for a long time =/= always correct
  13. Fiber is not as fragile as they are made out to be. No 90s, don't pinch and don't pull from the collar are pretty much the only rules and I have seen some pretty mangled patches that work flawlessly when hit with the OTDR. But people hear glass and refuse to touch it.
  14. Should be a termination for whoever made that decision. Working with and around even a handful of DACs is a nightmare and from a support standpoint with their failure rates, even more so. There is a reason why SM optics are becoming the only option in enterprise as companies are ditching MM and DAC as SM cost difference diminishes. No bulk, no replacing the entire DAC, no replacing MM runs when upgrading past what MM can do, patch cables are cheap if a kink occurs, less heat, less power... Yeah I can back up your hatred for DACs but I'm throwing MM in the same pile.
  15. He specifically states "there is more processing involved in the switch side of things" which is not true. As far as less cooling, the SFP and SFP cage is the cooling with air being pulled in in and around them to dissipate the heat. There is actually more cooling.
×