User's Manual

Chapter 2 - Commissioning Initial NPU Configuration
4Motion 56 System Manual
2 Configure the IP address (x.x.x.x) and subnet mask (y.y.y.y). For details refer
to “Assigning an IP address to an interface” on page 121:
npu(config-if)# ip address x.x.x.x y.y.y.y
3 Configure the MTU of the interface to 1500 bytes: npu(config-if)# mtu 1500
4 Exit the interface configuration mode: npu(config-if)# exit
5 Exit the configuration mode: npu(config)# exit
2.1.3.4 Save and Apply Changes in Site Connectivity Configuration
1 Save the configuration: npu# write (otherwise, after the next time reset you will
lose the configuration changes).
2 If you changed the Connectivity Mode, reset the system to apply the changes:
npu# reset
2.1.4 Static Route Definition
Static Route must be configured whenever the EMS server and the NPU are on
different subnets. For more details refer to “Adding a Static Route” on page 168.
Run the following command: npu(config)# "ip route 0.0.0.0 0.0.0.0 x.x.x.x"
(x.x.x.x is the next hop IP address, 0.0.0.0 0.0.0.0 define the IP address and mask
as “any destination”. Depending on your backhaul network, you may define
different IP address and mask to allow only specific destinations).
2.1.5 SNMP Manager Definition
To define the communities to be used by the SNMP manager, run the command:
npu(config)# snmp-mgr ReadCommunity public ReadWriteCommunity private.
For more details refer to “Adding an SNMP Manager” on page 371.
For proper operation of the manager you should configure also the Trap Manager
parameters and enable sending traps to the defined Trap Manager (this can also
be done later via the management system):
1 npu(config)# trap-mgr ip-source x.x.x.x port 162 TrapCommunity public
( x.x.x.x is the IP address of the EMS server). For more details refer to
“Adding/Modifying a Trap Manager entry” on page 374
2 npu(config)# trap-mgr enable ip-source x.x.x.x
Note that if the management system is behind a NAT router, the NAT Outside IP
address (the IP of the router’s interface connected in the direction of the managed
device LAN) must be defined in the device as a Trap Manager, with traps sending
enabled. In the NAT router, Port Forwarding (NAT Traversal) must be configured