01-12-2018 05:26 AM
Can anybody tell me what doest the er_zone_miss counter shows?
In the help I got the following explanation:
er_zone_miss , er_lun_zone_miss
The number of frames discarded due to hard zoning miss
or LUN zoning miss. If Rx port hard zoning is enabled,
frames will be discarded at the Rx port. If TX port
hard zoning is enabled, frames will be discarded at the
TX port. If both RX and TX port hard zoning is enabled,
frames will be discarded at the RX port. (LUN zoning is
currently not supported.)
But what does the hard zoning means? In my case the port which get this counter increased is a N_PORT (a port where an AG switch is connected).
Few hours after counter reaseat I got the following:
admin> portstatsshow 1/22
stat_wtx 588476020 4-byte words transmitted
stat_wrx 2511408128 4-byte words received
stat_ftx 130933445 Frames transmitted
stat_frx 134040754 Frames received
stat_c2_frx 0 Class 2 frames received
stat_c3_frx 134040754 Class 3 frames received
stat_lc_rx 0 Link control frames received
stat_mc_rx 0 Multicast frames received
stat_mc_to 0 Multicast timeouts
stat_mc_tx 0 Multicast frames transmitted
tim_rdy_pri 0 Time R_RDY high priority
tim_txcrd_z 41652 Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc 0- 3: 0 0 0 0
tim_txcrd_z_vc 4- 7: 41652 0 0 0
tim_txcrd_z_vc 8-11: 0 0 0 0
tim_txcrd_z_vc 12-15: 0 0 0 0
tim_latency_vc 0- 3: 1 1 1 1
tim_latency_vc 4- 7: 1 1 1 1
tim_latency_vc 8-11: 1 1 1 1
tim_latency_vc 12-15: 1 1 1 1
fec_cor_detected 0 Count of blocks that were corrected by FEC
fec_uncor_detected 0 Count of blocks that were left uncorrected by FEC
er_enc_in 0 Encoding errors inside of frames
er_crc 0 Frames with CRC errors
er_trunc 0 Frames shorter than minimum
er_toolong 0 Frames longer than maximum
er_bad_eof 0 Frames with bad end-of-frame
er_enc_out 0 Encoding error outside of frames
er_bad_os 0 Invalid ordered set
er_pcs_blk 0 PCS block errors
er_rx_c3_timeout 0 Class 3 receive frames discarded due to timeout
er_tx_c3_timeout 0 Class 3 transmit frames discarded due to timeout
er_unroutable 0 Frames that are unroutable
er_unreachable 0 Frames with unreachable destination
er_other_discard 0 Other discards
er_type1_miss 0 frames with FTB type 1 miss
er_type2_miss 0 frames with FTB type 2 miss
er_type6_miss 0 frames with FTB type 6 miss
er_zone_miss 24 frames with hard zoning miss
er_lun_zone_miss 0 frames with LUN zoning miss
er_crc_good_eof 0 Crc error with good eof
er_inv_arb 0 Invalid ARB
er_single_credit_loss 0 Single vcrdy/frame loss on link
er_multi_credit_loss 0 Multiple vcrdy/frame loss on link
phy_stats_clear_ts 01-12-2018 CET Fri 07:55:34 Timestamp of phy_port stats clear
lgc_stats_clear_ts 01-12-2018 CET Fri 07:55:34 Timestamp of lgc_port stats clear
Also, in the past there was an error against this port:
admin> errdump |grep "1/22"
2018/01/11-21:19:58, [MAPS-1002], 8502, SLOT 7 | FID 128, ERROR, sharnlgesan02, F-Port 1/22, Condition=ALL_F_PORTS(C3TXTO/hour>10), Current Value:[C3TXTO,25 Timeouts], RuleName=fw_cust_ALL_F_PORTSC3TXTO_AH_10, Dashboard Category=Port Health.
Solved! Go to Solution.
01-12-2018 06:08 AM
Please find attached a Knowledge base article that can provide you some guidance.
01-12-2018 06:28 AM
In your case, I do not believe the increments of C3TXTO and er_zone_miss at different point of time have a relationship.
01-13-2018 02:30 AM
Interesting article about the NPIV issue, thanks!
From my experience, er_zone_miss might be triggered in the following situations:
1. The target is not zoned to the initiator since some time, but the initiator still remembers the presence of the target and periodically tries to poll for its presence somehow. I've seen AIX and HPUX hosts doing this. But this usually comes together with "other discards".
2. A device experienced some internal issue and decided to perform some sort of self reset on its FC port. Incoming traffic to that device could show a short burst of er_zone_miss increase.