Skip to content

Conversation

@mjbear
Copy link
Collaborator

@mjbear mjbear commented Sep 27, 2025

resolves #2191

Match additional unmatched lines related to Fibre Channel.

During past template updates we matched more of the lines and added an Error directive. Unfortunately test data didn't have example raw output from old switches or Fibre Channel so those weren't accounted for (as to be expected).

@mjbear mjbear marked this pull request as ready for review September 27, 2025 14:36
@mjbear mjbear changed the title Fix older FC interface statistics Fix nxos older FC interface statistics Sep 30, 2025
@mjbear mjbear changed the title Fix nxos older FC interface statistics Fix older FC nxos interface statistics Sep 30, 2025
Comment on lines +21 to +41
fc4/11 is down (Link failure: loss of signal)
Port description is UCS Cisco Fiber-Channel (FI-B Port 31)
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:cb:00:2a:6a:73:4d:80
Admin port mode is auto, trunk mode is on
snmp link state traps are enabled
Port vsan is 1
Receive data field Size is 2112
Beacon is turned off
1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
95020 frames input, 4941396 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
95026 frames output, 53208452 bytes
0 discards, 0 errors
1 input OLS, 1 LRR, 1 NOS, 0 loop inits
1 output OLS, 0 LRR, 1 NOS, 0 loop inits
last clearing of "show interface" counters never
Interface last changed at Tue Jun 3 11:51:29 2025 No newline at end of file
Copy link
Contributor

@itdependsnetworks itdependsnetworks Sep 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the following be captured?

  • Port WWN is 20:cb:00:2a:6a:73:4d:80 (as MAC???)
  • 0 errors (as output_errors)
  • 1 minute input rate 0 bits/sec (as bandwidth_input_rate) (same for output)

there may be some more in the numbers

Copy link
Collaborator Author

@mjbear mjbear Sep 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Port WWN
    • Like others, I initially took a double take at the WWN, but it has more hex chars than a MAC address
  • Errors
    • I'm open to capturing it if we think it's worth it -- this would require a state transition
  • input/output rates
    • I'll take a closer look at this since the labels do include (in|out)put 😇
    • Edit: These are captured and it probably doesn't hurt that they are, right?

@jvanderaa
Copy link
Contributor

@mjbear I think we are all set here right?

@mjbear
Copy link
Collaborator Author

mjbear commented Oct 15, 2025

@mjbear I think we are all set here right?

@jvanderaa
Are the questions posed earlier remaining items that need addressed?

  • Do we need to capture the FC WWN?
    • (By definition of hex length, it's not a MAC, but I see where Ken is going.)
  • Is capturing the error counters (for FC interfaces) worth the effort?
  • Worth capturing in/out rates and a couple of other items?
    • Similar to the previous bullet about error counters, for FC interfaces this may not be worth the effort.

🙂 Otherwise, I believe we're all set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New error in cisco_nxos_show_interface.textfsm

4 participants