Comtech EF Data MM200 - Manual (Page 71)

MM200 High-Speed Microwave Modem User Interfaces
TM086 - Rev. 4.1 4-47
This section refers to the Boot Host.
1.
Select 36, ‘Server Host Name’. Enter the Server Host Name and press . This is
a descriptive entry only.
Example: SERVER
4.30 Router IP Address
Select 37, ‘Router IP Addr’. Enter the router Internet Address in dot notation and press .
Please consult your network administrator for valid addresses.
Example: 192.168.0.254
4.31 IP Address Mask
In the mask (more clearly seen in the binary format), binary 1s indicate the position of the network
and subnet portion of the IP Address while binary 0s identify bits that represent the individual
interfaces. To recognize a subnet, each system in the subnet must have the same subnet mask.
Please consult your network administrator for a valid address class mask.
1.
Select 38, ‘IP Address Mask’. Enter the IP Address mask in dot notation and press
.
Example: 255.255.0.0
4.32 Boot Mode (Optional)
1.
Select ‘31’ from the Controls Menu and press . Scroll through the various
selections to ‘NVBOOT’ and press . The above settings will be enabled the next
time the system is rebooted. If a bootp server is available, the MM200 can be remotely
configured by selecting bootp mode. This option is currently not available.
4.33 Community
Each managed station controls its own local MIB and must be able to control the use of that MIB
by a number of management stations. This relates to security concerns. A managed MIB such
as the MM200 needs to protect itself from unwanted and unauthorized access. SNMP, as defined
in RFC 1157, provides only a limited capability for such security, namely the concept of a
community. An SNMP Community is the relationship between an SNMP Agent and Management
Stations.
1.
To set the community string on the MM200, select 9, ‘Community’. Enter the desired
community name and press .
Example: “public”
4.34 Trap Type and Trap Hosts
Traps enable the modem to notify the management station of significant events such as alarms.
Version1 and version2 Traps are supported at this time. These are Operator selectable using
Terminal Command Number 5. The messages are sent to specific pre-defined hosts. The
Primary and Secondary Trap Hosts IP Addresses are setup using Terminal Commands 6 and 7.
Each host should be acceptable to the transport layer. In other words, the transport layer needs to
be able to open a connection to the entities specified by the trap host fields.