cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2519
Views
5
Helpful
1
Replies

tcp-mss and ip mtu not taking effect on AWS interface

dpmon11
Level 1
Level 1

Hello all,

 

I am currently trying to troubleshoot packet loss I am having from our pexip management source, which uses 1500byte MTU value, to our AWS cloud instance through Direct connect, configured on a subinterface.

 

This is my current setup:

interface GigabitEthernet0/0/1
description aws direct connect
no ip address
ip mtu 1300
ip tcp adjust-mss 1260
no negotiation auto

!
interface GigabitEthernet0/0/1.102
description aws direct connect vlan
encapsulation dot1Q 102
ip address X.X.X.25 255.255.255.248
ip access-group 111 in

!
interface GigabitEthernet0/0/1.103
description "Direct Connect to VPC"
encapsulation dot1Q 103
ip address X.X.X.2 255.255.255.252
ip mtu 1300
ip tcp adjust-mss 1260

 

But when I do show commands to verify if the configuration took effect, I do not see the new 1300 MTU value.

I only see the original 1500 MTU value, as seen below:

 

Router# sho interface gigabitEthernet 0/0/1
GigabitEthernet0/0/1 is up, line protocol is up
Description: aws direct connect
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
Keepalive not supported
Full Duplex, 1000Mbps, link type is force-up, media type is LX
output flow-control is on, input flow-control is on
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:03, output hang never
Last clearing of "show interface" counters never

 

AND

 

Router# sho interface gigabitEthernet 0/0/1.103
GigabitEthernet0/0/1.103 is up, line protocol is up
Description: "Direct Connect to VPC"
Internet address is X.X.X.2/30
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 103.
ARP type: ARPA, ARP Timeout 04:00:00
Keepalive not supported
Last clearing of "show interface" counters never

 

Is there a reason the new configured value is not reflected on the main interface G0/0/1 nor the subinterface G0/0/1.103?

 

Thank you for any guidance!

1 Reply 1

rrsmith
Level 1
Level 1

Very late reply but just got stuck on the same issue and hopefully this helps. In order to see the actual value you've set you'll need to use "show ip interface gigabitEthernet 0/0/1".  I came across this when adjusting the "ip mtu" & "ip tcp adjust-mss" size for DMVPN after experiencing some fragmentation issues. 

Review Cisco Networking for a $25 gift card