09-20-2023 04:44 AM
We have a cisco ASR1009-X, here we have configured bridge-domain interface using 2x10Gbps interface. But the new virtual interface bdi1 is showing low bandwidth of 1Gbps only.
Query:
- Even if 10G link is bundled in bridge-domain interface, if the traffic goes beyond 1G, that time will we face bandwidth crunch?
- Because of 1G BW in BDI1 interface, EMS showing 95-100% utilization. How to recover it?
All configurations is shared below.
Please guide....
DC-BBR-RTR-01#show bridge-domain
Bridge-domain 1 (3 ports in all)
State: UP Mac learning: Enabled
Aging-Timer: 300 second(s)
Maximum address limit: 65536
BDI1 (up)
TenGigabitEthernet1/0/0 service instance 1
TenGigabitEthernet1/0/1 service instance 1
AED MAC address Policy Tag Age Pseudoport
0 A2D7.6800.000A forward dynamic 300 TenGigabitEthernet1/0/0.EFP1
- 3C57.31FD.BF3F to_bdi static 0 BDI1
DC-BBR-RTR-01#show run inte TenGigabitEthernet1/0/0
Building configuration...
Current configuration : 180 bytes
!
interface TenGigabitEthernet1/0/0
description DC-INTRANET-FW-01
no ip address
load-interval 30
service instance 1 ethernet
encapsulation untagged
bridge-domain 1
!
end
DC-BBR-RTR-01#show run inte TenGigabitEthernet1/0/1
Building configuration...
Current configuration : 180 bytes
!
interface TenGigabitEthernet1/0/1
description DC-INTRANET-FW-02
no ip address
load-interval 30
service instance 1 ethernet
encapsulation untagged
bridge-domain 1
!
end
DC-BBR-RTR-01#show inter
DC-BBR-RTR-01#show interfaces TenGigabitEthernet1/0/0
TenGigabitEthernet1/0/0 is up, line protocol is up
Hardware is EPA-10X10GE, address is 3c57.31fd.be80 (bia 3c57.31fd.be80)
Description: DC-INTRANET-FW-01
MTU 1500 bytes, BW 10000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 3/255, rxload 3/255
Encapsulation ARPA, loopback not set
Keepalive not supported
Full Duplex, 10000Mbps, media type is SFP-SR
output flow-control is on, input flow-control is on
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:09:26, output hang never
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
30 second input rate 122744000 bits/sec, 21319 packets/sec
30 second output rate 132608000 bits/sec, 20204 packets/sec
84339047618 packets input, 99229752970751 bytes, 0 no buffer
Received 78 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 3896268 multicast, 0 pause input
49162758211 packets output, 20536527373377 bytes, 0 underruns
Output 2143 broadcasts (0 IP multicasts)
0 output errors, 0 collisions, 2 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
1 carrier transitions
DC-BBR-RTR-01#show interfaces TenGigabitEthernet1/0/1
TenGigabitEthernet1/0/1 is up, line protocol is up
Hardware is EPA-10X10GE, address is 3c57.31fd.be81 (bia 3c57.31fd.be81)
Description: DC-INTRANET-FW-02
MTU 1500 bytes, BW 10000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not supported
Full Duplex, 10000Mbps, media type is SFP-SR
output flow-control is on, input flow-control is on
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:09:28, output hang never
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 2000 bits/sec, 1 packets/sec
33 packets input, 1980 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
7405709 packets output, 2352269502 bytes, 0 underruns
Output 2221 broadcasts (0 IP multicasts)
0 output errors, 0 collisions, 2 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
1 carrier transitions
DC-BBR-RTR-01#show interfaces bdi1
BDI1 is up, line protocol is up
Hardware is BDI, address is 3c57.31fd.bf3f (bia 3c57.31fd.bf3f)
Description: DC-INTRANET-FW-01&02
Internet address is 10.198.214.35/29
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 33/255, rxload 28/255
Encapsulation ARPA, loopback not set
Keepalive not supported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:01, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
30 second input rate 112067000 bits/sec, 20315 packets/sec
30 second output rate 130207000 bits/sec, 19871 packets/sec
84339120119 packets input, 99229798781247 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
49162834860 packets output, 20333509412912 bytes, 0 underruns
Output 0 broadcasts (0 IP multicasts)
0 output errors, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
DC-BBR-RTR-01#
09-21-2023 02:28 AM
Have you tried setting a 10g bandwidth statement on the BDI?
09-21-2023 10:35 AM
I do not think there is any real problem with bandwidth. Bear in mind that this is a virtual interface. Bandwidth is a meaningful attribute for a physical interface. Not so much for a virtual interface. There are similar situations for other virtual interfaces such as GRE tunnel where show interface for the tunnel shows a quite low bandwidth but the performance of the tunnel is fine.
09-21-2023 03:34 PM
Rick raises an important point. If you believe the interface bandwidth statement directly limits bandwidth, it does not. Management software, though, will often report interface utilization on what it believes the interface supports. As Rick also describes, the BDI is a virtual interface, so its "default" bandwidth assumption can be incorrect, and could need a manually configured bandwidth statement to insure % stats are correctly reported.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide