Layer 3 config design on Nexus 5500 with Fabric Path

I trying to Network deisgn for new data Center , i am new to DataCenter desgin, i attached the network diagram
i would like to know if can configure my layer3 on 5500 and configure Fabric path to uplink switch
please help give your suggestions on this design

You can configure layer-3 on the 5500 series, but you need to install a daughter cards in each 5500.
See this link:
Layer 3 Daughter Card and Expansion Module Options for Cisco Nexus 5548P, 5548UP, 5596UP, and 5596T Switches
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/data_sheet_c78-618603.html
HTH

Similar Messages

Uplink-ID 0 in Nexus 5500 with FEX 2248.

Hi all,
I've got 2 Nexus 5548 and a fex 2248 connected to both of them via a vPC. 1 Uplink port goes to N5K-01 e1/10 and a second Uplink port goes to N5K-02 to port e1/10.
On the log of the first Nexus 5500 I see this:
N5K-01 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet1/10 changed its status from Configured to Fabric Up
N5K-01 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 103 that is connected with Ethernet1/10 changed its status from Fabric Up to Connecting
N5K-01 1 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 103 that is connected with Ethernet1/10 changed its status from Connecting to Active
On the log of the second nexus 5500, I see this:
N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet1/10 changed its status from Configured to Fabric Up
N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 103 that is connected with Ethernet1/10 changed its status from Fabric Up to Connecting
N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 103 that is connected with Ethernet1/10 changed its status from Connecting to Active
What is the difference between Uplink-ID 0, 1 and 2? If I only have 2 uplink ports, why is there a third one?
Thanks in advace for your assistance.

Hi Sonu,
I see the similar problem on my nexus5ks. show cfs peer does not display the peer information. I have been waiting for hours now.
sw01# sh cfs peerCFS Discovery is in Progress ..Please waitCould not get response. The network topology may be under going change.Please try after about 30 seconds
Did you find the fix7workaround of this problem ?
Regards,
Umair

Connecting the nexus 5500 with multiple vsans

Hi,
it's my first experience in the fibre channel world and i have a few doubts about the best way to connect the nexus 5500 to a EMC storage.
This is my scenario
this is my configuration:
vsan database
vsan 2
vsan 2 interface fc 1/1
vsan 3
vsan 3 interface fc 1/2
interface fc1/1
switchport mode f
no shut
interface fc1/2
switchport mode f
no shut
now I don't know how can I connect the port fc1/3 to the vnx storage, I think I can't make a trunk like ethernet, can anyone help me?
Or i only can do this with zoning
Thanks
Fred

Hello Fred,
All interfaces must be in the same vsan for them to see each other
vsan database
vsan 2 interface fc1/1, fc1/2, fc1/3
exit
Then you can zone each separately
example:
zone name host1 vsan 2
member pwwn 11:11:11:11:11:11:11:11    (host1 pwwn)
member pwwn 33:33:33:33:33:33:33:33    (VNX)
zone name host2 vsan 2
member pwwn 22:22:22:22:22:22:22:22    (host2 pwwn)
member pwwn 33:33:33:33:33:33:33:33    (VNX)
zoneset name Zoneset1 vsan 2
mem host1
mem host2
zoneset activate name Zoneset1 vsan 2
Thanks

Shape layer / round corners does not work with merge paths

hi.
thought I'd try something that works just fine in Illustrator.
merge 2 paths, and then run a round corner on the resulting path.
it doesn't work. I think if you asked any user if they thought it should work, they'd say: Yes I'd expect the round corner to work in that instance.

upon further reflection, it's not just ellipses. it's any shapes that are already roundish in the intersection area.
when I collapse the tension on the points of the same two paths...

Nexus 5500 to Nexus 5500 Fiber Etherchannel with different lengths

Hi,
I'm in the very first phase of designing a small datacenter infrastructure based on the Nexus 5500 series. I haven't got any hands-on nexus experience yet so please forgive me if I'm asking a silly question here...
What I would like to build is a 4 unit, redundant datacenter design. Two units in one DC, and two units in the other. I would like to connect both DCs together using a redundant darkfiber. One link is 10 miles, the other is 20 miles.
The Nexus switches are going to be connected "back-to-back" with and the redundant etherchannel between the DCs, like this http://www.netcraftsmen.net/component/content/article/69-data-center/859-configuring-back-to-back-vpcs-on-cisco-nexus-switches.html
Can I expect any problems with this design? In particular with the different lengths of fiber, like buffering issues or failing transmissions?
Thanks!

That should not be an issue. You will need single mode fiber and single mode optics, and as long as all your optics support distance of 20 miles or more, then you should be fine.
HTH

Port-channel L2 problem with Fabric Interconnect and Nexus 7010

Hi,
i using port-channel from both fabric interconnect to N7k with 3 cables per Fabric Interconnect.
but, my problem is when i creating port-channel, Fabric Interconnect don't support mode ON dan rate-mode share in Interface 10G Nexus 7010.
I was trying :
1. I using non dedicated port in Nexus 7010.
      - rate-mode share
      - channel-group 1 mode active
      - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was suspended
2. I using non dedicated port in Nexus 7010
     - rate-mode share
     - channel group 1 mode on
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
3. I using dedicated port in Nexus 7010
     - rate-mode share
     - channel group 1 mode active
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was suspended
4. I using dedicated port in Nexus 7010
     - rate-mode dedicated
     - channel group 1 mode active
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was came up and running well.
but, the problem is my costumer do not want using a dedicated rate-mode. if i using dedicated mode the only available port is 8 interfaces instead of 32 ports. i want to using rate-mode share in nexus 7010.
is there any way to configuring port-channel using mode on in fabric interconnect ? i was trying using CLI to create port-channel in Fabric interconect but i cannot configure the channel group protocol.
i attach the topology of N7K with Fabric interconnect.
regards,
Berwin H

Hi Manish,
the issue was solved, i was fix it last week.
the solution is:
i enable the license grace-priode (since my license is Enterprise so cannot create VDC) then i create a VDC (ex: VDC 2) so i allocate the interface on all module
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
N7K-M132XP-12 to VDC 2. after that i delete VDC 2 then all interface back to VDC 1 (default vdc). then i enable the rate-mode share in dedicated port and bundle into port-channel and its working.
i dont know why it must move to VDC first then it will working, maybe cisco can explain the reasons.
So here the result of my port-channel :
SVRN7KFARM-HO-01# show port-channel summary
Flags: D - Down        P - Up in port-channel (members)
        I - Individual H - Hot-standby (LACP only)
        s - Suspended   r - Module-removed
        S - Switched    R - Routed
        U - Up (port-channel)
Group Port-       Type     Protocol Member Ports
      Channel
1     Po1(SU)     Eth      LACP      Eth1/1(P)    Eth1/2(P)    Eth1/3(P)
                                     Eth1/4(P)    Eth1/25(P)
2     Po2(SU)     Eth      LACP      Eth1/9(P)    Eth1/10(P)   Eth1/11(P)
                                     Eth1/12(P)   Eth1/26(P)
3     Po3(SU)     Eth      LACP      Eth1/17(P)   Eth1/18(P)
4     Po4(SU)     Eth      NONE      Eth10/32(P) Eth10/34(P) Eth10/35(P)
                                     Eth10/36(P)
Thanks.
Berwin H

Nexus 7000, 2000, FCOE and Fabric Path

Hello,
I have a couple of design questions that I am hoping some of you can help me with.
I am working on a Dual DC Upgrade. It is pretty standard design, customer requires a L2 extension between the DC for Vmotion etc. Customer would like to leverage certain features of the Nexus product suite, including:
Trust Sec
VDC
VPC
High Bandwidth Scalability
Unified I/O
As always cost is a major issue and consolidation is encouraged where possible. I have worked on a couple of Nexus designs in the past and have levergaed the 7000, 5000, 2000 and 1000 in the DC.
The feedback that I am getting back from Customer seems to be mirrored in Cisco's technology roadmap. This relates specifically to the features supported in the Nexus 7000 and Nexus 5000.
Many large enterprise Customers ask the question of why they need to have the 7000 and 5000 in their topologies as many of the features they need are supported in both platforms and their environments will never scale to meet such a modular, tiered design.
I have a few specific questions that I am hoping can be answered:
The Nexus 7000 only supports the 2000 on the M series I/O Modules; can FCOE be implemented on a 2000 connected to a 7000 using the M series I/O Module?
Is the F Series I/O Module the only I/O Module that supports FCOE?
Are there any plans to introduce the native FC support on the Nexus 7000?
Are there any plans to introduce full fabric support (230 Gbps) to the M series I/O module?
Are there any plans to introduce Fabric path to the M series I/O module?
Are there any plans to introduce L3 support to the F series I/O Module?
Is the entire 2000 series allocated to a single VDC or can individual 2000 series ports be allocated to a VDC?
Is Trust Sec only support on multi hop DCI links when using the ASR on EoMPLS pwire?
Are there any plans to inroduce Trust Sec and VDC to the Nexus 5500?
Thanks,
Colm

Hello Allan
The only IO card which cannot co-exist with other cards in the same VDC is F2 due to specific hardware realisation.
All other cards can be mixed.
Regarding the Fabric versions - Fabric-2 gives much bigger throughoutput in comparing with Fabric-1
So in order to get full speed from F2/M2 modules you will need Fab-2 modules.
Fab2 modules won't give any advantages to M1/F1 modules.
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/data_sheet_c78-685394.html
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/prodcut_bulletin_c25-688075.html
HTH,
Alex

Mix of Nexus 5500 & Catalyst 6500

Hi there,
Does Nexus 5500 series require a Nexus 7000 parent device? or it will be supported with Catalyst 6509?
If this is the scenario :
CAT6509 - Core Layer 3
CAT6509 - Distribution Layer 2/3
NX-5548 - Access Layer 2
And FYI, no VSS on Catalyst 6509.
Thanks in advance,
Gerard

Hello Chad,
Cool thanks ... that is perfect. We're eventually moving towards NX at the Core and Distribs really soon. Yeah, that's what I've known with the Extenders requirement with parent 5k or 7k too ...
Gerard

Nexus 5500 - inband via default vrf and out-of-band via management vrf

Nexus 5548 with no layer 3 module. Want to manage the device via 10.122.122.5 9 (inband) and 10.122.123.58 (out-of-band)
Currently i can get to the device using 10.122.123.58 via management vrf but can't get to 10.122.122.5 via default vrf.
A couple of questions please:
1) Is this design support? or do i need a layer 3 module + licensing to use the default vrf?
2) What does "pending" in the default vrf routing table indicate?
interface Vlan12
no shutdown
ip address 10.122.122.5/25
ip route 0.0.0.0/0 10.122.122.1
interface mgmt0
vrf member management
ip address 10.122.123.58/26
vrf context management
ip route 0.0.0.0/0 10.122.123.1
sh ip route vrf all
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
0.0.0.0/0, ubest/mbest: 1/0, pending
*via 10.122.122.1, [1/0], 3w1d, static
10.122.122.0/25, ubest/mbest: 1/0, attached, pending
*via 10.122.122.5, Vlan12, [0/0], 3w1d, direct
10.122.122.5/32, ubest/mbest: 1/0, attached, pending
*via 10.122.122.5, Vlan12, [0/0], 3w1d, local
IP Route Table for VRF "management"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
0.0.0.0/0, ubest/mbest: 1/0
*via 10.122.123.1, [1/0], 3w1d, static
10.122.123.0/26, ubest/mbest: 1/0, attached
*via 10.122.123.58, mgmt0, [0/0], 3w1d, direct
10.122.123.58/32, ubest/mbest: 1/0, attached
*via 10.122.123.58, mgmt0, [0/0], 3w1d, local

Hi,
Yes, it is possible. When you login as admin and you want to get to another vdc, you just use this command:
switchto vdc
This will take to the that vdc. If you want to switch back to the admin vdc, you just type "switchback"
HTH

DCNM SAN 6.2 + Nexus 5500 not using interface mgmt

When trying to discover a newly setup fabric we have set the SVI of one of the Nexus 5500 switches as seed device in DCNM SAN server. Problem do seem to be the same in DCNM 6.2 as in DCNM 5.x, one can not use a SVI.... After adding the seed switch with the IP adress of the SVI it appears in the Admin->Data sources->Fabric with the ip address of the mgmt interface. Thing is that this ip address can not be reached from the DCNM SAN server since we have only used a cross over ethernet cable for peer-keepalive over the mgmt interfaces.
Is there a way in DCNM SAN 6.2 to force SAN management over a SVI instead of the mgmt interface?

Here is the solution:
in the menubar on the top, in the lower one go to Admin > Server Properties
scroll to the middle of the list, locate “fabric.managementIpOverwrite” and set it to false
restart the DCNM Servers

NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX

Hi All,
Please tell me how to do "NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX" without downtime for FEX.
The Server are connected to FEX.
Attached the diagram.

Hi,
If the 5500s are layer-2 with vPC running between them than you can use ISSU to upgade.
here is doc to follow:
ISSU Support for vPC Topologies
An ISSU is completely supported when two switches are paired in a vPC configuration. In a vPC configuration, one switch functions as a primary switch and the other functions as a secondary switch .They both run the complete switching control plane, but coordinate forwarding decisions to have optimal forwarding to devices at the other end of the vPC. Additionally, the two devices appear as a single device that supports EtherChannel (static and 802.3ad) and provide simultaneously data forwarding services to that device.
While upgrading devices in a vPC topology,you should start with the switch that is the primary switch. The vPC secondary device should be upgraded after the ISSU process completes successfully on the primary device. The two vPC devices continue their control plane communication during the entire ISSU process (except when the ISSU process resets the CPU of the switch being upgraded).
This example shows how to determine the vPC operational role of the switch:
link:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/upgrade/513_N1_1/n5k_upgrade_downgrade_513.html
HTH

Modify layer in a document made up with model

I made a site without tables (all tag DIV), I have saved the
page in a model, I selected one layer in a model and mark the layer
(not his contained) in a modifiable area. I saved a page. After I
create a new document from model.. when I try to modify a layer
(move, resize) I can't because the code is blocked. in a livedoc I
read that is possible. My dreamweaver version is 8.02 please help
me.
I also tried whin new simple page with 3 layers (head - body
- footer)... but the problem it's the same

If you have this -
<div id="layer1">...
You will not be able to drag that layer in design view on any
child page.
Why? because the *layer* is not editable. Its contents are,
but not the
layer itself.
Nevertheless, you will still be able to edit that layer's
position in the
CSS that is applied to the page - just not by dragging it in
design view.
But - there are some flaws in your 'going in' methods
(assuming I understand
your post). Using layers the way you have is not optimal. A
page that is
build from multiple layers will surely produce unexpected
results when the
visitor resizes the text display in their browser, and
dragging things
around in Design view is just a bad practice - with tables or
with layers.
The trick is to learn enough HTML and CSS that you no longer
need to do
this.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"ruffonibus" <[email protected]> wrote in
message
news:[email protected]...
>I made a site without tables (all tag DIV), I have saved
the page in a
>model, I
> selected one layer in a model and mark the layer (not
his contained) in a
> modifiable area. I saved a page. After I create a new
document from
> model..
> when I try to modify a layer (move, resize) I can't
because the code is
> blocked. in a livedoc I read that is possible. My
dreamweaver version is
> 8.02
> please help me.
> I also tried whin new simple page with 3 layers (head -
body - footer)...
> but
> the problem it's the same
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN"
> "
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="
http://www.w3.org/1999/xhtml">
> <head>
> <meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1" />
> 
> <title>sample</title>
> 
> <style type="text/css">
> 
> </style>
> 
> </head>
>
> <body>
> <div id="head"></div>
> <div id="body"></div>
> 
> <div id="Layer3"></div>
> 
> </body>
> </html>
>

Nexus 7004 with N2K-B22HP-P FEX won't connect

Hello
I'm trying to connect an HP Blade server with an N2K-B22HP-P to our Nexus 7004 but it stays in de download mode.
# sh fex
FEX         FEX           FEX                       FEX
Number    Description      State            Model            Serial
116        FEX0116        Image Download         N2K-B22HP-P   FOCxxxxxxxx
# sh fex detail
FEX: 116 Description: FEX0116   state: Image Download
FEX version: 5.2(1)N1(1a) [Switch version: 6.1(4)]
FEX Interim version: 5.2(1)N1(1a)
Switch Interim version: 6.1(4)
Module Sw Gen: 12594 [Switch Sw Gen: 21]
pinning-mode: static    Max-links: 1
Fabric port for control traffic: Eth3/44
Fabric interface state:
    Po116 - Interface Up. State: Active
    Eth3/44 - Interface Up. State: Active
Fex Port        State Fabric Port
Logs:
08/07/2013 18:04:24.424401: Requesting satellite to download image
08/07/2013 18:04:46.442690: Module register received
08/07/2013 18:04:46.443233: Registration response sent
08/07/2013 18:04:46.443516: Requesting satellite to download image
08/07/2013 18:05:10.475657: Module register received
08/07/2013 18:05:10.476109: Registration response sent
08/07/2013 18:05:10.476390: Requesting satellite to download image
08/07/2013 18:05:36.703639: Module register received
08/07/2013 18:05:36.704118: Registration response sent
08/07/2013 18:05:36.704434: Requesting satellite to download image
08/07/2013 18:06:04.741774: Module register received
08/07/2013 18:06:04.742505: Registration response sent
08/07/2013 18:06:04.742628: Requesting satellite to download image

Hi Martin,
At this point in time the N2K-B22-HP FEX is not supported with the Nexus 7000 series switches as the parent switch. If you look at Table 2 in the Cisco Nexus B22 Blade Fabric Extender Data Sheet you'll see it only lists the following:
Cisco Nexus parent switch model or line card
Cisco Nexus 5010 or 5020 Switch for Cisco Nexus B22HP and B22F
Cisco Nexus 5548P Switch
Cisco Nexus 5548UP Switch
Cisco Nexus 5596UP Switch
Cisco Nexus 6001 Switch
Cisco Nexus 6004 Switch
Regards

Connecting two Nexus switches with link

Hi,
I would like to connect two nexus switches with a link. Like one c5020 and one c5548p. How do i need to configure the ports at both the switches which will be joined with a fiber cable.
For MDS switches such links becomes E-port and fabric is merged. Not sure what happenes at the Nexus swictches. Any input will be appreciated.
Thanks,

Do you have fc modules in each nexus? If so, they act much like the MDS 9148. All ports should be default auto speed and auto switchport mode. Insert fc-sfp's and a regular multimode fc cable between them. Default mode is fc switch.
If that doesn't work, configure the mode on each port as E.
Once done, the fc switch portion of each nexus will merge.
Dave

Cannot InterVlan on Cisco Nexus 5500

Dear All,
I have problem with my nexus 5500,
Intervlan on my nexus not work,
i dont know why..
Before i have only this kind of license:
Feature                      Ins Lic   Status Expiry Date Comments
                                 Count
FCOE_NPV_PKG                  No    -   Unused             -
FM_SERVER_PKG                 No    -   Unused             -
ENTERPRISE_PKG                Yes   -   Unused Never       -
FC_FEATURES_PKG               Yes   -   Unused Never       -
VMFEX_FEATURE_PKG             Yes   -   Unused Never       -
ENHANCED_LAYER2_PKG           No    -   Unused             -
LAN_BASE_SERVICES_PKG         No    -   Unused        -
LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
and feature i used is :
- feature privilege
- feature telnet
- feature interface-vlan
- feature hsrp
- feature dhcp
- feature lldp
I make few vlan on nexus and then i check the interface status and the result is all vlan Interface is UP but intervlan is not work.
And then, i install license for LAN_BASE_SERVICES_PKG, this is result for install licensed:
Feature                      Ins Lic   Status Expiry Date Comments
                                 Count
FCOE_NPV_PKG                  No    -   Unused             -
FM_SERVER_PKG                 No    -   Unused             -
ENTERPRISE_PKG                Yes   -   Unused Never       -
FC_FEATURES_PKG               Yes   -   Unused Never       -
VMFEX_FEATURE_PKG             Yes   -   Unused Never       -
ENHANCED_LAYER2_PKG           No    -   Unused             -
LAN_BASE_SERVICES_PKG         Yes   -   In use Never       -
LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
I used vlan configuration vlan before, but the interface VLAN is DOWN/DOWN.
and then i read this article:
http://www.layerzero.nl/blog/2012/10/nexus-5000-non-routable-vdc-mode/
Yes, thats solution work for 1 Vlan with "management" command on interface VLAN.
But, the other vlan is still DOWN. and Intervlan is not work to.
Anyone, can help me please?
I have experience configure Nexus 5000 with VPC, FEX, Storage, etc, and everything fine without isue in intervlan.
Thanks.

Marvin,
This is the output.
`show module`
Mod Ports Module-Type                       Model                  Status
1   48    O2 48X10GE/Modular Supervisor     N5K-C5596UP-SUP        active *
Mod Sw              Hw      World-Wide-Name(s) (WWN)
1    5.2(1)N1(1b)    1.0     --
`show interface brief`
Ethernet      VLAN    Type Mode   Status Reason                   Speed     Port
Interface                                                                    Ch #
Eth1/1        1       eth trunk up      none                        10G(D) --
Eth1/2        1       eth trunk up      none                        10G(D) --
Eth1/3        1       eth trunk up      none                        10G(D) --
Eth1/4        1       eth trunk up      none                        10G(D) --
Eth1/5        1       eth trunk down    Link not connected          10G(D) --
Eth1/6        1       eth trunk up      none                        10G(D) --
Eth1/7        1       eth trunk up      none                        10G(D) --
Eth1/8        1       eth trunk down    Link not connected          10G(D) --
Eth1/9        1       eth access down    SFP not inserted            10G(D) --
Eth1/10       1       eth access down    SFP not inserted            10G(D) --
Eth1/11       1       eth access down    SFP not inserted            10G(D) --
Eth1/12       1       eth access down    SFP not inserted            10G(D) --
Eth1/13       1       eth access down    SFP not inserted            10G(D) --
Eth1/14       1       eth access down    SFP not inserted            10G(D) --
Eth1/15       1       eth access down    SFP not inserted            10G(D) --
Eth1/16       1       eth access down    SFP not inserted            10G(D) --
Eth1/17       1       eth access down    SFP not inserted            10G(D) --
Eth1/18       1       eth access down    SFP not inserted            10G(D) --
Eth1/19       1       eth access down    SFP not inserted            10G(D) --
Eth1/20       1       eth access down    SFP not inserted            10G(D) --
Eth1/21       1       eth access down    SFP not inserted            10G(D) --
Eth1/22       1       eth access down    SFP not inserted            10G(D) --
Eth1/23       1       eth access down    SFP not inserted            10G(D) --
Eth1/24       1       eth access down    SFP not inserted            10G(D) --
Eth1/25       1       eth access down    SFP not inserted            10G(D) --
Eth1/26       1       eth access down    SFP not inserted            10G(D) --
Eth1/27       1       eth access down    SFP not inserted            10G(D) --
Eth1/28       1       eth access down    SFP not inserted            10G(D) --
Eth1/29       1       eth access down    SFP not inserted            10G(D) --
Eth1/30       1       eth access down    SFP not inserted            10G(D) --
Eth1/31       1       eth access down    SFP not inserted            10G(D) --
Eth1/32       1       eth access down    SFP not inserted            10G(D) --
Eth1/33       1       eth access down    SFP not inserted            10G(D) --
Eth1/34       1       eth access down    SFP not inserted            10G(D) --
Eth1/35       1       eth access down    SFP not inserted            10G(D) --
Eth1/36       1       eth access down    SFP not inserted            10G(D) --
Eth1/37       1       eth access down    SFP not inserted            10G(D) --
Eth1/38       1       eth access down    SFP not inserted            10G(D) --
Eth1/39       1       eth access down    SFP not inserted            10G(D) --
Eth1/40       1       eth access down    SFP not inserted            10G(D) --
Eth1/41       1       eth access down    SFP not inserted            10G(D) --
Eth1/42       1       eth access down    SFP not inserted            10G(D) --
Eth1/43       1       eth access down    SFP not inserted            10G(D) --
Eth1/44       1       eth access down    SFP not inserted            10G(D) --
Eth1/45       1       eth access down    SFP not inserted            10G(D) --
Eth1/46       1       eth access down    SFP not inserted            10G(D) --
Eth1/47       1       eth trunk down    SFP not inserted            10G(D) --
Eth1/48       1       eth trunk down    SFP not inserted            10G(D) --
Port   VRF          Status IP Address                              Speed    MTU
mgmt0 --           down   --                                      --       1500
Interface Secondary VLAN(Type)                    Status Reason
Vlan1     --                                      down   Administratively down
Vlan199   --                                      up     --
Vlan999   --                                      down   Non-routable VDC mode
sh ip int bri
IP Interface Status for VRF "default"(1)
Interface            IP Address      Interface Status
Vlan199              192.168.36.10   protocol-up/link-up/admin-up
Vlan999              192.168.99.1    protocol-down/link-down/admin-up
sh vlan
VLAN Name                             Status    Ports
1    default                          active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/9, Eth1/10, Eth1/11
                                                Eth1/12, Eth1/13, Eth1/14
                                                Eth1/15, Eth1/16, Eth1/17
                                                Eth1/18, Eth1/19, Eth1/20
                                                Eth1/21, Eth1/22, Eth1/23
                                                Eth1/24, Eth1/25, Eth1/26
                                                Eth1/27, Eth1/28, Eth1/29
                                                Eth1/30, Eth1/31, Eth1/32
                                                Eth1/33, Eth1/34, Eth1/35
                                                Eth1/36, Eth1/37, Eth1/38
                                                Eth1/39, Eth1/40, Eth1/41
                                                Eth1/42, Eth1/43, Eth1/44
                                                Eth1/45, Eth1/46, Eth1/47
                                                Eth1/48
5    A                       active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
199 B                          active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
391 C                     active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
392 D                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
393 E                       active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
394 F                        active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
395 G                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
500 H                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
526 I                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
VLAN Type Vlan-mode
1    enet CE
5    enet CE
199 enet CE
391 enet CE
392 enet CE
393 enet CE
394 enet CE
395 enet CE
500 enet CE
526 enet CE
Remote SPAN VLANs
Primary Secondary Type             Ports

Layer 3 config design on Nexus 5500 with Fabric Path

Similar Messages

Maybe you are looking for