My company (small company) just bought two Cisco 2950 switches to add to our
network, we currently have two other HP 2424M ProCurve switches. What do I
need to do to add the other two Cisco switches to the network? Can I just
add a Xover cable to uplink the swithces to provide basic switching?
Eventually I would like to setup VLAN's with all four of the switches but we
don't have a layer 3 device to route for the VLANS (from what I have read
this is necessary). Can someone please give me some advice? My active job
is a developer but I get to play network administrator on the side! Thanks

Report this post to a moderator

You should be able to just plug and play for switching purposes. Also, you
shouldn't need a xover cable. The 2950's have the autosensing. To be sure
just check the port numbers on the front - if they have an x after the
number, then it will autodetect.

How you do the VLAN's depends on your situation. You don't actually have to
"route" between VLAN's. It all depends how your setup is and what you are
using the VLAN's for. If you just want to keep the VLAN's separate, but
pass between the switches, then you can use trunking. Or, maybe there are
only a couple devices that need to talk with each VLAN, then add them to
each. This would require them all being in the same subnet, but you would
not need a L3 device. I'd suggest that you get you a good book on VLAN's,
preferably one that has Cisco information so it can help you with configs.



"Eric" <none@none.com> wrote in message
news:hVNdb.3960$bw5.2868297841@newssvr12.news.prodigy.com...
> My company (small company) just bought two Cisco 2950 switches to add to
our
> network, we currently have two other HP 2424M ProCurve switches. What do
I
> need to do to add the other two Cisco switches to the network? Can I just
> add a Xover cable to uplink the swithces to provide basic switching?
> Eventually I would like to setup VLAN's with all four of the switches but
we
> don't have a layer 3 device to route for the VLANS (from what I have read
> this is necessary). Can someone please give me some advice? My active
job
> is a developer but I get to play network administrator on the side! Thanks
>
>

Report this post to a moderator

"Scooby" <mmscooby1@removeme.earthlink.net> wrote in message news:<9BXdb.41002$ai7.18527@newsread1.news.atl.earthlink.net>...
> You should be able to just plug and play for switching purposes. Also, you
> shouldn't need a xover cable. The 2950's have the autosensing. To be sure
> just check the port numbers on the front - if they have an x after the
> number, then it will autodetect.
>
> How you do the VLAN's depends on your situation. You don't actually have to
> "route" between VLAN's. It all depends how your setup is and what you are
> using the VLAN's for. If you just want to keep the VLAN's separate, but
> pass between the switches, then you can use trunking. Or, maybe there are
> only a couple devices that need to talk with each VLAN, then add them to
> each. This would require them all being in the same subnet, but you would
> not need a L3 device. I'd suggest that you get you a good book on VLAN's,
> preferably one that has Cisco information so it can help you with configs.
>
>
>
> "Eric" <none@none.com> wrote in message
> news:hVNdb.3960$bw5.2868297841@newssvr12.news.prodigy.com...
> > My company (small company) just bought two Cisco 2950 switches to add to
> our
> > network, we currently have two other HP 2424M ProCurve switches. What do
> I
> > need to do to add the other two Cisco switches to the network? Can I just
> > add a Xover cable to uplink the swithces to provide basic switching?
> > Eventually I would like to setup VLAN's with all four of the switches but
> we
> > don't have a layer 3 device to route for the VLANS (from what I have read
> > this is necessary). Can someone please give me some advice? My active
> job
> > is a developer but I get to play network administrator on the side! Thanks
> >
> >

What are you talking about? An X does not mean that it is autosensing
to whether a crossover or not. The 2950 autodetects speed and duplex,
not crossover or straight through.

Have you actually connected 2 2950s together before? Did it work?

Report this post to a moderator

"Trent Collicutt" <tcollicutt@hotmail.com> wrote in message
news:4610dc52.0310010305.6b46d691@posting.google.com...
> "Scooby" <mmscooby1@removeme.earthlink.net> wrote in message
news:<9BXdb.41002$ai7.18527@newsread1.news.atl.earthlink.net>...
> > You should be able to just plug and play for switching purposes. Also,
you
> > shouldn't need a xover cable. The 2950's have the autosensing. To be
sure
> > just check the port numbers on the front - if they have an x after the
> > number, then it will autodetect.
> >
> > How you do the VLAN's depends on your situation. You don't actually
have to
> > "route" between VLAN's. It all depends how your setup is and what you
are
> > using the VLAN's for. If you just want to keep the VLAN's separate, but
> > pass between the switches, then you can use trunking. Or, maybe there
are
> > only a couple devices that need to talk with each VLAN, then add them to
> > each. This would require them all being in the same subnet, but you
would

> > not need a L3 device. I'd suggest that you get you a good book on
VLAN's,
> > preferably one that has Cisco information so it can help you with
configs.
> >
> >
> >
> > "Eric" <none@none.com> wrote in message
> > news:hVNdb.3960$bw5.2868297841@newssvr12.news.prodigy.com...
> > > My company (small company) just bought two Cisco 2950 switches to add
to
> > our
> > > network, we currently have two other HP 2424M ProCurve switches. What
do
> > I
> > > need to do to add the other two Cisco switches to the network? Can I
just[
color=darkred]
> > > add a Xover cable to uplink the swithces to provide basic switching?
> > > Eventually I would like to setup VLAN's with all four of the switches[/color]
but
> > we
> > > don't have a layer 3 device to route for the VLANS (from what I have
read[
color=darkred]
> > > this is necessary). Can someone please give me some advice? My[/color]
active
> > job
> > > is a developer but I get to play network administrator on the side!
Thanks
> > >
> > >
>
> What are you talking about? An X does not mean that it is autosensing
> to whether a crossover or not. The 2950 autodetects speed and duplex,
> not crossover or straight through.
>
> Have you actually connected 2 2950s together before? Did it work?

Ooops, okay, my bad. I did not have 2950's to test this with. Some new
ones just showed up at my door, so I was able to perform a scientific test
(and it failed). But here is why I stated that.... I do remember hearing or
reading something to that effect - it does make total sense, because the
techonology is out there (called autouplink), and x traditionally stands for
an uplink port. Anyway, this leaves the question just what does the x stand
for? I've tried looking on Cisco's site and can not find anything about it.
There does appear to be some 2950's with the x and some without. Just why
would they do that? Hmmmm, I'm curious. If anyone has the answer, I'd like
to know.

About 15 minutes after I had set these up and tested, someone came in and
said "Hey, they look pretty cool, what's the x for?". ROFL.

Report this post to a moderator

Yeah basically, you need to use a Xover cable to connection a 2950 to a hub
or switch.
there are 2 models,

what X are we talking about here ? theres a 2950 switch and a 2950T switch.
2950T switch comes with 2x 10/100/1000 TX ports.



"Scooby" <mmscooby1@removeme.earthlink.net> wrote in message
news:2ZIeb.11728$NX3.8895@newsread3.news.pas.earthlink.net...
> "Trent Collicutt" <tcollicutt@hotmail.com> wrote in message
> news:4610dc52.0310010305.6b46d691@posting.google.com...
> > "Scooby" <mmscooby1@removeme.earthlink.net> wrote in message
> news:<9BXdb.41002$ai7.18527@newsread1.news.atl.earthlink.net>...
> > > You should be able to just plug and play for switching purposes.
Also,
> you
> > > shouldn't need a xover cable. The 2950's have the autosensing. To be
> sure
> > > just check the port numbers on the front - if they have an x after the
> > > number, then it will autodetect.
> > >
> > > How you do the VLAN's depends on your situation. You don't actually
> have to

> > > "route" between VLAN's. It all depends how your setup is and what you
> are
> > > using the VLAN's for. If you just want to keep the VLAN's separate,
but[c
olor=darkred]
> > > pass between the switches, then you can use trunking. Or, maybe there
> are
> > > only a couple devices that need to talk with each VLAN, then add them[/color]
to[co
lor=darkred]
> > > each. This would require them all being in the same subnet, but you
> would
> > > not need a L3 device. I'd suggest that you get you a good book on
> VLAN's,
> > > preferably one that has Cisco information so it can help you with
> configs.
> > >
> > >
> > >
> > > "Eric" <none@none.com> wrote in message
> > > news:hVNdb.3960$bw5.2868297841@newssvr12.news.prodigy.com...
> > > > My company (small company) just bought two Cisco 2950 switches to[/color]
add
> to

> > > our
> > > > network, we currently have two other HP 2424M ProCurve switches.
What
> do

> > > I
> > > > need to do to add the other two Cisco switches to the network? Can
I
> just
> > > > add a Xover cable to uplink the swithces to provide basic switching?
> > > > Eventually I would like to setup VLAN's with all four of the
switches
> but
> > > we
> > > > don't have a layer 3 device to route for the VLANS (from what I have
> read
> > > > this is necessary). Can someone please give me some advice? My
> active
> > > job
> > > > is a developer but I get to play network administrator on the side!
> Thanks
> > > >
> > > >
> >
> > What are you talking about? An X does not mean that it is autosensing
> > to whether a crossover or not. The 2950 autodetects speed and duplex,
> > not crossover or straight through.
> >
> > Have you actually connected 2 2950s together before? Did it work?
>
> Ooops, okay, my bad. I did not have 2950's to test this with. Some new
> ones just showed up at my door, so I was able to perform a scientific test
> (and it failed). But here is why I stated that.... I do remember hearing
or
> reading something to that effect - it does make total sense, because the
> techonology is out there (called autouplink), and x traditionally stands
for
> an uplink port. Anyway, this leaves the question just what does the x
stand
> for? I've tried looking on Cisco's site and can not find anything about
it.
> There does appear to be some 2950's with the x and some without. Just why
> would they do that? Hmmmm, I'm curious. If anyone has the answer, I'd
like
> to know.
>
> About 15 minutes after I had set these up and tested, someone came in and
> said "Hey, they look pretty cool, what's the x for?". ROFL.
>
>
>
>
>

Report this post to a moderator

The x is listed with the port number on some of the 2950's (front panel
display leds), and it is not on others. For example, some of them have 1x,
2x, 3x....24x, while others just have 1, 2, 3...24. Why would they have
started putting an x after the port number? My understand was the these
supported the autouplink, apparently not. But, the question is what does it
really mean?



"Val" <gryphonix@hotmail.com-nospam> wrote in message
news:1065050619.38622@radsrv1.tranzpeer.net...
> Yeah basically, you need to use a Xover cable to connection a 2950 to a
hub
> or switch.
> there are 2 models,
>
> what X are we talking about here ? theres a 2950 switch and a 2950T
switch.
> 2950T switch comes with 2x 10/100/1000 TX ports.
>
>
>
> "Scooby" <mmscooby1@removeme.earthlink.net> wrote in message
> news:2ZIeb.11728$NX3.8895@newsread3.news.pas.earthlink.net...
> > "Trent Collicutt" <tcollicutt@hotmail.com> wrote in message
> > news:4610dc52.0310010305.6b46d691@posting.google.com...
> > > "Scooby" <mmscooby1@removeme.earthlink.net> wrote in message
> > news:<9BXdb.41002$ai7.18527@newsread1.news.atl.earthlink.net>...
> > > > You should be able to just plug and play for switching purposes.
> Also,
> > you
> > > > shouldn't need a xover cable. The 2950's have the autosensing. To
be
> > sure
> > > > just check the port numbers on the front - if they have an x after
the[c
olor=darkred]
> > > > number, then it will autodetect.
> > > >
> > > > How you do the VLAN's depends on your situation. You don't actually
> > have to
> > > > "route" between VLAN's. It all depends how your setup is and what[/color]
you
> > are
> > > > using the VLAN's for. If you just want to keep the VLAN's separate,
> but
> > > > pass between the switches, then you can use trunking. Or, maybe
there

> > are
> > > > only a couple devices that need to talk with each VLAN, then add
them
> to

> > > > each. This would require them all being in the same subnet, but you
> > would
> > > > not need a L3 device. I'd suggest that you get you a good book on
> > VLAN's,
> > > > preferably one that has Cisco information so it can help you with
> > configs.
> > > >
> > > >
> > > >
> > > > "Eric" <none@none.com> wrote in message
> > > > news:hVNdb.3960$bw5.2868297841@newssvr12.news.prodigy.com...
> > > > > My company (small company) just bought two Cisco 2950 switches to
> add
> > to
> > > > our
> > > > > network, we currently have two other HP 2424M ProCurve switches.
> What
> > do
> > > > I
> > > > > need to do to add the other two Cisco switches to the network?
Can
> I
> > just
> > > > > add a Xover cable to uplink the swithces to provide basic
switching? [colo
r=darkred]
> > > > > Eventually I would like to setup VLAN's with all four of the
> switches
> > but
> > > > we
> > > > > don't have a layer 3 device to route for the VLANS (from what I[/color]
have
> > read
> > > > > this is necessary). Can someone please give me some advice? My
> > active
> > > > job
> > > > > is a developer but I get to play network administrator on the
side!

> > Thanks
> > > > >
> > > > >
> > >
> > > What are you talking about? An X does not mean that it is autosensing
> > > to whether a crossover or not. The 2950 autodetects speed and duplex,
> > > not crossover or straight through.
> > >
> > > Have you actually connected 2 2950s together before? Did it work?
> >
> > Ooops, okay, my bad. I did not have 2950's to test this with. Some new
> > ones just showed up at my door, so I was able to perform a scientific
test
> > (and it failed). But here is why I stated that.... I do remember
hearing
> or
> > reading something to that effect - it does make total sense, because the
> > techonology is out there (called autouplink), and x traditionally stands
> for
> > an uplink port. Anyway, this leaves the question just what does the x
> stand
> > for? I've tried looking on Cisco's site and can not find anything about
> it.
> > There does appear to be some 2950's with the x and some without. Just
why
> > would they do that? Hmmmm, I'm curious. If anyone has the answer, I'd
> like
> > to know.
> >
> > About 15 minutes after I had set these up and tested, someone came in
and
> > said "Hey, they look pretty cool, what's the x for?". ROFL.
> >
> >
> >
> >
> >
>
>

Report this post to a moderator