<div>
Port BW is the overall available BW of that interface, shaping can be performed on several classes of traffic which are a subset of all traffic that passes through that interface. <br />
<br />
Sound QOS/COS policies reserve BW for non defined traffic flows that do not fit COS profiles, for example best effort, what happens if your interface receives traffic flows not accounted for? You must allow for some default classes, you see?<br />
<br />
harbor235 ;}
</div>


Port BW is the overall available BW of that interface, shaping can be performed on several classes of traffic which are a subset of all traffic that passes through that interface.

Sound QOS/COS policies reserve BW for non defined traffic flows that do not fit COS profiles, for example best effort, what happens if your interface receives traffic flows not accounted for? You must allow for some default classes, you see?

harbor235 ;}

<div>
Please eloberate on &quot;if your interface receives traffic flows not accounted for ?&quot;<br />
<br />
How much should this default traffic be??<br />
<br />
Harbour, Yo Da maan...
</div>


Please eloberate on "if your interface receives traffic flows not accounted for ?"

How much should this default traffic be??

Harbour, Yo Da maan...

<div>
<div class="content wysiwyg-content">
I am looking at the QoS shaping for incoming traffic, and need to know why is the 'shape average &lt;<b>BW</b>&gt;' always less than port-bW? (BW configured is always less than the port BW).
</div>
</div>


I am looking at the QoS shaping for incoming traffic, and need to know why is the 'shape average <BW>' always less than port-bW? (BW configured is always less than the port BW).

QoS shaping

Networking hardware includes the physical devices facilitating the use of a computer network. Typically, networking hardware includes gateways, routers, network bridges, modems, wireless access points, networking cables, line drivers, switches, hubs, and repeaters. But it also includes hybrid network devices such as multilayer switches, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, ISDN terminal adapters and other related hardware.

Networking Hardware-Other

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.

Network Management

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.