Recent content by awj

Simple, Use LACP to create aggregated links. Decide which ports you are going to use on the 42xx and 49xx for your aggregate links. Enable LACP on these ports and then connect the cables. That's all there is to it, if you have two 100Mb links between the 42xx and the 49xx it will create a...

First thing to recognise is the 8 port unmanaged switch if this is the officeconnect switch then the memory in this switch is low, if you have power users attached or servers then this is the wrong device, it cannot cope with sustained high levels of traffic. A cheap analyer is Ethereal, in...

You can link using port on different units in the stack. Latest code for the 4228 is 2.03. If the other end of the aggregated link can also used LACP then this is the best way to set up an AL. Enable LACP on the ports that you want to use, then connect the cables. Do not connect the cables first...

The other thing to try out is the port capabilities. The 4924 can autonegotiate at 10/100/1000. Go in the ethernet options and disable autonegotiation and set the port capablities to only advertise at 1000Full duplex.

Also disable spanning tree if possible, if not then change each port to FastStart

Depends on which product. The 3300 stacking works as though the stack is one single unit, in regards to management so 1 IP address. CPU and memory are not shared. If one unit goes down then the other units still work, but really it depends which unit goes down. For example if the unit with the...

Also available is the SUU (Serial upgrade utility) this is also the method for software recovery. It's a little bit slower than TFTP, but it much better for doing individual units.

This should work ok, disable LACP on the 4924 ports that you are using and set up a standard link aggregation. On the 9300 create your trunk but DO NOT use TCMP as the trunking protocol.

Check the duplex and baud rate settings on your end devices, if you have anything set to half duplex set them to full duplex if possible. Using half duplex can cause memory/buffer issues as the switch has to store the frame in the buffer.

Yes use the up down cables to stack ( a maximum of 4 units) the switch uses a protocol to create the stack. This would leave you with 2 spares ports (unit 1 and unit 4) as both 2+3 would have both up/down in use. These spare ports can be used for normal 1000Base-t connections.

Make sure that you actually have routing enabled, the router is a bridge by default. setd -ip rout = e Also check that you have a routing protocol (rip or ospf) enabled as well if the networks are different. You could also trying using a static route. Make sure that you have any SAP/RIP...

Ok, the main things to note are. 1. The matrix module and cables create a single stack, i.e you can manage the stack with one IP address. 2. The matrix runs stack wide at around 850Mb across the stack, to get the same bandwidth using trunks, you would have to use around 4 x 100Mbps ports, so...

Are you using a matrix module and cascade cables ?. If so make sure that these are connected firmly. Also try and work out where the traffic is going, spread connections across the stack rather than have heavy users on one unit. You should also upgrade to 2.70 code it has some fixes in it that...

Create a seperate vlan for your voice traffic and let an intelligent L3 device sort out the QoS. An alternative to the cisco products mentioned, would be the 3com 4400 series or 42xx/38xx series they also have QoS built into the hardware and are probably a lot cheaper.

It's not possible to use roving analysis to monitor all ports on the switch, think about it, if you try and monitor using a 100Mb port, but try and mirror 10 other 100Mb ports you have a 10:1 contention no switch can do this. Also this has an overhead on the CPU, the main function of a switch is...