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.

    Note:

    This field is applicable only to the Junos Space hardware appliances (JA2500).

    50000

    50000

    CPU Min Fan (RPM)

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

    Note:

    This field is applicable only to the Junos Space hardware appliances (JA2500).

    1000

    1000

    CPU Min Voltage (mV)

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

    Note:

    This field is applicable only to the Junos Space hardware appliances (JA2500).

    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 log entry showing ID 406, identifier space-000c29d796f5, count 1, timestamp 3/27/14 12:25:51, navigation buttons, and status 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 display SNMP Trap Details, highlighting Request ID, Community set to public, Error Index and Status as 0, IP Address 10.205.56.39, Trap Type SNMPv2c, and Variable Bindings with metrics like system uptime and disk space usage.

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 showing disk usage warning; 63 percent free space, below 95 percent threshold. Timestamp 3/27/14 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 ThresholdTrap Details windows showing SNMP traps with Request ID 1141303069, IP 10.205.56.39, and disk space usage trigger under 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 NormalEntry 379: space-000c29d796f5, count 1, logged at 3/27/14 12:00:48. Status: 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 NormalScreenshots of Trap Details window showing SNMP trap info: Request ID, Community public, Error Status 0, IP 10.205.56.39, SNMPv2c, 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 a monitoring system interface showing alerts for CPU load average thresholds exceeded with alert IDs, server instance, severity levels, timestamps, and navigation links.

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 ThresholdSNMP trap details showing request ID 1861140846, community string public, no errors, IP 10.205.56.39, SNMPv2c version, and variable bindings with OIDs and values indicating a CPU load issue with a message 5 min Load Average too high 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 UpCheckbox to select row 384; ID space-000c29d796f5; Count 1; Timestamp 3/27/14 12:10:05; Status: Process NMA started; Navigation symbols present.

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

Figure 10: Trap Details When NMA Is UpSNMP trap details with trap type SNMPv2c from IP 10.205.56.39. Fields include Request ID, Community, Error Status, and Variable Bindings with OIDs and values.

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

Figure 11: NMA is DownLog entry 382 with ID space:000c29d796f5 shows Process NMA stopped on 3/27/14 at 12:09:25. Red border indicates a critical event.

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

Figure 12: Trap Details When NMA is DownNetwork monitoring tool screenshots showing SNMP trap details: Trap Details window with Request ID 737117913, Community public, IP 10.205.56.39, SNMP version SNMPv2c, Error Index and Status 0. Variable Bindings table includes sysUpTime, OID values, Type, and Value with examples NMA stopped and 103.

Parameter: Webproxy

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

Figure 13: WebProxy Is UpSystem log entry with ID 390: space-000c29d79ef5 at 3/27/14 12:12:55. WebProxy process started.

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

Figure 14: Trap Details When WebProxy Is UpScreenshots of SNMP Trap Details showing Request ID 1861139988, Community public, Error Status 0, IP 10.205.56.39, and Trap Type SNMPv2c. Displays Variable Bindings table with OIDs and values like system uptime and web proxy status. Includes options to close, show raw data, and navigate traps.

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

Figure 15: WebProxy Is DownLog entry showing ID 386, process space-000c29d796f5, status 1, timestamp 3/27/14 12:12:24, and message Process WebProxy stopped.

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

Figure 16: Trap Details When WebProxy Is DownTwo screenshots compare SNMP trap details, highlighting OID formatting differences. Both show a "webproxy stopped" event with uptime of 15.70 seconds.

Parameter: JBoss

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

Figure 17: JBoss Is UpCheckbox with ID 394 and label space-000c29d796f5 shows status Process Jboss started on 3/27/14 12:14:46.

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 window in SNMP monitoring tool displaying SNMP traps. Request ID: 1861140020, Community: public, Error Index: 0, Error Status: 0. Source IP: 10.205.56.39, Trap Type: SNMPv2c. Variable Bindings show OIDs in numeric and full numeric formats, including sysUpTime: 0 days 00h:00m:06.29s and status info like Jboss started.

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

Figure 19: JBoss Is DownCheckbox followed by 391 space-000c29d796f5 1 date 3/27/14 12:13:01 with arrows and Process Jboss stopped.

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

Figure 20: Trap Details When JBoss Is DownSNMP trap details showing Request ID, community string public, no errors, IP 10.205.56.39, SNMPv2c, and Jboss process stopped with specific OID and values.

Parameter: Mysql

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

Figure 21: Mysql Is UpLog entry showing ID 392; space identifier space-000c29d796f5; count 1; timestamp 3/27/14 12:13:07; description Process Mysql started; navigation controls.

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 a network management interface showing SNMP trap details, including Request ID, Community, Error Index, Error Status, IP Address, Trap Type SNMPv2c, and Variable Bindings with OID, Type, and Value.

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

Figure 23: Mysql Is DownLog interface showing entry 398: space-000c29d796f5, MySQL process stopped on 3/27/14 at 12:21:44, indicating error.

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

Figure 24: Trap Details When Mysql Is DownTwo screenshots of Trap Details windows showing SNMP network trap info: Request ID, Error Index, Error Status, Community, IP Address, Trap Type SNMPv2c, and Variable Bindings with OID, Type, and Value like uptime and MySQL status.

Parameter: Postgresql

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

Figure 25: Postgresql Is UpLog entry showing row number 393; space 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 Trap Details windows showing SNMPv2c traps with Request ID 1861140052 and IP 10.205.56.39. Variable Bindings list Postgreql started message with OID, Type, and Value columns.

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

Figure 27: Postgresql Is DownLog entry with ID 389: Process space-000c29d796f5 stopped. Timestamp 3/27/14 12:12:53. Navigation links present.

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

Figure 28: Trap Details When Postgresql Is DownSNMP Trap Details with Request ID 737120205 show community 'public', no errors, IP 10.205.56.39, SNMPv2c. Variable Bindings indicate PostgreSQL stopped.

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 405 with resource ID space-000c29d796f5, timestamp 3/27/14 12:28:43, and status message Swap memory usage is normal.

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 interface displaying SNMP network event. Request ID 1861140788, community public, IP 10.205.56.39, SNMPv2c trap type, variable bindings differ between panels indicating swap memory events.

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: Swap memory usage threshold exceeded. ID 410, Space space-000c29d796f5, Count 1, Timestamp 3/27/14 12:30:56.

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 LimitTwo panels of SNMP Trap Details showing Request ID, SNMP community string as public, Error Index and Status as 0, IP Address 10.205.56.39, Trap Type SNMPv2c, and variable bindings with sysUpTime and OID values indicating a swap memory issue.

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 NormalRow 41 log entry: ID space-025610201100007, Value 1, Timestamp 3/27/14 12:44:58, 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 NormalTwo screenshots of Trap Details window from an SNMP monitoring tool with Request ID, Community string, Error Index, Error Status, IP Address, SNMP version, and Variable Bindings table showing OIDs and values.

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 280: Identifier space-0256042012000014, 1 occurrence, timestamp 3/28/14 12:33:16. CPU fan speed warning; 5625 RPM.

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 ThresholdScreenshots of Trap Details window in SNMP tool showing: Community set to public, Request ID 709615918, Error Index 0, Error Status 0, IP Address 10.205.56.39, Trap Type SNMPv2c, and 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 NormalLog entry 42: space-0256102011000007, value 1, timestamp 3/27/14 12:44:58, CPU voltage is normal.

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

Figure 38: Trap Details When CPU Voltage Is NormalNetwork management system interface showing SNMP trap details with request ID, community, error index, error status, and IP address. Variable bindings section lists OIDs, types, and values like CPU voltage clear. Navigation with Show Raw, prev, and next buttons.

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 ThresholdCPU voltage warning: Log entry 60 with identifier space-025610201100007 shows CPU voltage too low at 3328 mV on 3/27/14 12:58:20.

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 ThresholdTrap Details window from an SNMP monitoring tool showing SNMP trap info with fields like Request ID, Community, Error Index, Error Status, IP Address, Trap Type, and Variable Bindings listing OIDs, types, and values. Navigation buttons allow viewing raw data and navigating traps.

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 at 3/28/14 12:33:16 with message 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 traps with fields: Request ID 737109630, Community public, Error Index 0, Error Status 0, IP Address 10.205.56.39, and Trap Type SNMPv2c. Variable Bindings include sysUpTime.0 and CPU temperature clear. Navigation buttons: prev, next, and Show Raw.

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: High CPU temperature alert at 3/27/14 12:44:58. Severity 1. Temperature 51000 mC.

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 ThresholdTrap Details window from SNMP tool showing request ID, community string 'public', error index 0, error status 0, IP 10.205.56.39, trap type SNMPv2c, and variable bindings with OIDs.

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 UpUnchecked checkbox, ID 642, Node space-000c294ed8bc, Status 1, Timestamp 6/14/17 19:54:41, Node is 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 UpTrap details from SNMP monitoring tool showing request ID 987944205, community public, IP 192.168.26.179, trap type SNMPv2c, with variable bindings and symbolic names.

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

Figure 47: Junos Space Node is DownStatus log entry with ID 204 indicating space node space-000c295d757a is down as of 6/23/17 22:45:29.

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 DownSNMP trap details with Request ID, Community, IP Address, Trap Type, OIDs, and Variable Bindings for network monitoring.

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 RemovedLog entry with checkbox, ID 1076, space ID space-000c2990f597, status 1, timestamp 6/21/17 15:33:04, noting space node removal 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 traps from devices 192.168.26.173 and 192.168.26.179, both with status "Space node removed successful".

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 DetectedID 846: Multi-master issue observed in cluster on 6/15/17 at 14:58:43.

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 DetectedTwo panels displaying SNMP trap details with request IDs 1056642132 and 977942577, showing IP addresses, trap types, and variable bindings like uptime and module 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)Checkbox, number 217, code space-000:294edb9c, number 7, date 6/14/17 14:58:18, message VIP bind issue detected in Jboss nodes.

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 showing Request ID, Error Index 0, Error Status 0, Community public, IP 192.168.26.173, SNMPv2c, and Variable Bindings like sysUpTime and Problem Detected yes.

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

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

Figure 55: VIP Bind Issue Detected In Database Node(s)Alert log entry with ID 463: space-000c294ed8bc, severity 3, on 6/14/17 at 17:02. VIP bind issue detected in Database Nodes.

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

Figure 56: Trap Details When VIP Bind Issue Is Detected In Database Node(s)Two SNMP trap details windows show network event info. Left window: Request ID 1700258359, IP 192.168.26.173, Trap Type SNMPv2c. Right window: Request ID 573482564, IP 192.168.26.179, Trap Type SNMPv2c. Both have options to close, show raw data, and navigate traps.

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

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

Figure 57: VIP Bind Issue Detected In FMPM Node(s)Checkbox, ID 394, Reference space-000c294ed8bc, Count 1, Timestamp 6/14/17 16:39:06, VIP bind issue detected in FMPM Nodes.

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

Figure 58: Trap Details When VIP Bind Issue Is Detected In FMPM Node(s)Two panels of SNMP trap details from network devices with IPs 192.168.26.173 and 192.168.26.179. Both use SNMPv2c version and have no errors. Left panel shows OIDs for device uptime, fabric health, and node VIP. Right panel shows OIDs for sysUpTime, platform traps, fabric health, and node VIP issue detected.

Parameter: Fabric Monitoring Process Inactive

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

Figure 59: Fabric Monitoring Process InactiveCheckbox for selection, ID 706, label space-000c29555936, status 1, timestamp 6/20/17 18:59:08, alert Fabric monitoring process inactive for node jb1.

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

Figure 60: Trap Details When Fabric Monitoring Process Is InactiveSNMP trap details for two devices with IPs 192.168.26.206 and 192.168.26.173 showing uptime, health monitoring, and specific event identifiers.

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 61 is generated:

Figure 61: Tables Exceed Size LimitCheckbox for entry 838; space name space-000c294ed8bc; count 1; timestamp 6/15/17 14:41:36; warning: database table size exceeds 10GB.

Figure 62 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 62: Trap Details When Tables Exceed Size LimitSNMP trap details for devices with IPs 192.168.26.173 and 192.168.26.179 showing request IDs, community, trap type, and variable bindings related to 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 63 is generated:

Figure 63: Device Session Count Exceeds Threshold LimitLog entry with ID 844 from space-00c29118aa47 on 6/15/17 at 14:58:26 shows device session count exceeded threshold in node jb2.

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

Figure 64: Trap Details When Device Session Count Exceeds Threshold LimitSNMP trap interface displaying trap details for request ID 110117107 from IP 192.168.26.237 with error status 0 and community string public. Variables include sysUpTime at 7 hours 32 minutes, Fabric Health Monitoring, Device Connection 1, and ib1. Navigation options present.

Parameter: HPROF Availability

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

Figure 65: HPROF AvailabilityMonitoring interface screenshot showing Event ID 5226 with a Warning severity. Occurred on 6/15/17 at 15:40:29 from system space-000c294ed8bc with IP 192.168.26.173. Event description is related to JbossHprofDetected. Includes a link to edit notifications.

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

Figure 66: Trap Details When HPROF Files Are AvailableSNMP trap details from device 192.168.26.173. Both panels show SNMPv2c traps with community public. Key info: sysUpTime, snmpTrapOID, and jnxSpaceNode IP, app module, process, category, problem status, and node name. Different Request ID and sysUpTime values indicate separate events.

Parameter: JGroup Membership Issue Detected

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

Figure 67: JGroup Membership Issue DetectedCheckbox with ID 644, code space-0002911aa47, number 1, timestamp 6/14/17 19:56:49, and message Jgroup Membership issue detected.

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

Figure 68: Trap Details When JGroup Membership Issue DetectedTwo SNMP trap panels showing details for IPs 192.168.26.171 and 192.168.26.179. Both report Fabric Health Monitoring and Cluster Issue. The left panel notes JBoss node ib2. The right panel indicates Problem Detected set to yes. SNMPv2c version used, with no request errors.

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 69 is generated:

Figure 69: MySQL In Out Of Sync StateRow 343 MySQL database out of sync in node DB1 on 12/11/17 11:09:55 with space ID space-00506938252 status 1.

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

Figure 70: Trap Details When MySQL Is In Out Of Sync StateTwo panels showing SNMP Trap Details with IP 192.168.26.20; left panel has human-readable OIDs, right panel has numeric OIDs.

Parameter: File Intrusion Detection Monitoring

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

Figure 71: File Intrusion Detection MonitoringID 199; Node space-000c29c82c4a; Count 1; Timestamp 12/16/17 18:26:17; Filesystem changes detected in node jboss.

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

Figure 72: Trap Details for File Intrusion Detection MonitoringTwo panels show SNMP trap details for IP 192.168.26.35 comparing human-readable names and numeric OIDs.

Parameter: Audit Logs Forwarding Failed

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

Figure 73: Audit Logs Forwarding FailedLog entry 622 for space-000294ed8bc on 6/14/17 at 19:56:17 shows status 27; Audit Log Forwarding process failed.

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

Figure 74: Trap Details When Audit Logs Forwarding FailsSNMP monitoring tool showing Trap Details with Request IDs 532070112 and 390622533. Includes community string public, device IP 192.168.26.173, SNMPv2c trap type, and variable bindings like sysUpTime.0 and snmpTrapOID.0. Navigation buttons for trap browsing and a Show Raw option are present.

Parameter: One Or More Expected Process Are Inactive

Junos Space monitors critical process like JBoss, MySQL, Apache Web Proxy, OpenNMS and PostgreSQL. If any of these expected processes are inactive, the trap shown in Figure 75 is generated:

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

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

Figure 76: Trap Details When One or More Expected Processes Are InactiveNetwork monitoring tool panels showing SNMP trap details with Request ID 2019887467, community string public, IP 192.168.26.249, and SNMPv2c. Left panel includes OIDs for Fabric Health Monitoring and Juniper_Slave; right panel includes sysUpTime.0 and jnxSpaceNodeName. Navigation buttons for trap details.

Parameter: One or More Expected Processes Are Inactive On Dedicated FMPM Nodes

When one or more expected processes are inactive on dedicated FMPM nodes, the trap shown in Figure 77 is generated:

Figure 77: One or More Expected Processes Are Inactive On Dedicated FMPM NodesLog entry with ID 218: Inactive process in node jb2 at 6/14/17 14:57:48. Space ID: space-000c29118a47.

Figure 78 shows the OID details for the trap generated when one or more expected process are inactive on dedicated FMPM nodes.

Figure 78: Trap Details When One or More Expected Processes Are Inactive On Dedicated FMPM NodesSNMP monitoring tool showing Trap Details with Request ID, Community set to public, IP 192.168.26.171, SNMPv2c Trap Type, and Variable Bindings displaying device uptime and fabric health data.
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 79 shows a sample view of network monitoring details for the selected fabric node.

    Figure 79: Network Monitoring Details for the Selected Fabric NodeScreenshot of a network monitoring tool showing node space-0256042012000017 with 94.751% availability, IPs 10.205.56.40 and 10.205.57.40, and recent events.

    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

Download the StorMan RPM package from https://github.com/Juniper/open-media-flow-controller/blob/master/mfc/nokeena/src/base_os/linux_el/el6/arch_x86_64/packages/StorMan-7.31-18856.x86_64.rpm.

To install StorMan RPM:

From Junos Space Platform CLI, run the following command:

Related Documentation