Difference between EMS and NMS

Posted by Admin in Difference Between, Telecom In telecom industry, these two terms EMS aka Element Management System and NMS aka Network Management System are used interchangeably most often. But, these two terminologies do differ in their true meaning and should be used wisely. Below are the definitions of EMS and NMS which clearly states the differences between these two.

Element Management System (EMS)
• •

An element management system (EMS) manages one or more of a specific type of network elements (NEs). Using an EMS a user can manage all the features of each NE individually, but not the communication between NEs. Communication between NEs is managed by the network management system (NMS). One or more management interfaces are exposed by NEs that the EMS uses to communicate with and to manage them. These management interfaces use a variety of protocols such as SNMP, TL1, CLI, XML, and CORBA.

Network Management System (NMS)
• •

A network management system is a combination of hardware and software used to monitor and administer a network. Network management refers to the maintenance and administration of large scale computer networks at the top level. Network management is the execution of the set of functions required for controlling, planning, allocating, deploying, coordinating and monitoring the resources of a network including performing functions such as fault management, configuration management, accounting management, performance management, security management and bandwidth management. A large number of protocols exist to support network and network device management. Common protocols are SNMP, TL1 and JMX etc.

The network elements in the network each communicate with their respective EMS. The NEspecific EMSs communicate to a higher level NMS that provide integrated multivendor network management. This is depicted in the diagram below:

queries or suggestions…!! 2 inShare Related Posts: • • • • • • • What Is Above Network Management – Service Management & Business Management – TMN Logical Model Explained Difference between NorthBound Interface and SouthBound Interface FCAPS in Network Management Difference between Trap and Alarm What Is Monitored Under Fault Management in Network Management Difference between ColdStart and WarmStart trap in Network Management Difference between trap and informs in SNMP 15 Comments on “Difference between EMS and NMS” . It is the sole mediator of this information and the control of the NEs to the Network Management Layer Hope you find this information useful. Please leave your footprints in comments section below for any feedback.Only the EMS is exposed to complete management information content of all the NEs in its domain.

Difference between NorthBound and SouthBound Interfaces | Vertical Horizons August 2nd. in this case. Guru 2. Hope this clarifies your doubt. Practically. similarly Vendor B and otherVendor EMS’s manage NE from their Manaufactuers. The post is realy good and useful. Admin May 26th. usually SouthBound Interface refers to the interface exposed to lower layers and the NorthBound [. Vendor A EMS will manage NE’s from Vendor A. similarly this applies for other EMS’s. So all these vendor specific EMS’s will forward the information which they collected from their NE’s to the NMS in a Common Format which the NMs can understand and the NMS will communicate with the Vendor EMS’s in a genric way.. NMS should expose both these interfaces to southbound i. Thank you for the positive feedback Now coming to your query. many a times the reason being that we deal with legacy systems. Please let us know for further queries 3..e.1.. To achieve a common format. similarly Vendor B and otherVendor EMS’s manage NE from their Manaufactuers. we can introduce a mediation layer between NMS and EMSs that can take care of these protocols from southbound and provide data in same format to north bound. can you explain this. I need a small clarification. The Information given by a NE from Vendor A could be understood only by the Vendor A EMS.. Anonymous May 26th. similarly this applies for other EMS’s. The Information given by a NE from Vendor A could be understood only by the Vendor A EMS. it is difficult (of course possible) to achieve the same. which the Vendor EMS’s translate to the format which the vendor specific NE’s can understand? Thanks. 2011 at 11:45 AM [. EMSs. 2011 at 11:40 PM Hi Guru. you are absolutely correct till here “Vendor A EMS will manage NE’s from Vendor A. For instance EMS A exposes Corba interface and EMS B exposes SNMP interface.] .] network management. 2011 at 10:32 AM Hi. So all these vendor specific EMS’s will forward the information which they collected from their NE’s to the NMS” Having a common format between different vendor EMS’s and NMS is the best case scenario.

...4. 2011 at 12:56 AM [..] are messages send by a managed element to the network manager to indicate an abnormal condition such as a fault or an exception. What Is Above Network Management – Service Management & Business Management Difference – TMN Logical Model Explained | Vertical Horizons April 25th.] 6... we explained the network hierarchy starting from bottom as Network Element -> Element [.] used to monitor and administer a network.] Difference – TMN Logical Model Explained Posted by Admin in TelecomIn one of our previous post...] Simple Network Management Protocol i.] 7. SNMP PDU Types | Vertical Horizons September 15th. Keep visiting us. 2011 at 10:56 AM [. 2012 at 3:29 PM helpful thanks … 10. 2012 at 11:23 AM [.. 11.e.Thank you 8.] 5. Suresh Tummala February 21st. Any other autonomous messaged [. 2012 at 3:37 PM Thanks Canute for dropping by. we are glad that it helped. 2012 at 10:53 PM Thank you Suresh for feedback.. Admin February 21st. SNMP is a simple request/response protocol in which SNMP manager communicates with SNMP agents/managed devices using SNMP PDU’s (Packet Data Unit)... There are 7 [. We really appreciate it.. Difference between Trap and Alarm | Vertical Horizons August 12th.. 9.] .. 2012 at 10:27 PM Its really helpful for me. overview of "NMS" February 4th. You may want to look at link below for further details: Difference between EMS and NMS | Vertical Horizons Reply With Quote + Post New Thread « Data Rate and [.. canute March 20th. 2012 at 3:24 PM [. Admin March 20th.

12..” I did interpret that you are saying the communication between NEs of the *same* vendor also cannot be managed by EMS. 2012 at 12:57 PM What is the Differece between VCAT and LCAS? Why it is required? 14. 2012 at 7:09 AM This complete post is awesome . can you please explain why it is not possible for the EMS to manage the NEs communication when all belong to same vendor? Many Thanks! MPk30 15. If my understanding is correct... we explained the network hierarchy starting from bottom as Network Element -> Element [.] Management – TMN Logical Model Explained Posted by Admin in TelecomIn one of our previous post. What Is Above Network Management – Service Management & Business Management – TMN Logical Model Explained | Vertical Horizons April 25th. Communication between NEs is managed by the network management system (NMS).. but not the communication between NEs.] 13. but NMS only can do that. I need a small clarification on the point: “Using an EMS a user can manage all the features of each NE individually. jyoti August 4th. 2012 at 11:27 AM [. Prasad Kumar June 11th. thanks for your fantastic explanation. 2012 at 11:43 AM Hi. First off. MPk30 July 25th.

Sign up to vote on this title
UsefulNot useful