fixup! software/ors-amarisoft: fix enb monitoring

software/ors-amarisoft/buildout.hash.cfg

@@ -24,7 +24,7 @@ md5sum = 762d55291e75e8b61e35f9f28d29915a
 
 [template-lte-enb]
 _update_hash_filename_ = instance-enb.jinja2.cfg
-md5sum = 77024b4bc87903f1a2ed86245e691800
+md5sum = b24b41a9e6d5c5cb135ed647ab14b0f6
 
 [template-lte-gnb-epc]
 _update_hash_filename_ = instance-gnb-epc.jinja2.cfg
@@ -36,7 +36,7 @@ md5sum = 9ac219ea7c331bfc0e5ed3fd4c9991e2
 
 [template-lte-epc]
 _update_hash_filename_ = instance-epc.jinja2.cfg
-md5sum = af285212bf8e15402416b58a65d103f8
+md5sum = dc9c317631dd7d037215b23ae05ff8b3
 
 [ue_db.jinja2.cfg]
 filename = config/ue_db.jinja2.cfg

software/ors-amarisoft/instance-enb.jinja2.cfg

@@ -4,6 +4,7 @@ parts =
   ltelogs
   lte-enb-config
   lte-enb-service
+  monitor-base
   publish-connection-information
 
 extends = {{ monitor_template }}

software/ors-amarisoft/instance-epc.jinja2.cfg

 [buildout]
 parts =
   directory
-#  publish-connection-parameter
   ltelogs
   lte-mme-config
   lte-mme-service