Infiniband Mellanox MTU size change

Hello to all.
I am new to Solaris and know nothing about its administration tools.
We are willing to test Infiniband and need to change MTU of the adapter (Mellanox) to 4K (which is the default configu for our subnet manager).
Which command should be used to archieve the task ?
Next we need to configure an SRP target. Any specific howto ?
Thanks in advance for your kind reply

Thank you for your reply, Darren.
As per my test, ifconfig will work for the IPoIB (when creating a derivative interface to run IP over infiniband).
Actually the driver is installed, link comes up, fabric negotiates 2048 MTU and no interface is available to configure for IPoIB since I did not create it.
Ifconfig lists only the gigabit eth nic, since no ib0 card is defined (only ib device in /proc).
I am not going to run IP over Infiniband, al least not for storage access, since poses a huge penalty in performance.
To configure the device MTU (not the virtual ethernet over infiniband MTU) I think must be done at driver level, using something related to the low level adapter
•cfgadm_ib(1M) - InfiniBand hardware-specific commands for cfgadm
•datadm(1M) - maintain DAT static registry file
•ifconfig(1M) - configure network interface parameters
•libdat(3LIB) - direct access transport library
•ib(4) - InfiniBand device driver configuration files
•ibmf(7) - InfiniBand Management Transport Framework
•daplt(7D) - Tavor uDAPL service driver
•ib(7D) - InfiniBand Bus Nexus Driver
•ibcm(7D) - InfiniBand Communication Manager
•ibd(7D) - Infiniband IPoIB device driver
•ibdm(7D) - Solaris InfiniBand device manager
•tavor(7D) - InfiniBand (IB) Tavor driver
I guess it wil be cfgadm, but do not know syntax and parameters.
In vmware, using Mellanox tools, you issue esxcfg-module -s "port_type_default=1 set_4k_mtu=1" mlx4_en, where mlx4_en is the kernel module.
How to achieve this with Solaris ?
As per the SRP question, if Solaris supports COMSTAR it should support SRP target mode, right ?
Thank for sharing your thoughts.

Similar Messages

  • Mid 2010 Macbook Pro - Change MTU size kills internet (Jumbo Frames)

    Hi everyone, i'm hoping someone here can enlighten or help me solve my problem I'm having.
    I am trying to change my MTU size to enable Jumbo frames on my 13 inch Mid 2010 Macbook Pro. I recently bought a ReadyNAS Ultra and would like to speed up transfers to the unit.
    My setup is as follows:
    I have my ReadyNAS Ultra 2 and 2010 Macbook Pro (Core 2 Duo) wired via cat6 ethernet to my 5th Generation Apple Airport Extreme. The Airport Extreme is connected via cat5e to my AT&T Uverse Gateway which is set up to allow my Airport to assign DHCP and NAT (gateway is in bridge mode with wireless off).
    Anyways, I have enabled Jumbo frames on my ReadyNAS, when I enable them on my MBP.. it applies fine. It disconnects / reconnects the ethernet like it should, but then my connection drops. I can't see any devices on my LAN and I cannot access any internet websites, but according to the network pane I am still assigned a valid dhcp address. When I manually try to increase my MTU size, the same thing happens (from 9000 to 1600 I tried every size).....
    Could it be my MBP just can't suppose the increase of MTU size? It leaves them at 1500 when I set it to automatic... if it doesn't support the increased MTU size, why would it let me custom change the MTU and even give an option to select "Jumbo Frames (9000)"?
    I appreciate any help in advance!!

    asdftroy wrote:
    If you did read my post then you would have saw that the option is there, but that is not entirely what my inquiry is about. The option isn't working as intended, and I was wondering if anyone had the same issues as me. Thanks anyways.
    Anyone else?
    The way you responded to someone trying to help you probably means others will be hesitant to try.

  • How do you change the MTU size in a Cisco 871?

    This 871 is at a remote site and is an ezvpn IPsec client (network extension mode) back to a 3030 headend.
    We're having problems with a PC trying to connect through the IPsec tunnel and we think it may be an MTU size problem.
    Int F4 is the outside interface.
    We are using a virtual-template associated with the crypto ipsec client ezvpn statement.
    When I go into any of the 871 interfaces and type 'mtu 1370' it errors out with 'The F4 (or whatever interface) does not allow manual MTU size configuration.
    If I type 'ip mtu 1370' on F4 (or vlan1 or virtual-template 1) this is accepted, but when I do a 'show int f 4', it still shows MTU of 1514 - even after a reload.
    What is the correct way to set the MTU size in the 871 router - and is it best set on the F4 interface, the vlan, or the virtual-template interface?

    Hi
    As per the supporting doc Cisco 871 has one want ethernet interface and 2 switch ports.
    I feel you are trying to change the mtu under the switch port which may not be possible.
    You can refer the below link for more info..
    http://www.cisco.com/en/US/products/hw/routers/ps380/products_data_sheet0900aecd8028a976.html
    regds

  • How do you change the mtu size

    i recently bought a WRT54G wireless router and i have my desktop directly hooked up (not wireless) and every time i go to play games or surf the net it has some pretty severe lag spikes. i have done some searching and i see something about changing the MTU to a certain amount but i have no idea what that is or how to change it. so if u have any suggestions for me that would be appreciated

    connect a computer to the router's port#1 and access the router using http://192.168.1.1 . the default password is admin
    on the ui , under the " basic setup " subtab , you have an option to change the MTU size..by default the MTU is disabled...change it to enable and change the MTU size as required...

  • Link Aggregation dladm on T2000 with 2 e1000g. How can i change mtu size

    Hello
    I made a Link Aggregation on a T2000 with e1000g1 & e1000g2 successfully.
    Now i want to raise up the mtu size to mtu 9000 for the aggregation.
    I tried /etc/hostname.aggr
    mtu 9000
    unsuccessfully- MTU size still 1500
    /kernel/drv/etc/e1000g.conf
    setting Max Fram Size for 1 2 3 interface to 2(upto 8k)
    also not successfully
    MaxFrameSize=0,2,2,2;
    # 0 is for normal ethernet frames.
    # 1 is for upto 4k size frames.
    # 2 is for upto 8k size frames.
    # 3 is for upto 16k size frames.
    # These are maximum frame limits, not the actual ethernet frame
    # size. Your actual ethernet frame size would be determined by
    # protocol stack configuration (please refer to ndd command man pages)
    # For Jumbo Frame Support (9k ethernet packet)
    # use 3 (upto 16k size frames)
    Has someone an idea?
    thanx for advice

    Bug is described:
    http://sunsolve.sun.com/search/document.do?assetkey=1-1-6326664-1
    Solution is
    T-Patch 125020-01
    Message was edited by:
    sunibk

  • MTU Size Problem Loading Certain Webpages

    Hello Colleagues,
    I'm having a strange problem dealing with MTU sizes and loading certain webpages. I am aware of the default Microsoft MTU of 1500 and also using GRE IPSEC Tunnels recommended at MTU size 1400. I have since manually set some users PC's to MTU of 1400 and most of those users are experiencing no issues. However, there are a few users who still experience website loading issues even though I have manually changed their MTU size to 1400.
    These are domain accounts will the same image loads on their machines, so all have the same permissions, rights, firewall settings, etc. They all use the same LAN, switches, and routers.
    Here are the router configs, router 1 and router 2
    Router 1
    Current configuration : 9006 bytes
    version 15.3
    no service pad
    service timestamps debug datetime msec localtime
    service timestamps log datetime msec localtime
    service password-encryption
    hostname R-US-RS-WVPN1
    boot-start-marker
    boot system flash:c1900-universalk9-mz.SPA.153-1.T1.bin
    boot system flash:c1900-universalk9-mz.SPA.151-3.T1.bin
    boot-end-marker
    logging buffered 64000
    enable secret 5 *removed*
    no aaa new-model
    clock timezone CET 1 0
    clock summer-time CET recurring last Sun Mar 2:00 last Sun Oct 3:00
    errdisable recovery cause udld
    errdisable recovery cause bpduguard
    errdisable recovery cause rootguard
    errdisable recovery cause pagp-flap
    errdisable recovery cause dtp-flap
    errdisable recovery cause link-flap
    errdisable recovery interval 303
    ip cef
    ip domain name corp.com
    ip name-server 10.###.8.21
    ip name-server 10.###.8.96
    ip inspect dns-timeout 90
    ip inspect tcp idle-time 60
    ip inspect name fw smtp timeout 120
    ip inspect name fw ftp timeout 120
    ip inspect name fw realaudio
    ip inspect name fw tftp timeout 30
    ip inspect name fw udp timeout 30
    ip inspect name fw tcp timeout 60
    no ipv6 cef
    multilink bundle-name authenticated
    crypto pki trustpoint TP-self-signed-316595902
    enrollment selfsigned
    subject-name cn=IOS-Self-Signed-Certificate-316595902
    revocation-check none
    rsakeypair TP-self-signed-316595902
    crypto pki certificate chain TP-self-signed-316595902
    certificate self-signed 01
      *removed*
            quit
    license udi pid CISCO1921/K9 sn FTX153182M8
    spanning-tree vlan 229 priority 8192
    redundancy
    ip ssh version 2
    crypto isakmp policy 10
    hash md5
    authentication pre-share
    lifetime 3600
    crypto isakmp key *removed* address 70.###.172.142
    crypto isakmp key *removed* address 184.###.###.254
    crypto isakmp keepalive 35 11
    crypto ipsec transform-set FY-WVPN-Tunnel esp-aes esp-md5-hmac
    mode tunnel
    crypto map vpn 10 ipsec-isakmp
    set peer 70.###.172.142
    set peer 184.###.###.254
    set transform-set FY-WVPN-Tunnel
    match address gre-tunnel-list
    interface Loopback0
    ip address 10.###.0.10 255.255.255.255
    interface Tunnel2291
    description Primary-TimewarnerTelecom-Ral-FayWVPN1
    ip address 10.###.99.26 255.255.255.252
    no ip redirects
    cdp enable
    tunnel source 66.###.161.126
    tunnel destination 184.###.###.254
    crypto map vpn
    interface Tunnel2293
    description Primary-TimewarnerTelecom-Ral-FayWVPN2
    ip address 10.###.99.154 255.255.255.252
    no ip redirects
    cdp enable
    tunnel source 66.###.161.126
    tunnel destination 70.###.172.142
    crypto map vpn
    interface Embedded-Service-Engine0/0
    no ip address
    shutdown
    interface GigabitEthernet0/0
    description TW Telecom/DMVPN1
    ip address 66.###.161.126 255.255.255.252
    ip access-group Block-Internet in
    ip access-group Block-Internet out
    duplex auto
    speed auto
    no cdp enable
    crypto map vpn
    interface GigabitEthernet0/1
    no ip address
    duplex auto
    speed auto
    interface GigabitEthernet0/0/0
    switchport access vlan 229
    no ip address
    interface GigabitEthernet0/0/1
    switchport access vlan 229
    no ip address
    interface GigabitEthernet0/0/2
    switchport access vlan 229
    no ip address
    interface GigabitEthernet0/0/3
    description PBX Eth1
    switchport access vlan 229
    no ip address
    interface Vlan1
    no ip address
    shutdown
    interface Vlan229
    ip address 10.###.229.253 255.255.255.0
    ip helper-address 10.###.231.201
    standby 229 ip 10.###.229.254
    standby 229 priority 105
    standby 229 preempt
    router eigrp 100
    network 10.0.0.0
    ip forward-protocol nd
    no ip http server
    ip http secure-server
    ip route 70.###.172.142 255.255.255.255 66.###.161.125
    ip route 184.###.###.254 255.255.255.255 66.###.161.125
    ip route 205.###.96.180 255.255.255.252 66.###.161.125
    ip access-list extended Block-Internet
    permit esp host 66.###.161.126 host 184.###.###.254
    permit esp host 184.###.###.254 host 66.###.161.126
    permit udp host 66.###.161.126 host 184.###.###.254 eq isakmp
    permit udp host 184.###.###.254 host 66.###.161.126 eq isakmp
    permit esp host 66.###.161.126 host 70.###.172.142
    permit esp host 70.###.172.142 host 66.###.161.126
    permit udp host 66.###.161.126 host 70.###.172.142 eq isakmp
    permit udp host 70.###.172.142 host 66.###.161.126 eq isakmp
    permit icmp host 66.###.161.126 host 184.###.###.254
    permit icmp host 184.###.###.254 host 66.###.161.126
    permit icmp host 66.###.161.126 host 70.###.172.142
    permit icmp host 70.###.172.142 host 66.###.161.126
    permit icmp any any echo-reply
    permit icmp any any time-exceeded
    permit icmp any any packet-too-big
    permit icmp any any traceroute
    permit icmp any any unreachable
    deny   ip any any
    deny   icmp any any
    ip access-list extended gre-tunnel-list
    permit gre host 66.###.161.126 host 184.###.###.254
    permit gre host 66.###.161.126 host 70.###.172.142
    logging host 10.100.###.254
    logging host 10.100.###.246
    snmp-server community a RW 20
    snmp-server community r RO 20
    snmp-server community a RW 20
    snmp-server community r RO 20
    snmp-server community P_RW RW
    snmp-server community P_RO RO
    snmp-server enable traps entity-sensor threshold
    snmp-server host 10.100.###.246 public
    snmp-server host 10.100.###.254 public
    access-list 20 permit 10.###.9.3
    access-list 20 permit 10.###.8.16
    access-list 20 permit 10.100.###.249
    access-list 20 permit 10.100.###.254
    access-list 20 permit 10.100.###.246
    control-plane
    banner motd ^CCCCCCC
    ****************** Warning! Warning! Warning! ********************
    This system is restricted to authorized users for business
    purposes.  Unauthorized access is a violation of the law.  This
    service may be monitored for administrative and security reasons.
    By proceeding, you consent to this monitoring
    ****************** Warning! Warning! Warning! ********************
    ^C
    line con 0
    login local
    line aux 0
    line 2
    no activation-character
    no exec
    transport preferred none
    transport input all
    transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
    stopbits 1
    line vty 0 4
    exec-timeout 60 0
    password 7 *removed*
    login local
    transport input ssh
    line vty 5 15
    exec-timeout 60 0
    password 7 *removed*
    login local
    transport input ssh
    scheduler allocate 20000 1000
    ntp server 10.###.8.8 prefer
    ntp server 10.###.231.200 prefer
    ntp server 10.###.8.69
    ntp server 10.###.1.6 prefer
    end
    Router 2
    Current configuration : 9013 bytes
    version 15.3
    no service pad
    service timestamps debug datetime msec localtime
    service timestamps log datetime msec localtime
    service password-encryption
    hostname R-US-RS-WVPN2
    boot-start-marker
    boot system flash:c1900-universalk9-mz.SPA.153-1.T1.bin
    boot system flash:c1900-universalk9-mz.SPA.151-3.T1.bin
    boot-end-marker
    logging buffered 64000
    logging console critical
    enable secret 5 *removed*
    no aaa new-model
    clock timezone CET 1 0
    clock summer-time CET recurring last Sun Mar 2:00 last Sun Oct 3:00
    errdisable recovery cause udld
    errdisable recovery cause bpduguard
    errdisable recovery cause rootguard
    errdisable recovery cause pagp-flap
    errdisable recovery cause dtp-flap
    errdisable recovery cause link-flap
    errdisable recovery interval 303
    ip cef
    ip domain name corp.mann-hummel.com
    ip name-server 10.###.8.21
    ip name-server 10.###.8.96
    ip inspect dns-timeout 90
    ip inspect tcp idle-time 60
    ip inspect name fw smtp timeout 120
    ip inspect name fw ftp timeout 120
    ip inspect name fw realaudio
    ip inspect name fw tftp timeout 30
    ip inspect name fw udp timeout 30
    ip inspect name fw tcp timeout 60
    ipv6 multicast rpf use-bgp
    no ipv6 cef
    multilink bundle-name authenticated
    crypto pki trustpoint TP-self-signed-3179596086
    enrollment selfsigned
    subject-name cn=IOS-Self-Signed-Certificate-3179596086
    revocation-check none
    rsakeypair TP-self-signed-3179596086
    crypto pki certificate chain TP-self-signed-3179596086
    certificate self-signed 01
      *removed*
            quit
    license udi pid CISCO1921/K9 sn FTX153182M2
    spanning-tree vlan 229 priority 1###84
    redundancy
    ip ssh version 2
    crypto isakmp policy 10
    hash md5
    authentication pre-share
    lifetime 3600
    crypto isakmp key *removed* address 70.###.172.142
    crypto isakmp key *removed* address 184.###.###.254
    crypto isakmp keepalive 35 11
    crypto ipsec transform-set Fay-Ral-WVPN-Tunnel esp-aes esp-md5-hmac
    mode tunnel
    crypto map vpn 10 ipsec-isakmp
    set peer 184.###.###.254
    set peer 70.###.172.142
    set transform-set Fay-Ral-WVPN-Tunnel
    match address gre-tunnel-list
    interface Loopback0
    ip address 10.###.0.12 255.255.255.255
    interface Tunnel2292
    description Failover-TimewarnerCable-Ral-Fay-WVPN2
    ip address 10.###.99.30 255.255.255.252
    no ip redirects
    cdp enable
    tunnel source 96.###.25.226
    tunnel destination 184.###.###.254
    crypto map vpn
    interface Tunnel2294
    description Failover-TimewarnerCable-Ral-Fay-WVPN2
    ip address 10.###.99.158 255.255.255.252
    no ip redirects
    cdp enable
    tunnel source 96.###.25.226
    tunnel destination 70.###.172.142
    crypto map vpn
    interface Embedded-Service-Engine0/0
    no ip address
    shutdown
    interface GigabitEthernet0/0
    description Fay-Ral WVPN
    ip address 96.###.25.226 255.255.255.252
    ip access-group Block-Internet in
    ip access-group Block-Internet out
    duplex auto
    speed auto
    no cdp enable
    crypto map vpn
    interface GigabitEthernet0/1
    no ip address
    shutdown
    duplex auto
    speed auto
    interface GigabitEthernet0/0/0
    switchport access vlan 229
    no ip address
    interface GigabitEthernet0/0/1
    switchport access vlan 229
    no ip address
    interface GigabitEthernet0/0/2
    switchport access vlan 229
    no ip address
    interface GigabitEthernet0/0/3
    description PBX Eth2
    switchport access vlan 229
    no ip address
    interface Vlan1
    no ip address
    shutdown
    interface Vlan229
    ip address 10.###.229.252 255.255.255.0
    ip helper-address 10.###.231.201
    standby 229 ip 10.###.229.254
    standby 229 preempt
    router eigrp 100
    network 10.0.0.0
    ip forward-protocol nd
    no ip http server
    ip http secure-server
    ip route 70.###.172.142 255.255.255.255 96.###.25.225
    ip route 184.###.###.254 255.255.255.255 96.###.25.225
    ip route 205.###.96.180 255.255.255.252 66.###.161.125
    ip access-list extended Block-Internet
    permit esp host 96.###.25.226 host 184.###.###.254
    permit esp host 184.###.###.254 host 96.###.25.226
    permit udp host 96.###.25.226 host 184.###.###.254 eq isakmp
    permit udp host 184.###.###.254 host 96.###.25.226 eq isakmp
    permit esp host 96.###.25.226 host 70.###.172.142
    permit esp host 70.###.172.142 host 96.###.25.226
    permit udp host 96.###.25.226 host 70.###.172.142 eq isakmp
    permit udp host 70.###.172.142 host 96.###.25.226 eq isakmp
    permit icmp host 96.###.25.226 host 184.###.###.254
    permit icmp host 184.###.###.254 host 96.###.25.226
    permit icmp host 96.###.25.226 host 70.###.172.142
    permit icmp host 70.###.172.142 host 96.###.25.226
    permit icmp any any echo-reply
    permit icmp any any time-exceeded
    permit icmp any any packet-too-big
    permit icmp any any traceroute
    permit icmp any any unreachable
    deny   ip any any
    deny   icmp any any
    ip access-list extended gre-tunnel-list
    permit gre host 96.###.25.226 host 184.###.###.254
    permit gre host 96.###.25.226 host 70.###.172.142
    logging host 10.100.###.254
    logging host 10.100.###.246
    snmp-server community P_RW RW
    snmp-server community P_RO RO
    snmp-server community a RW 20
    snmp-server community r RO 20
    snmp-server community a RW 20
    snmp-server community r RO 20
    snmp-server enable traps entity-sensor threshold
    snmp-server host 10.100.###.246 public
    snmp-server host 10.100.###.254 public
    access-list 20 permit 10.###.9.3
    access-list 20 permit 10.###.8.16
    access-list 20 permit 10.100.###.249
    access-list 20 permit 10.100.###.254
    access-list 20 permit 10.100.###.246
    control-plane
    banner motd ^CCCCCC
    ****************** Warning! Warning! Warning! ********************
    This system is restricted to authorized users for business
    purposes.  Unauthorized access is a violation of the law.  This
    service may be monitored for administrative and security reasons.
    By proceeding, you consent to this monitoring
    ****************** Warning! Warning! Warning! ********************
    ^C
    line con 0
    login local
    line aux 0
    line 2
    no activation-character
    no exec
    transport preferred none
    transport input all
    transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
    stopbits 1
    line vty 0 4
    exec-timeout 60 0
    password 7 *removed*
    login local
    transport input ssh
    line vty 5 15
    exec-timeout 60 0
    password 7 *removed*
    login local
    transport input ssh
    scheduler allocate 20000 1000
    ntp server 10.###.8.8 prefer
    ntp server 10.###.231.200 prefer
    ntp server 10.###.8.69
    ntp server 10.###.1.6 prefer
    end

    UPDATE
    I have since applied the following config to the tunnel interfaces:
    ip mtu 1400
    ip tcp adjust-mss 1400
    tunnel path-mtu-discovery
    This worked and I was able to reset each users PC to default MTU size of 1500, but only until just now. I got a call from a user who explained that he wasn't able to reach some websites, again.
    Sure enough, I've just confirmed that all of the users are unable to access the websites any longer.
    This is crazy, does anyone have any ideas?

  • Can I set the MTU size for the Airport Extreme?

    Can I change the MTU size setting of the Airport? How would this be possible? In my Linksys router I was able to change this.

    Since the AirPort Extreme base station (AEBS) does not modify the packets in any way. So as neptune2000 stated, there is no MTU setting. Whatever MTU your computer broadcasts with is unchanged by the AEBS.
    You will need to configure the MTU on the computer sending the packets.

  • EIGRP MTU Size Causing Neighbor Flap - Pls help!

    I've been reading the post here which is quite good but, I have some outstanding questions I hope someone can help me with?
    https://learningnetwork.cisco.com/thread/43100#233367
    Essentially, we have a DCI which is an evpl link - layer 2. The evpl connection is terminated with a Cisco 3925 at each location (once it comes out of the provider's Ciena box). It is a dot1g tagged trunk - L2 connection. We are running EIGRP between the two. Before setting up OTV, all link sizes were 1500 MTU...which obviously will not work with OTV....and it didnt!. OTV is running on 7Ks a few hops away from each 3925. So, I went on each and every link - (pain stakingly) and configured MTU size for 9216 - enabling jumboframes at the system level too where applicable. What do you know, OTV started working and i could ping to at least up to 2000 bytes with DF-bit set too! (I didn't try any higher).
    Last night, our provider did some 'maintenance' without telling us - which brought the link down. The link was 'down' even after the maintenace was completed. After looking in the logs and seeing this, I suspected it had to do with MTU sizes after quickly googling around.
    May 13 12:33:13.698: %DUAL-5-NBRCHANGE: EIGRP-IPv4 10: Neighbor 198.28.132.30 (GigabitEthernet0/0.2) is down: Interface PEER-TERMINATION received
    May 13 12:33:13.976: %DUAL-5-NBRCHANGE: EIGRP-IPv4 10: Neighbor 198.28.132.30 (GigabitEthernet0/0.2) is up: new adjacency
    May 13 12:33:24.266: %SYS-5-CONFIG_I: Configured from console by izzi on vty0 (10.241.6.12)
    May 13 12:34:00.286: %DUAL-5-NBRCHANGE: EIGRP-IPv4 10: Neighbor 198.28.132.30 (GigabitEthernet0/0.2) is down: Interface PEER-TERMINATION received
    May 13 12:34:00.616: %DUAL-5-NBRCHANGE: EIGRP-IPv4 10: Neighbor 198.28.132.30 (GigabitEthernet0/0.2) is up: new adjacency
    May 13 12:34:46.922: %DUAL-5-NBRCHANGE: EIGRP-IPv4 10: Neighbor 198.28.132.30 (GigabitEthernet0/0.2) is down: Interface PEER-TERMINATION received
    May 13 12:34:47.280: %DUAL-5-NBRCHANGE: EIGRP-IPv4 10: Neighbor 198.28.132.30 (GigabitEthernet0/0.2) is up: new adjacency
    May 13 12:35:37.364: %DUAL-5-NBRCHANGE: EIGRP-IPv4 10: Neighbor 198.28.132.30 (GigabitEthernet0/0.2) is down: holding time expired
    May 13 12:37:29.725: %SYS-5-CONFIG_I: Configured from console by izzi on vty0 (10.241.6.12)
    May 13 12:37:47.430: %DUAL-5-NBRCHANGE: EIGRP-IPv4 10: Neighbor 198.28.132.30 (GigabitEthernet0/0.2) is up: new adjacency
    May 13 12:39:01.508: %SYS-5-CONFIG_I: Configured from console by izzi on vty0 (10.241.6.12)
    May 13 12:39:11.943: %DUAL-5-NBRCHANGE: EIGRP-IPv4 10: Neighbor 198.28.132.30 (GigabitEthernet0/0.2) is down: Interface PEER-TERMINATION received
    May 13 12:39:13.973: %DUAL-5-NBRCHANGE: EIGRP-IPv4 10: Neighbor 198.28.132.30 (GigabitEthernet0/0.2) is up: new adjacency
    So, I reduced the MTU size back to 1500 and low and behold, adjacency stayed. Let me also say that there weren't any errors on the links too. So, I decided to try and increase the MTU back up to 9216 - OTV started working again and adjancey held - it didnt flap. I thought for a second and decided to bounce the link. Once i did this, EIGRP started flapping again with the same exact behavior. After calling the provider, they claim that their max MTU is only 1522 for our EVPL link. I don't see this being possible since I was able to ping DF-BIT set way above 1522. Maybe I'm missing something. We are going to coordinate with them to increase the MTU size on the link. But why/how did it work to begin with - especially since OTV doesn't support fragmenation....I understand that OTV adjacency can still form since ISIS only needs 14xx something...but I wasn't able to get certain protocals/services like esxi host management to work via OTV until i increased MTU size.
    Also, after reading the above article it sounds like EIGRP will 'peer' or decide on MTU of it's update packets? If that's the case, maybe the bouncing of the link allowed EIGRP to negotiate it's packet sizes to above 1500 and that's why if I change the MTU size to above 1500 everything works fine - OTV/2000 byte bf-bit set ping, until I bounce the link? If this is the case, is there anyway to 'force' EIGRP to use 1500 for it's packets for its protocol traffic and allow everything else to use the MTU set on the link?
    I would appreciate any help explaining this - hopefully you're not as confused as I was after reading it again!

    Did you ever find the root cause and this solution for this?  We are experiencing the same issues with our 2 4500  Catalyst and a couple of routers on our inter routing VLAN that we use for only the 2 chassis and a couple of router.  MTU is already set at 1500 on the 2 chassis.
    005326: Jan 19 11:30:02: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 65001: Neighbor 10.190.254.21 (Vlan990) is down: Peer goodbye received
    005327: Jan 19 11:30:05: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 65001: Neighbor 10.190.254.1 (Vlan990) is up: new adjacency
    005328: Jan 19 11:30:05: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 65001: Neighbor 10.190.254.21 (Vlan990) is up: new adjacency
    005329: Jan 19 11:30:07: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 65001: Neighbor 10.190.254.12 (Vlan990) is down: holding time expired
    005330: Jan 19 11:30:27: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 65001: Neighbor 10.190.254.21 (Vlan990) is down: Peer goodbye received
    005331: Jan 19 11:30:28: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 65001: Neighbor 10.190.254.11 (Vlan990) is down: Peer goodbye received
    005332: Jan 19 11:30:28: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 65001: Neighbor 10.190.254.1 (Vlan990) is down: Peer goodbye received
    005333: Jan 19 11:30:30: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 65001: Neighbor 10.190.254.12 (Vlan990) is up: new adjacency
    005334: Jan 19 11:30:30: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 65001: Neighbor 10.190.254.11 (Vlan990) is up: new adjacency
    005335: Jan 19 11:30:30: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 65001: Neighbor 10.190.254.1 (Vlan990) is up: new adjacency
    005336: Jan 19 11:30:32: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 65001: Neighbor 10.190.254.21 (Vlan990) is up: new adjacency

  • SSLv3 and MTU size

    Hi there,
    in the bank network enviroment between 2 sites (first with the clients and the second with the server) we have performance problems with one application. One point which might be the cause of our problem is MTU size. The application is using SSLv3. The WAN link is encrypted by IPSec. What would be the suitable MTU size configured on the router? What is the size of overhead of SSLv3? What we need to add in terms of MTU size when we use SSLv3?
    Thanks a lot in advance for the answer.
    Regards,
    Jovica

    You need to increase the MSS to more than 812 bytes when using SSLv3. Another way is to change the communication profile ie change the POST.

  • System MTU size on Cisco switch

    after setting sys mtu to something other than 1500 on a WS-C3750G-24TS-1U it appears that this setting will stay in effect even if the startup config is erased and the switch is reloaded. My question is. Does this mean that if I need to replace the switch and I just load a saved version of the config and the vlan.dat files. Most likley if I am running a non default MTU this will not be in effect on the new switch.

    Hi IP,
    if i was understood properly, you have changed the MTU size of cisco 3750 from default 1500 bytes to 1998(eg.) now even after restarting the switch, this MTU size doesn't come to the default value of 1500 bytes & also when you tried put this config & vlan.dat file you wanted to know whether this changed MTU value will be in effect. Answer is NO, bcoz config & vlan.dat doesn't contain this MTU settings. but you can again manually change the MTU size to 1500 bytes & restart the switch.
    hope this helps.
    rate this post if it is been clarified.

  • VPN MTU Size

    Get this same problem with any Cisco router site-site VPN. Have various customers with 857, 877, 1841, 2811 routers, same problem every time. I'm setting up a VPN with the SDM, link goes up ok, but traffic seems oddly sluggish.
    Installing the Cisco VPN client on all PCs seems to resolve the problem - I'm guessing because it sets the MTU size to 1300 - but you always get this error message when testing the VPN from the SDM:
    Failure Reason(s)
    A ping with data size of this VPN interface MTU size and 'Do not Fragment' bit set to the other end VPN device is failing. This may happen if there is a lesser MTU network which drops the 'Do not fragment' packets.
    Recommended Action(s)
    1)Contact your ISP/Administrator to resolve this issue. 2)Issue the command 'crypto ipsec df-bit clear' under the VPN interface to avoid packets drop due to fragmentation.
    The crypto command doesn't make any difference.
    Any ideas gratefully received.

    I see the same problem - I have a VPN configured across the Internet between a Cisco 2811 router to a Checkpoint firewall.
    Lowering the MTU size on the clients to below the usual 1500 bytes (to below 1300 as specified above) and traffic flows without problem across the VPN. It seems the additional header when going through the tunnel is causing problems.
    Is reducing the MTU size on the router interface a possibility? This may cause increased overhead to the router as it has to fragment each packet, and I understand some firewalls may not even allow fragmented packets through. However, changing settings on users desktops / servers is not very scalable, and there will come a time when this isn't possible (old printers??). Is there any specific configuration advice that can be recommended?

  • MTU And change connection's MTU limit

    Changed MTU to 1472.
    Not open VPN with SonicWALL
    netextender on my PC windows 7
    pro 64 bit
    Should changed MTU on a
    windows 7 pro 64 bit.
    I found a Fixit from Microsoft,
    64 bit, but the error message:
    were not for this computer.
    http://support2.microsoft.com/kb/826159
    This was over for PPP
    connections.
    shall have a fixit for non
    PPP connections.
    Has the internet with cable
    connection. DHCP
    Where can I find such a
    fixit to change the MTU setting
    on nettverksortet to
    1472.
    or a program that can change this.  
    Gunnar                                                    
    gunnar jensen

    Hi gunnar jensen,
    We can change the MTU from the command line.
    Open the command Prompt window and follow the steps below to change the MTU size:
    Type “netsh interface ipv4 show subinterface”.
    Press Enter.
    You will see a list of network interfaces.
    Type “netsh interface ipv4 set subinterface `Local Area Connection` mtu=1472 store=persistent”.
    You should replace Local Area Connection with the name that appeared in the “Interface” column from steps 1-3.
    Press Enter.
    Type “netsh interface ipv4 show subinterface” to check the result.
    Best regards

  • ACE 4710 MTU Size on Interface

    Hello
    I have a Problem with an an ACE4710 Setup. Between my 2 Ace's there are Switches which don't Support Jumbo Frames -
    Is there a way to configure the Interface on the ACE to an Standard MTU Sive (15xx)
    I'm using SW-Version A3(2.7). 

    default MTU is 1500 bytes on an interface. i.e.
    interface vlan 178
      ip address 10.x.x.x 255.255.255.0
      access-group input ALL
      service-policy input MGMNT
      service-policy input jim1
      no shutdown
    MR23100315-ACE01/Admin# show int vlan 178
    vlan178 is up, VLAN up on the physical port
      Hardware type is VLAN
      MAC address is 00:23:8b:03:74:61
      Mode : routed
      IP address is 10.x.x.x netmask is 255.255.255.0
      FT status is non-redundant
      Description:not set
      MTU: 1500 bytes
      Last cleared: never
      Last Changed: Sun May 22 13:37:09 2011
      No of transitions: 3
      Alias IP address not set
      Peer IP address not set
      Assigned on the physical port, up on the physical port
      Previous State: Sun May 22 13:36:03 2011, VLAN not up on the physical port
      Previous State: Thu May 19 15:10:11 2011, VLAN up on the physical port
         8654836 unicast packets input, 2693257658 bytes
         1 multicast, 0 broadcast
         0 input errors, 0 unknown, 0 ignored, 0 unicast RPF drops
         9672812 unicast packets output, 2671360745 bytes
         0 multicast, 8914 broadcast
         0 output errors, 0 ignored
    you can change it with mtu command
    MR23100315-ACE01/Admin(config)# int vlan 178
    MR23100315-ACE01/Admin(config-if)# m?
    mac-address  mac-sticky   mtu
    MR23100315-ACE01/Admin(config-if)# mtu ?
      <68-9216>  MTU size in bytes
    This is configured on the logical interfaces of the ace (vlan interfaces) not the physical gig ports.
    Regards

  • Vm-fex mtu size

    Hello,
    I need to configure mtu 9000 on dynamic vnics (vm-fex vnics).
    But I have not found any guide on how to do it. I followed the vm-fex config guide for KVM, but in dynamic vnic connection policy I have not found any parameter to change the mtu size. By default all dynamic vnics are getting mtu 1500.
    Has anybody some documentation or hints on how to configure mtu 9000 for dynamic vnics (vm-fex) ?
    Sent from Cisco Technical Support iPad App

    Hi Alois,
    The MTU size can be changed to the VM-FEX interface by using a QoS policy in the port-profile.
    This is how you change the MTU size when using Vvm-fex:
    1) Create a QoS policy under the LAN tab,
    2) While selecting a Priority, pick the QoS system class which has a modified MTU size configured.
    3) Create a port-profile to be used by a VMs NIC (which in turn will get it one of the dynamic interfaces)
    4) In the port-profile specify this QoS Policy
    Hope this helps!
    ./Abhinav

  • Wifi traffic MTU size

    For WiFi traffic from source to  destination MTU size should ping up to 1472 Now the MTU is pinging up to  1468 because port level MTU size is 1500 we need to increase 1522.
    while we changing size it will impact my traffic ?
    Model number: WS-C3550-24-DC-SMI
    #sh version
    Cisco IOS Software, C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(25)SEE4, RELEASE SOFTWARE (fc1).
    Any suggestions on this.
    Thanks in advance.
    NagaPrasad

    Hello Prasad,
    Changing the MTU size in general will not cause any impact except if it is VPC domain.
    But it is advisible that MTU size keep same at both ends.
    FYI...
    Changing the MTU value (with the mtu interface configuration command) can affect the IP MTU value. If the current IP MTU value is the same as the MTU value, and you change the MTU value, the IP MTU value will be modified automatically to match the new MTU. However, the reverse is not true; changing the IP MTU value has no effect on the value for the mtu command.
    Please rate the helpfull posts.
    Regards,
    Naidu.

Maybe you are looking for