800xA5.1 system RNRP shows "same address defined in 2 locations" message
Hi ,
In 800xA 5.1 system RNRP shows message as
1. "Same network address 172.17.4.0 defined on two locations"
2. "No ConnectDataReply from node12" (Node12 is redundant Aspect sever) can anyone please provide the reason for this message .
All Servers , workstations & Controllers primary & secondary network shows UP .
Please refer Screenshot for more details.
In 800xA 5.1 system RNRP shows message as
1. "Same network address 172.17.4.0 defined on two locations"
2. "No ConnectDataReply from node12" (Node12 is redundant Aspect sever) can anyone please provide the reason for this message .
All Servers , workstations & Controllers primary & secondary network shows UP .
Please refer Screenshot for more details.
Asked 2 months ago
Answers
2
The same address could stem from "ghost" NICs; with E144 health check scripts you can iterate all known (and unknown!) adapters and IP-address aliases in a PC.
I suspect you have a duplicate or alias somewhere. The NIC settings are also possible to view via RegEdit.exe (please Google for help)
The "not equal" error is due to wrong calculation of node number, e.g. 172.16.4.11/22 is 11, but if you increase the subnetwork mask to 127.16.4.11/16 you must include more bits from the 3rd byte and the node number becomes 4*256+11 = 1035. Go through all your NICs and RNRP parameters; there is a wrong value entered somewhere.
No ConnectDataRply is an "old" and latched error (=no longer existing). Usually this error is due to Windows Firewall blocking an interface because it is listed as "Unknown"; proper detection as "Home", "Work" or "Public" is required, or else the firewall will block all incoming traffic. When this happen; RNRP will report "No ConnectDataRply" as it is unable to query the remote nodes it comes in contact with.
I suspect you have a duplicate or alias somewhere. The NIC settings are also possible to view via RegEdit.exe (please Google for help)
The "not equal" error is due to wrong calculation of node number, e.g. 172.16.4.11/22 is 11, but if you increase the subnetwork mask to 127.16.4.11/16 you must include more bits from the 3rd byte and the node number becomes 4*256+11 = 1035. Go through all your NICs and RNRP parameters; there is a wrong value entered somewhere.
No ConnectDataRply is an "old" and latched error (=no longer existing). Usually this error is due to Windows Firewall blocking an interface because it is listed as "Unknown"; proper detection as "Home", "Work" or "Public" is required, or else the firewall will block all incoming traffic. When this happen; RNRP will report "No ConnectDataRply" as it is unable to query the remote nodes it comes in contact with.
Add new comment