Hi, That is what everyone is telling me. That its just for routing protocols. However, page 12 in the Cisco QoS book tells me this:
"Some QoS tools refer to interface bandwidth, which is defined with the bandwidth command. Engineers should consider bandwidth defaults when enabling QoS features. On serial interface on Cisco routers, the default bandwidth setting is T1 speed - regardless of the actual bandwidth." page 302: "CBWFQ provides several variations of how to configure the bandwidth reserved for each queue. For instance, the bandwidth 64 class subcommand reserves 64kbps of bandwidth, regardless of the bandwidth setting on interface. The Bandwidth percent 25 class subcommand would also reserve 64 kbps for a class if the interface bandwidth had been set to 256kbps, using the bandwidth 256 interface subcommand." >From that is seems crystal clear the the bandwidth statement on the interface IS used for QoS. And this back to my question, should I set the bandwidth on the Interface to match the shaped value? Thanks! On Thu, Jul 1, 2010 at 5:30 PM, Benjamin Lovell <[email protected]> wrote: > The bandwidth statement just alters the EIGRP bandwidth metric. So if you > are using EIGRP and want it to reflect the true bandwidth of the link, then > yes. Else it does not matter. > > -Ben > > > On Jul 1, 2010, at 10:43 AM, Roger Wiklund wrote: > > Hi >> >> When using a physical interface of 100meg with an outbound policy-map that >> shapes all traffic to 30meg, should the bandwidth of the physical >> interface >> reflect the shaped value? >> >> The policy-map is also using remaining bandwidth percentage x for >> different >> classes. >> >> I would assume you want the percentage level to calculate based on the >> 30meg, rather than on the 100meg right? >> >> Thanks! >> >> Regards >> Roger >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
