Give me two switchs...

I am gona install workgroup switchs in 3days..I am confusing to choose ones.
The followings are required.
<<1>>
(packets switching over 38.7Mbps).
1.24ports.
2.FabricSwitch Bandwidth: 28Gbps
3.supporting 10/100/1000 Mbps Ethernet ports each(over 24 ports).
4.supporting 2GIBC ports( over 2 ports).
5. supporting 16MB Flash, 128MB DRAM.
6. Supporting Dynamic VLAN and Voice Vlan.
7. Supporting PVST+ and IGMPv3 snooping.
8. supporting Radius and TACACS+ Authentication.
<<2>>
(packets switching over 10.1Mbps).
1.48ports
2.FabricSwitch Bandwidth 13.6Gbps.
3. over 48 10/100 Ethernet ports
4. over 2 GIBC ports
5. 8MB Flash, 16MB DRAM
6. IEEE 802.1W(RSTP) and IEEE 802.1S(MSTP)
7. Supporting IEEE802.1x authentication.
8. Supporting traffic controling base on TCP&UDP and MAC.
Could U recommand me any switchs please........

Hi,
I would suggest you to go for 3750's and that suits your all the requirement.
Please see the following links :
http://www.cisco.com/en/US/products/hw/switches/ps5023/index.html
Product specifications:
http://www.cisco.com/en/US/products/hw/switches/ps5023/products_data_sheet09186a0080161371.html
HTH,
-amit singh

Similar Messages

Using Trunking 1.3 to create a trunk accross two switches

Hi:
I have installed Solaris Trunking 1.3 on my SF 880 which is running Solaris 10. It has two CE interfaces which i have configured in one trunk. Failover works fine when I connect them to a single Nortel 8000 switch. The problem is that I can't get failover working properly when I connect one CE interface to a Nortel 8000 switch and the other CE interface to another Nortel 8000 switch. Should this work? I have seen many references, eg in the Solaris Trunking 1.3 documentation, that actually says you can't create a trunk accross switches but i also found BUG ID 5079123 which says you can.
By the way I can't use the version of trunking software that is bundled with Solaris 10 because it doesn't support the CE interfaces.
Cheers
Steve

Thanks for your reply. I should have mentioned that i don't need load balencing over the trunk to work. I just need failover to work. In fact that is just what the bug id says i should be able to do across two switches. Here's a copy of the bug id:
Bug ID: 5079123
Synopsis: Trunking 1.3 to support L2 failover across switches
Category: enet_trunking
Subcategory: softwareState: 10-Fix Delivered
Description: Due to overwhelming requests to support L2 failover solution for Sun NIC across two switches. This is not trunking or Link aggregation feature as it breaks the standard of all trunk members connect to one switch.
Requirements are :
1. provide Layer 2 failover similar to IPMP(layer 3) and yet be simple enough to configure.
2. No loadbalancing.
3. Connect across two switches. and when one switch/nic fails, the traffic moves seemlessly and instantly.
4. Failback: When the failed link is back online, traffic moves back to original link. Date Modified: 2004-09-08 06:13:32 GMT+00:00
Cheers
Steve

Can I create a port channel to two switches that are not stacked?

Two switches, not stacked, but connected together via 802.1q trunk.
Server with four NICs, capable of trunking and LACP.
Can the switches be setup to have an etherchannel between the two switches and the server?

Hi,
In short NO
You would need to connect your server to only ONE switch if you want all 4 nics in the same TEAM.
You could use 2 TEAMS and put 2 nics in each forming a 2 port etherchannel to each switch
Regards,
Alex.
Please rate useful posts.

Two Switches with same MAC+Priority running STP

Hi
what will happen if two switch with same MAC-ADDRESS and same STP priority will run STP , how will elect to the root bridge ???? how the STP process will handle this situation?
thanx

Well, first off, no two switches (or switchports) will have the same MAC (if they do, you're buying switches from the wrong, very bad place).
Every port of the switch will have (at least) one MAC of it's own.
Given the same priority for all switches/bridges on the LAN, the lowest switch/bridge MAC on the LAN will win as the root.
VLANS take on the MAC of the administrative interface ("CPU"): i.e., xxxx.xxxx.5000, the first port (i.e., fa0/1) is xxxx.xxxx.5001, the second (fa0/2) is xxx.xxxx.5002, and so on
If you do a "show interface", the MAC / bia is displayed in the second line.
Good Luck
Scott

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
Kevin

Hello,
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.

Fiber connection between two switches

Hi All,
Here is the situation, I have two switches which are SF200 and SG300 and trying to link them up using sfp module ( fiber).
They are both in trunk mode and the connection is up but nothing or no ip traffic goes through it .
I have ensured allowed vlans are correct, native vlan do match but still nothing .
Then i did a port monitor on it ( replicate it to another port) but all I could see was bunch of stp,arp , mdsn and llc traffic. nothing to do with do1q extension.
I used wireshark , would I be able to monitor trunk traffic at all? would the protocol be dot1q ?
However the fiber link works if I plug one of the connection which goes to the sg300 to a fiber convertor and then connect a rj45 cable from the convertor to the sg300 rj45 port. that is the only way which it works. This suggest to me a possible issue with the fiber module on the sg300 however I have tried few differnet modules and still nothing , I did even try the one which is on the sf200 ( working ) and still nothing .
What boggles me is the fact that the link is seen as up and all good by both switches but nothing does go through them.
Any one know what the cause could be ?
Thanks

Wrong forum, post in "Small Business switches". You can move your posting with the Actions panel on the right.

Link aggregation stradling two switches?

Hey guys, I'm back with more questions about Link agregation. I figured out that I do have to manually configure both of my switches to support it. Now though I'm stuck with trying to figure out the best way to implement it. I have a Netgear FSM726 and a Linksys EF24G2. Both are 24-port 100BT switches with 2 Gigabit ports on them. They are currently setup like this: The Xserve runs with one gigabit port going into one of the gigabit ports on the Linksys. The other gigabit port on the linksys runs into the Netgear to join the two together. That leaves one open gigabit port on the netgear.
So in order to setup link aggregation I'd have to use two gigabit ports on one of the switches, or use two 100BT ports. Alternatively, I was thinking if I setup link aggregation on the Xserve and then just ran each of the two lines into one gigabit port on both switches it may work without having to do any configuring on the switches? Will that cause any problems with network traffic?
If I go with the gigabit port on one switch idea, as far as I see, I'd have to join the two switches with a 100BT connection instead of the current gigabit line. I'm not even sure if that matters really. So which way is a better way to go? Also, if I go with using the gigabit ports on one switch, can I use two open 100BT ports to join into the other switch for increased bandwidth? Thanks for helping out here.

Steve has it right. Link aggregation only works between two devices (e.g. a server and a switch, or two switches). You cannot link three devices (a server and two switches) using a single link aggregation. That's because of how the traffic flows over the link.
Your best solution depends on the traffic patterns on your network - where are the clients that are hitting this server?
If you have a dozen clients that hit the server a lot, plus more clients that don't hit it much (or at all), plus printers, etc., you could use two of the gigabit ports on one switch as a link aggregate to the server and plug the busy clients into that switch, then plug the other clients into the other switch, using a 100base-T link (or multiple 100base-T links) to connect to two switches together.
This may or may not be viable, in which case a separate gigabit switch to connect the server and the two existing switches may be the best solution.

HT1766 Hi can I add the touch define to my iPad 4 my iPhone 5 has this feature when I touch word it give me two choices copy and define but only copy with iPad 4 please answer me

Hi can I add the touch define to my iPad 4 my iPhone 5 has this feature when I touch word it give me two choices copy and define but only copy with iPad 4 please answer me

Because...!
I've no idea why either.
Although it isn't normally possible to sync an iPod/iPad/iPhone with two computers (or manually manage an iPhone from more than one) it can be achieved if all computers have copies of the self same library. See Re: how do i sync on a second laptop without the data on my iPhone 5 being erased?
tt2

If I do a creative cloud membership does it give me two computers and other devices like an ipad? Or just one computer one mobile device?

If I do a creative cloud membership does it give me two computers and other devices like an ipad? Or just one computer one mobile device?
Thanks

You can have functional installations on two machines. The machines have to meet the system requirements for the software.

How can i subtract two numeric numeric numbers from two switch cases ?

I have two switch cases in my labView program. I can see them individually on front panel but i need to subtract them and see the result on front panel.
Can someone please help me out...
I am trying to display (Result1 - Result 2) on my front panel. Result1 and Result2 will change with time.
Regards,
Awais
Attachments:
play4.vi ‏122 KB

Move result 1 and result 2 out of the case structures and subract them.
Right now result 1 or result 2 only get written to if its respective comparison is true. What do you want to do with the math if either comparison is false? You haven't defined your problem clearly enough.

IDS and two switches

I have an IDS "listening in" on two switches. Problems begin when a host connected to switch1 talks to another host connected to switch2. Apparently I can see the packets twice (the only difference is TTL decreased by one). To make it more interesting SigID:1300-0 Sig:TCP Segment Overwrite starts firing.
Any suggestions greatly appreciated.
-A

This signature 1300 will only fire when the data in the stream is attempting to be overwritten with different data than what was previously seen at that sequence offset. The issue is due to Networking stacks based on BSD4.2 implementations might use a older method of sending TCP keepalives. The IDS flags this as a TCP overwrite and fires signature 1300. The resolution is to Upgrade to sensor v5.0 where this trigger will not cause an alarm to fire.

Enable port security between Two switches

Hi Everyone,
I connected two switches together via below config
Switch A
int gi0/1
switch mode access
switchport access vlan 10
Switch B
int gi0/1
switch mode access
switchport access vlan 10
They work fine with above config.
I did the Test below
However when i changed Config of Switch B as below
int gi0/1
switch mode access
switchport access vlan 10
switchport port-security
Switch B is unable to ping its default gateway.
Also Switch B is not reachable via SSH.
Port is up up and in STP forwarding state.
Switch B can see Switch A as a neighbour.
Also Switch B is not reachable via SSH.
I know that switchport port-security we use only when connecting to PC.
S does this mean that on above scenario layer 1 and layer 2 are up but layers beyond 3 and above are not reachable like ping,ssh etc??
Regards
MAhesh

I was just trying to see how the switches behave with this config.Nothing much just exploring the options in the network world
Ideally if you want to connect two switches together in Layer 2, Dot1Q trunking is the way to go. You do not want to put port security because it is useless.

LSB in two switch 6500 series

i need to configure one lsb virtual address in two switchs 6500, it is for a server farm backup and they might respond to the same IP address.

check out the following link for configuring virtual address on catalyst 6500 series :
http://www.cisco.com/en/US/products/hw/switches/ps708/products_installation_and_configuration_guide_chapter09186a00801c589b.html

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

Give me two switchs...

Similar Messages

Maybe you are looking for