As a Wide Area Network (WAN), the circuit provided by telecom backhaul between two endpoints—whether it’s point-to-point between two sites (EVPL, SDH) or customer site to provider PE (Internet, IPVPN, VPLS, etc.)—should be connected to the provider’s equipment or router devices to deliver the service. If you’re referring to dark fiber in a limited area… um… okay, next.
How do you verify the circuit service? Check your site router configuration? Check your IP routing?
The basic mindset: I believe we should start by checking the cabling. Yes, Layer 1, isn’t it?
If your port is UP and able to send and receive packets, WELL, at least confirm both endpoint IP addresses and perform a ping test. (Yes, a PING test—please don’t tell me you don’t know what PING is.)
PIC from #Google
From past experience, field engineers often argue that the device configuration is incorrect, but guess what? The issue ends up being the WRONG port connected.
Therefore, HOW IMPORTANT IS PHOTO CAPTURE!!!!!!!
What if the ping fails? Yes, it happens—cable quality issues, loose connectors, poor signaling, etc.
Have you ever checked the DUPLEX setting????????????? Confirm both ends have the SAME duplex setting!!
PIC from Cisco Press
Then you’ll mention bandwidth: “Speedtest.com, huh? Why can’t I get full bandwidth?!”
Please understand: we cannot guarantee a test server will allocate all resources for your test. The Internet is unmanaged, and you need to be aware of overhead and your device’s processing power. Do you really think your mobile can hit 2Gbps over Wi-Fi, bro?
For standard testing, running tests between the client site and the ISP backhaul provides a great reference for your service quality—this is typically done during installation.
But anyway… PLEASE confirm the cabling is correct before spending too much time checking the configuration. Start with Layer 1 first!
#circuit #physical #cabling #ISP #provider #Internet #EVPL #IPLC #IPVPN #P2P #IP #testing #ping #bandwidth #speedtest #traffic #packetlost #duplexing #router #WIFI
