system

Restarts the clustering daemon (clusterd) process or expedites the relaunching of this process. For example:

(config) # system process clusterd restart

Note:  This command only applies to cluster control. It does not affect traffic distribution.

Restarts the NTP daemon (ntpd) process or expedites the relaunching of this process. For example:

(config) # system process ntpd restart

Restarts the SNMP agent daemon (snmpd) process or expedites the relaunching of this process. For example:

(config) # system process snmpd restart

Restarts the Unified Gateway daemon (ugwd) process or expedites the relaunching of this process. For example:

(config) # system process ugwd restart

Enables the secure cryptography mode, which provides enhanced security on the management interface of the GigaVUE node.

For the secure cryptography mode to take effect, reload the GigaVUE node or cluster.

For example:

(config) # system security crypto enhanced

(config) # reload

or

(config) # system security crypto enhanced

(config) # cluster reload

Refer to the “Configuring Secure Cryptography Mode” section in the GigaVUE Administration Guide for details.

IMPORTANT: TLS version 1.2 is required for secure cryptography mode. When enabling secure cryptography mode, TLS version 1.2 is enabled by default. If you disable secure cryptography mode and want to change the TLS version, use GigaVUE‑OS CLI command: web server ssl min-version tls<version>.

Enables the Martian logs that appear in the kernel logs to also appear in the syslog messages in the device.

Selects the legacy mode for stacking. For example:

(config) # system stacking-mode legacy

Selects the default stacking mode.

Note:  After user confirmation the system stacking-mode legacy command immediately resets the traffic configuration and initiates a cluster reload of all nodes. After the cluster is up, the configuration saved in the backup file must be applied manually to restore the traffic configuration.

For example:

[cluster: leader] (config) # no system stacking-mode legacy

! WARNING: Changing stacking mode will automatically

! - Take backup of config in file stacking_mode_config_backup.txt

! - Reset factory only traffic config

! - RELOAD the cluster

! - User must manually apply stacking_mode_config_backup.txt after bootup

Confirm stacking mode change? [no] YES

Configuration saved to database 'initial'

System shutdown initiated -- logging off.

# after the cluster is up and user is logged back in, apply the saved configuration in the backup file:

[cluster: leader] (config) # configuration text file stacking_mode_config_backup.txt apply fail-continue

(config) # no system stacking-mode legacy

By default the system would disable the stacking-mode legacy parameter.

Specifies the Neighbor Discovery Protocol (NDP) refresh time interval. The timer is configurable from 3 to 30 seconds. The default is 30 seconds.

When an IP interface is configured, Neighbor Solicitation (NS) packets are sent out on the IP interface associated with tool port to find the gateway MAC address, and Neighbour Solicitation (NS) packets are sent out on the IP interface to find the local tool address. In response, the gateway sends an Neighbor Advertisement (NA) packet and the control card tries to match the IP interface's IP address with the IP address of the received NA message. If a match is found, the IPv6 neighbor status changes to resolved (otherwise, the IPv6 Neighbor status is not resolved).

Once IPv6 Neighbor is resolved, this tunnel NDP timer controls the interval at which an NS packet is sent to the gateway as well as to the local tool to detect if the gateway and local tool is reachable or not.

For example:

(config) # system ndp refresh-interval 30

Use the show system ndp command to display the NDP refresh time interval.