![]() (that will work on 6200 series FIs, if they are 6300, the command is different) Nxos# show hard internal carmel counters interrupt match mtu* Try running the following on each of your FIs: Personally I would set it back to 1500, unless you know jumbo frames are allowed end to end.Ģnd question, I got a prompt to reboot the HX rack servers I tried to test that on, so I'm guessing you have to reboot to apply the change.Īlso MTU violations will show up CRCs in your FIs/IOMs. VMware is a bit different due to the VMK port, and vswitch/port-groups defaulting to 1500. ![]() I've seen windows boot from iSCSI san cases where the installer started and due to windows baremetal OS reading the 9000mtu setting from the VNIC, it tried to communicate with iSCSI target LUN which of course lost communication due to frames being fragmented and dropped. Other's may question having only a single network with management though and I'd be interested to hear others solutions.For your first question about vnic being set to 9000 when overall network doesn't support it, it depends. On the interfaces tab change from all the IPs to select only the one you want. To configure this, open the DNS manager, select the DNS server and right click and select properties. As such I only see name/ip mappings in DNS for my lab management NIC. ![]() As such the other NICs can't reach DNS to register themselves. A few things I would suggest looking at is:ġ - I don't provide a default gateway on any NICs except the lab management NICĢ - I don't have DNS entries on the 'other' NICs in my environmentģ - I have my lab management NIC ordered first in WindowsĪnd what I believe your issue will turn out to be is:ĥ - in my DNS servers I have DNS enabled ONLY on the lab management NIC. when I look in my AD servers running DNS I only see the lab management network having registered which is why it always responds with the proper IP for the name. I use static addressing, not DHCP for my bare metal servers and only designate my lab management NIC to have DNS entries. I have UCS B and C series server running Server 2012R2 and then have a lot of VM's on top of them with Hyper-V. I am not seeing the issue you are having in my environment. I'm honestly not certain if this is a UCS or a Windows issue at this point.įairly new to the UCS world so any help/insight would greatly be appreciated! There is an application that's going to be used on the box which pings its hostname and with it coming back with the iSCSI subnet IP and not the LAN IP it fails the service since it doesn't think its running.ĭNS is not setup on the 2 vNIC for the iSCSI, we've disabled NETBios xer TCP/IP, changed the bind ordering, changed the metric but to no avail. If we ping a hostname of one of the other servers from the one consoled into it resolves the correct IP from the LAN subnet. If we are on the host of any of the servers and ping the hostname of the server itself of the server we are consoled into it always brings back one of the IPs from the iSCSI pool subnet (192.x.x.x), no matter what binding order we apply in win2k12 it will not bring back the IP on the subnet for the LAN (10.x.x.x). ![]() We have the environment up and running but have run into a issue which is as follows We have a 5108 w/ 5 Blades booting from SAN from a Nimble controller.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |