MonitorLink

5 min

asternos monitorlink monitor link module provides a capability to monitor the status of uplink and downlink interfaces on a network device user can add a couple of members into a monitor link group with different mode, if uplink member is down, the downlink member will be shutdown automatically create monitor link group request example to create a monitor link group via edit config \<config> \<top> \<monitor link> \<monitor link group operation="create"> \<name>ce uplink al2\</name> \<delay>30\</delay> \<members> \<member> \<port>ethernet18\</port> \<mode>uplink\</mode> \</member> \<member> \<port>ethernet19\</port> \<mode>downlink\</mode> \</member> \</members> \</monitor link group> \</monitor link> \</top> \</config> response example \<rpc reply xmlns="urn\ ietf\ params\ xml\ ns\ netconf\ base 1 0" message id="urn\ uuid\ c9dae25f 3302 4874 8439 35c074b6fc8c"> \<ok/> \</rpc reply> get monitor link group request example to retrieve the current monitor link group configuration via get config \<filter type="subtree"> \<top> \<monitor link/> \</top> \</filter> response example \<rpc reply xmlns="urn\ ietf\ params\ xml\ ns\ netconf\ base 1 0" message id="urn\ uuid 1c4f4ec8 d66d 494e a266 0071bdcad92d"> \<data> \<top> \<monitor link xmlns="http //asterfusion com/ns/yang/asternos monitor link"> \<monitor link group> \<name>ce uplink al2\</name> \<delay>30\</delay> \<members> \<member> \<port>ethernet18\</port> \<mode>uplink\</mode> \</member> \<member> \<port>ethernet19\</port> \<mode>downlink\</mode> \</member> \</members> \</monitor link group> \</monitor link> \</top> \</data> \</rpc reply> delete monitor link group request example to delete a specific monitor link group via edit config \<config> \<top> \<monitor link> \<monitor link group operation="delete"> \<name>ce uplink al2\</name> \</monitor link group> \</monitor link> \</top> \</config> response example \<rpc reply xmlns="urn\ ietf\ params\ xml\ ns\ netconf\ base 1 0" message id="urn\ uuid 25ba6658 4551 40e9 a335 c35deb9d3b9b"> \<ok/> \</rpc reply>