Could connect two Nexus 5648 to a stack of Catalyst 3750?

Good Morning,
Can I connect a two Nexus 5600 (switchs distribution) with switch Catalyst 3750 (switch access)?
I have tried to integrate the Nexus switch in the network as switch distribution, replacing a Catalyst 6500 switch and does not work. Everything is going very slow. Although all the ping function properly.
Is there any incompatibility connect two nexus 5648 to a stack of Catalyst 3750 by VPC?
Thank you.
Greetings.

Hi,
There can be many reasons for the switches not joining the stack like SDM template mismatch.
You may go through the following document:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750/software/troubleshooting/switch_stacks.html#wp40112
Thanks
Ankur
"Please rate the post if found useful"

Similar Messages

  • 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

  • Connecting two Nexus 5020 with 10G ISL link

    Hi Experts,
    I am trying to connect two nexus 5020 with a 10G ISL link.
    Per my understanding, with new release 5.0.3 N2(2a) ISL link between two nexus switch is supported.
    Following is my config
    c5020-1(config)# show running-config int vfc 32
    !Command: show running-config interface vfc32
    !Time: Fri Dec  2 01:14:38 2011
    version 5.0(3)N2(2a)
    interface vfc32
      bind interface Ethernet1/32
      switchport mode E
      switchport trunk allowed vsan 3040
      no shutdown
    c5020-1(config)#
    c5020-1(config)# sho running-config int eth1/32
    !Command: show running-config interface Ethernet1/32
    !Time: Fri Dec  2 01:16:15 2011
    version 5.0(3)N2(2a)
    interface Ethernet1/32
      switchport mode trunk
      spanning-tree port type edge trunk
    c5020-1(config)#
    I have similar config on the other switch. But for some reason the link does not come up. vfc port keep "initializing" and Eth port stays isolated.
    c5020-1(config)# sh int vfc32
    vfc32 is trunking (Not all VSANs UP on the trunk)
        Bound interface is Ethernet1/32
        Hardware is Virtual Fibre Channel
        Port WWN is 20:1f:00:0d:ec:ca:04:bf
        Admin port mode is E, trunk mode is on
        snmp link state traps are enabled
        Port mode is TE
        Port vsan is 3040
        Trunk vsans (admin allowed and active) (3040)
        Trunk vsans (up)                       ()
        Trunk vsans (isolated)                 ()
        Trunk vsans (initializing)             (3040)
        1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
        1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
          0 frames input, 0 bytes
            0 discards, 0 errors
          0 frames output, 0 bytes
            0 discards, 0 errors
        last clearing of "show interface" counters never
        Interface last changed at Fri Dec  2 01:17:28 2011
    c5020-1(config)#
    c5020-1(config)# sh int eth1/32 fcoe
    Ethernet1/32 is FCoE Isolated
    c5020-1(config)#
    If any expert throw some light to make me understand things better will be helpful.

    i have not connected two Nexus before but looking at your eth 1/32 interfaces ..do you think it needs to be "
    switchport trunk allowed vlan" your "FCOE" VLAN ?

  • Help, Issues Connecting two Wireless Routers

    Ahead of time I would like to thank everyone for their responses and help. I tried to be as clear as possible. I believe I got all the details right. Some things are repetitive and might be a little confusing,  but please ask questions for any clarification. Thanks  for the help. 
    Current Routers:
    1. Linksys WRT600N ---- Used as primary router. Connected to the 4 ports are 3 PCs and a wireless router. All three PC have static IPs I reservered, also have a static IP reserved for the WGT624 wireless router. DMZ is also enabled and destination is the IP reserved for WGT624. 
    2. Netgear WGT624 ----  WGT624 is connected to WRT600N through  the WAN port on the WGT624 to port number X on the WRT600N . I was using Netgear WGT624 as an access point for a Xbox360 , a couple of macs and  ubuntu netbook.  This router recently died needs to be replaced.
    3. Linksys E3000 ---- Recently purchased to replace the Netgear WGT624 that has died. I want to use this as my new access point. Having trouble setting up the settings for this router. I want the same setup as before. 
    Detailed Problem
    I currently have the WRT600N located in the basement connected to a cable modem through the WAN port. Connected to the 4 ports on the back of WRT600N are 3 PCs and a Wireless router. Most of the settings on the WRT600N I left alone. The only thing I changed was reserving 4 IPs for the 3 PCs and the WGT624 wireless router. I also enabled the DMZ for the destination IP of the WGT624.  I also opened a couple of ports.
    The Netgear WGT624 that died was located on the upper level third floor. I was using it primarily as an access point. It was connected through the WAN port  of the WGT624 to port X on the WRT600N which is located in the basement. Settings on this are a little different. On the WGT624 I disabled the firewall. I left both the Auto DHCP enabled and the DHCP server. WPA was enabled on the WGT624. With these settings on the WGT624 I was able to connect to a xbox 360 and a few macs wirelessly to the internet with no issues .  I also noticed that the the internet IP displayed on the status tab on the WGT624 was the IP I had reserved on the WRT600N.  
    Recently the WGT624 died after  years of usage. So I purchased a Linkys E3000. I want to have a similar setup as before with the WGT624. However I have been running into issues. Wirelessly I cannot get access to the internet through the E3000. The E3000 is connected to the WRT600N in the same was as the WGT624. The WAN port of the E3000 is connected to the port number X of WRT600N.  On the status tab of the E3000 I seem to be getting a strange Internet IP address. 127.0.0.1. This I think is a loopback address, I am not sure? Same with the subnet mask of 255.0.0.0
    So the problem is I want the keep the same setup as before if I can. I don't want to the any computers who connect to the access point to have access to any computers that are connected to the 600N.
    I read on another thread I could connect two wireless routers together by connecting port X on the 600N to port X on the E3000.   Then changing the internal IP of the second router from 192.168.1.1 to 198.168.1.2 and then disabling the DHCP server.
    I really want to keep the same set up as before if posslble. More importantly I want to know why my setup prior, the WRT600N  to the WGT624 worked with no problems. Why could I use the WGT624 as an access point and not the E3000? Should I switch the the two routers use the 600N as the access point and E3000 as my main router?
    Thanks again.

    1. You have chained two routers. The WRT600N uses LAN IP address 192.168.1.1 subnet mask 255.255.255.0. The Netgear is connected with the WAN port to the WRT (thus uses an 192.168.1.* address on the WAN port) and uses 192.168.0.1 by default on the LAN side. Your new E3000, however, uses the Linksys default 192.168.1.1 on the LAN side. If you connect the E3000 to the WRT600 without making any changes it won't work. A router cannot work if WAN and LAN side both use 192.168.1.0/255.255.255.0. That's impossible.
    2. Thus, the quick and easy setup to get the same as before would be to change the LAN IP address of the E3000 from 192.168.1.1 to 192.168.0.1. After that change you can connect the internet port of the E3000 to the WRT and everything works like before.
    3. However, in particular because you need port forwarding and you do port forwarding through two routers I would recommend not to run two routers chained. I can't see why it is necessary for you to run two routers and two separated networks. The basic setup and an explaination why a different setup may be better is here. I think in your case it would make things much simpler and you have full connectivity between all your computers. You can set up a roaming wireless network, too. The only problem is that you will "loose" one port on the E3000 because you cannot use the internet port.

  • WAD 7.0 Connection BW7.0 ABAP and BI stack JAVA ?? & WEBEX

    Hi experts,
    My question is probably too simple but .....
    I am from basis components and I have some littles questions..
    I have 2 systems :
    - 1 BW 7.0 ABAP stack only
    - 1 BI 7.0 JAVA standalone
    I have configure UME and Webex between the two systems.
    For testing, I use internet explorer on the portal...It's OK.
    But consultants wants to use a "WAD 7.0"...
    What i would like to know :
    - WAD could connect directly on the ABAP BW ? Or throw the BI 7.0 JAVA?
    - In case they could connect directly to the ABAP, a BI JAVA was necessary? SP 07  for abap STACK?
    Last question :
    In my Bi portal user from abap stack are created by UME (from abap)  but tkey don't have any permissions...This is normal or my user mapping is wrong?
    Thanks for your help in this new world for me.
    cdt,
    patrick

    Hello,
    there are any new's on this posting? We are in the same situation now and the question is - if its possible to install on a Non-Unicode 2004s environment the Javastack.
    Thanks for your answer
    Regards
    Jochen

  • Servers connected to Nexus 5548 only getting 200 Mbps of throughput

    Servers connected to NExus 5k were only getting 100 Mbps of throughput. So I disabled Flow control recieve on all the ports. After this we are getting 200 Mbps of speed. The servers are connected throuh 10 gig port. Could you guys please suggest why the throguhput is still low? Atleast we should get 1Gbps of thrpoughput.

    Hi Adam,
    I think we probably need a little more information to go on. Can you answer the following?
    What type of servers and NICs?
    What OS are you running on the servers?
    What cables do you have from the servers to the switch?
    Are the two servers in the same subnet or is the traffic between them routed?
    If routed, is that in the Nexus 5548 or some other router?
    How are you testing throughput?
    Presumably you're not seeing any errors on the switch ports that the servers are connected to?
    Regards

  • Can i connect two monitors to my mac book pro with HDMI?

    can i connect two monitors to my mac book pro with HDMI?

    I retract my previous "No." If you can live with limited performance (slow refresh/choppy action video/no gaming) on the second external monitor, you could use a USB video adapter and a DVI-HDMI adapter to connect it to a USB port on your computer.
    http://eshop.macsales.com/item/NewerTech/VIDU2DVIA/
    Just a note about the system information that appears below your post: iOS 4.3.3 does not run on Macs, only on iPods, iPads and iPhones. When you're posting about your MBP, it would be more useful to those responding to know which version of Mac OS X you're running. Doesn't matter for purposes of this post, but something to remember for future posts.

  • With MacBooks Retina 13" can you connect two external monitors with resolution each 2560x1600?

    I'm not talking about Thunderbolt displays, but other brands like ASUS, LG, SAMSUNG, etc.
    Has anyone tested?

    You can connect two displays to the two Thunderbolt ports with appropriate Mini DisplayPort cables or adapters.
    <http://www.apple.com/macbook-pro/specs-retina/>
    "Simultaneously supports full native resolution on the built-in display and up to 2560 by 1600 pixels on up to two external displays"
    If the display supports HDMI, you could connect one to the computer's HDMI port, but not at 60Hz.
    "Support for 3840-by-2160 resolution at 30Hz"

  • How do I connect two Queries?

    Hello all,
    How do I connect two Queries and add some numbers.
    Here is what I am trying to do.
    Query 1: Gets G/L Credit Amounts for Jan 2007  Feb 2007 March 2007.....Dec 2007
    Query 2: Gets G/L Debit Amounts for Jan 2007 Feb 2007 march 2007.....Dec 2007
    I need to put both these Queries in a worksheet one below the other and add the totals by each month.....so the final report looks something like this:
    I am using two structures to hold the query values.
    G/L Credit Amount        Jan 2007    Feb 2007.............Dec 2007
                                        +100         +200                   +400
    G/L Debit Amount           -50           -100                     -200
    Total                              50             100                      200
    Also, I would like to allow the users to enter Year as a variable. Any suggestions?
    Your help is greatly appreciated.

    Venkata,
    Thanks for your reply. Could you explain how I insert two query results into one worksheet? And, also how do I link the two structures ( one structure per query) so I can total the amounts by each month?
    Thank you in advance.

  • Is it possible to directly connect two Xserves with a Promise VTrak E610fD via Fibre?

    I have two Xserves and I'd like to connect them with a Promise VTrak E610fD. As this storage has two controllers, I'd like to connect both Xserve with both controllers. Is this setup possible? Can I access (read and write) the same disk array with both Xserves simultaneously (Xsan?) or do I have to create two separate arrays?

    Hello bleistift, and welcome to the AppleBoards,
    Fibre channel is SCSI which means that any device connected by fibre assumes it is in sole control of that device. When you attach more than one machine via fibre both machines assume they are in control and unexpected behaviors and data corruption ensues. SAN (like Apple's XSAN) provides a layer of arbitration over the shares allowing multiple fibre connections to play nicely with one another while still being connected over fibre.
    You could easily connect two machines to a single RAID box if they are accessing different RAID volumes at the same time, but once you start connecting to the same data at the same time you need SAN.
    HTH,
    =Tod

  • Can I connect two non-TB external displays to a new MBP?

    Looking to pick up a new MBP and I would like to connect two non-Thunderbolt monitors, they are nice but WAY too expensive, and I'm wondering if this is possible.  I know I can use Matrox Head2Go line of products, but I would like to avoid shelling out another 2-300 on other hardware if I can avoid it. 
    So any other ways to drive two monitors?   I'm surprised there is no Thunderbolt -> DVI adapter or something.  Heck maybe there is, but I haven't seen it yet.
    Thanks

    here is the adapter your were looking for http://store.apple.com/us/product/MB570Z/A
    you'll also need to consider getting something that supports usb to dvi which will make your third monitor connnected via a usb port. This uses DisplayLink Drivers which let you connect a monitor via usb. Warning, it does not have full support for Lion yet.
    I'm using the arkview usb display adapter. there are other on the market, they all use DisplayLink. And since I'm on Lion I'm waiting for DisplayLink to fix their drivers to work on it (it's been a struggle).
    If you're on Snow Leopard it will do you well to stay on it. .
    you could get on Thunderbolt display and then connect a monitor to that with the dongle I showed you. Then you will have no issues with Lion and your three displays.
    Thunderbolt tech is new and new adapters will be coming out for it, especially something that handles mutliple screens. but you'll have to wait for this technology to be made.

  • Connecting Two Displays

    I now have two Cinema displays that I would like to connect to my G5. Where the DVI ports are I'm short one FireWire port since both displays require a USB and FireWire connection along with the DVI.
    Can someone suggest a good way around this to allow for two displays? Is there such a thing as an extension for a FireWire cable that I can then run to the other side of the G5 where there is another FW port? The problem with this is that I have no FW ports left on the G5. Do I run any risks if I try to daisy-chain my display's FW to a port on one of my external hard-drives?
    Do FireWire hubs exist and are they reliable? I could be overlooking something with regard to connecting two displays as I'm sure it's done all the time. I'm just not sure about the best way to proceed. Thanks for any info.

    There are FireWire hubs and extension cables, but
    unless you need to use the FireWire ports on the
    displays, you don't have to connect their FireWire
    cables.
    I'm in the same situation as Stuart - I'm short one Firewire port.
    I tried plugging a powered Firewire Hub into the back of my new G5, and then tried plugging the 2 ACD Firewire cables into the hub - the G5 crashed on Startup.
    Surely there has to be more support info "out there" than "There are hubs & extension cables...
    Can we plug a Powered Hub into ACD #1, then plug the ACD Firewire cable into the Hub?
    Is it safe to use an Extender/Repeater?
    Is there a "Splitter" available, and it it safe to use?
    C'mon Apple: let's get a Knowledge Base Article available for your loyal users!

  • Connecting two extra displays

    I was wondering whether it would be possible to connect two external monitors to my macbook. I currently have one connected but would like to add another- any help?

    It's possible that you could get what you're after.
    You'll need an external hardware that can split your display output. There are third party solutions for PC's - even for desktops that don't have internal PCI/AGP/PCIe expansion.
    Matrox has a LONG standing history at providing solutions for Windows. Actually I just took a look at their site and saw "Matrox DualHead2Go DisplayPort Edition"
    Specifically I read: "Run two monitors from your notebook or desktop computer even if that system only supports one monitor output" & "Includes Matrox PowerDesk software for Windows and Mac"
    Be careful though. Currently I saw lack of support for 10.6.
    "Mac® OS X v10.4, Mac OX v10.5 Leopard"
    Source: http://www.matrox.com/graphics/en/press/releases/2009/gxm/gxm_dp/
    Take a look around to see their competitors which has begun to flourish in the past 3-5yrs.
    Hope this helps.
    Donny

  • Generate query  at a time &  connect  two database ?

    Hi
    Could u help me? it is necessary  that  
    I have  two database ( RSHPL,RSPL)  and both data base have  same table name and same fieldname (Table Name :-OITM, Fieldname :ONHAND ,pk- ITEMcode,) 
    At first I tell u what I want?
    I want to generate query  at a time &  connect  two database and same table name(OITM)  to select the TOTAL VALUE of this  field(ONHAND) and pk-key is Itemcode.  
    Is it Possible? If  Possible  plz  write this query and send me.

    Hi,
    I don't think its possible to write a query from within SAP that allows you to get data from another SAP database. 
    I have used SQL Reporting Services to report on data from multiple databases, and this works very well for many of my clients.  It depends on what you want to do with the data, do you need to display it on the screen in SAP and it to a field or will a report suffice?
    Regards,
    Adrian

  • Networking Best Practices - Connecting Two Switches

    Connecting two switches together is an easy task, which makes it so frustrating when it doesn’t work. Here we will outline a basic scenario of connecting two switches and achieving connectivity. In these scenarios we will be using commands and settings that will work for most modern PowerConnect switches. However this does not cover all possible scenarios and the commands may differ slightly from switch to switch.
    For instance, in most cases you can use General or Trunk mode when connecting two switches. However, on the PowerConnect 62xx series switches, you must use General mode if you want to allow management traffic onto the switch over the PVID.  If you use Trunk mode, you will not have the default VLAN on those ports.  The ports will only allow tagged traffic.
    For more details on the difference between Access, General, and Trunk modes, follow this link.
    http://en.community.dell.com/support-forums/network-switches/f/866/p/19445142/20089157.aspx#20089157
    It is always a good idea to have the user and CLI guide for your switch, to reference any possible changes in command syntax.
    http://support.dell.com/support/edocs/network/
    Layer 2
    Layer 2 switches operate at the data link layer of the OSI model. Layer 2 is responsible for error checking and transmitting data across the physical media. MAC addressing sources and destination protocols are layer 2 protocols. Layer 2 switches use the MAC address of data packets to determine where those packets should go. It learns the MAC addresses of all devices and creates a segment/forwarding table.
    When a switch receives a frame with a destination address that isn't in its forwarding table, the switch forwards the frame to all other ports. If the destination machine responds to the server, the switch will listen to the reply and learn which port the destination machine is attached to. It then adds that MAC address to the forwarding table.
    The Dell PowerConnect Layer 2 switches have ports that all operate in VLAN 1 by default. If it is acceptable to have all traffic on the same broadcast domain, then you can simply leave the default alone, connect the two switches and traffic will flow.
     If you do not want all traffic on the same broadcast domain, then we need to look at adding additional broadcast domains through the use of VLANs.
     We will use 3 VLANs for the following scenario.
    VLAN 1=Management
    VLAN 2=Client
    VLAN 3=Server
    To create these VLANs we do the following commands (VLAN 1 is already created by default)
    console(config)# vlan database
    console(config-vlan)# VLAN 2
    console(config-vlan)# VLAN 3
    console(config-vlan)# exit
    We can then name the VLANs to help keep things organized.
    console(config)# interface vlan 2
    console(config-vlan)# name Client
    console(config-vlan)# exit
    console(config)# interface vlan 3
    console(config-vlan)# name Server
    console(config-vlan)# exit
    Once we have the VLANs created we can place a device in that VLAN by placing the port it plugs into, in access mode for the specific VLAN.
    So we have a workstation on port e2 we want to be placed in VLAN 2, we would issue the following commands.
    console(config)# interface ethernet 1/e2
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 2
    console(config-if)# exit
    The next port plugs into a server on port e3 we want on VLAN 3, we would issue these commands.
    console(config)# interface ethernet 1/e3
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 3
    console(config-if)# exit
    For the ports connecting the two switches together, we place the ports in trunk mode and specify the native VLAN and allowed VLANs.
    For the port e1 that connect the two switches to each other would be configured like this.
    console(config)# interface ethernet 1/e1
    console(config-if)# switchport mode general
    console(config-if)# switchport general allowed vlan add 2,3 tagged
    console(config-if)# switchport general pvid 1
    console(config-if)# exit
    Once these VLANs and port settings are made on both switches. A server connected to switch A on VLAN 3 should be able to communicate with another Server connected to switch B that is also in VLAN 3.  Without the use of a router the devices in VLAN 3 will not be able to communicate with devices that are outside of their broadcast domain (i.e. VLAN 2 devices could not reach VLAN 3 devices)
    Layer 3 + Layer 2
     Until recently, routers were the only devices capable of layer 3 protocols. Switches capable of routing are now available and in widespread use. In most cases we will connect our layer 2 switches to a Layer 3 capable switch to perform our routing for us.
     On the layer 3 switches we will use the same VLANs and setup that we did with the layer 2 switches.  Then we will add to the configuration.
     We can assign an IP address to each switch with the following command.
    Switch A
    console(config)#ip address 172.16.1.1 255.255.255.0
    Switch B
    console(config)#ip address 172.16.2.1 255.255.255.0
    Then we will enable routing only on Switch A
    console(config)# ip routing
    Switch A we assign an IP address to VLAN 2 and enabling routing on the VLAN.
    console(config)# interface vlan 2
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.20.1 255.255.255.0
    console(config-if-vlan2)# exit
    Switch A we assign an IP address to VLAN 3 and enabling routing on the VLAN.
    console(config)# interface vlan 3
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.30.1 255.255.255.0
    console(config-if-vlan2)# exit
    On both switch A and switch B we will keep things simple and use interface 1/e1 for the connection between each switch. Setting both switches 1/e1 to general mode, allowing the additional VLAN 2,3, and keeping the PVID of 1.
    console(config)# interface ethernet 1/e1
    console(config-if)# switchport mode general
    console(config-if)# switchport general allowed vlan add 2,3 tagged
    console(config-if)# switchport general pvid 1
    console(config-if)# exit
    We will have one client computer connect to switch A on port 1/e2 and one client connect to switch B on port 1/e2. These ports will be in access mode for VLAN 2, and the config should look like this on both switches.
    console(config)# interface ethernet 1/e2
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 2
    console(config-if)# exit
    We will have another client computer connect to switch A on port 1/e3 and one client connect to switch B on port 1/e3. These ports will be in access mode for VLAN 3, and the config should look like this on both switches.
    console(config)# interface ethernet 1/e3
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 3
    console(config-if)# exit
    On Clients connected to Switch A we will assign an IP address and gateway based on the VLAN they are in access mode for.
    Client connected to access port for VLAN 2.
    IP Address:172.16.20.11
    Default Gateway:172.16.20.1
    Client connected to access port for VLAN 3.
    IP Address:172.16.30.11
    Default Gateway:172.16.30.1
    On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
    Client connected to access port for VLAN 2.
    IP Address:172.16.20.12
    Default Gateway:172.16.20.1
    Client connected to access port for VLAN 3.
    IP Address:172.16.30.12
    Default Gateway:172.16.30.1
    External Connection
    At some point we may want traffic to have an external connection. To do this we can create a new VLAN for our point to point connection from Switch A to our router. We will use VLAN 7 for this and assign an IP address.
    console(config)# vlan database
    console(config-vlan)# VLAN 7
    console(config-vlan)# exit
    console(config)# interface vlan 7
    console(config-vlan)# name WAN
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 10.10.10.2 255.255.255.0
    console(config-if-vlan2)# exit
    On our router we will assign an IP address of 10.10.10.1
    Then place the port connecting the switch and router into access mode for VLAN 7.  In this case we use port e4.
     console(config)# interface ethernet 1/e4
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 7
    console(config-if)# exit
    We will then need to put in a default route with the next hop as the router IP address.  This allows the switch to know where to route traffic not destined for VLANs 2, 3, or 7.
    console(config)#ip route 0.0.0.0 0.0.0.0 10.10.10.1
    Next on the router we’ll need to add a route back so the router knows about the networks attached to switch A.  Generally adding a static route on most routers is done with the following command: 
    ip route {Network} {Wildcard Mask} {Next Hop-IP}
    In our case here are the 2 static routes we could use.
    Ip route 172.16.20.0 0.0.0.255 10.10.10.2
    Ip route 172.16.30.0 0.0.0.255 10.10.10.2
    The routing that we enabled on Switch A will enable traffic from the other VLANs to traverse over port 1/e4 to the router, connecting us to external traffic. The routes we added to the router allow the traffic to flow back to the switch over port 1/e4.
    Layer 3 + Layer 3
    In some situations we have two switches, each setup to route for its own broadcast domain, which we want to connect together. In this situation we no longer have a need to use Trunk or General mode between the switches. Instead we can create a common VLAN that will be used for the connection between the two switches.
    To create this VLAN we will run the following commands on both switch A and B
    console(config)# vlan database
    console(config-vlan)# vlan 6
    console(config-vlan)# exit
    console(config)# interface vlan 6
    console(config-vlan)# name Connection
    console(config-vlan)# exit
    On switch A we assign an IP address to VLAN 6 and enable routing on the VLAN.
    console(config)# interface vlan 6
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.60.1 255.255.255.0
    console(config-if-vlan2)# exit
    On switch B we assign an IP address to VLAN 6 and enable routing on the VLAN.
    console(config)# interface vlan 6
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.60.2 255.255.255.0
    console(config-if-vlan2)# exit
    On both switch A and B we place the connecting ports into Access mode for VLAN 6.
    console(config)# interface ethernet 1/e1
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 6
    console(config-if)# exit
    We then need to make some changes to switch B now that it is layer 3 and not layer 2 and has its own broadcast domain.
    We will enable routing on Switch B
    console(config)# ip routing
    What used to be VLAN 2 and 3 will now be VLAN 4 and 5 for our separate broadcast domains.
    Switch B we assign an IP address to VLAN 4 and enabling routing on the VLAN.
    console(config)# interface vlan 4
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.40.1 255.255.255.0
    console(config-if-vlan2)# exit
    Switch B we assign an IP address to VLAN 5 and enabling routing on the VLAN.
    console(config)# interface vlan 5
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.50.1 255.255.255.0
    console(config-if-vlan2)# exit
    On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
    Client connected to access port for VLAN 4.
    IP Address:172.16.40.11
    Default Gateway:172.16.40.1
    Client connected to access port for VLAN 5.
    IP Address:172.16.50.11
    Default Gateway:172.16.50.1
    The end result should look like this.
     Troubleshooting
    If we are having issues with connectivity, we may need to place some static routes in place to help traffic to the next hop in the network.
    On switch A we configure a static route to help traffic to the next hop in the network, which is the router.
    console(config)# ip route 0.0.0.0 0.0.0.0 10.10.10.1
    The external router will also need a path defined back to all networks/VLANs.
    To check the status of a port we can use the command. Show interfaces detail, this will help us see the port status. For example to check the status of port 48, we would run this command.
    console# show interfaces detail ethernet 1/g48
     To check routing paths:
    console# show ip route
    The IP address of the network for each VLAN should be listed as C – Connected. Then also a path or default route to your upstream router.
    We can use basic ping commands from a client to help test where connectivity is dropping off at. By doing this we can narrow down where in the network to start troubleshooting.
    -Ping from client to default gateway, being the VLAN the client is in access mode for. If this fails then we may need to double check our client settings making sure the proper IP and gateway are being used.
    -Ping from client to the ip address of the switch the client plugs into. If this fails we may not have VLAN routing enabled on the VLAN the client is in.
    -Ping from client to another client on same VLAN, same switch. If this fails we need to check on client settings, IP address and gateway.
    -ping from client to another client on different VLAN, same switch. If this fails we need to double check the VLAN routing commands are in place.
    -ping from client to the ip address of the next switch in the network. If this fails then check Trunk port configuration from switch to switch, ensuring the VLAN is added to the Trunk port.
    -ping from client to another client on same VLAN, different switch. If this fails, check Trunk port settings.
    -ping from client to another client on different VLAN, different switch. If this fails then check trunk settings and VLAN routing configuration.

    Derek,
    I tried to draw my prefered setup for this network configuration.
    I would create a Team with the two 1 GBit NICs and use it for Domain, DNS, Backup and any SystemCenter Agents.
    I would also Team the two 10 GBit NICs and than assign it to a Hyper-V Switch for the VMs. In Windows Server 2012 it is posible to create vNICs for the Management OS that use this Hyper-V Switch (Converged Network Design). I would create two vNICs SMB1
    and SMB2 to use them for Cluster and Livemigration traffic with SMB Multichannel. If your storage system supports SMB Multichannel you can also use both as storage NICs (but this depends wich vendor you have).
    Hope this helps.
    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa |
    www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

Maybe you are looking for