At Fixya.com, our trusted experts are meticulously vetted and possess extensive experience in their respective fields. Backed by a community of knowledgeable professionals, our platform ensures that the solutions provided are thoroughly researched and validated.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Hi,
Any Network where different types of systems from different companies and having different technology are connected and must communicate with each other successfully is known as a Multi Vendor Network Environment. The important thing here is that the Protocol layers such as TCP/IP and SS7 allow for such a communication and are thus important for this reason.
Simplest example is the internet. Thousands of Windows and Linuxs and Macintoshes and UNIXs connected together to create the internet and ll communicating efficiently all thanks to the TCP/IP set of protocols...
Hope you find it useful.
Your feedback is appreciated.
Askari :)
Obstacles and Incompatibilites of Multivendor Networking environment.
01. No clear knowledge about the Network project.
02. Lack of Technical Knowledge by the Network Multivendors.
03. Improper knowkedge by the MIS Dept. Person who is not familiar with Patch Cables, Routers, Modems, Hubs, Switches, Ports, OFC Cables, Transceivers etc.
04. Better pricing of the product not analysed.
05. Meeting Delivery Completion with Quality work not planned.
06. Penalty Clause not laid for Networking Project delay, incase of delay, penalty will be imposed to complete project ON TIME.
07. Flexibility and Leniency shown to the Vendor by the MIS Dept.
08. No Proper Layout / design about the Departments where networking connections to be given not shown to the vendors.
09. Mere assumption about the Project that it will complete within the time frame. No Proper co-ordination with the Network vendors.
10. Any cost saving methods for the company not tried by the MIS Dept. by negotiating the price, labour and materisla etc.
for all practical purposes, there are not any problems except for administrative purposes ie: learning login and password procedures for different routers, switches and telephony equipment. It is in my opinion better to stay with the same brands. Cisco is what I have alway used and i prefer it. Their support is unmatched as well.
No real problems with a multivendor network. You will have to use open standards. These are usually just as good as the proprietary protocols, and in some cases better.
In general, it creates a tech support nightmare. Mostly you will run into hardware incompatibilities, differing protocols...and worst of all, you will have to hire people who are familiar with each type of hardware -- some are familiar with Cisco, for example, but not other types of hardware, etc. Or at least someone who can support most of it and obtain further support from the vendor. You will also have to deal with several different types of SLA's and make sure each vendor will provide the necessary support in that environment -- if you have a switch from 3COM that is not working with a Cisco router, for example, you have to do the extra work of figuring out which tech support to call, 3COM or Cisco?
Multivendor networking is typically an unavoidable headache unless you have a very small network, but one can limit the number of vendors to those that already provide good service, unless you are overhauling the network (yikes) and searching for new vendors. My advice is to ask for an awesome salary and buy a few big bottles of Excedrin :-)
multivendor networking" problem,
i have problem of multivendor networking .
please reslove me
×