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

CMIP vs. SNMP Ne twork Management see yourself as a communicate executive, responsible for a 2000 uservane. This network reaches from atomic number 20 to New York, and some branchesover seas. In this situation, any matter can, and usu whollyy does go wrong, but itwould be your job as a system administrator to resolve the problem with itarises as quickly as possible. The last thing you would want is for your bossto call you up, asking why you havent done anything to designate the 2 major systemsthat have been down for several hours. How do you relieve to him that youdidnt even know about it? Would you even want to tell him that? So now,picture yourself in the same situation, only if this time, you were using a networkmonitoring program. Sitting in front of a large screen door displaying a map of theworld, leaning back gently in your chair. A gentle warning tone sounds, andlooking at your display, you see that California is now glowing a soft red incolor, in place 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 company has within California. Two systemsare flashing, with an X on choke of them indicating that they are experiencingproblems. Tagging the two systems, you press enter, and with a flash, the screendisplays all the statitics of the two systems, including anything they mighthave in common causing the problem. Seeing that some(prenominal) systems are linked to thesame card of a network switch, you take apart up the phone and give that branch officea call, nonifying them not only that they have a problem, but how to fix it aswell. other(a) in the days of computers, a central computer (called a mainframe) was connected to a bunch of dumb terminals using a standard fuzz wire. Not 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 diagra m of theseearly systems. If something went wrong with this type of system, it was fairly gentle to troubleshoot, the blame almost always fell on the mainframe system. short after the introduction of Personal Computers (PC), came Local AreaNetworks (LANS), forever ever-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 individualist LANS together forming