Nexus 1000v.  Some of the Cisco documents I have seen indicate it is ok to combine two or all of the interfaces for the Nexus 1000v. We would like to combine control and packet on one NIC and keep mgmt on a separate NIC (vlan) in a L2 deployment. Unfortunately when I try to load the ISO I get an error.  Unable to detect three e1000 ethernet devices.  Found only eth0 and eth1. I can not find any document clearly outlining the configurations required to get the switch to work with just two NICs. Please help if you know where the directions can be found. ... View more

All, We had four fully loaded chassis (B series, B200 M2) and the two redundant 6140s reboot yesterday.  It all just died apparently.   We think the issue was power but the event log on the fabrics doesn't go back far enough to show us the start of the event.  We only have events logged showing everything starting back up. Is there a way to gather information from the system that would let us see the 5 or 10 minutes before the system reboot? thanks ... View more

All, We have B Series UCS, version 2.0(1s) with 6140s.  Two connections from 6140A to MDS1 and two connections from 6140B to MDS2.  The physical link is up, the VSAN ids match. The MDS 9148 is running version 5.0(4). I found the pwwn in the flogi database and added it to the zone on the MDS. However we can not establish connectivity to the SAN.  We have noticed that in the fcns database the first server, and the one having troulbe on this new system does not have an FC4-TYPE: Feature.  It is blank and it is the only one.  NPIV is enabled on the MDS.  XX-XXX-MDS1# show fcns database vsan 410 VSAN 410: -------------------------------------------------------------------------- FCID        TYPE  PWWN                    (VENDOR)        FC4-TYPE:FEATURE -------------------------------------------------------------------------- 0x2d2800    N     20:81:54:7f:ee:45:9a:00 (Cisco)         npv 0x2d2801    N     20:00:00:25:b5:0e:01:df                                           <--- why blank? 0x2d2900    N     20:82:54:7f:ee:45:9a:00 (Cisco)         npv show flogi internal event-history msgs 42) Event:E_FLOGI_FAIL, length:20, at 566066 usecs after Thu Feb  9 19:53:03 2012     WWN: 20:00:00:25:b5:0e:01:df  VSAN: 410  ifindex: fc1/43  ev_id: 38     rjt reason: 45 OPC: MTS_OPC_NULL(0) ------------------------ VSAN:410   FCID:0x2d2801 ------------------------ port-wwn (vendor)           :20:00:00:25:b5:0e:01:df node-wwn                    :20:00:00:25:b5:0d:00:ff class                       :3 node-ip-addr                :0.0.0.0 ipa                         :ff ff ff ff ff ff ff ff fc4-types:fc4_features      :   <---- something should be here, correct? symbolic-port-name          : symbolic-node-name          : port-type                   :N port-ip-addr                :0.0.0.0 fabric-port-wwn             :20:2b:00:05:9b:24:3d:b0 hard-addr                   :0x000000 permanent-port-wwn (vendor) :20:81:54:7f:ee:45:9a:00 (Cisco) Connected Interface         :fc1/43 Switch Name (IP address)    :XX-XXX-MDS1 (10.4.x.x) Comparison to working UCS server on this MDS, running 1.4 ------------------------ VSAN:410   FCID:0x2d0d0f ------------------------ port-wwn (vendor)           :20:00:00:25:b5:0c:00:2f node-wwn                    :20:00:00:25:b5:0b:00:2f class                       :3 node-ip-addr                :0.0.0.0 ipa                         :ff ff ff ff ff ff ff ff fc4-types:fc4_features      :scsi-fcp fc-gs  <---- why is the one above missing this feature? symbolic-port-name          : symbolic-node-name          : port-type                   :N port-ip-addr                :0.0.0.0 fabric-port-wwn             :20:19:00:05:9b:24:3d:b0 hard-addr                   :0x000000 permanent-port-wwn (vendor) :20:41:00:05:73:a9:31:c0 (Cisco) Connected Interface         :fc1/25 Switch Name (IP address)    :XX-XXX-MDS1 (10.4.x.x) ... View more