Load-interval command is used on interfaces to change the time period of packet-rate and throughput statistics. On the Nexus switches we can have upto three different counter for different time period.
You can configure load-interval on the interface regardless of its mode .i.e switch port or routed port
Nexus-9K--1# show interface eth1/3
Ethernet1/3 is up
admin state is up, Dedicated Interface
Hardware: 100/1000/10000/25000 Ethernet, address: 003a.9c5e.86ca (bia 003a.9c5e.86ca)
MTU 1500 bytes, BW 25000000 Kbit , DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, medium is broadcast
Port mode is access
auto-duplex, auto-speed
Beacon is turned off
Auto-Negotiation is turned on FEC mode is Auto
Input flow-control is off, output flow-control is off
Auto-mdix is turned off
Switchport monitor is off
EtherType is 0x8100
EEE (efficient-ethernet) : n/a
admin fec state is auto, oper fec state is auto
Last link flapped never
Last clearing of "show interface" counters never
0 interface resets
Load-Interval #1: 30 seconds
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 0 bits/sec, 0 packets/sec
input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
Load-Interval #2: 5 minute (300 seconds)
300 seconds input rate 0 bits/sec, 0 packets/sec
300 seconds output rate 0 bits/sec, 0 packets/sec
input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
RX
4 unicast packets 0 multicast packets 0 broadcast packets
4 input packets 2452 bytes
0 jumbo packets 0 storm suppression bytes
0 runts 0 giants 0 CRC 0 no buffer
0 input error 0 short frame 0 overrun 0 underrun 0 ignored
0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
0 input with dribble 0 input discard
0 Rx pause
TX
4 unicast packets 0 multicast packets 0 broadcast packets
4 output packets 2452 bytes
0 jumbo packets
0 output error 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble 0 output discard
0 Tx pause
Nexus-9K--1(config)# interface eth1/3
Nexus-9K--1(config-if)# load-interval ?
<5-300> Load interval delay in seconds
counter Specify counter for this load interval
Nexus-9K--1(config-if)# load-interval counter ?
<1-3> Specify counter for this load interval
Nexus-9K--1(config-if)# load-interval counter 3 ?
<5-300> Load interval delay in seconds
Nexus-9K--1(config-if)# load-interval counter 3 60
Nexus-9K--1(config-if)# end
Nexus-9K--1# show int eth1/3
Ethernet1/3 is up
admin state is up, Dedicated Interface
Hardware: 100/1000/10000/25000 Ethernet, address: 003a.9c5e.86ca (bia 003a.9c5e.86ca)
MTU 1500 bytes, BW 25000000 Kbit , DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, medium is broadcast
Port mode is access
auto-duplex, auto-speed
Beacon is turned off
Auto-Negotiation is turned on FEC mode is Auto
Input flow-control is off, output flow-control is off
Auto-mdix is turned off
Switchport monitor is off
EtherType is 0x8100
EEE (efficient-ethernet) : n/a
admin fec state is auto, oper fec state is auto
Last link flapped never
Last clearing of "show interface" counters never
0 interface resets
Load-Interval #1: 30 seconds
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 0 bits/sec, 0 packets/sec
input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
Load-Interval #2: 5 minute (300 seconds)
300 seconds input rate 0 bits/sec, 0 packets/sec
300 seconds output rate 0 bits/sec, 0 packets/sec
input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
Load-Interval #3: 1 minute (60 seconds)
60 seconds input rate 0 bits/sec, 0 packets/sec
60 seconds output rate 0 bits/sec, 0 packets/sec
input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
RX
4 unicast packets 0 multicast packets 0 broadcast packets
4 input packets 2452 bytes
0 jumbo packets 0 storm suppression bytes
0 runts 0 giants 0 CRC 0 no buffer
0 input error 0 short frame 0 overrun 0 underrun 0 ignored
0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
0 input with dribble 0 input discard
0 Rx pause
TX
4 unicast packets 0 multicast packets 0 broadcast packets
4 output packets 2452 bytes
0 jumbo packets
0 output error 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble 0 output discard
0 Tx pause
However, when the port is configured as routed port make sure that it not configured with p2p medium. You can only configure load-interval when the port is in default medium of broadcast.
Nexus-9K--1# show run int eth1/1
!Command: show running-config interface Ethernet1/1
!Running configuration last done at: Mon Sep 12 10:36:57 2022
!Time: Mon Sep 12 10:38:56 2022
version 9.3(8) Bios:version 05.44
interface Ethernet1/1
description UPLINK TO SPINE-1
mtu 9216
logging event port link-status
medium p2p
no ip redirects
ip address 10.1.1.1/31
ip ospf network point-to-point
ip router ospf 65001 area 0.0.0.0
ip ospf bfd
ip pim bfd-instance
ip pim sparse-mode
ip arp timeout 900
no shutdown
Nexus-9K--1# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Nexus-9K--1(config)# int eth1/1
Nexus-9K--1(config-if)# load ?
*** No matching command found in current mode, matching in (exec) mode ***
bootflash: Enter image URI
volatile: Enter image URI
Nexus-9K--1(config-if)# medi
media-type medium
Nexus-9K--1(config-if)# medium broadcast
Nexus-9K--1(config-if)# load-interval ?
<5-300> Load interval delay in seconds
counter Specify counter for this load interval
Nexus-9K--1(config-if)# load-interval counter 1 ?
<5-300> Load interval delay in seconds
Nexus-9K--1(config-if)# load-interval counter 1
