Juniper’s Professional Services team is often asked for recommendations on the integration of products into service provider environments. This integration is often “north-bound”, linking to Operational Support Systems (OSS) and Business Support Systems (BSS), and it’s not unusual for the interfaces to those systems to introduce hidden complexity and cost.
The answer? Well, I’ve been working recently on deployments of Juniper’s Junos Pulse MSS, which have a focus on system monitoring and alerting. Here’s an example of one approach, which, in this case, was for a virtual or cloud solution. It got me thinking about how best to provide at least a subset of FCAPS within cloud or virtual environments. This view ended up being similar to that presented in the design:
We recommend the use of both inherent and supplementary logging and alerting capabilities. In this case, supplementary logging came in the form of an existing, agent-based capability (Openview, BMC, etc.) to carry out some smarter aggregation and filtering of the logging and alerting available from the MSG server up to the application layer.
Where possible, it is always desirable to have some basic Root Cause Analysis (RCA) to support operations teams. The ability to link the logging and alerting from the hypervisor hardware, up through hypervisor to VM OS, virtual infrastructure and application layer offers the chance to extract information to fulfill the needs of FCAPS management practices.
The use of the FCAPS model is not uncommon among our service provider customers here in Asia Pacific. Applying it universally across physical and virtual infrastructure allows for a universal fault management architecture to be applied across even the latest cloud services.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.