Networking Newbie: Patching

[Stevehewitt]

Hi guys,

Not sure if this is the right forum, if not hopefully someone can point me in the right direction.

I've recently changed carrer direction from a systems guys who does some basic network (basic TCP/IP stuff and networking with unmanaged hubs / switches etc.) to working in a call centre enviroment.

It's still being setup at the moment, but the cabling is already mostly done. The problem is that I haven't got the first clue regarding patching, and only just managed to identfiy that the panel in the comms rack is a patch panel.

Can anyone give me some advise on patching, how it compares with cabling using unmanaged switches only and basically how to set it up!?!?!
If someone knows of any good references for it.

Steve.

 

[macphoneguy]

a couple of basic thoughts, One is Numbering on the patch panels, should match what is out at the users jack, where the phone and PC plug into, 2nd Color of the patch Cords, Make Phone cord one color, and Data another Color, so you can look at it and say thats running a phone, 3rd Get Various Lenghts of Cords, some 3 ft, some 5ft, Etc, the number will depend on how many racks/patch panels you have


Have a few of Spare jacks that match the existing as the user's will sometimes Kick/pull or otherwise damage the connector creating a interment problem,

 

[Stevehewitt]

Hey,

Thanks for that. The system is VoIP so I haven't got to worry about cable coloring etc.

The main problem I have is that on a switch on setup I have all of the workstation plugged in and then any services I want them to use (e.g. servers, internet, wireless access points) are plugged into the switch are well. Then obviously the switch does it's magic and the services are avaliable.

How does this work using a patch panel? Do I have to plug each patch into the swtich which as the services I want also plugged into it?

Thanks,

Steve.

 

[bkrike]

a patch panel is just a jack. it is the other end of the Jack that the computer plugs in to. Look at which jacks have something plugged in, find the corresponding number on the patch panel, patch to the switch.

 

[Stevehewitt]

Great. OK.

So it really does all have to go into a switch!

Thanks for your help guys. Stupid basic questions like these that are so simple you have to double check with later on!

Thanks,

Steve.

 

[macphoneguy]

to somewhat address "managed Switches" vers Unmanaged the answer is it depends, on how many devices you need to support, and of course the Cost, Managed switch's will usually have Web or other interfaces, where you can have more direct control but of course are more expensive, Unmanaged are Just that, they will give you a "Link" & collision led perhaps but not much else, Nor will the unmanaged devices tell you if a given PC/device is generating a "network storm"
For Intranet or the "WorldwideWait" as it's sometimes called I definately recommend putting a Firewall of somekind between the

http://WWW and

You, as you don't want someone coming in stealing any info,
as bkrike mentioned Patch panels are just "jacks" they usually come in 12,24,48 & 96 port again depending on how many devices you have,

 

[ISDNman]

But it goes further too. For VOIP to be done properly you need on eof the latest switches that allow prioritization.

I believe pretty much all switches at this level are managed.

 

[Stevehewitt]

Sorry, what is a 'eof'?
I will be putting in a firewall of some sort between the

http://WWW and

our network.
I'm familar with networking in a smaller way, (unmanaged switches and wireless) but never VoIP or patches!

Thanks for your help guys.

Steve.

 

[jkupski]

Sorry, what is a 'eof'?

EOF means end of file, but what he was saying wasn't "on eof" it was "one of."

 

[MaintOrphan]

Even in a VoIP environment, I'd look at color-coding the patch cables...Most of the VoIP installs I've seen use either a seperate switch for the voice, or have seperate ports on a switch set up on their own VLAN.

I'll not EVEN say anything that gets the "VoIP Vs. copper" thread going!