Cmip Vs. Snmp : Network Management :: essays research papers fc

CMIP vs. SNMP Network ManagementImagine yourself as a network administrator, responsible for a 2000 usernetwork. This network reaches from atomic number 20 to New York, and some branchesover seas. In this situation, anything can, and usually does go wrong, nevertheless itwould be your job as a system administrator to reconcile the problem with itarises as quickly as possible. The last thing you would extremity is for your bossto call you up, asking why you havent d star anything to fix the 2 major systemsthat have been down for several hours. How do you explain to him that youdidnt raze k straight port about it? Would you even want to tell him that? So now, television yourself in the same situation, merely this time, you were using a network observe program. Sitting in front of a large screen displaying a map of theworld, leaning back gently in your chair. A benignant warning tone sounds, andlooking at your display, you see that California is now glowing a soft red incolor, in come out of the green glow just moments before. You select the state ofCalifornia, and it zooms in for a closer look. You see a network diagramoverview of all the computers your community has within California. Two systems be flashing, with an X on top of them indicating that they argon experiencingproblems. Tagging the two systems, you press enter, and with a flash, the screendisplays all the statitics of the two systems, including anything they powerhave in common causing the problem. Seeing that both systems are linked to thesame card of a network switch, you pick up the phone and give that branch officea call, notifying them not only that they have a problem, merely how to fix it aswell.Early in the days of computers, a central computer (called a mainframe) wasconnected to a bunch of dumb terminals using a standard copper wire. non muchthought was put into how this was done because there was only one way to do itthey were either connected, or they werent. Figure 1 shows a diagram of theseearly systems. If something went wrong with this type of system, it was fairlyeasy to troubleshoot, the charge up almost always fell on the mainframe system.Shortly after(prenominal) the introduction of Personal Computers (PC), came Local AreaNetworks (LANS), forever changing the way in which we look at networked systems.LANS originally consisted of just PCs connected into groups of computers, butsoon after, there came a need to connect those individual LANS together forming