Let’s say that we configured Huawei SmartAX MA5683T, and also created dba-profile, ont-lineprofile and ont-srvprofile, as I wrote in the article Configuring Huawei SmartAX MA5683TContinue reading “Adding ONT on Huawei SmartAX MA5600”
Suppose you configured OLT as I wrote in this article Configuring the Huawei SmartAX MA5683T through the console.
Now connect via telnet or console to the Huawei SmartAX MA5683T.
After entering the login and password, we will go into configuration mode by typing the command:
In this article I will give an example of viewing and configuring logs on the Huawei SmartAX MA5683T.Continue reading “View and configure logs on the Huawei SmartAX MA5600”
For example, to allow to connect to the Huawei SmartAX MA5600 series via telnet only to the specified IP address ranges 192.168.0.100-192.168.0.254 and 172.16.24.1-172.16.24.50 we will connect to the device and go into the configuration mode:
And execute the following commands (for non-specified IP access is immediately prohibited):
sysman ip-access telnet 192.168.0.100 192.168.0.254 sysman ip-access telnet 172.16.24.1 172.16.24.50 sysman firewall telnet enable
Similarly for SSH:
sysman ip-access ssh 192.168.0.100 192.168.0.254 sysman firewall ssh enable
And SNMP for example for one IP:
sysman ip-access snmp 192.168.0.100 192.168.0.100 sysman firewall snmp enable
To deny access to the specified subnet, we specify ip-refuse instead of ip-access, for example:
sysman ip-refuse telnet 192.168.1.200 192.168.1.220 sysman firewall telnet enable
On the test, I performed the settings for Huawei SmartAX MA5683T, they are essentially the same for the entire MA5600 series.
Once when executing commands in the Huawei SmartAX console, the MA5683T began to notice often the message:
Failure: System is busy, please retry after a while
As it turned out, the reason in my case was Zabbix, which every hour received SNMP levels ONT and drew graphics. SNMP requests from him were packed with packets of 30-50, separately for each port. I solved the problem by increasing the timeout in the Zabbix server configuration and the verification period for more hours, because OLT was slowly issuing information, Zabbix was not available, considered it inaccessible, paused briefly and sent requests again.
Also, in the settings of the Zabbix node, you need to uncheck “Use bulk requests”.