On Thursday, 29 October, 2015 16:25, "Martin T" said:
> Where does this inconsistency come from? Is there a way to increase
> the amount of characters returned by NX-OS SNMP agent for interface
> descriptions?
Vanilla IOS has "snmp ifmib ifalias long" - you could check if
Hi All,
Can any share if a L2VPN ingress policing on a ME3600, is doing accounting at
L1 or L2 frame ?
(a) L2 Frame ( aka MEF service frame ) without the
"Inter-Frame Gap" and "Preamble & Start of Frame"
(b) L1 Frame ( aka 802.3 frame ) that is inclusive of
"Inter-Frame Gap" and
> I'd be inclined towards using policing in both directions. It's a maximum
> limit after all, same
> thing that happens when you run a physical interface to capacity.
Not quite. If you hit physical interface limit you have output queues that
behave like a shaper,
not like a policer.
Lukas
>Ok, cool. Thanks for getting me thinking a bit upstream...looks like it
>will really make my life easier. I need to do a bit more research on
>"policing" vs. "shaping". My first inclination is that I don't ever
>want to drop traffic in any direction in a co-lo environment so policing
>seems
Hi,
I have a Cisco Nexus 5548 switch with NX-OS version 6.0(2)N2(6) and it
allows one to insert 80 characters long interface descriptions:
Nexus5548(config-if)# description
Nexus5548(config-if)# description
On Thu, 2015-10-29 at 18:25 +0200, Martin T wrote:
> However, over SNMP it returns only the first 64 characters of this 80
> characters interface description:
[...]
> Where does this inconsistency come from? Is there a way to increase
> the amount of characters returned by NX-OS SNMP agent for