Thread Content
There are two operation stations: one is the engineer’s station as well as Operator Station A, and the other is a pure operator station, Operator Station B. It has been found that the B operation station cannot be used to query historical trends, as station B operates on a single network. When releasing the configuration, I discovered that it is not possible to send it to this B operation station via the operation network, but it can be sent through network A. Is it because Bilibili doesn’t have dual network cards that this phenomenon occurs?
Check the settings of the operation team on B Station; I’m not sure what your settings are. The IP range should be the same as that of A Station. The setup with two network cards is intended to ensure redundant communication, and using the same IP range should resolve this issue. As for the policy settings, it’s not necessary to query trends
There is only one operation team, that’s true. The IP range was set based on the previous IP address; it’s just that the computer broke down, so I replaced it with another computer that has a single network card.
Is your historical trend based on a historical server? Check the disk space of the standalone machine.
Even if it’s republished on a different computer, it will be impossible to access the previous data, but at least the data after publication will have a history record. Also, copy the data from the DCSRUN folder of the good machine over