Nexus 4000 fcoe & ethernet connectivity

[bradleyordner]

Hi!

I have a question about the Nexus 4000. We currently have a Nexus 4000 connected to a Nexus 5000 connect to a 6500 Switch.

We have VLAN 115 for Ethernet & Vlan 1115 for Fcoe.

The FCOE part of the configuration is working, it is doing a fabric login to the 5K by FIP Snooping.

We are having trouble with the Ethernet component, we can't seem to get a response. The vlans are allowed end to end but all mac addresses on the port are visible in VLAN 1115.

How do we get the Ethernet part of the CNA working? The Nexus 4000 does not seem to learn the Ethernet MAC from the CNA.

Thanks

Brad

[ddulek]

How is the port on the 4k defined?

Which CNA card are you using?

Which OS is the server running?

[bradleyordner]

Hi,

Port on the 4k -

interface Ethernet1/5
  switchport mode trunk
  switchport trunk allowed vlan 1,115,1115
  spanning-tree port type edge
  speed auto

CNA used -Qlogic....the 4 k is part of the IBM Blade Chassis

OS on 4K - n4000-bk9.4.1.2.E1.1b.bin

We also modifed the native vlan to VLAN 115 which the MAC appeared in VLAN 115 but still no connectivity. From the looks of things, the ethernet part takes the native vlan, now is this probably because the server is sending an untagged packet, as it may not be setup to do dot1q trunking.

[ddulek]

Do you have other blades that are working on this chassis?  It could be a driver issue or a misconfigure on the blade itself that is causing the issue.  How is connectivity being tested?

[bradleyordner]

We have tried two blades with no sucess.

We have assigned an IP Address to the ethernet ports and cannot ping them.

We have IP connectivity to the 5K, anything beyond that on the 4K is unreachable.

[ddulek]

On the blades themself, can you ping the IP that you have assigned them?

If so, what about the default gateway?

Are you statically assigning an IP?

Verify on the blade OS that the interface is up and the IP is assigned.

[bradleyordner]

We have got Cisco TAC involved now. Seems the Nexus 4000 with a static IP and a Nexus 5000 with a static IP can't ping each other ov

er a trunk link....very wierd issue....mac addresses seen in correct VLAN but no ping.

[aviyoshi10]

Hi,

i understand that you succeeded with FCoE between N4K & N5K.

can you please send me the configuration ?, the ETH vlan is up but i cannot see the MAC for the FCoE vlan under show fip-snooping vlan discovery.

many thanks,

Avi.

[sbhadrav@cisco.com]

The 4000 Series switches extend the benefits of the Cisco Nexus Family to blade servers. The series addresses the challenges of having more switches and cables in a single chassis, implementing virtual machine mobility, and meeting high bandwidth and power requirements. These Fibre Channel over Ethernet (FCoE) switches are fully compliant with the IEEE Data Center Bridging specification.

[sbhadrav@cisco.com]

Before following the steps in this example, be sure to complete a basic configuration on the Cisco Nexus Series switch (for example, IP Address (mgmt0), switch name, and password for the administrator) and FCoE has not been enabled.
To use this configuration example in production, you must have the FC Features Package license installed otherwise there will be a temporary license that expires after 90 days. When the license expires, the feature is disabled.
On the Cisco Nexus Series switch, by default FCoE is not enabled.
This example shows how to enable FCoE:
 n4k-2# show interface brief
There are no FC interfaces, even though there is a 4x4 GEM card installed in the Cisco Nexus 5010 switch.
 n5k-2# configure terminal
 Enter configuration commands, one per line. End with CNTL/Z.
 n5k-2(config)# feature fcoe
 FC license checked out successfully fc_plugin extracted successfully FC plugin loaded
successfully FCoE manager enabled successfully FC enabled on all modules successfully
Beginning with Cisco NX-OS Release 4.1(3)N1(1), the switch does not need to be reboot when you enable FCoE. The Cisco Nexus 5000 Series switch is in switching mode by default when FCoE is enabled.
 n5k-2(config)# show feature
 Feature Name Instance State
 fcsp 1 disabled
 fcoe 1 enabled
 fex 1 enabled
 n5k-2(config)# show interface brief