Monitoring controler
Adding new service instance
• What has to be done on MA/cMA? Configuration
steps:
–
–
–
–
–
Add new VLAN
Add new netnamespace
Assign VLAN to namespace
Set the IP address in namespace on the VLAN
Set the link to up
• All these are shell commands – can be prepared
as a script to be started with the VLAN number
argument
• Deleting service instance is similar.
Adding new service instance
• How to monitor the parameters?
– For p2p link
• on one (or both) sides start the server in the
appropriate namespace
• On the other side start the owping and ping the server
– For p2mp services:
• on all sides start the server in the appropriate
namespace
• On all sides start the owping towards all the servers
(full mesh)
Initiating monitoring
• Solution 1
– Add owping to crontab (resolution 1 minute, can
do the trick to make it less than 1 minute)
– Pipe the results to the script which would send
them to the MRR/Correlator, wherever...
• Solution 2
– Invoke ping from the central management
console, and gather results on the central station
Software solutions
• Configuration – easy with ansible (or similar)
• Starting the server side – easy with ansible (or similar)
• Initiating the service monitoring – which one is better:
– If cron is used – better to do it with ansible (or similar)
– If each monitoring request is separately invoked from the
central station – better to do it with sensu (or similar)
• What about Mode 2 and 3 – what kind of interaction
do they require from MC? Is it management or
monitoring?
• How to monitor the health of MAs?
HW
TA
TA
KG
(PV)
TA
DS,
PM
PV
DS,
PM
DS,
PM
DS,
PM