Forgot that the command is for 6200 series FI and you are using UCS mini, hence it didnt worked.   If, as you mentioned, that configuring Jumbo MTU on Best effort class, this worked; it means that the issue is with tagging the packet correctly for gold class at either end. Looks like you have configured jumbo MTU correct but one of the ends is not tagging it correctly for Gold class, hence it ends up in best effort class. On UCS make sure that you have configured jumbo MTU on vnic as well on Gold class policy and have assigned this policy to the vnic. ... View more

Agreed with the comment above, that you should not have a UCSM managed NIC card, for a integrated server, not connected to FIs. However unsure if Intel X520 is UCSM managed.   The original issue does not seem with setup, but as you already identified, with VMware kernel switching which seems to be allowing isolated pvlan ports to communicate. When the VMs are on different hosts the traffic goes to upstream switch (from DvS perspective) and, as you said, it works in this case. ... View more

Hi   The appliance port traffic will never traverse the Uplink ports, the reason same VLAN is required to be configured and it appears to be pinned to an uplink port, is how the appliance port is treated internally within UCSM (ie it is treated similar to a vnic and hence pinned to a uplink port). The traffic between UCS server to FI (appliance port) will directly go to the Storage. Note that you dont need to configure this VLAN on upstream switch, since this is not required, and in your case you also dont need Jumbo MTU on 4500. Note that since appliance port is pinned to an Uplink port, in an event that uplink port goes down, the appliance port will also be brought down though it is not physically down. Again this is just how a vnic is brought down when the pinned Uplink port goes down. So its best to have uplink as a port-channel.   It looks like Jumbo MTU config is still not applied or not correctly configured end to end, thats why the ping fails. To test this in UCSM CLI run "connect nxos" and then " show hardware internal carmel counters interrupt match mtu " on both FIs. Start ping and check the values before and after the ping fails. The value on the port will increment if there was an MTU violation because of jumbo MTU.     ... View more

Driver release notes mention what bug was fixed, or feature added, to the new version. Those fixes will still be there in newer releases than the recommended version.   A driver downgrade is sort of like brute method to try to fix the issue (as it involves a complete reboot of the system) rather than a precise answer. Though it can uncover new bugs. ... View more

Hi   Do the existing 3 port-channels carry all same vlans (default behavior) or you have segeregated vlans on different port-channels?   In the first case, ie carry all vlans (default behavior), you can create a new port-channel and add new uplink ports to it (you can even move ports from existing port-channel, but dont move all ports as it will bring down that port-channel) and this will not cause a re-pinning of vnics. Re-pinning will only happen when exisiting pinned uplink goes down, ie when you finally shutdown the existing port-channel/s.   In the second case, which is more likely, that you have vlans segeregated on different uplink port-channels, you will need to manually add the vlans to the new uplink port-channel. Again, this wont cause an automatic re-pin of the vnics if the existing pinned uplink is working.   In any of the scenarios it is not recommended to have same vlan on two or more different uplink port or port-channels (ie the first case discussed above), as this causes issue with broadcast and multicast traffic for UCS.   Also note that if you ahve configured manual vnic pinning then you will need to change this to pin to the new uplink port-channel after this comes up. ... View more

Hi   Yes, you can use a newer driver version than the version recommended in HW/SW compatability matrix. ... View more

Do you also get similar message when login to UCS manager? What is the domain name you are using? There is a 32 character limit in UCSM for username. As per document " For systems using remote authentication protocol, the authentication domain name is considered part of the user name and counts toward the 32-character limit for locally created user names. Because Cisco UCS inserts 5 characters for formatting, authentication will fail if the domain name and user name combined character total exceeds 27 " The UCS Central document also mentions this limit but only for RADIUS authentication. " For systems using RADIUS, the authentication domain name is considered part of the user name. Therefore, it counts toward the 32 character limit for locally created user names. Because Cisco UCS reserves five characters for formatting, you cannot have a combined total of more than 27 characters for the domain name and user name " ... View more

Q: How can I verify which vNIC inside UCS represents vmnic1 and vmnic2 inside vsphere? A: Usually vnic1 is vmnic1 in vSphere. In case of doubt, check the mac address in UCSM and vSphere to map these. ... View more

Hi VIC 1227 does support aRFS, however the firmware and driver support is also required. Is the adapter configured for aRFS? If the server is manged by UCSM you can config as per http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/2-2/b_UCSM_GUI_Configuration_Guide_2_2/b_UCSM_GUI_Configuration_Guide_2_2_chapter_010101.html#concept_F619741FCCCA4E20A4166901A793DF02 ... View more

Hi Per This depends upon your setup. UCS can directly connect to NetApp, using appliance ports; however if you are doing native FC and need to configure zoning you will have to use FC switching mode. Following documents explain these scenarios http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-5100-series-blade-server-chassis/116075-ucs-app-connectivity-tshoot-00.html http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-infrastructure-ucs-manager-software/116082-config-ucs-das-00.html ... View more

Hi gustavo Chassis discovery policy only describes that how many links are necessary for the chassis to be discovered, and initially these links come up. After this if you do a reack of chassis all the links will come up. To check how many ports are being used, in the UCSM GUI Equipments tab expand Chassis > IO Modules > Fabric ports.  ... View more

Hi vantonenko It is common for security appliances (like FWSM) which are doing IP proxy to reply to IP address query; however this is supposed to be for outside network and not for the same subnet. Check the config on your FWSM. ... View more

Hi slipherslipher you can connect the breakout cable from C3260 to N2k in portchannel. Note that this has to be a static portchannel (mode on) instead of LACP (mode active). ... View more

I believe the following is what you are looking for https://supportforums.cisco.com/document/12500371/expert-webcast-slides-cisco-ucs-mini-architecture-troubleshooting-and-upgrade ... View more