Thanks. Could someone confirm this? Can policy be applied on physical bundle members at all ?
Also, what would be the closest thing to "show policy-map interface Bundle-Ether X" but for physical member interface? Since there's not policy on member? I have couple of commands but that's not exactly it: show qos interface bundle-Ether x input member texxx show qos-ea interface bundle-Ether x output member texxx show qos summary interface bundle-Ether x output member texxx Regards On Thu, Oct 2, 2014 at 2:50 PM, Tom Hill <[email protected]> wrote: > On 02/10/14 13:32, redscorpion69 wrote: > > I believe management requested since one of the servers is reading > > bandwidth allocation from bundle port, rather than aggregate info from > > all individual ports. Something stupid along those lines. > > Fixing management-crazy with config-crazy is... Crazy :) > > > Nonetheless, let's say we're configuring policy on physical member. Is > > there a reason why I can't apply it? Can it be applied ? > > Someone may correct me, but I suspect not - the assumption of a bundle > (or any other sort of LACP LAG) is that all of the interfaces there-in > are equal. > > If you have unequal interfaces, Bad Things would happen. So I imagine > you're not allowed to add that configuration in order to protect you > from yourself (or your management). :) > > -- > Tom > > _______________________________________________ > 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/
