Input queue: 0/75/4112322298/0 (size/max/drops/flushes); Total output drops: 0
The provider performed (sigh) another testto isolate the problem (again), but this time up to their router. We found out that outgoing is okay, only incoming has problem. We also isolated that the problem is most likely between MUX and Router at the provider building. Which means the UTP (or Fibre) Cable that connects the Provider Router to the MUX.
It could either be faulty wiring cable at the provider building or interference if its copper.
I have a hunched a month ago when consolidating my test result and provider technician test result that the problem is most likely at the provider end (after the MUX).
In most cases, troubleshooting doesn't need special tools. Isolation using simple freely available tools will bring you nearer to the source of the problem and would be able to concentrate the tests to pinpoint the root of the problem.
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...