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

Similar Messages

Aironet 1140 series units won't connect to a gigabit switch

I just installed 2 new units and neither will connect to a new HP gigabit switch - no link light, other devices can connect to the switch OK. Their gigabit ethernet settings are set to auto for duplex and speed. I also tried forcing one of them to full duplex and 1000 Mbps which didn't work either. They're both powered by POE injectors. If I connect them to a 10/100 switch they work fine.
Am I missing something?

Leo,
Thanks for the reply, sorry I'm late getting back to this, I was lucky enough to have a long weekend off.
I'm no cabling expert, that's why I hired somebody else to do it. But I have a question: should standard cat 5 cable work?
If so, I disconnect the WAP from the cabling that was installed and hooked it up with cat 5 patch cables that I confirmed to be work OK by using them to connect the gigabit switch to a laptop. When I used the same patch cables on the WAP I still got a failure to connect to the same switch. So unless it's not standard cat 5 that I should be using it doesn't appear that cabling is my problem.

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 again

Alright, 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).

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.

Cant connect two linksys routers to each other.

well the routers we have are the WRT54G and the WRTSL54GS but i m not sure about the second one (it has three antenna) . so we have the WRT54G hooked to the modem and its recieving internet and working with the (wired) main computer. so now we have to go about 1 block away to a neighbors house. and we set up the WRTSL54GS set up 1/3 of the way. now the laptop a block away from the main computer is recieving a signal (3 bars) from the WRTSL54GS. but it can not connect to the internet. what am i doing wrong?
Main comp-WRT54G----------------------WRTSL54GS--------------------------------------------------------laptop

Both routers are “transmit” devices and were not made to talk to other routers. You would need a wap54g or third-party firmware to make your router an access point.
WRT310N
WRT350N
WPC4400N
EG1032
NAS200
SD2005
PAP2
WPS54G

G5 imac wont connect to gigabit switch at 1000

Hi,
I've got a G5 imac that wont connect to my gigabit switch at 1000. It looks like it connects at that speed for a few seconds then it drops to 100. I have a new Macbook pro that can easily connect at 1000 using that exact same cable.
Has anyone heard of any gigabit issues with G5 imacs?
Thanks,
Scott

I am now pretty sure it is the imac ethernet port. Connected the imac and mini together and eventually it set itself to 100Mbs.
Now trying to decide if it is worth getting fixed or just dealing with it only connecting at 100Mbs.
Thanks
Jason

Adding a Gigabit switch to HH2 - any point?

I currently run my home network though a 10/100 switch connected to my HH2. My son plays on-line games and watches 'on demand' TV programmes. Occasionally there's some 'stuttering' on sound and picture.
Would there be any improvement if I swapped out my 10/100 switch for a Gigabit one, or would this only affect 'internal', home network file swapping/sharing?
I've tried asking BT Technical what the speed of the ethernet ports are on the HH2...
Solved!
Go to Solution.

JohnX wrote:
I currently run my home network though a 10/100 switch connected to my HH2. My son plays on-line games and watches 'on demand' TV programmes. Occasionally there's some 'stuttering' on sound and picture.
Would there be any improvement if I swapped out my 10/100 switch for a Gigabit one, or would this only affect 'internal', home network file swapping/sharing?
I've tried asking BT Technical what the speed of the ethernet ports are on the HH2...
I think you've guessed the answer already... it won't make online access any better, the bottleneck will be your broadband connection. The gigabit switches (and NICs for that matter) tend to use more power and run hotter in my experience, so I wouldn't recommend the switch unless you have a definite requirement for one.

Connect two routers-wireless

Hello, I am looking around the forums and can't find and i'd like to know next:
I have two routers Linksys (wrv200 and wrt110). One on one side of the house, the other will be at the other side od the house. Questions:
- Is it possible to wirelessly connect second to frist
- Second willl broadcast the same SSID (wireless and other settings) as the first and will have the function of covering the signal on the other side of the house and outside, where the first virtually could not
- Which one of these two routerja recommend as the first (connect to a modem)
- What is all need to set athe first and second routerj
Thanks for help.

You cannot connect two Linksys Routers Wirelessly, you have to have them connected with cables...see this

Connect two G5 with 1000BASE-T (Gigabit) - how?

what i need to connect two G5 dual 1.8 with 1000BASE-T (Gigabit)?
just a cable or some cards and routers and ....?

Yeah, like tele_player said, it's a little harder if you want them to both have internet. We just set up our MDD and quad on a gigabit switch that so they can communicate with each other at gigabit speeds and then the switch was hooked up to a router for internet access. It wasn't that bad and we got all the supplies online for cheap. 50 foot sections of CAT 6 cost about $10. If you need to go through walls or anything like that, get the tool-less keystone jack connectors...they'll make your life much easier.

Linksys Cisco SRW248G4P 48-port 10/100 + 4-port Gigabit Switch Help

The switch which is a Linksys Cisco SRW248G4P 48-port 10/100 + 4-port Gigabit Switch, was configured by a contractor which was long ago run off, and the documentation left behind to log into the switch is incorrect. How can we reset this switch so we can configure to the new required settings?
I have attempted to go in through the web browser gui, and no luck logging in via factory default creditials, cannot log in using any of the common admin creditials, nor can we get in via the documented admin name and pw the contractor left.
Attempted ot go in through the console, that doesn't work right at all. Takes 15-20 min before I start even seeing user name or password boxes. Cannot type a single thing into those boxes. I have set the hyperterminal to com1, 38400, 8, none, 1, hardware. It kinda lets me see some of the log in screen, but will not let me type into the username whatsoever.
Logging via web browser I see all the login option but not a single username or pw works. Please if anyone can help, this has been an issue which is now critical.

Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center.
The settings for connection using Hyperterminal through the Console port should be:
Bits per second: 38400
Databits: 8
Pairity: None
Stop bits: 1
Flow Control: None
When you finish configuring the HyperTerminal, the Login screen appears. The first time you open the Console Interface, use the default username admin and leave the password blank and press the Enter key. You can set a password later from the User and Password Settings screen.The Main Menu screen displays six menu choices: System Configuration Menu, Port Status, Port Configuration, PoE Configuration, Help, and Log Out.
User and Password Settings, IP Configuration, File Management, Restore System Default Settings, Reboot System and Back to Main Menu.
To restore the Switch back to the factory default settings, select Restore System Default Setting and press Enter. A confirmation message appears asking Are you sure? [Y/N]. Press the Y key to continue or the N key to cancel the action.
System Configuration Menu options: (Which is where you will need to go) consist of: System Configuration, Management Settings
After pressing Y, at this point reboot your system and it will be back to Factory Fresh.
If you have any questions or this doesn't work, please let me know. I am attachng the Admin Guide for you as well.
Eric Moyers
Cisco Support Network Engineer
1-866-606-1866

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.

Adding Two Gigabit Switches to Airport Extreme

I want to add an 8-port D-Link gigabit switch to my brand new Airport Extreme to network my Mac Pro, my iMac and two printers in the office. The MacBook Pro would run wirelessly. Then, I want to add a 5-port switch 100-feet away (and down another floor) to directly wire the Apple TV, the DSS tuner, the blu-ray player and maybe use my older non-n Airport Extreme to radiate in that far away room also. Sound like a plan to you wizards? :--) Or am I nuts. Using gigbit cables.

Nope just get a small ethernet to go from one of the 4 hookups on the AE to go to the switch.

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

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 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
Ehab

The 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

Connecting two linksys gigabit switches

Similar Messages

Maybe you are looking for