I would like to add a disclaimer to our contracts that says something about the clients responsibility in regards to their network cabling infrastructure. I have run into several problems with sub standard cabling and would like to get a statement out front instead of waiting for it to be a problem. What I am talking about is bare wire and two network cables being made out of one run, cables ran against lights and electric outlets things of that nature. It works fine for them on their data networks but I can have problems with voice which leads to poor voice quality. I am wondering if Cisco has a statement on the quality of CAT 5 cabling and that it must be certified to run at CAT 5 standards. Or if Cisco does not have any what is everyone else doing with this problem?
This messege is posted by Kevin Tucker Network Analyst not gpartch. email@example.com
The solution is rather elementary follow proper layer 1 procedures and you will not have a problem. You seem to know what the problem is, if I were you I would fix them. Also your data flow is most definitely being effected if your cat 5 cabling is in the disarray that you describe. A disclaimer I believe is not required from Cisco. I take full resonsibility for my cabling infrastructure and elminate any Layer 1 variables before A call is made to TAC. I would give my client an estamate on the cost of repairing their layer 1 issues and educate them while the repairs are taking place.
Well unfortunatly we do not do any layer 1 work. We sever customer all around the country and do not have the staff to do cabling. We leave that up to local contractors. Also the networks are usually in place and running before we do an IPT install and the normal response is that it is working for their data network so it can not be the cabling's fault. I guess I am asking if there are any documents that explain how layer 1 problems can be more of a noticable problem when you start running voice over an already unstable foundation.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.