Troubleshooting Management Connection Problems
If service traffic passes through the Actelis system, but management traffic does not, then
please check that the Management VLAN is configured correctly;
Management traffic (defined to be forwarded with HIGHEST priority) fails when HSL is
congested by service traffic. Check that Ingress Traffic limiting is not enabled on HSL (in
ML700 only). To resolve the problem, disable the feature via TL1.
If both Management and Service traffic do not pass through the Actelis system then
probably the Ethernet port setting does not match with network configurations:
The ETH-<ID> port MDI pinout is by default MDI and requires an RJ45 connector
with straight-through cable;
Speed and Duplex mode of ETH-<ID> by default are auto-negotiated. You can
connect via Craft port and configure ML device Ethernet port according to your
network setting;
Connector is damaged. It is recommended to check physical connectivity.
IP connectivity parameters problem
Incorrect IP address was typed in the "Connect" dialog box. In this case, MetaASSIST
View tries to connect to the NE and displays the following tooltip when the cursor is
located on the NE: 'Started Connecting...'. Re-connect with correct IP address.
Invalid IP attributes (i.e., Incorrect or duplicated IP address, incorrect subnet mask or
gateway address) configured on ML NE.
On directly accessed NE, MetaASSIST View tries to connect to the NE and displays
the following tooltip when the cursor is located on the NE: 'Started Connecting...'.
Re-connect with correct IP address.
On in-directly accessed NE (subtended via HSL NE), MetaASSIST View tries to
connect to the NE but fails to connect. In this case, the NE will be displayed in the
NEs linked via HSL pane. Reconfigure the parameters on the ML NE using this
pane and then re-connect via this pane.
Access is not granted by IP Access Control feature
In this case, MetaASSIST View tries to reconnect indefinitely. Resolve the problem and
MetaASSIST View will reconnect automatically.
In this case, you need to add your IP address to the IP Access Control List with the Telnet
protocol specified as enabled for connection or connect through the Craft port and disable
IP Access Control. IP Access Control feature is enabled on ML device and the IP address
of your host (PC/Workstation) is not in the IP Access Control List.
SSH Authentication Failures and Warnings (optional - for secure version only)
Private Key file not found.
If the Private Key cannot be found in the workstation file system, you will receive the
following error message: 'Private Key file cannot be found.'
Public Key of the Management Host not found.
If the Public Key of the Network Element cannot be found in the workstation file system,
you will receive the following warning message: 'Accept Key <Signature> for Host <IP
Address>.' Click Yes to continue with the login and save it for the next login.
To Next Page
Loading...