Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Adding a Cisco 3560 series POE-48 switch

Status
Not open for further replies.

Sneakerpimp911

Technical User
Aug 19, 2009
1
DE
Good Day All

I'm adding a new Cisco 3560 series POE-48 Switch to our LAN at work.The switch will be connected via fibre straight to our CORE switch(4510r). Before plugging the switch in is there things I should look out for? & in the core switch how will I know where to plug the black fibre point & the red fibre Point into the Gbic?

thanks
 
Dunno about the fibre but things I would check that spring to mind are:

* Obviously wipe startup-config and vlan.dat and reboot
* STP - Will this switch become your route bridge?
* VTP - Set to transparant mode to set the revision to 0 so you don't accidentally wipe your vlans
* I would also change all layer 2 ports to access mode


It should be clean if new but you never know :).
 
As far as the fiber goes you will either get a link light or you won't ,if not reverse the fiber. Is it being trunked etc.. Verify your trunk settings match for both sides , speed/duplex on the links match on both sides etc. Addressing and masking is correct in new switch.
 
Brand new they come as VTP Server...

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!
 
Yes, Cisco have basically ruined VTP by doing that. I noticed on a bunch of 4500s I got earlier this year that they came with VTP set to transparent by default - too late, nobody seems to trust or use VTP any more.
 
In big installs where you have vlans on numerous different switches vtp saves time. Problems are created when you have people doing network work who don't understand how it works . We have had a huge vtp installation running for years without any issues at all because the people that work on the gear understand it. There is nothing wrong with vtp if you know the ins and outs of it .
 
Problems are created when you have people doing network work who don't understand how it works ."
Exactly.
And you don't manage that kind of risk by shipping switches set to "VTP Server" by default! What *were* they thinking?!?!?!
Because an IT manager's response to just one VTP-related cock-up is going to be very simple: "turn it all off and never use it again".

Personally I always configure VTP on any new installs I do, but I have to admit that VTP isn't very useful - in a decently-designed network you shouldn't have the same VLAN spanning loads of different switches - on the contrary: the ideal design is one VLAN/one switch and pruning on all the trunks.
 

I do use VTP at work and I like it. However, I also from time to time need to add different switches to the network and I found certain model becomes server right out from the box. Even when I set it up at client, when I connect to the domain, it becomes server again. Unless it is a model that I worked with in the past and know how it works - I sweat every time I introduce a new switch to my network.

Yes, where were they think by shipping switches set to VTP server by default!!! I think the 3560 do that..
 
That's where you have specific templates you use for a given model and part of that template is to set the vtp mode as transparent and then you don't have to worry about it . First step write erase and then reload then use your template with the vtp mode as transparent , you will never get into a issue. Oh yes also keep people away from network gear who don't know what they are doing !!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top