Manualshelf

User manual

ManualsBrandsMotorola ManualsOther9000SM - Canopy 900 MHz Subscriber Module
21222324252627282930
SM User Manual January 2004
Software Release 4.1
4.6 REINSTATING REMOTE ACCESS CAPABILITY
Where ease of network administration is more important than the additional security that the No
Remote Access feature provides, this feature can be disabled as follows:
Procedure 3: Reinstating remote access capability
1. Insert the override plug into the RJ-11 GPS sync port of the AP.
2. Power up or power cycle the AP.
3. Access the web page
http://169.254.1.1/lockconfig.html.
4. Click the check box to uncheck the field.
5. Save the changes.
6. Reboot the AP.
7. Remove the override plug.
RESULT: Access to this AP is possible through HTTP, SNMP, FTP, telnet, or over an RF link.
4.7 SNMP
SNMPv2 (Simple Network Management Protocol Version 2) can be used to manage and monitor
the Canopy modules under SMI (Structure of Management Information) specifications. SMI
specifies management information definitions in ASN.1 (Abstract Syntax Notation One) language.
SNMPv2 supports both 32-bit and 64-bit counters. The SMI for SNMPv2 is defined in RFC 1902 at
http://www.faqs.org/rfcs/rfc1902.html.
4.7.1 Agent
In SNMP, software on each managed device acts as the agent. The agent collects and stores
management information in ASN.1 format, in a structure that a MIB (management information
base) defines. The agent responds to commands to
• send information about the managed device.
• modify specific data on the managed device.
4.7.2 Managed Device
In SNMP, the managed device is the network element that operates on the agent software. In the
Canopy network, this managed device is the module (AP, SM, or BH). With the agent software, the
managed device has the role of server in the context of network management.
4.7.3 NMS
In SNMP, the NMS (network management station) has the role of client. An application (manager
software) operates on the NMS to manage and monitor the modules in the network through
interface with the agents.
4.7.4 Dual Roles
The NMS can simultaneously act as an agent. In such an implementation, the NMS acts as
• client to the agents in the modules, when polling for the agents for information and
sending modification data to the agents.
• server to another NMS. when being polled for information gathered from the agents
and receiving modification data to send to the agents.
Issue 5 Page 29 of 119