Network Monitoring using RNRP
We have one additional network card in all servers and client for managing the PC ( Backup/AV/Logging etc) .
Is it possible to create a explicit addressing mode to monitor the network failure alarms ( IP address range 192.168.10.x , mark 255.255.252.0 )
Is it possible to create a explicit addressing mode to monitor the network failure alarms ( IP address range 192.168.10.x , mark 255.255.252.0 )
Asked 5 months ago
Answers
0
Technically speaking, yes.
However, you can’t have more than two paths connecting an RNRP area (primary + secondary) so this network will need a different RNRP area than the regular client/server network.
The computers connected here will see and report this area as a valid connection path. The RNRP Local Area Flag can be set to avoid propagating the area to other nodes not connected. Implicitly, this is done by adding 128 to the third byte in the IP address, eg area 10 hidden: 172.16.40+128.0: this is how 800xA for Advant Master hide their PU410 boxes.
The 800xA system has a Network Filter setting that should not include this network to avoid routing any client/server traffic on this LAN.
The area number should be higher than the client/server area to make RNRP favorize the regular client/server network(s). This also takes care of giving the regular client/server network the best Metric Value.
There is no real difference in using 192.168.10.0/24, 192.168.10.0/22, 172.16.40.0/22 or 172.16.168.0/22 other than that the two first require explict parameterizing (=more work).
However, there might be more things to consider or effects that may backfire on System 800xA, eg the ”Network Connection ...” alarms that the System Status service offer.
Proper testing is required...
However, you can’t have more than two paths connecting an RNRP area (primary + secondary) so this network will need a different RNRP area than the regular client/server network.
The computers connected here will see and report this area as a valid connection path. The RNRP Local Area Flag can be set to avoid propagating the area to other nodes not connected. Implicitly, this is done by adding 128 to the third byte in the IP address, eg area 10 hidden: 172.16.40+128.0: this is how 800xA for Advant Master hide their PU410 boxes.
The 800xA system has a Network Filter setting that should not include this network to avoid routing any client/server traffic on this LAN.
The area number should be higher than the client/server area to make RNRP favorize the regular client/server network(s). This also takes care of giving the regular client/server network the best Metric Value.
There is no real difference in using 192.168.10.0/24, 192.168.10.0/22, 172.16.40.0/22 or 172.16.168.0/22 other than that the two first require explict parameterizing (=more work).
However, there might be more things to consider or effects that may backfire on System 800xA, eg the ”Network Connection ...” alarms that the System Status service offer.
Proper testing is required...
Add new comment