13 router ip address, 14 ip address mask, 15 boot mode (optional) – Comtech EF Data SFC1800A User Manual
Page 61: 16 community, 17 trap type and trap hosts, 18 trace mode

SFC1800A Synthesized Frequency Upconverter
User Interfaces
TM111 – Rev. 1.0
4-37
4.6.2.13 Router IP Address
Select 42.RouterIPAddr :. Enter the router Internet Address in dot notation and press
Please consult your network administrator for valid addresses.
Example: 192.168.0.254
4.6.2.14 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 43.IPAddressMask:. Enter the IP Address mask in dot notation and press
Example: 255.255.0.0
4.6.2.15 Boot Mode (Optional)
1.
Select 37.Boot Mode : from the Controls Menu and press
various selections to ‘NVBOOT’ and press
enabled the next time the system is rebooted. If a bootp server is available, the
upconverter can be remotely configured by selecting bootp mode. This option is currently
not available.
4.6.2.16 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 upconverter 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 SFC1800A Upconverter, select 34.Community:.
Enter the desired community name and press
Example: “public”
4.6.2.17 Trap Type and Trap Hosts
Traps enable the converter 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 30. The messages are sent to specific pre-defined hosts. The
Primary and Secondary Trap Hosts IP Addresses are setup using Terminal Commands 31 and
32. 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.
4.6.2.18 Trace Mode
1.
For debugging purposes, a trace mode is specified by the Operator users for various
diagnostic levels.