The QoS-policy will be set on a router in a branch-office. The servers are in our central office.
The routers connect to a central router of our provider, and are bundled together in a E1-connection to our main router. Therefore, configuration on the main router per branch-office is very difficult and that's why I want to use an ingress-policy.
An ingess policy that polices traffic will get you what you want in terms of limiting the traffic to the remote hosts. However, you need to consider if that is wise. What you are doing is carrying all this traffic across potentially expensive WAN links only to drop it at the destination. Does that really help you ? I really don't think so.. Say you had just the one E1 and at one point in time, it had 1900 kbps of HTTP traffic and 50 kbps of Citrix. Now, if you had an ingress policer at the more site which drop half of the HTTP traffic, your Citrix won't suddenly increase, since that is being controlled at egress.
So you really do need to apply this policy outbound at your host site.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...