Uplogix 500 - Configuring an Optional Pulse Server; Configuring Communication with the Uplogix Control Center (UCC)

Installation Guide for Uplogix Local Managers 28
Configuring an optional Pulse server
Specify a Pulse server using the config system pulse command.
[admin@UplogixLM]# config system pulse
--- Existing Values ---
Use Pulse: false
Pulse Server IP 1: 127.0.0.1
Pulse Server Port: 7
Enable Outband on Pulse Failure: no
Change these? (y/n) [n]: y
--- Enter New Values ---
Use Pulse (y/n) [n]: y
Pulse IP 1: [127.0.0.1]: 203.0.113.1
Pulse Port 1: [7]:
Pulse IP 2: [127.0.0.1]:
Pulse Port 2: [7]:
Pulse IP 3: [127.0.0.1]:
Pulse Port 3: [7]:
Enable Outband on Pulse Failure (y/n) [n]: n
Do you want to commit these changes? (y/n): y
The above example enables Pulse to one pulse server, but does not enable the automatic dial-
out PPP function. The Uplogix Local Manager can use rules to generate alarms even when
Pulse fails. For more information on Pulse and alarms, consult the User Guide for Uplogix Local
Manager.
Configuring communication with the Uplogix Control Center (UCC)
Use the config system management command if you wish to manage the Uplogix Local Manager
with a UCC. Uplogix recommends using the default values and setting the ‘Hostname or IP:’
field to contain the hostname or IP address of your UCC.
[admin@UplogixLM]# config system management
--- Existing Values ---
Use Management Server: false
Hostname or IP: 127.0.0.1
Port: 8443
Heartbeat interval (seconds): 30
Heartbeat band: all
Always use minimal heartbeat: false
Last successful heartbeat: (not yet contacted)
Change these? (y/n) [n]: y
--- Enter New Values ---
Use Management Server (y/n) [n]: y
Hostname or IP [127.0.0.1]: 203.0.113.3
Port [8443]:
Heartbeat interval (seconds) [30]:
Heartbeat during [all]:
Do you want to commit these changes? (y/n): y