Connecting two 5k's together

Hi,
How do we best connect our two 5596's together for redundancy and multipathing, both physically and configuration-wise? I see information about vPC's in the manuals, but I'm not sure if this is really what we need to do. We have a simple design--just servers connecting to the 5596's via fc, then the 5596's connecting to our storage via fc. Thanks!

If you are using these for FC SAN connectivity and no Ethernet then you do not need vPC as it is for providing Ethernet port channels across 2 switches.
For FC only you would treat them just like MDS switches. You will not connect them together and each should be in their own VSAN.
The SAN will connect to both and your servers will connect to both.
Your servers will need SAN multipathing software to provide load balancing and redundancy

Similar Messages

HT4259 Direct Connect Two Time Capsules together with Ethernet.

I have TWO Time Capsules ( One upstairs providing Time Machine backup to IMAC #1 ) and (One downstairs providing Time Machine Backup to IMAC#2)
I would like to extend the wireless network portion of this to reach the whiole house with ONE wireless network. I know I can EXTEND the network, but my question is can Connect the two time capsules together via Ethernet cable ( my house is pre wired). This will essentially ensure that the two devices have a solid connection instead of relying on WIRELESS.
Any reasons to NOT do this?
Time Machine will be used differently on the two devices.
Thanks
Ron

Hello!
I have the same problem, i am trying to do this
Timecapsule nr 1, ISP uplink to WAN.
from this one i have LAN to the other timecapsule to WAN.
On the first timecapsule i have DHCP/NAT enable.
On the second i have, Bridge mode.
But when i am connected with eth to the second one i wont recive dhcp addresses or anything... like it wont passtrough.
Any ideas?

Connecting two EG005W's together?

Hello,
I need to connect two 5-port EG005W workgroup switches together. The ports are labeled #1, ..., #5 & non is marked as an "uplink" port. The documentation (user guide) does not cover connecting this device to another switch. Is one of the ports an uplink or is a crossover cable required between the two switches?
Thanks!

Hi!
Sorry to bring back this old topic (not that old!!!) but I'm having the same problem!
At first, I tried to connect both computers to one EG005W... the computer close to it connected fine. The computer downstairs (20m cable, if that much) didn't even lit the green light on the routers. Although it's rated for 100m, I thought maybe this small switch just can't handle such distance. Heck... not even this computer connected directly to the WRT54GL worked, green light but no data transfer, no network activity (I tested the cable, it was perfect). So, I changed the network a bit... connected the computer that was previously working to the router (OK, 2m cable, working on port 2), connected the 20m cable to the router on port 3 and the other RJ45 of this 20m cable to the switch. And it worked, but my network was limited to 100mbps due to the router's limitation.
EUREKA! All I need is another Gb switch to cascade, right??? WRONG!!!!!!!!!!!!
It's just not working... and it's not IP issue because the green leds on the switches don't even light up! Even it I messed the cable, had electrical interference, I would get at least the green lights, right?
Here's what I got now:
Cable Modem -> WRT54GL Router -> EG005W (one computer, 2m cat6 cable) -20m cat6 cable-> EG005W (another computer).
The cable is fine, it works if I remove the EG005W and attach it directly to the router... the switch downstairs work fine.
One other thing... I tried to cascade both switches with a short cable (cat5e) and it didn't work too. I crossed-over the cable and it worked...
Do you have any idea what's going on??? Is 20m of cable too much for this small device? It's the only thing I can think...
I'm an IT Manager, I deal with Cisco routers and switches... those things work so smooth, I don't understand why this thing is not working.
Thanks!

Connecting two macbook pros together to form an extended desktop

I have two macbook pros and I wanted to connect them together to form an extended desktop. How would I go about doing that. I already have them connected together for file sharing. But I want to connect them to form an extended desktop.

Use a product such as ScreenRecycler over your existing network.
(112192)

Possible to connect two base stations together?

What I want to do is connect my Mini, Wii, and X-Box 360 to an N network but it's too far from my DSL line coming in.
What I would like to see is if it is possible to have one base station connected to my DSL and another on the other side of the house connected to the devices...all at N speed on 5GHZ range.
Is this at all doable without a drop-off in speed?
Message was edited by: Shelbz

Is this at all doable without a drop-off in speed?
Yes if you connect the 2 AirPort Extreme base station (AEBS) via Ethernet.
If you connect them wirelessly there will be a bandwidth penalty.

Computers doubling up when connecting two apple routers together

I seem to be getting multiple iterations of the same computers on my network. I have 2 apple routers. One is a master the other is in bridge network extend mode.
The iterations look like this:
Luke's Macbook Air
Luke's Macbook Air (2)
Luke's Macbook Air (3)
Luke's Macbook Air (4)
Merinda's iMac
Merinda's iMac (2)
Apple TV
Apple TV (2)
etc...
Thoughts?

Thanks for clarifying that for me.
Yosemite has a number of issues, and this is one of them. Unfortunately, there are no adjustments or settings on the Apple AirPorts, or in AirPort Utility to address the issue of "multiple" Macs, so your question is beyond the scope of this support forum.
You might be able to temporarily fix things by opening System Prefences (gear icon on the dock), the opening Sharing and adjusting the name of the Mac, but no guarantees.
I would recommend that you post in the Yosemite support forum regarding this issue. The link for that forum is just below:
OS X Yosemite

How do I connect two apple compuiters

I would like to connect two apple computers together - how can I do it.

And take 4x longer if not worse? and WHY and what is this for?
Want to make one client and the other the server? Heck, how about old Fibre interconnect? can't go out and buy an XRAID box but that would.
Do you want to use XSAN?
Xsan is a powerful and scalable solution for storage consolidation. Now everyone in your organization can have fast, concurrent access to terabytes of centralized data. Built into OS X, Xsan allows any Mac with a Thunderbolt to Fibre Channel adapter to access an Xsan volume. OS X Server includes the Xsan Admin application for hosting and configuring Xsan volumes.
http://www.apple.com/osx/server/features/
Xsan is Apple Inc.'s storage area network (SAN) or clustered file system for Mac OS X. Xsan enables multiple Mac desktop and Xserve systems to access shared block storage over a Fibre Channel network. With the Xsan file system installed, these computers can read and write to the same storage volume at the same time. Xsan is a complete SAN solution that includes the metadata controller software, the file system client software, and integrated setup, management and monitoring tools.
Xsan has all the normal features to be expected in an enterprise shared disk file system, including support for large files and file systems, multiple mounted file systems, meta data controller failover for fault tolerance, support for multiple operating systems, etc.
Interoperability
Xsan is based on the StorNext File System.[2] The StorNext File System and the Xsan file system share the same file system layout and the same protocol when talking to the meta data server. They also seem to share a common code base or very close development based on the new features developed for both file systems.
The Xsan website claims complete interoperability[3] with the Quantum Corporation StorNext File System: "And because Xsan is completely interoperable with Quantum’s StorNext File System, you can even provide clients on Windows, Linux, and other UNIX platforms with direct Fibre Channel block-level access to the data in your Xsan-managed storage pool."[4]
Quantum Corporation claims "Complete interoperability with Apple’s Xsan and Promise RAID and Allows Xsan and Xserve RAID to support AIX, HP-UX, IRIX, Red Hat Linux, SuSE Linux, Mac OS X, Solaris, and Windows clients, including support for 64 Bit Windows and Windows Vista."[5]
http://en.wikipedia.org/wiki/Xsan

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.

I'm using pages 5.2 and feeling completely stupid by not knowing how to link two text pages together. Can anyone help? please...

Hi there, I'm trying to use pages 5.2 for the first time and I cannot find how to connect two consecutive pages together as I use to do with earlier versions of Pages... Any help?

Word Processing templates have what is called a Document Body.
That is the area defined by the margins and holds a default text area which flows from page to page.
Examples of WP templates are the Letters, Reports, CVs etc.
Layout templates have that switched off and require you to add Textboxes or Shapes into which you can type text. Each page is an individual Section and no text flows from page to page.
Examples of Layout templates are the Brochures, Business Cards, Posters, Newsletters etc
In Pages '09 you can manually link Textboxes to flow in your own set order and across pages. Pages 5 has dropped this along with 100 other features.
Peter

Connecting two RV082 routers back to back

I'm looking for instructions on how to setup and connect two RV082 routers together with a crossover cable between their WAN ports.
This is to connect two separate LANS together via an ethernet connection. For staging we are setting everything up with a crossover cable in our shop. Ultimately the crossover cable will be replaced by a microwave link between the two LANS several miles apart. There will be no internet connection.

Switches would have been a good alternative except we needed 8 ethernet ports, so 16 port swirtches would have been required. So the cost is about the same in this situation for 8 port routers.
We have the system working properly now.
This is what we did:
On both routers in "Setup: Advanced Routing" switch from "gateway" to "router" , enable RIP and set RIP versions for transmit and receive to RIPv1.
In "Firewall", disable Firewall
Then in "Setup: Network" make the following settings;
Router 1:
WAN1 IP to static       static      192.168.10.5           with subnet mask of                     255.255.255.252
LAN IP           to                     192.168.1.1                     with subnet mask of                     255.255.255.0
Router 2:
WAN1 IP to static      static     192.168.10.6           with subnet mask of                     255.255.255.252
LAN IP to                     192.168.2.1                     with subnet mask of                     255.255.255.0
With these settings, devices connected to router 1 may have static addresses in range of 192.168.1.2 through 192.168.1.254 and should have default gateway set to 192.168.1.1
Devices connected to router 2 may have static addresses in range of 192.168.2.2 through 192.168.2.254
and should have default gateway set to 192.168.2.1
Experts may have some comments to make about firewall settings an so forth but this setup does what we want it to do.

Cisco 2950 MT-RJ ports - Connect two switches?

Hi Everyone,
I'm wondering if I can connect two cisco 2950s together via the two MT-RJ ports they have?
Basically, I'd like the fibre ports to be the trunk between the two switches if possible
I have two of these:
Thanks!

Hi,
Yes, that is possible. As long as your fiber patch cable is good there should be no issues.
HTH

Connecting Two ASAs together via local interface

Hi
I have two cisco ASA routers & wish to connect them together so that traffic between is permitted with out going outside interface.
Two asa are located at in ONE office and two have separate internet connection (ISP) configured.
So here is what I did so far.
configure one of the interface on each ASA with some IP adddress.
ASA 1 ------- interface 0/6 10.1.1.1 (ASA X 1512)
ASA 2 --------- interface 0/5 10.2.2.2 (ASA 5055)
now connected a Ethernet cable to these inferface.
I was able to addd a route on asa 2.
route add interface0/5 10.1.1.0/24 10.2.2.2
but when I add route on ASA 1 I get the following error.
route add interface0/6 10.2.2.2/24 10.1.1.1
%invalid next hop address it belongs to one of our interface.

Sorry if I was not clear
I have two separate ISPs connecting two two separate ASAs.. Two asa are now connecting separate LANs.
Now I want to communicate between LANs.
So I connected an ethernet cable bw ASAs and trying to configure the route.
But not able to establish
Here is the configuration of ASA where I am faceing problem, while trying to add route
route add voice-interface 10.1.1.1/24 255.255.255.0 10.2.2.2 1
I get error says
route already exsists
interface GigabitEthernet0/0
nameif outside0
security-level 0
ip address 0.2.5.2 255.255.255.252
interface GigabitEthernet0/1
shutdown
no nameif
no security-level
no ip address
interface GigabitEthernet0/2
nameif inside2
security-level 100
ip address 192.168.1.1 255.255.255.0
interface GigabitEthernet0/5
nameif voice-interface
security-level 100
ip address 10.1.1.1 255.255.255.0
object network NETWORK_OBJ_12.1.3.0_2
subnet 12.1.3.0 255.255.255.0
object network NETWORK_OBJ_192.168.1.0_24
subnet 192.168.1.0 255.255.255.0
object network OBJ_ALL_NETWORK
subnet 0.0.0.0 0.0.0.0
description Any Network
object network voice-asa-network
subnet 10.2.2.0 255.255.255.0
object network 10.1.1.1
host 10.1.1.1
access-list outside0_cryptomap extended permit ip 192.168.1.0 255.255.255.0 12.1.3.0 255.255.255.0
access-list inside2_access_in extended permit ip 192.168.1.0 255.255.255.0 any
nat (inside2,outside0) source static NETWORK_OBJ_192.168.1.0_24 NETWORK_OBJ_192.168.1.0_24 destination static NETWORK_OBJ_12.1.3.0_24 NETWORK_OBJ_12.1.3.0_24 no-proxy-arp route-lookup
object network OBJ_ALL_NETWORK
nat (any,outside0) dynamic interface
route outside0 0.0.0.0 0.0.0.0 0.2.5.2 1
dynamic-access-policy-record DfltAccessPolicy
user-identity default-domain LOCAL
snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
crypto ipsec ikev1 transform-set ESP-DES-MD5-TRANS mode transport
crypto ipsec security-association pmtu-aging infinite
crypto map outside0_map 1 match address outside0_cryptomap
crypto map outside0_map 1 set pfs
crypto map outside0_map 1 set peer 9.2.5.1
crypto map outside0_map 1 set ikev1 transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5
crypto map outside0_map 1 set ikev2 ipsec-proposal AES256 AES192 AES 3DES DES
crypto map outside0_map interface outside0
crypto ca trustpool policy
crypto ikev2 policy 1
encryption aes-256
integrity sha
group 5 2
prf sha
lifetime seconds 86400
crypto ikev2 policy 10
encryption aes-192
integrity sha
group 5 2
prf sha
lifetime seconds 86400
crypto ikev2 policy 20
encryption aes
integrity sha
group 5 2
prf sha
lifetime seconds 86400
crypto ikev2 policy 30
encryption 3des
integrity sha
group 5 2
prf sha
lifetime seconds 86400
threat-detection basic-threat
threat-detection scanning-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
ssl encryption aes128-sha1 3des-sha1
group-policy GroupPolicy_6.2.5.1 internal
group-policy GroupPolicy_6.2.5.1 attributes
vpn-tunnel-protocol ikev1 ikev2
class-map inspection_default
match default-inspection-traffic

Connecting two SRP527W's

So I'm trying to connect two SRP527W's. I have 2 different sites, 2 SRP527W's, 2 ADSL connections. I deally I would like to connect the 2 sites using an ethernet cable from the back of each SRP. The reason why I wanbt to do this is that we are located in an area with poor ADSL infrastructure and bandwidth is an issue. I don't want to share the ADSL connection at each site I just want one site to be able to access the network of the other as they need to access the server.
Below is my current setup:
Site 1.
SRP527W with ADSL connection
IP: 192.168.15.1
DHCP Server
D-Link unmanaged 24 port switch
15 Computers connected
Server
Site 2.
SRP527W with ADSL connection
IP: 192.168.1.1
DHCP Server
7 computers connected
Cisco 10 port managed switch
Is it possible to configure port from the SRP @ Site 2 (not from the switch) to connect with the server at site 2 without the DHCP interferring and trying to change IP addresses?
I'm quite new to networking so any suggestions would be appreciated.

Hi Will,
By default, the SRP issues DHCP address from 192.168.15.100 upwards. Choose anything from .2 to .99 to statically address your server.
Not sure about your requirement for connecting the two routers. Are you suggesting that both devices are close enough (<100m) to connect them via Ethernet on the LAN side of the SRPs? If so, sure you can do this a number of ways. Here is just one:
Make sure that you are using different IP subnets on the two SRPs (ie change the default on at least one of them)
Create a new VLAN (5 for example) on both routers and assign this as the only VLAN for the ports you wish to connect together.
Statically assign an IP address from the same subnet to this VLAN on both routers: 192.168.5.1 on one and 192.168.5.2 on the other.
Create static routes on each SRP pointing to the remote LANs via the other SRP's 192.168.5.x address.
So you might have:
192.168.15.x <-> SRP A <-192.168.5.1 ..Ethernet cable.. 192.168.5.2 -> SRP B <-> 192.168.20.x
At SRP A create route to 192.168.20.0 255.255.255.0 via 192.168.5.2 and at SRP B create a static route to 192.168.15.0 255.255.255.0 via 192.168.5.1.
Hope that makes sense.
Andy

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.

Cannot connect two computers to the same game server HELP!

I have a Linksys WRT54G Router. I have two computers and I want to be able to use them on the same gaming server. Unfortunately, the game only have one port, so I can only port forward one of my computers. How can I configure my router to have two external IP addresses to the server so it won't kick one of my computers out. Thanks!

Hi,
I am in a gaming community and many members have a Linksys at home (but I don't know which kind exactly). Many of us try to connect two computers to the same server (many have a family). It seems it is a common problem that no one can connect two computers to the same game server.
I have a BEFSR41 V3 Firmware version 1.04.8
I use fixed IP address and no connectivity problem on Internet.
I have win XP SP2 on both computer.
I am using a DSL modem
I can connect the two computers to two different game servers at same time, but not the same server. Default port for this game is the same for all servers I use. I tried with both port forwarding enabled (in that case one PCs can connect the other not) or not (in the second case, whenever the second PC connects, the first one lose his connection to the server, no mater the order I try to connect my PCs).
Now the weird thing is that one member in my community just decided to throw away his Linksys router and he bought another brand (which I won't name to remains politically correct). Now, without changing anything in his PCs or his connection type, he can now play with two PC on the same server.
I am seriously thinking doing the same move. Since more and more game are now using Internet (and servers that controls piracy, $$) and family want to play together, not being able to connect two PCs on the same game server makes Linksys in bad situation from marketing point of view.
For example, in my gaming communtity, we now all know that Linksys can't handle two PC on same server, but other brand can...
Thank you in advance for your help.

Connecting two 5k's together

Similar Messages

Maybe you are looking for