ML Link Visibility via MAV Management Configuration
MAV session connected to an ML NE (CO or CPE, via ETH-x, COLAN or HSL-x port),
shows directly (via ETH-x, COLAN) and indirectly connected (Linked via HSL) NEs if the
following conditions are true:
CO and CPE are connected by at least one copper pair.
L2 (LAN) and L3 (IP) settings on both ML NE (CO and CPE) are configured correctly.
For security reasons, remote (telnet) access to each ML NE can be secured enabling SSH,
ACL features on selected NE or by separating IP/LAN network, differently configured on
CO and CPE NE.
Note: If an IP on ML NE is configured (i.e. is different from 0.0.0.0) MetaASSIST View
will always try to connect by IP address (also to NEs linked via HSL). If an IP/LAN
configuration does not allow connection between this ML and the management host
(intentionally or due to configuration mistake) MetaASSIST View will not try to connect
by non-IP access.
In mixed configuration (CO NE has IP address and CPE NE does not have IP address),
MetaASSIST View will connect to the CPE NE without IP, using non-IP access (also
controlled by “Access From Peer”).
Note: CPE NE with SW earlier then R5.0a supports basic non-IP access capabilities for monitoring of
NE statuses and basic configurations. CPE NE with SW=R5.10 supports full non-IP access capabilities
(including file transfer-based features). Note that on any NE with no IP, SNMP communication is
disabled.
It operates as follows:
To show ML link, MetaASSIST View uses the following ML NE communication abilities:
Embedded Operational Channel (EOC) - single modem-based connectivity that is always
(if modem in synchronized) available from XTU-O modem to access XTU-R modem.
IP-less Ethernet - based on 802.1ah OAM (Operation Administration and Management)
PDU transport connectivity is available between ML devices via HSL ports only. IP-less
802.1ah OAM PDU transport allows full management access, including file transfer.
Notes:
CO NE requires an IP Address to enable file transfer to an IP-less CPE NE.
IP-less access from the Peer can be controlled: enabled (factory default) or disabled.
IP/Ethernet connection - requires configuration of IP Address, Gateway and Subnet Mask
configured on the NE. The MGMT VLAN must be consistently configured on all NEs.
Note: The IP/Ethernet access on each NE can be controlled and additionally secured (by
ACL or SSH).
To Next Page
Loading...