Filter
Top Products
ADCP-75-192 • Issue 2 • June 2007
Page 35
© 2007, ADC Telecommunications, Inc.
3.6.3 Accessing Nodes Locally
Nodes can be accessed locally through the serial link. The required hardware is as follows:
• Terminal with serial interface and terminal software such as Tera-Term Pro or Hyperlink.
• RS-232 cable 9 pin D shell male to male type.
• Adapter for the Digivance CXD/NXD CPU low profile I/O connector (DB-9F to RJ-11).
Once the link is made, run the terminal software. If a login prompt is not already available in the
terminal window, hit enter a few times to bring it up. Then follow a normal login procedure.
3.6.4 Accessing Nodes via TCP/IP
To perform some installation maintenance activities, the network operator will need to log into
Digivance CXD/NXD nodes. Each node runs a daemon for Telnet, File Transfer Protocol
(FTP), and Virtual Network Connections (VNC). Depending on the LAN’s DNS configuration,
a user may or may not be able to use hostnames (instead of literal IP addresses) when accessing
Digivance CXD/NXD nodes. Nodes can always be accessed by IP address. These three access
types are available for Windows and Unix strains.
There are two default user accounts that come standard in the Digivance CXD/NXD network.
The “operator” account has access to the Digivance CXD/NXD binaries and is used for regular
maintenance. The “root” account has full access privileges to the entire file system. In addition,
the “operator” account has “soda” privileges, which may be modified by the network operator to
tailor operator access. To learn more about “soda”, log onto any Linux operating system and
type “man soda” at the prompt. Note that, among other privileges, a “root” user can create more
user accounts on each node.
3.6.5 Using a Third Party Network Management System with Digivance CXD/NXD
Digivance CXD/NXD control and monitoring is executed via Simple Network Management
Protocol (SNMP). As such, any Network Management System (NMS) based on SNMP will be
compatible with the Digivance CXD/NXD system. However, not all NMS products are the
same. While it is up to the operator to determine which NMS is right for their needs, it is
recommended that the chosen NMS will have the following features:
• Auto-polling
• The NMS must regularly poll all nodes for MIB entry updates.
• The NMS must regularly search for new nodes on its network.
• Graphical User Interface for data display and manipulation
• At a minimum, a MIB browser capable of SNMP level 2 sets and gets, coupled with a
node map generator, would suffice.
• Ability to output poll data to a database for customizable GUI operations such as user
accounts and data sorting is strongly recommended.