Too many network managers are fighting losing battles. Since 2016, the number of enterprise NetOps teams that are fully successful has dropped from 49% to 27%, according to Enterprise Management Associates (EMA) research.
These slides discuss why NetOps teams are failing and how a monitoring solution with a service-centric view of the network can turn things around.
20. Key Elements of Business-Aware Network Monitoring
(BANM)
Real-time monitoring Proactive alerting Actionable insights
20
21. Benefits of BANM
Improved business agility through better information and visibility
Enhanced operational efficiency by increasing productivity
Increased customer satisfaction from reduced MTTR
21
22. Getting Started with BANM
22
Discover
Manage
Monitor
Establish baseline
Adjust alerting
Setup Services
Setup Notifications
Technical Steps
Identify the stakeholders
Identify the top business
processes
Revenue generating
Legal/legislative need
Core mission
Identify the applications used by them
Include core productivity
applications
Email
Internet
Collaboration tools
Business Steps
23. Core Concepts
• Shared vs Dedicated Infrastructure
• Reactive vs Proactive vs Business Impacting
• Labelling Devices with Metadata
23
25. Dedicated vs Shared Infrastructure
• Outages in shared infrastructure impact MANY
SERVICES
• Outages in dedicated infrastructure impact only
those depending on the SERVICE.
• What people need is to monitor the shared
infrastructure as a service.
• Then monitor the dedicated infrastructure and let
those impacted know what is happening.
25
Shared
Dedicated
Dedicated
Dedicated
Dedicated
Dedicated
Dedicated
Dedicated
Dedicated
26. What is in an Enterprise Application
26
frontend
application
workstation
database
A user, using their PC/mobile access an application, which probably
has a frontend, application logic and a database. This will be running
on one or more servers, or using microservices, containers and
databases, logically the same.
users network
It is likely these servers are dedicated
to running this application (the
database server might be shared).
27. Expanding the Enterprise Application
27
frontend
application
workstation
router1
switch1
database
switch2
switch3
firewall
network
router10
switch10
Physical and Logical Connections
• Layer 2 (Ethernet)
• Layer 3 (IP)
• Application (HTTP)
users
The network could be a lot of gear inside an enterprise. There could be a WAN or VPN to a
local location or connect directly to the cloud. There are still things to create and control
network connectivity.
This network infrastructure is shared by many users
and applications.
28. Simplify the Enterprise Application
28
frontend
application
IP subnet 1
workstation
router1
switch1
database
switch2
switch3
IP subnet 2
firewall
network
router10
switch10
IP subnet 10
IP subnet 4
Shared infrastructure, used by
many services
Dedicated infrastructure used
only by that service.
IP subnet 3
users
Shared Infrastructure
Dedicated
Infrastructure
Physical and Logical Connections
• Layer 2 (Ethernet)
• Layer 3 (IP)
• Application (HTTP)
29. Many dedicated services
29
IP subnet 1
workstation
router1
switch1
switch2
switch3
IP subnet 2
firewall
network
router10
switch10
IP subnet 10
IP subnet 4
IP subnet 3
users
Shared Infrastructure
frontend
application
database
Shared infrastructure, used by
many services
Dedicated infrastructure used
only by that service.
frontend
application
database
frontend
application
database
frontend
application
database
Dedicated
Infrastructure
frontend
application
database
Physical and Logical Connections
• Layer 2 (Ethernet)
• Layer 3 (IP)
• Application (HTTP)
30. What about a network?
30
Dedicated
Infrastructure
Shared
Infrastructure
Dedicated
Infrastructure
Same!
A network is a service, it
provides connectivity.
The core network is fault
tolerant (if built right) and the
distribution network is highly
available.
The customer equipment is the
least reliable. This is where
most faults happen.
Core
Distribution
32. Differentiate Reactive from Proactive
Reactive
events
Operations
Teams
Support
Teams
Proactive
events
Technology
Engineering
Teams
Capacity
Planning
32
• What is a reactive event?
• Node down
• Disk full
• Application Down
• What is a proactive event?
• CPU High
• Memory High
• Disk filling up
• Interface dropping packets
Action
Required
Reactive
Triage
Restore
service
Proactive
Investigate
Plan a
change
33. What sort of action is needed?
33
Proactive Events
Reactive Events
Business Impacting Events
router
A device has many elements.
Each of the elements have a
status made up of the metrics we
collect.
Roll all those up to the device
status.
A device has two states, up or down.
If the device is down, it is down.
Status
State
Some status events require
action now.
Some status events require
action later.
State events require action
now.
34. Right information to the right teams
34
Operations
Engineering
firewall
load balancer
nas
router
server
storage
switch
toaster
ups
vpn
wireless
Events
Proactive Events
Reactive Events
Customer Success
Business Impacting Events
Reduced noise Actionable insights
Much data/events
36. Labelling devices for context and correlation –
better metadata.
We need good
metadata
about our
devices
We know all the
devices are not
equal
We know
different people
need to be
involved
36
37. Automated, Manual, API's and Custom Metadata
Automated
metadata
• The NMIS Suite
will
automatically
set some device
metadata
Managed
metadata
• Manage the
device
metadata using
the GUI.
API's set metadata
• Use APIs to
integrate
metadata from
existing
systems.
Custom metadata
• Create and
manage custom
fields for data
important to
your business
processes.
37
41. Two critical events
41
Many supporting events created, but there are two actionable events.
One for the network engineering team
One for the customer relationship team
42. The right notifications to the right people
42
The Network Engineering
Team deal with the
network outage and can
see impacted customers.
The customer
relationship team
sees it’s a bigger
outage and lets
the customers
know.
Custom Groups are cool
43. Conclusion 43
Importance and Benefits of Business-
Aware Network Monitoring
Getting Started with Business-Aware
Network Monitoring
Core concepts
supporting BANM
Shared vs Dedicated
Infrastructure
Reactive vs Proactive vs
Business Impacting
Labelling Devices
How to implement Business-Aware
Network Monitoring with opCharts
Enterprise Services
44. Thank you
Questions?
For a copy of this slide pack and
other materials email:
marketing@firstwave.com
Learn more about Business Aware
Network Monitoring
• https://firstwave.com/banm
• sales@firstwave.com
FirstWave network management solutions are used by over 150,000 organizations globally, including: