trunk VSAN 6248 uplink interface

Hi all

I'm new to the UCS platform,

I want to master multiple VSANs in FI 6248 on the single interface / portchannel. to 5548 upstream switch. Since the location of different heterogeneous storage 2.

Ask let me know opportunities, configurations or any recommendations are available for configuring it.

Hello Christine,.

You can enable port FC port trunking and create port channels for FI of UCSM CF (SAN tab > SAN clouod).

On N5K, you must enable fport-channel-trunk feature and create CF port-channel.

Padma

Tags: Cisco DataCenter

Similar Questions

VLAN Trunking between 6248 and 2848

Hello

I have a Powerconnect 6248 switch connected to a 2848 and I try to get a VLAN on the 2848.

VLAN working and properly receive DHCP addresses, traffic lanes and DNS runs on the 6248.

The Protocol DHCP, DNS server is connected to port 1 on the 6248.

When I create a Trunk port on 3 the 6248 Port, allow all VLANS through it, creating a trunk on port 1 of the 2848 on VLAN10 and try to plug in devices inside, they can see all other devices connected to the L3 switch.

The two switches are running the latest firmware and the L3 on his own works as expected. I can't get any kind of circuits working at L2, tried with normal cable and crossover switch.

Here is the config of the L3 6248. Switch 2848 L2 has a blank canvas with 10 VLANS created on ports 1,2,3,4 with port 1 as the trunk port installation.

Any ideas pleeease? Anyone? It drives me crazy.

************************

_{! Current configuration:}_{! Description of the system "Powerconnect 6248, 3.2.0.7, VxWorks 6.5.}_{! Version of the software system 3.2.0.7}_{! Passage mode is configured as disabled}_!_Configure_{database of VLAN}_{VLAN 10,20,30}_{VLAN 10 1 routing}_{VLAN 20 2 routing}_{VLAN 30 3 routing}_output_battery_{1 2 Member}_output_{the IP 192.168.0.1 255.255.255.0}_{field of IP domain name}_{name-server IP 192.168.1.10}_{IP routing}_{interface vlan 10}_Routing_{IP 192.168.1.1 255.255.255.0}_output_{interface vlan 20}_Routing_{address 192.168.20.1 255.255.255.0}_{IP helper-address is 192.168.1.10}_output_{interface vlan 30}_Routing_{192.168.30.1 IP address 255.255.255.0}_{IP helper-address is 192.168.1.10}_output_{level password user name 'administrator' encrypted 15 5f4dcc3b5aa765d61d8327deb882cf99}_{l2relay DHCP}_{DHCP l2relay vlan 10-90}_!_{interface ethernet 1/g1}_{switchport mode general}_{pvid switchport General 10}_{No switchport acceptable-framework-type general tag only}_{VLAN allowed switchport General add 10,20,30}_output_!_{interface ethernet 1/g2}_{switchport mode general}_{pvid switchport General 10}_{No switchport acceptable-framework-type general tag only}_{VLAN allowed switchport General add 10}_output_!_{interface ethernet 1/g3}_{switchport mode trunk}_{switchport trunk allowed vlan add 10.20}_output_!_{interface ethernet 1/g4}_{switchport mode general}_{pvid switchport General 10}_{No switchport acceptable-framework-type general tag only}_{VLAN allowed switchport General add 10}_output_!_{interface ethernet 1/g5}_{switchport mode general}_{pvid switchport General 10}_{No switchport acceptable-framework-type general tag only}_{VLAN allowed switchport General add 10}_output_!_{interface ethernet 1/g6}_{switchport mode general}_{switchport General pvid 20}_{No switchport acceptable-framework-type general tag only}
_{VLAN allowed switchport General add 20}_output_!_{interface ethernet 1/g7}_{switchport mode general}_{switchport General pvid 20}
_{No switchport acceptable-framework-type general tag only}_{VLAN allowed switchport General add 20}_output_!_{interface ethernet 1/g8}_{switchport mode general}_{switchport General pvid 20}_{No switchport acceptable-framework-type general tag only}_{VLAN allowed switchport General add 20}_output_!_{interface ethernet 1/g9}_{switchport mode general}_{switchport General pvid 30}_{No switchport acceptable-framework-type general tag only}_{VLAN allowed switchport General add 30}_output_!_{interface ethernet 1/g10}_{switchport mode general}_{switchport General pvid 30}_{No switchport acceptable-framework-type general tag only}_{VLAN allowed switchport General add 30}_output

After turning off spanning tree on the 2848, all works now.

VLAN, trunking everything.

Thanks for the help! :)

I hope that if someone else can use what it took me ages to develop. I plugged on Netgear switches etc and they seem to work.

The issue was going on between the dell 6248 and 2848, Spanning tree is enabled on the default 2848. If I was going to the Netgear via the 6248, then at the 2848 switches worked.

My config on the l3 also works very well if someone would use :)

Channel ports (connection linked to the North) and uplink interface (private storage switch)

Hello

What will be the best configuration if I connect 2ports north bound connection and has been applied to the port channel. and I go to configuration 2ports uplink for storage (private switch) interface. All cisco switches.

2 x 2104XP IOM

2 x FI 6120XP

Thank you.

Dexter

Hi Dexter,

Since you will have two / several switches uplink to which you will have an Ethernet to the North, a what you will have to configure is the layer 2 disjoint.

You must be on any version 2.0 to configure that.

Here are a few documents to help you with the details:

http://www.Cisco.com/en/us/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-692008.html

http://www.Cisco.com/en/us/docs/unified_computing/UCS/SW/GUI/config/Guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_010101.html

Thank you!

. / Afonso

FCoE uplink is down on vsan

Hello, I have a problem connecting nexus switches in the fabric of the interconnections.

I created of vsan, vlan mappings of vsan unified uplinks, vfc interfaces on nexus, but I still see this flaw in the registry.

Models of HBA and HBA is created.

I have 2 5548up nexus switches connected to the UCS 6324 FI.

I hope your 500 vsan has FC zoning "disabled".

Before you setup zoning, your blades won't see any logical unit number.

Make the zoning on the N5k, and activation areas will repel the active zone to FI information.

is excluded them VLAN interfaces in the GAL

Hello community,

I have a problem with the configuration of LAG on Cisco SFE2010P 3xSwitch battery.

The switch has in fact only web GUI. Console - too, but it is not very useful.

I need to configure Interfaces 1/g3 and g3/2 in one SHIFT. And VLAN (vlan by default) of 60 and 110 (voice), through to allow.

After that I configured the LAG with both interfaces, "Port of Vlan" LAG settings show me the vlan 60 is untagged and vlan 110 is labeled.

But if I take a glance on the 1/g3 Interfaces and "Port to LAN" settings 2/g3, both VLAN interfaces are "excluded". I can't access the default gateway, which is directly connected with this settings. The default gateway is a 3750Stack whose address IP of HSRP. It has two uplinks in port the SFE2010P channel.

I have only one Interface to 100 Mbps on the SFE2010P connected to a trunk on the spine interface. And it works in this way. But using the links LWL LAG now does not work.

Why are the VLAN 60 and 110 is excluded on the interfaces in the GAL and how can I change it? Thank you.

Thank you

Sergej

Hi Sergei, you cannot configure the individual port within an OFFSET to a vlan. When you join the VLAN, you must select the offset group, not the individual port.

-Tom
Please mark replied messages useful

Host adapter interface 1/2/1/1 status of the link down

Dear all,

can any one help I have an error 'Host interface 1, 2, 1, 1 link adapter state down' and none of my network cards coming State 'up' error F0207. I'm on 2.2 (6f) and chassis as channel ports policy, set the server ports as two for each FI and they are up and running.

Any ideas?

Thank you

Actually, it isn't 4094, we have another VSAN defined in the N5K and for use in case of problems, it is replaced by default and I forgot to restore. We have this problem earlier when he used the same VSAN that is defined in the N5K.

Here is the output while he was assigned to the VSAN that is defined in N5K (1100)

Show vfc int 709
vfc709 is the trunking (not all VSANS upward on the trunk)
The related interface is port-channel80
The material is Ethernet
Port WWN is 22:c4:8 c: 60:4f:d2:01: ff
Port admin mode is NP, trunk mode is enabled
State link SNMP notifications are enabled
Port mode is PNT
Port vsan is 1
Trunk VSAN (authorized and active admin) (1.1100)
Trunk VSAN (top) (1100)
Trunk VSAN (isolated))
VSAN trunk (boot) (1)

You were right about the installation.

Network management using a trunk for the connectivity port

Hi all
I'm currently developing a couple of hosts with a unique vswitch esx. Ideally, I would like to allocate 4 physical NICS on the host to connect to my physical network via 802. 1 q trunks. These network interface cards will then be used by some groups of ports for example vlan 10,20 and 30. I also want the Group of ports management network the vswitch using one of/all of these ports of junction for its uplink to the physical network. However, I seem to lose connectivity to the host whenever I put the port network management group vmnic to one vmnic that is attached to an uplink of trunk. If I allocate an uplink access and secure it to the management network port group I do not seem to have everything get to the problem of the host.
I have to do something wrong as having to use a physical network adapter, mapped to a vlan access, just for hospitality management seems a bit exaggerated.
Any advice would be greatly appreciated.
See you soon,.
CiscoKid

Hello Ciscokid,

is not a problem to achieve what you want. What VLAN id you use for the management network? You specify this number VLAN on the portgroup of management?

Do you have any "vlan native" on the physical switch port?

2960 will not allow "switchport trunk encapsulation dot1q" CLI

I have a Cisco 2960 switch that does not allow me to configure the switchport trunk encapsulation dot1q on a trunking interface.

The features of the watch that the interface can use 802. 1 q, but when I try to CLI the command encapsulation of work is not an option.

Please give us a solution.

Thank you, S

Model - WS-C2960G-24TC-L

Version SW - 12.2 (44) SE6

Image of SW - C2960-LANBASEK9-M

S1 #.

S1 #sh int gi0/23 capabilities

GigabitEthernet0/23

Model: WS-C2960G-24TC-L

Type: 1000BaseLX SFP

Speed: 1000

Duplex: full

ENCAP of trunk. type: 802. 1 q

Trunk mode: on, off, desirable, nonegotiate

Channel: Yes

Removal of broadcast: percentage(0-100)

FlowControl: rx-(off,on,desired), tx-(none)

Fast Start: Yes

QoS scheduling: rx-(not configurable on a per port basis),

TX-(4q3t) (3T: two configurable values and one fixed.)

Rewrite coS: Yes

ToS rewrite: Yes

UNI-DIRECTIONAL: Yes

Food online: no

SPAN: source/destination

PortSecure: Yes

Dot1x: Yes

Several Types of media: rj45, sfp, automatic selection

S1 #.

S1 #.

S1 #.

S1(Config-if) #switchport?

Set the access mode characteristic of the interface

Backup set for the backup interface

block disable them unknown addresses forwarding uni/multi interpreters

host port Set

the interface Set trunking mode

nonegotiate device engage not in the negotiation protocol on this

interface

port-security security associated with order

priority Set 802 .1p device priority

protected configure an interface to be a protected Harbor

trunk trunking features Set of interface

device attributes voice voice

S1 #.

S1 #.

S1 #.

S1(Config-if) #switchport trunk?

admitted only allowed together features VLAN when the interface is in binding mode

native definition trunking features native when the interface is trunking

mode

pruning pruning Set VLAN features when the interface is in binding mode

S1 #.

S1 #.

S1 #.

New devices do not support ISL so you can run 802. 1 q. This means there is no need of an encapsulation command what an encapsulation being supported. If the device has support for ISL, then you must also this command.

Daniel Dib
CCIE #37149

Please evaluate the useful messages.

Interface WLC 5508 AP-Manager

Hi, I own a WLC 5508 and (probably), I do not understand the AP Manager interfaces. I have a laboratory with 2 x 1242AG and 1 x 1252AG connected to c2960. APs in vlan 10 (192.168.10.0/24, configured via DHCP), APs are connected to interface 'switchport access mode. C2960 is connected via a trunk to c4506 and WLC is plugged into article gi1/3 and article gi1/4 (both through twingig). The two ports are configured as 'switchport mode trunk ". WLC management interface is IDE oucederomsurlesecondport WLC 8 (linked to article gi1/4), and AP-Manager is on port 1 (connected to article gi1/3) WLC. WLC management interface has 'Management dynamic AP' set to off, and AP-Manager defined activated. The two are interfaces to management and AP-Manager tag, vlan id 12 and 13 (subnets 192.168.12.0/24, 192.168.13.0/24) respectively. APs receive their IP through DHCP configuration (server located in vlan 20, 192.168.20.0, in use ip helper-address) and try to discover DNS resolution WLC (CISCO-CAPWAP - CONTROLLER.some.domain resolves to AP-Manager IP correctly). But AP has the status "not connected" in monitor/statistics/AP join APs do not join to the controller, said WLC "Discovery request Ignoring received on the management interface".

But if I put management interface as "Dynamic AP activated" and change the DNS to resolve CISCO-CAPWAP... it's IP everything works well - AP is associated with the time. Please help, how to reach the KNEES a AP-Manager interface? Sign up for the Manager of WLC is simple, but my design requires at least 2 interfaces AP Manager.

If you have a 5508, why you have the AP Manager?

FEX Uplink and Ports on the side Server

I am very new to the environment of the UCS and having to return to the current fairly quickly. I decided to start with the chassis. But have a few questions.

I hope someone can clarify how serverside ports are assigned less than ports uplink, 2204XP and 2208XP.

My understanding is that the side ports server are assigned to the uplinks based on the number of uplink configured at the END.

Once the FEX is initialized ports are hardcoded.

Assuming 2 (6200 series) FI and 2 FEX (2204).

2 each to their respective FI FEX uplinks

8 blades width in the chassis.

My understanding is;

Uplink port 1 receive blades (1, 3, 5-7) and uplink 2 (2, 4, 6, 8)

Question: Which ports are active for each blade and that FEX.

For example the blade 1 assigned to Uplink on FEX A 1 with FEX B 1 uplink failover

Blade 3 assigned to Uplink on FEX B 1 with FEX A 1 uplink failover

Thanks in advance people...

Hello and welcome to the community,

"" My understanding is that the side ports server are assigned to the uplinks based on the number of uplink configured at the END.".

Server ports are assigned to connections rising from ports either automatic (load balanced by available uplink interfaces) or manual pin (PIN LAN groups hard coded)

2 fIs and IOM 2204 2 with 2 cables on each IOM: "UpLink port 1 receive blades (1, 3, 5-7) and uplink 2 (2, 4, 6, 8)" "< this="" is="" correct,="" odd="" blades="" through="" odd="" ports="" and="" even="" blades="" through="" even="">

Which ports are active for each blade and that FEX.?

In this case with a 2204, IOM provides 16 internal ports, 2 for each blade, and you can check which one is active with the command "Show software platform woodside m" mode FEX which is realized with the following commands:

UCS # connect the IOM

FEX-1 # display software platform woodside m

You can also go to the vNIC itself in the "Servers" tab by going to the Service profile > network and then double click on in the vNIC and you will see the configuration:

For example: blade 1 assigned to Uplink on FEX A 1 with FEX B 1 uplink failover

Blade 3 assigned to Uplink on FEX B 1 with FEX A 1 uplink failover

This will be the case if you have the 'discovery of the chassis/FEX policy' located in the 'grouping preference link' on 'None' instead of 'channel of Port "; If it is "Port Channel", I won't miss not until all other links fail in the same module e/s, see below

NOTE: this option is valid only if your hardware is ALL second generation, in other words, it does not work with fabric 61xx interconnections or 2104 IOM

I hope this helps, if it does, please note it.

-Kenny

Note ensure on the limitation of the function of the channel port between IOM and the tissue Message was edited by: Keny Perez

Pass the trunk between catalyst and PIX

Hello

Yesterday I had very good response on the forum how to create the VLAN on PIX, I created the subinterfaces and VLAN which their responsibilities. I configured the IP addresses as well. Did the same on the switch of Cat - created SVI and assined their IP add back. Cat shows switch port trunking is correctly but I can't ping from PIX to the switch and vice versa. Help, please.

RVR

Is it possible for you to view the configuration of the PIX? At least the configuration of the interface?

And configuration of the trunk on the switch interface?

Concerning

Farrukh

Mesh of Trunking

I recently inherited a network of mesh of all 6 PA campus and 14 cards. We have 4 switches remote, met through cards. As-is, the network works, but there are things that we would like to clean and sustainable on the local network.

In their current state, most of the remote switches use only 1 VLAN. We would like to separate the traffic as we do in the rest of the network. I had questions, get the circuits over-the-air implemented. As many have said, the Cisco documentation is very confusing. I got a glimpse of Scott powerpoint, but I still have problems of implementation. This is a part of the sample of what we have and what we're trying to accomplish. (All the management interfaces are in VLAN 95)

Current state:

[CORE]-> [SWITCH-NATIVE95]-> [RAP (normal Interface)] ~ ~ ~ [map-(Interface normal)]-> [REM-SWITCH-NATIVE95]

In this State, anything in VLAN 95 connects to the rest of the network, but nothing outside of VLAN 95 does not. If I flip to the trunk, with a map interface VLAN 95 native, I can ping everything in other virtual local networks, but lose connectivity to the switch.

That's what I've tried today, with 95 and my other VLAN as VLAN allowed (on the switch and the map):

[CORE]-> [SWITCH-NATIVE999]-> [RAP (Normal Interface)] ~ ~ ~ [MAP-(Trunk-Native999)]-> [REM-SWITCH-NATIVE999]

This also resulted in no connectivity to the switch. I also noticed that the cards which normally will connect to this RAP all chose to also connect.

I read that the interfaces of the RAPs should always be set to normal and you will get a warning when you try to set it on the trunk. I tried to put it in the trunk and had no warning, so I tried this:

[CORE]-> [SWITCH-NATIVE999]-> [RAP(Trunk-Native999)] ~ ~ ~ [MAP-(Trunk-Native999)]-> [REM-SWITCH-NATIVE999]

I got the same result as with the entire interface to normal. Also could not get map of reliably connect to the RAP even to do a controlled test.

Issues related to the:

What I am doing wrong? How the interfaces must be paid to the live trunk?

I have been comforted in [REM-SWITCH] and didn't get all messages misconfig VLAN, but I noticed the RAP up and down intermittently through NCS. SpanningTree would be a problem?

The AP management interface must be in the VLAN native?

Is it possible to force a card to connect to a RAP in particular?

(Access points in cisco AIR-CAP1552I, WLC-5508 worm 7.2.111.3)

Ok.. So after RAP and put perfectly using map:

> RAP and map should be in the same vlan and should not be in the vlan 1.

> Favorite parent command allows you to make the card to join a particular RAP or use different BGN.

It will behave like this on 7.2:

# With Vlan active transparent:

RAP and switch ports configured exactly the same card.

No configuration is necessary on the map and the RAP.

Only the VLANs native will be able to communicate through the RAP switch and card. 7.2 code tags vlan are stripped and only traffic VLAN native was able to communicate through the. So if vlan 262 is the vlan native and vlan 20 and 30 are allowed VLANs on the Switchport RAP switchport and the card, then only vlan 262 will be able to communicate through the stitch.

https://Tools.Cisco.com/bugsearch/bug/ CSCub63054

In 7.0 and 7.5, it has started to behave properly. So here with Vlan enabled transparent, RAP and card switchport configured correctly and in the same way, all the VLANS including vlan native will be filled in full transparency.

##With vlan disabled Tranparent i.e tagging vlan enabled:

RAP and card switchport configured the same way.

CARD interface configured the same way IE with even native and allowed VLAN. GUI > AP > mesh > Gigabit 0

RAP - no configuration required: automatic using save vlan

With this configuration in place, all the VLANS allowed will be able to communicate through the bridge. Do not share of vlan native on bridge design to avoid loops.

Concerning

Delphine

VLAN Trunking on vSS

Hello
I need trunk VLAN on vs.
Say there are three VLAN 10,20 and 30.
I am able to create the trunk on switch uplink physical, but not able to find out if how it should be done on vs.
Kind regards
Sushil

To configure the VLAN Tagging, you can define a VLAN on a PortGroup.

Let's say you want to have VM1 in VLAN 10, VM2 in VLAN 20 and VM3 in VLAN3.

Then, you can create 3 exchanges each with different VLAN as screenshot below

Connect to each appropriate virtual with PortGroup computer.

There is not something like "switchport mode trunk" in vSwitch, simply configure a VLAN ID in the PortGroup.

See this KB: VMware KB: VMware KB: example configuration of the virtual switch VLAN tagging (VST Mode)

Ethernet VMware with Cisco EtherChannel and Trunking Question

Hello
Trying to get our etherchannels works correctly with our network administrator. Here is our config with a few questions.
1. as it is to create the trunk between switch and host directly, can I use spanning tree portfast chest edge ?
2. when don't we use no ip address and when not for this configuration? I see online showing examples with and without it.
3. in some articles, he described in access mode , while in others he said dot1q trunk mode. See here for the access mode. Admin think it should use dot1q.
4 Etherchannel is fully support and preferred extending from links on maps, right? Not all of the links on the same card?
5 is this the case in order to change the load balancing algorithm in vmware first or first to the work of cisco? I did first vmware. (IP-hash)
It's on a series with 4 cards/blades 6500 switch.
```
!
interface Port-channel200
 switchport
 switchport access vlan 81
 switchport trunk encapsulation dot1q
 switchport trunk allowed vlan 69,81,172,896
 switchport mode trunk
 switchport nonegotiate
!
interface GigabitEthernet2/35
 switchport
 switchport access vlan 81
 switchport trunk allowed vlan 69,81,172,896
 switchport mode trunk
 switchport nonegotiate
 spanning-tree portfast edge
 channel-group 200 mode on
!
interface GigabitEthernet8/10
 switchport
 switchport access vlan 81
 switchport trunk encapsulation dot1q
 switchport trunk allowed vlan 69,81,172,896
 switchport mode trunk
 switchport nonegotiate
 spanning-tree portfast edge
 channel-group 200 mode on
```
DITGUY2012 wrote:

Wow Josh. If only you had written documentation. That's the trouble with him. People like me get final instructions, because we're not the guys from network 24 x 7. Great documentation would be layout, the reasons to go this way or that way you did just. That being said, here's my summary based on this discussion.

1. we have several VLANS that descends from 3 links on the etherchannel. Thus, we should use mode trunk because there is not a single.

2. we have an another etherchannel with just 1 vlan (vmotion), but in all of two links. This should be the access mode. Or is it still trunk because it's the multiple links?

3. I don't know what crash dump logger is, or how it applies to my situation.

4. I saw the bpduguard setting before what exactly is the syntax to use for us? 6500 series.

5. I don't know if our switch would deliver on that port. How can I tell? At this moment I have switchport setting in there.

Thank you!

No problem for reference, the other question of documentation is one of the languages. Their word etherchannel on HP networking hardware, 'trunk' and has nothing to do with the discussion of port "access vs circuit", which they call "tag unidentified vs.

1 Yes

2. you would certainly make an access port.

3. If your server never begins to have a problem with break, VMware can a copy of the accident for the debug log. You can see an article on setting up here: put in place the collector of Dump ESXi 5.0 | VMware vSphere Blog - VMware Blogs.

4 I'm sorry I'm not familiar with this model

5. I think if the switchport parameter is here and connectivity seems to work, you can consider yourself safe

6248UP FI Cisco Nexus 5Ks connectivity

Hi guys,.

Can someone advise me please on how best to implement the following connections?

I am trying to connect a pair of fabric of interconnection (6248UP with 32ports) to a pair of Nexus 5Ks (5548UP) with the 5Ks linking directly to the storage (CEG). It is a small deployment. The 5Ks will run full Services of fabric such as zoning configuration, etc. Either way, vPC will be running between FIs them and 5Ks ethernet only for traffic.

My question is:

1. what type of connection should I use between the 6248UP - FIs and the pair of 5Ks. should I configure say 2 ports on FIs them as Uplink FC ports and use an FC SFP (e.g. DS-SFP-FC8G-SW) for connections? In this way both the 5K and the FI will be clocked in-between native FC to 8G. What is the best practice?

2. is it possible to operate the FI directly to the 5Ks FCoE and just running the native FC from the 5 K to the EMC storage?

3. is there a doc from Cisco or a blog I can be pointed to which could contribute to the best practice for this scenario?

Answers or any other suggestions will be appreciated.

Thanks in advance...

Hello Luke,.

You can update to 2.1.1a UCSM

Here is example configuration for FCoE between FI and N5K switch.

# On UCSM # 2.1

(1) CF end mode

(2) configure a port as uplink FCoE and affect the VSAN 10 interface

http://www.Cisco.com/en/us/products/ps10281/products_installation_and_configuration_guides_list.html

# Check the output

See 01-6248-A (nxos) # run int vfc 1255

interface vfc1255

link interface Ethernet1/24

NP switchport mode

no downtime

# Configuration on N5K #.

(1) enable NPIV functionality, fcoe and lldp

(2) create the VLANs, configure ethernet and interfaces VFC

-example of configuration-

conf t

VLAN 1001

FCoE vsan 10

interface Ethernet1/19

switchport mode trunk

edge of the spanning tree port type

spanning tree enable bpdufilter

no downtime

VFC int 14

link interface Ethernet1/19

switchport trunk allowed vsan 1

switchport trunk allowed vsan add 10

no downtime

VSAN database

VSAN interface vfc 119 10

------------------------------------

# Comands to check the configuration.

displayed in the function

Show vlan

Show fcoe vlan

Show int vfc 119

See the database of fcoe

show flogi table

Padma

trunk VSAN 6248 uplink interface

Similar Questions

Maybe you are looking for