08-10-2012 08:19 PM - edited 03-01-2019 07:09 AM
Dear Mister
Is possible to do the next. I need to have the two protocols in one 10G interface : FCOE and IP.
The scenary is the next. I have a conection from the FCOE toward FC in Nexus 5596. The servers belong to Blade HP is not using a Virtual Connect. The nexus 5596 is functioning like a "bridge" FC. NPV mode.
This part, the VFC traffic toward the FC interface is functioning.
But I have another part not functioning. Is the IP part.
Is possible to do this? Two protocols (FCOE and IP ) functioning in the same wire? In the next configuration, FCOE is functioning, but IP, the vlan 500 IS NOT working. What is the mistake?
This is the configuracion about FCOE and FC.
slot 1
port 41-48 type fc
vlan 300
fcoe vsan 2
vlan 500-549 #Vlan about IP
vsan database
vsan 2
interface Vlan500
no shutdown
no ip redirects
ip address 180.122.228.3/26
ip router ospf 1 area 0.0.0.40
interface vfc37
bind interface Ethernet1/18
no shutdown
vsan database
vsan 2 interface vfc37
feature npv
npv traffic-map server-interface vfc37 external-interface fc1/41-42
npv auto-load-balance disruptive
interface fc1/41
no shutdown
interface fc1/42
no shutdown
interface Ethernet1/18
switchport mode trunk
spanning-tree port type edge trunk
interface fc1/41
switchport speed 8000
interface fc1/42
switchport speed 8000
FCOE:
show npv flogi -table
--------------------------------------------------------------------------------
SERVER EXTERNAL
INTERFACE VSAN FCID PORT NAME NODE NAME INTERFACE
--------------------------------------------------------------------------------
vfc37 2 0x010401 10:00:44:1e:a1:5c:7b:41 20:00:44:1e:a1:5c:7b:41 fc1/42
I need help.
Best regard
08-14-2012 08:44 AM
Unified fabric is all about FC and classical ethernet/IP traffic on the same wire and it should work. When you say IP part is not working. Can you ellaborate?
08-16-2012 02:40 AM
Hi,
I am not an expert but you could try to add the VLANs to the eth1/18 with command "switchport trunk allowed ..."
interface Ethernet1/18
switchport mode trunk
spanning-tree port type edge trunk
as accoring to the config output not all the vlan are allowed.
rgds
08-16-2012 09:33 AM
Thank you .
Well, the problem was in the server. The customer configure a tag 500 in the ethernet interface, and the traffic functioned ok.
Best Regarsd
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide