On Mon, Apr 05, 2010 at 04:41:25PM +0400, Alexandre Snarskii wrote: > That's from EX-3200 running 9.3R4.4, the same error still present in 9.3S7.2. > > Does anybody knows if it fixed in more recent JunOS ?
9.6R3 shows the same behavior on this EX-4200:
rvandegr...@switch> show interfaces ge-0/0/0 extensive
Physical interface: ge-0/0/0, Enabled, Physical link is Up
Interface index: 132, SNMP ifIndex: 215, Generation: 135
...
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Collisions: 0, Aged packets:
0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 4 in use
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 0 19050048 23076148
rvandegr...@malaclypse:~$ snmpget -v 2c -c hmscomm switch ifOutDiscards.215
IF-MIB::ifOutDiscards.215 = Counter32: 0
rvandegr...@malaclypse:~$ snmpget -v 2c -c hmscomm switch ifOutErrors.215
IF-MIB::ifOutErrors.215 = Counter32: 0
Ross
--
Ross Vandegrift
[email protected]
"If the fight gets hot, the songs get hotter. If the going gets tough,
the songs get tougher."
--Woody Guthrie
signature.asc
Description: Digital signature
_______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
