Cannot download to AC800M controllers from Clients, RNRP TCP/IP Forwarding is set to a 1
Cannot download to AC800M controllers from Clients
Cannot see the controllers through Control Builder on any node other than the primary and redundant 800xA connectivity servers.
Control Builder will open on all the nodes, but will not connect to the controller
TCP/IP forwarding already was set to a 1.Symptoms:
- Misconfguration of the managed switch on the Control Network Resolution:
It was found that the RNRP setting for the AC800M controllers were not completely set up correctly and the Hirschmann Switches were not configured for full duplex mode.
1) Change the RNRP Number of Remote Areas (Maximum number of remote Network Areas that this node can communicate with via routers) between 4 and 15. This is in the setting for the Controller in Control Builder.
From the manual: "A node for which the “max number of remote areas” is exceeded will not get routing entries for all network areas. This means that it will be unable to communicate with some nodes on the network, and it can not be predicted which nodes this is. To avoid this problem it must be made sure that, for all nodes the number of network areas that are within “max number of hops” does not exceed “max number of remote areas”.
2) The Hirschman switch needed its default gateway to point to the Connectivity Server's Primary Network interface on the Control network. Also the port configuration setting on switches should be set to Full Duplex.
From the manual: "Default Gateway Routing for Nodes without RNRP. If nodes that do not support RNRP are connected to the control network, e.g. managed switches or time servers, and these nodes need to be accessed (by nodes that use RNRP) via the RNRP routers, the necessary routing information can not be built up by RNRP. One way to solve this is to enter the primary Control Network address of the primary connectivity server as “Default Gateway" in these nodes to inform them about how to reach the Client Server network."