Connect two SRW 2024 switches together
I have been doing some research on this and I am getting mixed results. I have 5 VLANS setup, not including the native VLAN 1. VLAN1 has port 1 as untaggged and set to trunk. The rest excluded. VLAN 100 has port 1 set to trunk and tagged, and 9-12 untagged. VLAN 200 has port 1 trunk and tagged and 2-6 untagged. VLAN500 port 1 tagged/trunk, and ports 14-20 untagged. VLAN 600 has port one as trunk but excluded and 21-24 as untagged. VLAN 700 has port 1 as tagged and 7 and 8 as untagged. All I did was buy an exact duplicate of the switch, another srw2024 and I want to connect it to this existing switch. Could someone tell me how I can do this two ways: one way to expand the VLAN's to the second switch and one with just adding the second switch and be able to create new VLAN's? Any help is greatly appreciated! Thanks =)
Solved!
Go to Solution.
Yes; however, the number of VLAN port members doesn’t necessarily be the same. You may have more LAN ports on the other switch that will be a member of a certain VLAN ID. The most important configuration is the membership of the “trunk” port to the VLANs you want to pass through to the other switch.
Similar Messages
-
Connecting two linksys gigabit switches
Hi,
I just bought a slm2024 (24 port managed Gigbabit switch) to replace an older 100Mbit switch. The old switch had PCs and other switches connected to it. The other switches are EG005W ver. 3. (linksys workgroup 5 port gigabit switches)
With the new slm2024 switch, the PCs have no problems connecting. The problem is the EG005W switches. The port on the slm2024 which connects both switches is dark (the LED is dark - no lights at all). Any thoughts on what is the problem? Do I need to configure something special on the slm2024?
I do have an older 100Mbit switch and if I connect it to the new slm2024 switch, the lights are on and traffic is flowing. It is just the EG005W that does not seem to like being plugged in the gigabit switch. It used to work when plugged in the older 100Mbit switch.
Oh and if I try to plug in two EG005W together, I get the same problem. PCs connected to the 2nd switch cannot communicate out either.
I understand that in the past cross-over cables where needed to connect switches but I thought that new switches no longer require this (even my old 100Mbit switch did not require this for the EG005W to work through it).
Any thoughts on how to fix or debug this?
Thanks for any suggestions.there shouldn't be any configuration needed on the ports of the SLM2024 because they are already "smart ports"
this could be a possible problem between these 2 devices -- have heard of similar problem before bet. a switch and hub but i have forgotten their model numbers -- you would think that since they came from the same manufacturer you will have an easier set-up but sometimes that's just not the case -
Connecting two Cisco 2950 switches to a 2600 router
Hello,
I'm trying to have two LANs connected to 2950 switch each, connect to a 2600 router and have the two LANs communicate with each other...i can't seem to get it working...any help...thanks
LAN 1 192.168.10.1/20
LAN 2 192.168.12.1/21
Thanks againAlright, these are only basic configs here:
Router
hostname Router
int fastethernet0/0
description Network 1
ipaddress 192.168.10.65 255.255.255.192
int fastethernet0/1
description Network 2
ip address 192.168.10.129 255.255.255.192
end
Switch 1 (the one connecting to f0/0)
hostname SwitchNet1
int f0/1
description Host 1 Net 1
no ip address
no shut
int f0/2
description Host 2 Net 1
no ip address
no shut
int f0/3
description Host 3 Net 1
no ip address
no shut
int f0/4
description Host 4 Net 1
no ip address
no shut
int range f0/5 - 23
no description
no ip address
shut
int f0/24
description UPLINK to Router
no ip address
no shut
int vlan 1
ip address 192.168.10.66 255.255.255.192
no shut
default-gateway 192.168.10.1
end
Switch 2 (the one connecting to f0/1)
hostname SwitchNet2
int f0/1
description Host 1 Net 2
no ip address
no shut
int f0/2
description Host 2 Net 2
no ip address
no shut
int f0/3
description Host 3 Net 2
no ip address
no shut
int f0/4
description Host 4 Net 2
no ip address
no shut
int range f0/5 - 23
no description
no ip address
shut
int f0/24
description UPLINK to Router
no ip address
no shut
int vlan 1
ip address 192.168.10.130 255.255.255.192
no shut
default-gateway 192.168.10.129
end
This config assumes only ports f0/1 - f0/4 will be used on each switch. If that is not the case, you will need to modify the interface configs accordingly. You may want to use descriptions more suited than to your network on the switchports. Also, this config assumes the router is connected to port f0/24 on each switch as well.
The default-gateway for the hosts and the switches is going to be the router IP address for the subnet they are attached to. The hosts/switches attached to f0/0 use 192.168.10.65 as their gateway. The hosts/switches attached to f0/1 use 192.168.10.129 as their gateway.
You do not need to configure a port on the switch as the default-gateway. The default-gateway is an IP address the host/switch uses to direct all traffic from itself out past the router. In fact, if you don't need the switch to talk to devices on the other subnet, you don't even need to configure a default-gateway on the switches (but I would anyway). -
Connecting two seperate office networks together
Hi folks, really sorry for asking stupid questions but relatively new to the complexities of networks.
We have two offices. Each have their own networks running through wired and wireless routers all back to a single ADSL link. So all can access, share etc. This is simple to set up as each Mac just see's the other and hey presto it works. Cant get my head around manually configuring things though which I presume is the answer to this post.
I need an idiots guide as to how we now get each location to see the other, thus combing these two networks so that office A can now talk to B . I presume this is simple, does anyone have any pointers for us.
Many thanks for the help I am sure I will get.
GraNot daft at all. Networks are not easy to configure sometimes, and from reading your message, I may have erred in my understanding of your original post. I guessed they were in the same office complex and separated by a small distance. It should not be necessary to assign an IP number as DHCP works in most situations.
If you have two ADSL routers, this is not going to work. I presumed the words, "single ASDSL link" meant these were sharing the same ADSL. but that appears now not to be the case.
What you seem to say is:
ADSL 1 --> Network 1
ADSL 2 --> Network 2
Each ADSL router will be allocated an external IP address by the service provider (ISP) and the router will allocate a network address which is unrelated to the external IP address.
If you want to link these, you would need some additional software or another way to connect, depending what the purpose is: VPN, Back to My Mac.
More data please? -
Two srw switches with vlans and pfsense gatway
Hi,
I've got a bit of a problem that a can't seem to get a handle of things.
I've got two srw 48 port switches that I would like to link together and then on to the pfsense box.
First I'd like to connect the two switches to see if everything works and then on connect the pfsense box.
Now I would be very great full if someone with a bit more experience with VLANs would be so kind to walk me trough the procedure of creating VLANs, configuring them to ports on the switch and connecting the whole thing to another switch.
This is what I've done so fare.
1. I created 3 VLANs on both switches (VLAN2-office,VLAN3-WiFi, VLAN5-VoIP). I've created these VLANs with the same tags on all the devices.
2. I configured the ports that connect the switches as trunk. (I can't seem to be able to configure anything else on this port. Is there something else I should configure on these ports?)
Now as fare as I understand the documentation the VLANs on each switch should now see each other.
I'm still not sure on how to configure a physical port to one VLAN. After creating the VLANs on both switches and connecting them trough the trunk port I set ports 10-20 to VLAN2 by going to VLAN Management -> Ports to VLAN I selected VLAN2 and marked ports general and untagged and saved the settings. I repeated the procedure on the other switch. Now if I stuck my network cable into one of this ports I didn't get an IP anymore form the DHCP witch means that they were on a different VLAN than the other ports so I setup another router to act as a test DHCP with a different IP range as the main DHCPto see if it works. Now when I connectedthe test router to one of the ports in VLAN2 and my PC to the same VLAN2 port I got the test IP no problem. But when I connected the PC to the other switch VLAN2 port nothing happened until I connected the test DHCP to one of the VLAN2 ports. So clearly the switch VLANs are not communicating.
Now I don't know did I forget something, made a mistake with some setting or I just don't know what I'm doing because I think I need to get the VLANs between switches working before tackling the pfsense connection.
I would be really great full if someone explains to me how to set these VLANs up so that they would work between switches.
Thank you for your help.Hi,
I was successful and I did exactly that. I put all VLANs on trunk ports and the switch to switch to pfSense started to work.
The only thing that gave me some problems was the end port(port connecting to the device pc, phone, printer) configuration. I was under the impression that the port was supposed to be in general mode and tagged. But I figured out that the port is supposed to be in access mode and untagged and only a member of one VLAN(the one I wanted it to connect to).
Anyway all is working now and I've figured out all the kinks.
So thanks guys for the help.
Nice day to all.
Bye -
Linking two switches together.
hi Guys ,
quick question in relation to joining two switches together,
can I link a 2950 switch with a 1000 BASE-SX with a 3560G with 4 SPF ports with fibre and what pitfalls should i look out for .
Thanks in advance
KevinHello,
So you would like to connect GBIC to SFP, you need Multimode Duplex Fiber Optical cable with SC-LC connectors. If SFP to SFP you need the same cably type with LC-LC connectors.
http://www.cisco.com/en/US/products/hw/routers/ps341/prod_module_installation_guide09186a00801cc731.html
http://cisco.com/en/US/products/hw/modules/ps5455/products_data_sheet09186a008014cb5e.html
bye
FCS
Please rate me if I helped. -
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. -
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 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! -
hi,
What is the best way to connect switch together (with 2960 switch)..cross or stright cable...up/down or normal port ?
WAN ----Router 1 --- -SW1 ---- SW2
|
|
SW3----SW4----SW5 (no vlan)---PC1
all switch has up,down and normal port except SW5
Does SW5 will support vlan if it is connect to a layer 2 switch (let s say sw5 is connected to port 5 of SW4 (and port 5 is VLAN 20 access mode...then trunk between SW3 and SW1))...is there any inheritance ?
Hope, this time, this post will be post on the forum.
Thanks for help,Hi Loic the wire between switch 4 and 5 shouldn't make a difference in terms of rj45 so long as it is auto set (which by default it is). If you want switch 5 to be vlan 20, configure vlan 20 there and the port on switch 4 must also have vlan 20. So long as either switch is tag or untag, but both configuration matching it will work fine.
-Tom
Please mark answered for helpful posts -
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 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 san switch in cascade
I am planning to connect two San switch in cascade because the 2/16 san switch that I am using now only have one unused port and I am planning add four server more. So my less expensive solution is using a second 4/16 switch that I have.
- My questions
How I do that ?
Do I need a special license?
Do I need some other change in the ports configuration for this purpose?
Some care I must take?
Thank you
EhabThe answers to your questions are really going to depend on the make and model of your switches.
Some switch types require a license to configure E_Port (switch-to-switch) functionality, but most do not. Whichever port(s) you use to make the connection will need to either be configured as an E_Port or configured in a mode that will allow it to auto-negotiate itself to E (this could be a GL_Port, Gx_Port, or U_Port depending on switch vendor) after the switches establish communication.
If the switch that you are adding has some zoning defined on it that is different than the existing switch then you may run into some conflicts so it is often best to just clear the zoning config on the switch that is being added. Finally, you would want to make sure that each switch has a unique Domain ID otherwise the two switches will segment and not merge. By default, most switches are set to Domain ID 1 so just make sure they are both not set to 1.
hth.
-j -
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 -
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.
Maybe you are looking for
-
How do I get this beta IOS 7.0.2 JUNK TO WORK with my iPod touch 5???
How do I get this beta IOS 7.0.2 JUNK TO WORK with my iPod touch 5?? I was prefectly happy with my iPod until I got the notice to upgrade itunes to 11.1 and would you like to upgrade your iPod from IOS 6 to IOS 7. And like an idiot I took the little
-
I have had itunes forever!! When I try to open my itunes now...it says I am missing MSVCR80.dll. I had my computer tech in and he was unsuccessful after 2.5 hrs and 150.00 later. I run windows 7 and have for about 3 years....and only now, just lost
-
Hello, while monitoring AE I observed AE URL is not correct. My server name is ServerXX Then, I should see the URL for testing my message in RWB as below. http://ServerXX:50000/MessagingSystem/receive/AFW/ But it is showing ServerYY which i am not su
-
I cannot drag and drop for Photos in 10.10.3
I seem to be unable to drag and drop from the new Photos application in Yosemite 10.10.3. I have tried this with two different applications including Adobe's Photoshop Elements 13. It seems to work fine with other apple applications. (can drag and
-
Cannot print banners in Illustrator
I am using Illustrator CS6 and cannot for the life of me get the page setup right for the roll paper printing. I have an Epson Stylus Pro R3000, cannot print a banner when using the roll paper. Image size is 290mm x 583mm. Every paper selection, A3+