Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Monitoring Nodes in the Fabric

As an administrator or operator, you can use Junos Space to track the status of physical and logical components of deployed nodes in a fabric.

Junos Space Network Management Platform supports SNMP Monitoring by an SNMP Manager for SNMP v1, v2c, and v3.

The SNMP manager polls Junos Space to obtain information about the logical components of the nodes using an object identifier (OID) in SNMP v1 and v2, or v3 as a user. The response is provided by the Junos Space SNMP agent and the polled data is displayed in the Network Monitoring workspace.

This topic contains the following sections:

Viewing and Modifying the SNMP Configuration for a Fabric Node

To view and edit the Junos Space SNMP configuration for self-monitoring:

  1. Select Administration > Fabric.

    The Fabric page appears.

  2. Select the node whose configuration you want to view or modify, and from the Actions menu, select SNMP Configuration.

    The SNMP Configuration window appears with the title bar displaying the IP address of the selected node.

  3. Set the SNMP configuration parameters as required, using Table 1 to guide you.
    Note:

    By default, the system load parameters are set to 4, which means that an alert is indicated only when all CPUs are under 100 percent load.
    Table 1: SNMP Configuration

    Setting

    Explanation

    Recommended Settings

    Default Value

    Enable SNMP over TCP

    Enables SNMP communication over TCP

    Note:

    By default, SNMP communication occurs over UDP.

    Cleared

    Cleared

    Monitor Web Service

    Includes monitoring the performance of the Junos Space GUI

    Note:

    This parameter is enabled only for the Junos Space VIP node.

    Selected

    Selected

    Monitor All Disks

    Includes all disks on the current Junos Space server

    Cleared

    Cleared

    Monitor RAID

    Enables Net-SNMP to monitor the RAID state

    When a RAID controller fault is detected, a trap is sent.

    Note:

    From Junos Space Platform Release 16.1 onward, if you want to use the Monitor RAID option, you need to install StorMan-7.31-18856.x86_64.rpm . For installation instructions, see Installing StorMan RPM for Monitor RAID Functionality.

    Note:

    This field is not applicable to and is disabled for Junos Space Virtual Appliances.

    Selected

    Cleared

    Disk Usage %

    When the percentage of the disk in use exceeds the configured disk usage percentage, an alarm is triggered.

    5

    5

    System Load (1 min)

    When the average system load (over 1 minute) exceeds the configured value, an alarm is triggered.

    4

    4

    System Load (5 min)

    When the average system load (over 5 minutes) exceeds the configured value, an alarm is triggered.

    4

    4

    System Load (15 min)

    When the average system load (over 15 minutes) exceeds the configured value, an alarm is triggered.

    4

    4

    System Location

    Location of the fabric node

    Actual geographical or other location

    unknown

    System Contact

    E-mail address to which the system sends notifications

    E-mail address of actual person

    root <root@localhost>

    Disk Mount Path

    Disk mount path that is to be monitored

    Note:

    This field is disabled if the Monitor All Disks field is selected.

    Actual path, if available

    /

    CPU Max Temp (mC)

    When the temperature exceeds the configured value, an alarm is triggered.

    50000

    50000

    CPU Min Fan (RPM)

    When the CPU fan speed goes below the configured value, an alarm is triggered.

    1000

    1000

    CPU Min Voltage (mV)

    When the CPU voltage goes below the configured value, an alarm is triggered.

    1000

    1000
  4. Select Confirm to apply the SNMP configuration changes to the node, or select Cancel if you do not want to make any changes to the SNMP configuration.

Table 2 shows the configuration parameters for monitoring disk usage.

Table 2: SNMP Configuration Parameters: Monitoring Disk Usage

Monitoring Disk Usage

Parameter: Disk Usage (%)

Default: 5%

When the free disk space is greater than the configured threshold, the trap shown in Figure 1 is generated.

Figure 1: Disk Usage Threshold Is NormalSystem monitoring entry: ID 406, resource space-000c29d796f5, status 1, timestamp 3/27/14 12:25:51, disk usage is normal.

Figure 2 shows the OID details for the trap generated when disk usage is normal.

Figure 2: Trap Details When Disk Usage NormalTwo panels of a software interface showing Trap Details for SNMP traps with Request ID, Community set to public, Error Index and Status at 0, IP 10.205.56.39, Trap Type SNMPv2c, and Variable Bindings with different OIDs and values.

When the free disk space is less than the configured threshold, the trap shown in Figure 3 is generated.

Figure 3: Disk Usage Threshold Exceeds Configured ThresholdLog entry 377 alerts disk space-000c29d796f5 exceeded limits with 63 percent free. Severity level 2 on March 27, 2014, at 11:59:48.

Figure 4 shows the OID details for the trap generated when disk usage exceeds the configured threshold.

Figure 4: Trap Details When DIsk Usage Exceeds Configured ThresholdScreenshots of Trap Details window showing SNMP trap info. Key details: Request ID 1141303069, Community public, no errors, IP 10.205.56.39, SNMPv2c. Variable Bindings differ in OIDs and values. Event: Disk space usage trigger with less than 90 percent free.

Table 3 shows the configuration parameters for monitoring the CPU load average.

Table 3: SNMP Configuration Parameters: Monitoring the CPU Load Average

Monitoring the CPU Load Average (System Load)

Parameter: CPU Load (1 min, 5 min, 15 min)

Default Threshold Value: 4

When the CPU Load Average threshold is less than or equal to the configured threshold limit, the trap shown in Figure 5 is generated:

Figure 5: CPU Load Average Threshold Is NormalCheckbox for selection, ID 379, string space-000c29d796f5, single entry, timestamp 3/27/14 12:00:48 with navigation. CPU load average is normal.

Figure 6 shows the OID details for the trap generated when the CPU load is normal.

Figure 6: Trap Details When CPU Load Average Threshold Is NormalSNMP monitoring tool showing Trap Details with Request ID, Community set to public, Error Index 0, IP 10.205.56.39, SNMPv2c, and Variable Bindings with OIDs.

Figure 7 shows the traps generated when the 15 minute, 5 minute, or 1 minute CPU Load Average threshold is exceeded.

Figure 7: CPU Load Average Threshold – Upper Limit ExceededScreenshot of alert system interface showing high-priority alerts for CPU load exceeding thresholds with alert IDs and timestamps.

Figure 8 shows the OID details for the trap generated when the CPU load 5 minute average exceeds the threshold.

Figure 8: Trap Details When CPU Load 5 Minute Average Exceeds ThresholdTrap details showing SNMP request ID 1861140846, community public, no errors, from IP 10.205.56.39, SNMPv2c. Variable bindings report CPU load trigger with 5-minute load average of 1.14.

Table 4 shows monitoring processes for the Junos Space Network Management Platform.

Table 4: SNMP Configuration Parameters: Monitoring Processes

Monitoring Processes

Parameter: Node Management Agent (NMA)

When the NMA process is up, the trap shown in Figure 9 is generated:

Figure 9: NMA Is UpLog entry with ID 384: space-000c29d796f5, count 1, timestamp 3/27/14 12:10:05, status Process NMA started.

Figure 10 shows the OID details for the trap generated when the NMA process is up.

Figure 10: Trap Details When NMA Is UpScreenshots showing SNMP trap details with fields like Request ID, Community, Error Index, Error Status, IP Address, and Trap Type. Includes Variable Bindings table with OID, Type, and Value. Navigation buttons for viewing traps.

When the NMA process is down, the trap shown in Figure 11 is generated:

Figure 11: NMA is DownRow 382: Identifier space:000c29d796f5; Count 1; Timestamp 3/27/14 12:09:25; Message Process NMA stopped; Red background indicates error or warning.

Figure 12 shows the OID details for the trap generated when the NMA process is down.

Figure 12: Trap Details When NMA is DownTwo screenshots of Trap Details window from a network tool show SNMP trap info with Request ID, community string public, no errors, source IP 10.205.56.39, SNMPv2c, and variable bindings like sysUpTime, NMA stopped, and NMA.

Parameter: Webproxy

When the WebProxy process is up, the trap shown in Figure 13 is generated:

Figure 13: WebProxy Is UpLog entry with checkbox, ID 390, identifier space-000c29d79ef5, count 1, timestamp 3/27/14 12:12:55, message Process WebProxy started.

Figure 14 shows the OID details for the trap generated when the WebProxy process is up.

Figure 14: Trap Details When WebProxy Is UpTwo screenshots of Trap Details windows from a network management system showing SNMP traps with Request ID 1861139988, Community public, Error Index 0, Error Status 0, IP Address 10.205.56.39, and Trap Type SNMPv2c. Includes Variable Bindings with OID, Type, and Value columns featuring uptime, OID numbers, and strings like webproxy started.

When the WebProxy process is down, the trap shown in Figure 15 is generated:

Figure 15: WebProxy Is DownError alert: Process WebProxy stopped. ID 386, identifier space-000c29d796f5, timestamp 3/27/14 12:12:24.

Figure 16 shows the OID details for the trap generated when the WebProxy is down.

Figure 16: Trap Details When WebProxy Is DownTwo SNMP Trap Details windows showing trap info: Request ID 737109873, Community public, Error Index 0, Error Status 0, IP Address 10.205.56.39, Trap Type SNMPv2c, Variable Bindings with OIDs and values like webproxy stopped.

Parameter: JBoss

When the JBoss process is up, the trap shown in Figure 17 is generated:

Figure 17: JBoss Is UpLog entry with checkbox 394, ID space-000c29d79ef5, count 1, timestamp 3/27/14 12:14:46, status Process Jboss started.

Figure 18 shows the OID details for the trap generated when the JBoss process is up.

Figure 18: Trap Details When JBoss Is UpTrap Details for SNMP traps displaying Request ID 1861140020, Community public, IP Address 10.205.56.39, Trap Type SNMPv2c, with Variable Bindings showing OIDs, data types, and values like Jboss started.

When the JBoss process is down, the trap shown in Figure 19 is generated:

Figure 19: JBoss Is DownID 391; space-000c29d796f5; Count 1; Timestamp 3/27/14 12:13:01; Message: Process Jboss stopped; Light red/pink background may indicate an alert.

Figure 20 shows the OID details for the trap generated when JBoss is down.

Figure 20: Trap Details When JBoss Is DownTrap Details window from SNMP tool showing details of traps from device 10.205.56.39 using SNMPv2c. Request ID 737110115, community public, no errors. Variable Bindings show OIDs for Jboss stopped events. Includes Close, Show Raw, prev, and next buttons.

Parameter: Mysql

When the Mysql process is up, the trap shown in Figure 21 is generated:

Figure 21: Mysql Is UpSystem log entry: ID 392, space-000c29d796f5, count 1, timestamp 3/27/14 12:13:07, MySQL process started, navigation controls available.

Figure 22 shows the OID details for the trap generated when the Mysql process is up.

Figure 22: Trap Details When Mysql Is UpTwo screenshots of SNMP trap details from device 10.205.56.39 showing trap type SNMPv2c, including fields like Request ID and Error Status. Variable bindings indicate system uptime and events. Highlighted event shows Myud started.

When the Mysql process is down, the trap shown in Figure 23 is generated:

Figure 23: Mysql Is DownID 398, space-000c29d796f5, status 1, timestamp 3/27/14 12:21:44, message: Process Mysql stopped, red background indicates critical event.

Figure 24 shows the OID details for the trap generated when the Mysql process is down.

Figure 24: Trap Details When Mysql Is DownScreenshots of SNMP monitoring tool showing Trap Details with Request ID 73712741, Community public, no errors, IP 10.205.56.39, Trap Type SNMPv2c, and OIDs with values like MySQL stopped.

Parameter: Postgresql

When the Postgresql process is up, the trap shown in Figure 25 is generated:

Figure 25: Postgresql Is UpLog entry showing number 393 with identifier space-000c29d796f5, count 1, timestamp 3/27/14 12:13:48, message Process Postgresql started.

Figure 26 shows the OID details for the trap generated when the Postgresql process is up.

Figure 26: Trap Details When Postgresql Is UpTwo screenshots of a network monitoring tool showing SNMP trap details from device IP 10.205.56.39. Both show Request ID 1861140052, community string public, error index and status 0, and trap type SNMPv2c. Variable bindings include OIDs with values like system uptime and "PostgreSQL started." Navigation buttons for viewing other traps and raw data are available.

When the Postgresql process is down, the trap shown in Figure 27 is generated:

Figure 27: Postgresql Is DownTable showing a log entry: Event number 389, ID space-000c29d796f5, Priority 1, Date 3/27/14 12:12:53, Message Process Postgresql stopped.

Figure 28 shows the OID details for the trap generated when the Postgresql process is up.

Figure 28: Trap Details When Postgresql Is DownSNMP monitoring tool panels displaying trap details with Request ID 737120205. Both panels show PostgreSQL stopped alert from IP 10.205.56.39 using SNMPv2c. Left shows human-readable OIDs; right shows numeric OIDs.

Parameter: Free swap memory

When the free swap memory is greater than the upper threshold limit, the trap shown in Figure 29 is generated:

Figure 29: Swap Memory Usage Is NormalSystem monitoring log entry with ID 405, resource space-000c29d796f5, normal swap memory usage as of 3/27/14 12:28:43.

Figure 30 shows the OID details for the trap generated when swap memory usage is normal.

Figure 30: Trap Details When Swap Memory Is NormalTrap Details for SNMP messages showing Request ID 1861140788, community string public, Error Index and Status 0, IP 10.205.56.39, SNMPv2c version, and variable bindings with OIDs, types, and values like Swap memory clear.

When the free swap memory is less than the upper threshold limit, the trap shown in Figure 31 is generated:

Figure 31: Swap Memory Usage Threshold Exceeds Upper LimitCritical alert for swap memory usage threshold exceeded logged on 3/27/14 at 12:30:56. System running out of swap space.

Figure 32 shows the OID details for the trap generated when swap memory usage is exceeds upper limit.

Figure 32: Trap Details When Swap Memory Usage Exceeds Upper LimitTrap Details from an SNMP monitoring tool showing Request ID 1314711189, Community public, no errors, IP 10.205.56.39, SNMPv2c, sysUpTime 0 days 00h:00m:00.10s, swap memory alert.

Table 5 shows the configuration parameters for monitoring Junos Space Network Management Platform hardware.

Table 5: SNMP Configuration Parameters: Monitoring Linux Hardware

Monitoring Linux Hardware
Note:

LM-SENSORS-MIB is not supported by the Junos Space Virtual Appliance, but only by the Junos Space Appliance. Therefore the threshold settings of CPU Max Temp (mC), CPU Min Fan (RPM) and CPU Min Voltage (mV) will not trigger any traps in the virtual appliance.

Parameter: CPU min FAN (rpm)

Default Threshold Value: 1500

When the CPU fan speed is greater than the configured threshold (minimum fan speed), the trap shown in Figure 33 is generated:

Figure 33: CPU Fan Speed NormalCheckbox for entry selection, ID 41, label space-0256102011000007, value 1, timestamp 3/27/14 12:44:58, status CPU fan is normal.

Figure 34 shows the OID details for the trap generated when CPU fan speed is normal.

Figure 34: Trap Details When CPU Fan Speed Is NormalTrap Details interface for SNMP traps showing Request ID, Community, Error Index, Error Status, IP Address, Trap Type, and Variable Bindings. The second screenshot notes CPU fan clear.

When the CPU fan speed is less than the configured threshold (minimum fan speed), the trap shown in Figure 35 is generated:

Figure 35: CPU Fan Speed Is Below the Configured ThresholdLog entry with row number 280 reporting CPU fan speed issue. Identifier space-025604201200014. Timestamp 3/28/14 12:33:16. RPM 5625.

Figure 36 shows the OID details for the trap generated when CPU fan speed lower than the configured threshold.

Figure 36: Trap Details When CPU Fan Speed Is Below the Configured ThresholdTrap Details window from SNMP tool showing community public, request ID 708519518, no errors, IP 10.205.56.39, SNMPv2c, variable bindings with OIDs and values.

Parameter: CPU min Voltage (mV)

When the CPU voltage is greater than the configured value, the trap shown in Figure 37 is generated:

Figure 37: CPU Voltage NormalRow 42 with ID space-025610201100007 shows count 1, timestamp 3/27/14 12:44:58, status CPU voltage is normal. Navigation links present.

Figure 38 shows the OID details for the trap generated when CPU voltage is normal.

Figure 38: Trap Details When CPU Voltage Is NormalScreenshots of Trap Details window from a network tool showing SNMP trap info: Request ID 1314711267, Community public, Error Status 0, IP 10.205.56.39, SNMPv2c, data includes Time tick 0 days 00:00:00.11, CPU voltage clear, Gauge value 3328.

Default Threshold Value: 1000

When the CPU voltage is lower than the configured value, the trap shown in Figure 39 is generated:

Figure 39: CPU Voltage Is Lower Than Configured ThresholdID 60 space-025610201100007 CPU voltage too low mV 3328 at 3/27/14 12:58:20 Navigation options available

Figure 40 shows the OID details for the trap generated when CPU voltage is lower than the configured threshold.

Figure 40: Trap Details When CPU Voltage Is Lower Than Configured ThresholdSNMP Trap Details window showing request ID, community string, error status, IP address, trap type, and variable bindings including sysUpTime.0 and CPU voltage trigger.

Parameter: CPU Temperature

When the CPU temperature is lower than the configured threshold, the trap shown in Figure 41 is generated:

Figure 41: CPU Temperature NormalLog entry showing ID 260 for space-0256042012000014 with status 4 recorded on 3/28/14 at 12:33:16. CPU temperature is normal.

Figure 42 shows the OID details for the trap generated when CPU temperature is normal.

Figure 42: Trap Details When CPU Temperature Is NormalTrap Details window showing SNMP trap alerts with Request ID 737109630, Community set to public, no errors, IP Address 10.205.56.39, Trap Type SNMPv2c. Variable Bindings include TimeTick uptime 0 days 00h 00m 01.12s, String CPU temperature clear, and Gauge 47500. Navigation buttons Close, Show Raw, prev, and next.

When the CPU temperature exceeds the configured threshold, the trap shown in Figure 43 is generated:

Figure 43: CPU Temperature Exceeds The Configured ThresholdLog entry 40: Space ID space-025610201100007, Severity 1, Timestamp 3/27/14 12:44:58, Message: CPU temperature too high mC 51000.

Figure 44 shows the OID details for the trap generated when CPU temperature is higher than the configured threshold.

Figure 44: Trap Details When CPU Temperature Exceeds The Configured ThresholdTwo network monitoring windows display SNMP traps with details like Request ID, community set to public, IP 10.205.56.39, SNMPv2c type, and variable bindings.

Table 6 shows the configuration parameters for monitoring fabric health.

Table 6: SNMP Configuration Parameters: Monitoring Fabric Health
Monitoring Fabric Health

Parameter: Junos Space Node

When a Junos Space node is up, the trap shown in Figure 45 is generated:

Figure 45: Junos Space Node is UpTable entry with checkbox, ID 642, label space-000c294ed8bc, status 1, timestamp 6/14/17 19:54:41, and description The space node referred by jnxSpaceNodeIP is currently up.

Figure 46 shows the OID details for the trap generated when a Junos Space node is up.

Figure 46: Trap Details When Junos Space Node Is UpSNMP trap details interface with two panels showing Request ID 987944205, IP 192.168.26.179, Trap Type SNMPv2c, and Variable Bindings.

When a Junos Space node is down, the trap shown in Figure 47 is generated:

Figure 47: Junos Space Node is DownTable with a checkbox, number 204, string space-000c295d757a, number 1, date 6/23/17 22:45:29, message The space node referred by jnxSpaceNodeIP is currently down.

Figure 48 shows the OID details for the trap generated when a Junos Space node is down.

Figure 48: Trap Details When Junos Space Node is DownTwo panels display SNMP trap details. Left panel shows OIDs like sysUpTime and reports values such as uptime 0 days 00h:00m:00s and IP address 10.155.73.10. Right panel includes similar OIDs and trap OID jnxSpacePlatformTraps with same uptime and IP address.

Parameter: Junos Space Node Removal

When a Junos Space node is removed from the fabric, the trap shown in Figure 49 is generated:

Figure 49: Junos Space Node Is RemovedSystem log entry: Unchecked checkbox, ID 1076, Reference space-000c2990f597, Value 1, Timestamp 6/21/17 15:33:04, Message: The space node referred by jnxSpaceNodeIP is removed from fabric.

Figure 50 shows the OID details for the trap generated when a Junos Space node is removed..

Figure 50: Trap Details When Junos Space Node Is RemovedSNMP monitoring tool showing two panels of Trap Details with Request IDs 201599757 and 1065732676 from devices at IPs 192.168.26.173 and 192.168.26.179, detailing trap types, community names, and variable bindings.

Parameter: JBoss Multi-Primary Detected

When there is more than one JBoss AppLogic primary node detected in the cluster, the trap shown in Figure 51 is generated:

Figure 51: JBoss Multi-Primary DetectedTable with checkbox, ID 846, space-000c294ed8bc, status 1, timestamp 6/15/17 14:58:43, message Multi master issue observed in cluster.

Figure 52 shows the OID details for the trap generated when there is more than one JBoss AppLogic primary node detected in the cluster.

Figure 52: Trap Details When JBoss Multi-Primary Is DetectedSNMP trap details for two devices with IPs 192.168.26.173 and 192.168.26.179. Both relate to Fabric Health Monitoring and JBoss Cluster status.

Parameter: VIP Bind Issue Detected in JBoss Node(s)

When VIP Bind issue is detected in JBoss node(s), the trap shown in Figure 53 is generated:

Figure 53: VIP Bind Issue Detected In JBoss Node(s)Log entry 217: VIP bind issue detected in JBoss nodes on June 14, 2017, severity 7, space name space-000:294edb9.

Figure 54 shows the OID details for the trap generated when VIP Bind issue is detected in JBoss node(s).

Figure 54: Trap Details When VIP Bind Issue Is Detected In JBoss Node(s)SNMP trap details with request ID, error status 0, community public, IP 192.168.26.173, SNMPv2c. Variables: sysUpTime, Fabric Health Monitoring, Space Node Web IP, Problem Detected yes. Navigation buttons for traps.

Parameter: Fabric Monitoring Process Inactive

When fabric monitoring process is inactive, the trap shown in Figure 55 is generated:

Figure 55: Fabric Monitoring Process InactiveID 706 for space-000c29555936; status 1; timestamp 6/20/17 18:59:08; message: Fabric monitoring process inactive for node jb1.

Figure 56 shows the OID details for the trap generated when fabric monitoring process is inactive.

Figure 56: Trap Details When Fabric Monitoring Process Is InactiveTwo panels of SNMP trap details with Request IDs 422199000 and 1045592590, IPs 192.168.26.206 and 192.168.26.173, Trap Type SNMPv2c, and variable bindings for network monitoring.

Parameter: Tables Exceed Size Limit

When one or more tables in the MySQL database exceed the size limit of 10 GB, the trap shown in Figure 57 is generated:

Figure 57: Tables Exceed Size LimitCheckbox next to entry ID 838 with name space-000c294ed8bc. Alert: Database table size exceeds 10GB. Timestamp 6/15/17 14:41:36.

Figure 58 shows the OID details for the trap generated when one or more tables in the MySQL database exceed the size limit of 10 GB.

Figure 58: Trap Details When Tables Exceed Size LimitSNMP trap details for devices with IPs 192.168.26.173 and 192.168.26.179. Both show system uptime and values for Fabric Health Monitoring and MySQL Table Size.

Parameter: Device Session Count Exceeds Threshold Limit

When the device session count exceeds the threshold limit, the trap shown in Figure 59 is generated:

Figure 59: Device Session Count Exceeds Threshold LimitLog entry: ID 844. Node space-00c29118aa47. Session count 1. Timestamp 6/15/17 14:58:26. Device session count exceeded threshold in node jb2.

Figure 60 shows the OID details for the trap generated when the device session count exceeds the threshold limit.

Figure 60: Trap Details When Device Session Count Exceeds Threshold LimitTwo SNMP Trap Details panels showing network trap info: Request ID 110171107, Community public, IP Address 192.168.26.237, Trap Type SNMPv2c, Error Index 0, Error Status 0. Variable Bindings list OIDs, data types, and values for Fabric Health Monitoring and Device Connection.

Parameter: HPROF Availability

When Heap and CPU Profiling Agent (HPROF) files are detected on a Junos Space node, the trap shown in Figure 61 is generated:

Figure 61: HPROF AvailabilityEvent ID 5226 with Warning severity on 6/15/17 at 15:40:29 from space-000c294ed8bc IP 192.168.26.173. JBoss Hprof detected.

Figure 62 shows the OID details for the trap generated when HPROF files are detected on a Junos Space node.

Figure 62: Trap Details When HPROF Files Are AvailableSNMP trap details from device 192.168.26.173 showing request ID, community as public, no errors, SNMPv2c, and variable bindings with uptime and process data.

Parameter: JGroup Membership Issue Detected

When the removal of a JBoss node from JGroup is detected in the cluster, the trap shown in Figure 63 is generated:

Figure 63: JGroup Membership Issue DetectedLog entry with ID 644 for space-0002911aa47. Count 1. Timestamp 6/14/17 19:56:49. Issue: JGroup Membership issue detected.

Figure 64 shows the OID details for the trap generated when the removal of a JBoss node from JGroup is detected in the cluster.

Figure 64: Trap Details When JGroup Membership Issue DetectedSNMP trap details with two panels: Left panel shows Request ID 1484481523 from IP 192.168.26.171 with uptime 0:03:08.62 and issues like Fabric Health Monitoring. Right panel shows Request ID 730604150 from IP 192.168.26.179 with uptime 7:22:41.53 and similar issues.

Parameter: MySQL In Out Of Sync State

When a MySQL database synchronization issue is detected between nodes running the MySQL database, the trap shown in Figure 65 is generated:

Figure 65: MySQL In Out Of Sync StateID 343; Resource space-00506938252; Status 1; Timestamp 12/11/17 11:09:55; MySQL database out of sync in node DB1.

Figure 66 shows the OID details for the trap generated when a MySQL database synchronization issue is detected between nodes running the MySQL database.

Figure 66: Trap Details When MySQL Is In Out Of Sync StateTrap Details panels from SNMP tool show Request ID 1624086348, SNMPv2c traps from IP 192.168.26.20. Left panel has human-readable OIDs like sysUpTime.0, right panel has numeric OIDs like 1.3.6.1.2.1.1.3.0.

Parameter: File Intrusion Detection Monitoring

When changes in files or file permissions are detected, the trap shown in Figure 67 is generated.

Figure 67: File Intrusion Detection MonitoringTable with checkbox 199, string space-000c29c82c4a, number 1, timestamp 12/16/17 18:26:17, message Aide Filesystem changes detected in node jboss.

Figure 68 shows the OID details for the trap generated when file or file permission changes are detected in the system.

Figure 68: Trap Details for File Intrusion Detection MonitoringSNMP trap details for device 192.168.26.35 with SNMPv2c, Request ID 164085168, community 'public.' Shows OIDs, device uptime 0 days 01h:08m:05.10s, related to Fabric Health Monitoring and Audit File Changes. Device name jboss-35. Includes navigation and 'Show Raw' buttons.

Parameter: Audit Logs Forwarding Failed

When the system fails to forward audit logs to the configured system log server, the trap shown in Figure 69 is generated:

Figure 69: Audit Logs Forwarding FailedLog entry with ID 622; space identifier space-000294ed8bc; status code 27; timestamp 6/14/17 19:56:17; message Audit Log Forwarding process failed.

Figure 70 shows the OID details for the trap generated when the system fails to forward audit logs to the configured system log server.

Figure 70: Trap Details When Audit Logs Forwarding FailsSNMP trap details with two panels: Left panel shows Fabric Health Monitoring and Audit Log Forwarding OIDs; right panel indicates Problem Detected with value yes. Use navigation buttons to switch traps or view raw data.

Parameter: One Or More Expected Process Are Inactive

Junos Space monitors critical process like JBoss. If any of these expected processes are inactive, the trap shown in Figure 71 is generated:

Figure 71: One or More Expected Processes Are InactiveLog entry with ID 104: space-000c295d757a has status 2. Timestamp: 6/23/17 18:58:03. Issue: Inactive process on Juniper_Slave node.

Figure 72 shows the OID details for the trap generated when one or more expected processes are inactive.

Figure 72: Trap Details When One or More Expected Processes Are InactiveSNMP trap details with Request ID 2019887467, source IP 192.168.26.249, and SNMPv2c. Includes OID, data types, and values like Fabric Health Monitoring. Buttons: Close, Show Raw, prev, next.
Note:

LM-SENSORS-MIB is not supported by the Junos Space virtual appliance, but only by the Junos Space Appliance. Therefore the threshold settings of CPU Max Temp (mC), CPU Min Fan (RPM) and CPU Min Voltage (mV) will not trigger any traps in the virtual appliance.

Note:

Junos Space supports RAID-related traps on a Junos Space appliance. The following is a sample trap:

Starting SNMP Monitoring on Fabric Nodes

To start SNMP monitoring on one or more fabric nodes:

  1. Select Network Management Platform > Administration > Fabric.

    The Fabric page appears.

  2. Select the check box for each fabric node on which you want to start SNMP monitoring.
  3. From the Actions menu, select SNMP Start.

    The Confirm Start SNMP Agent dialog box is displayed.

  4. Click Yes.

    Junos Space begins SNMP monitoring on the selected fabric nodes.

    Note:

    This process might take a while.

  5. To view the status of SNMP monitoring on the selected fabric nodes, select Network Monitoring > Node List.

    The Network Monitoring > Node List page appears.

  6. Select the node on which you started the SNMP monitoring.

    The Junos Space node is represented as space-<number>.

    Figure 73 shows a sample view of network monitoring details for the selected fabric node.

    Figure 73: Network Monitoring Details for the Selected Fabric NodeNetwork monitoring tool interface displaying node name space-0256042012000017 status active availability 94.751 percentage recent events and outages.

    Under Notification / Recent Events on the right of the Node List page, you see the results of the SNMP monitoring operation.

Stopping SNMP Monitoring on Fabric Nodes

To stop SNMP monitoring on one or more fabric nodes:

  1. Select Network Management Platform > Administration > Fabric.

    The Fabric page appears.

  2. Select the check box for each fabric node on which you want to stop SNMP monitoring.
  3. From the Actions menu, select SNMP Stop.

    The Confirm Stop SNMP Agent dialog box is displayed.

  4. Click Yes.

    Junos Space stops SNMP monitoring on the selected fabric nodes.

Restarting SNMP Monitoring on Fabric Nodes

To restart SNMP monitoring on one or more fabric nodes:

  1. Select Network Management Platform > Administration > Fabric.

    The Fabric page appears.

  2. Select the check box for each fabric node on which you want to restart SNMP monitoring.
  3. From the Actions menu, select SNMP Restart.

    The Confirm Restart SNMP Agent dialog box is displayed.

  4. Click Yes.

    Junos Space restarts SNMP monitoring on the selected fabric nodes.

Adding a Third-Party SNMP V1 or V2c Manager on a Fabric Node

To add a third-party SNMP V1 or V2c manager on a fabric node:

  1. Select Network Management Platform > Administration > Fabric > SNMP Manager.

    The SNMP Manager page appears.

  2. Click the Add SNMP Manager icon.

    The Add 3rd Party SNMP Manager dialog box is displayed.

  3. In the Manager IP field, enter the SNMP manager IP address.
    Note:

    • Depending on whether the Junos Space fabric is configured with only IPv4 addresses or both IPv4 and IPv6 addresses, Junos Space Platform allows you to enter an IPv4 address or either an IPv4 or IPv6 address respectively for the SNMP Manager.

    • The IPv4 and IPv6 addresses that you use must be valid addresses. Refer to http://www.iana.org/assignments/ipv4-address-space for the list of restricted IPv4 addresses and http://www.iana.org/assignments/ipv6-address-space for the list of restricted IPv6 addresses.

  4. In the Version field, select the SNMP version (V1 or V2c) .
  5. In the Community field, enter the community string.

    Any alphanumeric string (up to 254 characters) is acceptable, including spaces and symbols.

  6. Click OK.

    The newly added SNMP v1 or v2c Manager is displayed on the SNMP Manager page.

Adding a Third-Party SNMP V3 Manager on a Fabric Node

To add a third-party SNMP V3 manager on a fabric node:

  1. Select Platform > Administration > Fabric > SNMP Manager.

    The SNMP Manager page appears.

  2. Click the Add icon.

    The Add 3rd Party SNMP Manager dialog box displays.

  3. In the Manager IP field, enter the SNMP manager IP address.
    Note:

    • Depending on whether the Junos Space fabric is configured with only IPv4 addresses or both IPv4 and IPv6 addresses, Junos Space Platform allows you to enter an IPv4 address or either an IPv4 or IPv6 address respectively for the SNMP Manager.

    • The IPv4 and IPv6 addresses that you use must be valid addresses. Refer to http://www.iana.org/assignments/ipv4-address-space for the list of restricted IPv4 addresses and http://www.iana.org/assignments/ipv6-address-space for the list of restricted IPv6 addresses.

  4. In the Version field, select V3.
  5. In the User Name field, type the user name.

    The user name can contain a maximum of 32 alphanumeric characters including spaces and symbols.

  6. In the Authentication Type field, enter the authentication type (MD5 or SHA).
  7. In the Authentication Password field, enter the authentication password.

    Click the red information icon next to the Authentication Password field for information on the password rules.

  8. In the Confirm Authentication password, enter the authentication password again to confirm the password.
  9. From the Security Level list, select the security level:

    • noAuthNoPriv—Do not specify an authentication or privacy password.

    • authNoPriv—Specify only an authentication password.

    • authPriv—Specify both authentication and privacy passwords.

  10. In the Privacy Type field, enter the privacy type (AES or DES).
  11. In the Privacy Password field, enter the privacy password.

    Click the red information icon next to the Authentication Password field for information on the password rules.

  12. In the Confirm Privacy password field, enter the privacy password again to confirm the password.
  13. Click OK.

    The newly added SNMP Manager entry is displayed on the SNMP Manager page.

Note:

The trap settings for the SNMPv3 manager are not automatically updated in Network Monitoring. Therefore, to ensure that the Network Monitoring receives the traps from Junos Space, you must add the same settings manually in the /opt/opennms/etc/trapd-configuration.xml file. Table 7 displays the mapping between the parameters in the /opt/opennms/etc/trapd-configuration.xml file and the fields in the Add 3rd Party SNMP Manager page.

The following is a sample configuration in the /opt/opennms/etc/trapd-configuration.xml file.
Table 7: Mapping of SNMP V3 Settings

Parameter in trapd-configuration.xml File

Field in Add 3rd Party SNMP Manager Page

security-name

User Name

auth-passphrase

Authentication Password

privacy-passphrase

Privacy Password

privacy-protocol

Privacy Type

Deleting a Third-Party SNMP Manager from a Fabric Node

To delete a third-party SNMP manager configuration from a fabric node:

  1. Select Platform > Administration > Fabric > SNMP Manager.

    The SNMP Manager page appears.

  2. Select the SNMP manager configuration that you want to remove.
  3. Click the Delete SNMP Manager icon.
  4. To confirm the deletion of the SNMP manager, click Yes.

    The deleted SNMP manager is removed from the SNMP Manager page.

Installing StorMan RPM for Monitor RAID Functionality

To install StorMan RPM:

From Junos Space Platform CLI, run the following command:

Related Documentation