![]() Running this command on eth1/5 shows the following: Polling this MIB for the switch in question shows a counter value of 11717716 on eth1/5. Reason for discarding such a packet could be to free The number of outbound packets which were chosen toīe discarded even though no errors had been detected ![]() I have found the source of the discards by using the Toolset MIB browser and polling the following MIB for this interface (note this is a 32 bit counter, while the interface utilization statistics are being polled using 64 bit counters): 0 0Įth1/5: lif_blk(pi) 0x97657bc foo vif_id_alloc_bmp 0x99b4aa4Įth1/5: cfg_lif_blk_size 0 lif_blk_base(pi) 0 lif_blk_size(pi) 4096Įth1/5: if_flags 0x0 num_sub_lif_tbls 0 Num HIFs pinned 0Įth1/5: sat lif_blk tbl base 1, size 4095Įth1/5: max_hifpc_mbrs 0, max_hif_ports 0Įth1/5: storm control (u: 0.10 m: 0.10 b: 0.10)Įth1/5 pd: slot 0 logical port num 4 slot_asic_num 0 global_asic_num 0 fwm_inst 4 fc 0Įth1/5 pd: pif_type 'data eth'(1) hw_present 1 port map idx 9Įth1/5 pd: fabric a info: voq 0-7 port_id 92 connected 1 up 1Įth1/5 pd: fabric b info: voq 0-7 port_id 92 connected 1 up 1Įth1/5 pd: subported 0 primary 1 atherton 0Įth1/5 pd: sup_src_dst_if 7 lif_blk -1-1Įth1/5 pd: policer info: uc (sel 14) mc (sel 13) bc (sel 12)Įth1/5 pd: tx stats: bytes 32426201560732 frames 5950038156 discard 0 drop 0Įth1/5 pd: rx stats: bytes 19582331248970 frames 3277001563 discard 0 drop 45722Įth1/5 pd fcoe: tx stats: bytes 0 frames 0 discard 0 drop 0Įth1/5 pd fcoe: rx stats: bytes 0 frames 0 discard 0 drop 0Įth1/5 pd cdce_addr: switchid 1086 sub-switchid 0, endnodeid 0Įth1/5 pd cdce_addr: Mcast 0, locally-adm 1, OutOfOrder/don't learn 0Įth1/5 pd cdce_addr: localid 15, pbp_idx 0 ![]() ![]() Input rate 25.88 Mbps, 528 pps output rate 41.46 Mbps, 970 ppsģ275948875 unicast packets 748892 multicast packets 192869 broadcast packetsģ276890636 input packets 19581540017667 bytesĢ488321762 jumbo packets 8212622 storm suppression bytesĠ input error 0 short frame 0 overrun 0 underrun 0 ignoredĠ watchdog 0 bad etype drop 0 bad proto drop 0 if down dropĥ949444361 unicast packets 210888 multicast packets 86652 broadcast packetsĥ949741901 output packets 32329239916867 bytesĠ output errors 0 collision 0 deferred 0 late collisionĠ lost carrier 0 no carrier 0 babble 0 output discardĭump pif info: ifindex 0x1a004000 dump_all 0 verbose 1Įth1/5: slot 0 port 4 state 0圆 pi_if 0x98e293c fwimpd ctx 0x899f18cĮth1/5: oper_mode 0x100000 rcvd_rbind: NoĮth1/5: iftype 0x1 encap 0x1 bound_if? N #lifs 1 fwimpd ctx (nil)Įth1/5: unique_fcf_mac? N fcf_mac 0 0. Last clearing of "show interface" counters neverģ0 seconds input rate 29066544 bits/sec, 638 packets/secģ0 seconds output rate 28721848 bits/sec, 774 packets/sec Input flow-control is off, output flow-control is off I'm beginning to question the accuracy of the statistics being reported by NPM ?!? Logging onto the switch, I see no evidence of any type of transmit discards on the interface in question. The discards are not continuous, rather they occur sporadically according to Orion. Orion NPM 10.3 is reporting transmit discards on a lightly used10G ethernet interface ~ 1 million/hr on a Nexus 5596 switch - System version: 5.2(1)N1(3).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |