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

Similar Messages

Connecting two Nexus switches with link

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

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

UCS connecting to SAN switches

I've configued UCS direct connecting into the SAN before, but not SAN switches. My understanding of the main differences between the two is this:
1) With SAN switches, you configure vSANs. To do this go to SAN tab -> SAN Cloud and configure your vSAN ID's here. Then in your vHBA template, configure it to use the appropriate vSAN ID you configured under SAN cloud. Anything else to do here?
2) Whereas with direct attached storage you connect FI-A to SPA and SPB and FI-B to SPA and SPB, with san switches FI-A goes to 'switch-1' and FI-B goes to 'switch-2'. Is this correct? If so, anyone know why it has to be this way?

No problem, tbone-111
As far as I know, only two vHBAs are supported at this time. It's best to use 1 from the A-side and 1 from the B-side.
The vHBAs that are used depend on which wwpns you zoned to your boot luns.
For the example below, assume the following convetions:
1.) my vHBAs are named, vHBA_A1, vHBA_B1, vHBA_A2, vHBA_B2 (A for A-side fabric, and B for B-side)
2.) vHBA_A1 is the first HBA on my A side, and vHBA_B1 is the first HBA on B side
AND
3.) These HBAs' wwpns are zoned properly to my boot LUNs' Storage Processor (SP) ports on the FC Switch
AND
4.) These HBAs' wwpns are LUN masked properly on my array
Those are logical ANDs, by the way, they must ALL be true to prevent headaches later on.
5.) Disk Array SP ports A0 and B1 are connected to my A Fabric FC switch. B0 and A1 are connected to my B Fabric.
6.) This example boot policy will have the A Fabric be the primary boot path
-FYI, best practice to have at least 2 SAN Boot policies (1 for A-side and 1 for B-side, and evenly distribute among your Service Profiles).
In my boot policy, I check the enforce vHBA naming option and specify my vHBAs names (sorry I don't have screenshots available. just started with a new company and don't have lab access yet).
My SAN Primary setting might be: Primary Target: A0's wwpn and Secondary Target: B1's wwpn
My SAN Secondary setting might be: Primary Target: B0's wwpn and Secondary Target: A1's wwpn
It would be a good idea to confer with your Storage Admins while you are setting up the first couple of servers to boot on each Fabric to help with any troubleshooting.
If zoning and LUN masking are configured correctly, you should see WWPNs listed during the UCS Server Boot sequence at the point where the FC Boot driver is being loaded.
Of course, get Cisco TAC on the line if you run into any obstacles that you cannot get past.
I hope that helps,
Trevor
======================================================================================
If my answers have been helpful in any way, please rate accordingly. Thanks!
Message was edited by: Trevor Roberts Jr

Connecting two SRW2048 switches over multimode fiber

I've bought several SRW2048 switches to upgrade our old 10/100 switches, but I can't get them to connect over my multimode fiber. I bought some MGBSX1 SFP GBICs and LC-ST fiber cables to connect to the fiber runs, but the two won't talk to each other... any ideas? I'm pretty sure I have the ST connectors set up right... on one switch it goes red/black (Tx/Rx) and on the other end it's black/red (Rx/Tx). This is my first time trying to upgrade fiber equipment so my vocab may not be exact... any help would be GREATLY appreciated...
Kevin

Sorry, I'm just now getting back to this issue... I turned off the auto-negotiated speeds on the ports connecting miniGBIC to miniGBIC, but I'm still getting broadcast storms on the network and I think it's slowing things down... All I did was plug in all the switches and make the auto-negotiated speed change...
I don't know anything about VLANs and port trunks... I didn't change any of those settings... Could that be part of the problem? I have 7 SRW2048s connecting to each other in a cascade(?) and could the fact that they're all on the default VLAN1 without any changes to the trunking be the issue?

Best way to configure and connect two 4500 switches

I have a core 4507r+e in our production environment. We just acquired a 4500r and I would like to use it a distribution switch. What’s the best way to configure the new 4500r switch to connect to the core 4500 switch?

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
BTW, when you link your core to your distribution, the connecting link can be L2, L3 or both.
What I wanted to bring to your attention, 4500s can often easily oversubscribe some of their ports. Much depends on the sup and line cards being used. When you want to interconnect a core and distribution, you don't want to use a port that's something like 8:1 oversubscribed. (Further, if you're doing mostly L2, and all traffic L3 has to go to the core, depending on you traffic flows, a single link might have insufficient bandwidth.)
Also from core to distribution, if possible, it's good to avoid single points of failure. So if you only have one link between them, that link's transceivers (if used), the ports connected to, the line card connected to, are all single points of failure. (Of course, with only single sups in each chassis, that too is a single point of failure. From what you've described, from a performance and redundancy standpoint, you might actually be better off using a 4510R, with your two sups [if same model] and line cards - creating a collapsed core/distribution.)

Regarding San Switch

Dear All,
I have some quaries about the San switch -DS-C9148D-4G48P-K9 and DS-C9148D-8G48P-K9.We need the cable specification for the connectivity between San switch and servers and tape library and SAN to switch.
waiting for your feed-back .
Thanks,
Whead-Ul-Islam

The parts listed are port licenses. The following document may be of value.
Cisco MDS 9000 Family Pluggable Transceivers Data Sheet
http://www/en/US/prod/collateral/ps4159/ps6409/ps4358/product_data_sheet09186a00801bc698.html
Thank You,
Dan Laden

Do we need to create two zones for Two HBA for a host connected with SAN ?

Hi,While creating Zone , Do we need to create two zones for Two HBA for a host connected with SAN ? Or a zone is enough for
a host which having Two HBAs...We have two 9124s for our SAN fabric...
As I found like one zone below, I little bit confused that , if a host having two HBA connected with SAN, should I expect two zones for every Host?
from the zone set, I gave the command show zoneset
zone name SQLSVR-X-NNN_CX4 vsan 1
    pwwn 50:06:NN:NN:NN:NN:NN:NN
    pwwn 50:06:NN:NN:NN:NN:NN:NN
          pwwn 10:00:NN:NN:NN:NN:NN:NN
But I found only one zone for the server's HBA2:by the same time in the fabric I found switches A & B showing the WWNs of those HBAs on its
connected N port...Its not only for this server alone, but for all hosts..Can you help me to clarify on this please..that should we need to create one zone for
one HBA?

if u have two independent fabrics between hosts and storage, i think the below confs are recommended.
Scenario 1: 2 HBAs single port each ( redundancy across HBA / Storage port )
HBA1 - port 0 ---------> Fabric A ----------> Storage port ( FAx/CLx )
HBA2 - port 0 ---------> Fabirc B ----------> Storage port ( FAy/CLy )
Scenario 2: 2 HBAs of dual port each
HBA1 - port 0 -------> Fabric A ---------> Storage port ( FAx/CLx )
HBA2 - port0 ---------> Fabric A ---------> Storage port ( FAs/CLs )
HBA1 - port 1 --------> Fabric A --------> Storage port ( FAy/CLy )
HBA2 - port 1 ---------> Fabric B --------> Storage port ( FAt/CLt )
the zone which is in your output is VSAN 1. if its a production VSAN, Cisco doesn't recomends to use VSAN 1 ( default vsan ) for production.

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

Physical redundancy (CSS connected on two different switches)

Hello,
Is it possible for redundancy reasons to connect a CSS to two different switches (like we do for access switches) ?
I know that one option is to configure both interfaces in the same vlan and use the spanning-tree for the redundancy. However, this will not be transparent for the end-user due to the slow convergence of the spanning-tree (uplinkfast or rapid-pvst is probably not supported).
Are there any other options ? One interface active, the other backup ?
Thanks in advance for your reply.
Gaetan

Gaetan,
for the CSS we suggest to be connected to only 1 switch and if the CSS detect a failure with the switch, force failover to the redundant css.
If you have ASR configured, failover will be stateful.
Gilles.

Can I connect two switches to a server?

We share an office with another company but we currently have separate servers and networks.
I'm looking into the possibility of us sharing their server.
The thing is we both have our own switches and and I want to avoid any rewiring of the network. Will I be able to use two switches?
It's a 2x 2.8 GHz quad core intel xeon (with dual ethernet). So is it just a matter of connecting both switches to the server and configuring them in some way?

Hi Christiaan,
I end up doing this quite often. You have a few options, the simplest is below...
How many users and devices that require network connections does each company have? If it's under 254 which it sounds like it is and your happy to have the users on the same network, sharing the same ISP. Then the easiest option is going to be your company sharing their network. You'd save a bit of money on your internet connection which could be used to increase the bandwidth on the other companies line if needed.
You would do following. Make sure all devices that need a fixed IP address such as printers/mfds'/switches/WiFI/phone system (if applicable) are changed to a fixed IP address with the relevant subnet mask, dns and gateway from the other companies network. You'd obviously need to get the relevant numbers from their IT guy.
Then you could use your switch as extra capacity on their network by linking it with their switch. Obviously you'd want to use the fastest possible connection between the switches or look to buying something new with more ports. If you both have something like the HP 1810G ProCurve or a compatible switch you can buy two fibre transceivers and connect them with a fibre cable, this will free up more ports for users on the switch or simply connect them via an ethernet cable. On the 1800 series you can use LACP which allows you to use up to 4 ethernet ports to improve the bandwidth thus giving you a 4gigabit connection to their network. Depending on how much traffic there is going to be you might want to skip that as there might be no need.
Then it's just a case of creating your users on their server and creating an area for your company that only you have the access rights to and creating a shared area inter-company area if you want to easily ping them over files.
What do you both use for email? Are you going to look to share a server for it?
Hope that helps
Beatle

WLC5508 connected two switches

Dear All,
I have a WLC 5508 and a brief connected like below.
Internet->Router->2960G A-> (Port0) WLC5508 (Port1) -> 2960G B-> Access Points <-> wireless clients
My Question : Is the above topology work? The access points register to the controller via 2960B, and the data traffic ffrom wireless clients go through from 2960G B to WLC port 1, and WLC pass it to port 0 itself and then go to internet?
Thanks.
Mic

As long as you don't have LAG enabled that will work. You do need to specify a dynamic interface in which the Internet traffic will egress. Your management will be primary port 1 and the your dynamic interface will be primary port 2. Of course port 1 and port 2 would have to be on a different subnet.
If you have both on the same subnet, that will not work. You would trunk the ports and only allow the vlans for that port. Port 1 connected to the switch would only allow the vlan for the management. Port 2 connected on the switch will only allow the vlan for that dynamic interface.
Sent from Cisco Technical Support iPhone App

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 WAP4410N

Dear Friends
I have TWO simple questions and I hope you will help me to find answers
Q1:
I have 2 WAP4410 , in two floors in a building,
some computer clients connect to one of them.
other clients connect to other one.
I want to connect both of 4410N together without cable.
I read ,if I set one of them as REPEATER, it will not acceibble for clients to connect !
I dont want it !
I need clients to be able connect to each one , and both of them connects together normally.
please help me how to do that ? (the exact config please)
Q2:
In another building , I want to put 6 of 4410N to 6 floors.
do u suggest to connect all of to a 8 port gigabit switch via cable ?
or connect all of them exactly as above question (wireless) ?
which one is better ?
THANK YOU VERY VERY VERY MUCH FOR YOU HELP
MRR

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
Hello MRR,
I am not quite sure your question (Q1). Why do you need to connect two AP together without cable? Usually we can provide end-users with ESS solution which can provide users roaming from one area to another if you have two or more APs. Anyway on the backend of AP generally connect to wire-network to give user scalability of network access. It may also solve your Q2.
Repeater is only needed if your provided area is too far away from wire-network or out of reachable of wire-network and signal is too weak at that area.

Connecting two san switch in cascade

Similar Messages

Maybe you are looking for