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 for space-000c29d796f5 on 3/27/14 at 12:25:51 with normal disk usage status.

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

Figure 2: Trap Details When Disk Usage NormalSoftware interface displaying Trap Details for SNMP traps with Request ID, Community set as public, Error Index and Status at 0, IP 10.205.56.39, Trap Type SNMPv2c, and Variable Bindings showing OIDs and values for network monitoring analysis.

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 ThresholdDisk usage alert: Threshold exceeded with 63 percent free space. Date 3-27-14 at 11-59-48. Identifier space-000c29d796f5.

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 window from an SNMP tool showing Request ID 1141303069, Community public, no errors, source IP 10.205.56.39, SNMPv2c, with OIDs for uptime and disk space usage.

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 NormalSystem monitoring entry showing ID 379, name space-000c29d796f5, count 1, timestamp 3/27/14 12:00:48, and 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 NormalSoftware interface showing SNMP Trap Details with Request ID, Community set to public, Error Index and Status at 0, IP Address 10.205.56.39, Trap Type SNMPv2c, and Variable Bindings with OIDs and values. Two panels differ in Variable Bindings, left includes CPU LA clear and Load=15, right includes Load=15. Used for network monitoring.

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 ExceededTable of CPU alerts showing IDs 368, 362, 360 with space ID space-000c29d796f5 and severity 3, 3, 4. Alerts generated on 3/27/14 at 11:59:49 and 11:59:48 indicate CPU load average exceeded thresholds for 1-minute and 5-minute averages with values 1.01, 1.11, 1.04.

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 ThresholdTwo panels display SNMP trap details with Request ID 1861140846, Community public, no errors, source IP 10.205.56.39, Trap Type SNMPv2c, and Variable Bindings table with OIDs and values like CPU LA trigger.

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 table with checkbox, ID 384, space-000c29d796f5, count 1, date 3/27/14 12:10:05, navigation symbols, 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 UpTwo SNMP Trap Details windows showing trap info: Request ID, Community 'public', no errors, IP 10.205.56.39, SNMPv2c type, 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 showing row 382 with ID space:000c29d796f5, value 1, timestamp 3/27/14 12:09:25, and message Process NMA stopped.

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

Figure 12: Trap Details When NMA is DownSNMP trap screenshots showing request ID, community string, error index and status set to 0, source IP 10.205.56.39, SNMPv2c, and variable bindings like sysUpTime.0.

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 and identifier space-000c29d79ef5 shows event at 3/27/14 12:12:55. 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 UpSNMP trap details with Request ID, Community, IP Address 10.205.56.39, Trap Type SNMPv2c, and OIDs like sysUpTime.0 showing device uptime.

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

Figure 15: WebProxy Is DownLog interface showing ID 386, name space-000c29d796f5, status 1, timestamp 3/27/14 12:12:24, 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 SNMP interface panels show trap details: request ID, community, error index, status, IP, trap type, and variable bindings like OIDs and messages such as webproxy stopped.

Parameter: JBoss

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

Figure 17: JBoss Is UpLog entry showing ID 394, resource space-000c29d79ef5, status 1, timestamp 3/27/14 12:14:46, message 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 showing SNMP traps with Request ID 1861140020, community string public, no errors, source IP 10.205.56.39, SNMPv2c version, and variable bindings with OID, type, and value information.

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

Figure 19: JBoss Is DownLog entry showing ID 391 with name space-000c29d796f5 recorded on 3/27/14 12:13:01. Message: Process Jboss stopped.

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

Figure 20: Trap Details When JBoss Is DownScreenshots of SNMP trap details interface showing Trap Details window with fields like Request ID, Community as public, Error Index and Status as 0, and IP Address 10.205.56.39. Variable Bindings table lists OIDs, Types, and Values. Event reports Jboss stopped. Navigation buttons for previous and next traps.

Parameter: Mysql

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

Figure 21: Mysql Is UpLog entry showing MySQL process started with ID 392 on 3/27/14 at 12:13:07 for space-000c29d796f5.

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

Figure 22: Trap Details When Mysql Is UpNetwork monitoring tool with SNMP trap details: Trap Details Window showing Request ID, Community, Error Index, Error Status, IP Address, Trap Type, and Variable Bindings with OIDs, types, and values.

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 MySQL process stopped red alert message

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 an SNMP trap details window with identical information: Request ID 73712741, Community set to public, Error Index and Error Status both 0, IP Address 10.205.56.39, Trap Type SNMPv2c. Variable Bindings include sysUpTime.0 showing 0 days 0:14:12.20s and OID indicating Mysql stopped. Buttons include Close, Show Raw, prev, and next.

Parameter: Postgresql

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

Figure 25: Postgresql Is UpLog entry 393 for space-000c29d796f5: 1 occurrence on 3/27/14 12:13:48; PostgreSQL process started.

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

Figure 26: Trap Details When Postgresql Is UpScreenshots of a network monitoring tool show SNMP trap details from device 10.205.56.39 with PostgreSQL started message.

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

Figure 27: Postgresql Is DownLog entry 389: Resource space-000c29d796f5, status 1, timestamp 3/27/14 12:12:53. 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 DownTrap Details of SNMP interface showing identical network alerts for PostgreSQL stopped. Request ID 737120205, Community public, Error Index 0, Error Status 0, IP Address 10.205.56.39, Trap Type SNMPv2c. Contains Variable Bindings with OID, Type, and Value columns.

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 identifier 405, resource space-000c29d796f5, value 2, timestamp 3/27/14 12:28:43, status 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 window with two panels showing SNMPv2c traps. Request ID 1861140788, community public, error index 0, error status 0, IP address 10.205.56.39. Variable bindings include OID, Type, Value like Swap memory clear. Navigation buttons for prev and next traps, show raw data option available.

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 swap memory issue logged with ID 410 on 3/27/14. Swap memory usage exceeded threshold, risking system instability.

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 showing Trap Details from an SNMP tool with Request ID 1314711189, community public, no errors, IP 10.205.56.39, SNMPv2c. Left panel details swap memory trigger event; right panel adds more OIDs and values. Message indicates swap space 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 NormalSystem log entry 41 shows identifier space-025610201100007 with status 1 on 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 SNMP Trap Details showing alerts from devices. Key fields include Request ID, Community string public, Error Index and Status, IP Address 10.205.56.39, Trap Type SNMPv2c, and Variable Bindings with OIDs. Left screenshot shows CPU fan clear; right screenshot shows similar data with different OIDs. Used for network monitoring and troubleshooting.

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 ThresholdRow 280: Entry ID space-0256042012000014. Quantity 1. Timestamp 3/28/14 12:33:16. Warning: CPU fan too slow, 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 screenshots showing SNMP trap info: Request ID, Community, Error Index, Error Status, IP Address, Trap Type, and Variable Bindings with OID, Type, and Value. Identical data suggests similar or same trap views.

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 with ID space-025610201100007 shows row 42. Timestamp 3/27/14 12:44:58. Status: 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 NormalTwo screenshots of Trap Details window from a network monitoring tool showing SNMP trap info: Request ID 1314711267, Community public, Error Index 0, Error Status 0, IP Address 10.205.56.39, Trap Type SNMPv2c, Variable Bindings with OID, Type, Value like CPU voltage clear.

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 ThresholdLog entry indicating low CPU voltage of 3328 mV on 3/27/14 at 12:58:20 with identifier space-025610201100007.

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 interface for SNMP traps showing Request ID, Community, Error Index, Error Status, IP Address, Trap Type SNMPv2c, and Variable Bindings table with OIDs, types, and values. Includes navigation buttons for viewing raw data.

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 NormalTable showing checkbox, number 260, string space-0256042012000014, number 4, date 3/28/14 12:33:16, 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 NormalTwo Trap Details windows show SNMP network trap info, including Request ID, Error Status, IP Address, and Trap Type. Variable Bindings list OID, Type, and Value with data like uptime and CPU temperature. Navigation buttons for viewing traps.

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 alert: ID 40, Space ID space-025610201100007, CPU temperature too high at 51 degrees Celsius, Timestamp 3/27/14 12:44:58.

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 ThresholdSNMP Trap Details interface with Request ID, Community public, Error Index and Status 0, IP 10.205.56.39, SNMPv2c. Variable Bindings show OIDs like sysUpTime.0 and CPU temperature trigger. Buttons: Close, Show Raw, navigation.

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 UpCheckbox for selecting entry with 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 UpSNMP Trap Details with Request ID 987944205 and community public from IP 192.168.26.179. Panel 1 shows raw OIDs with values like TimeTick 0 days 06h:10m:59.53s, IpAddress 192.168.26.171, Integer 2. Panel 2 translates OIDs into names like sysUpTime.0, snmpTrapOID.0, inxSpaceNodeIP, and inxSpaceNodeType.

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

Figure 47: Junos Space Node is DownLog entry showing status code 204 for space-000c295d757a. Timestamp 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 of SNMP trap details showing Request ID, Community, IP Address, Trap Type, OID, Type, and Value.

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: 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 RemovedTwo SNMP trap panels showing request IDs 201599757 and 1065732676, both indicate a space node was removed successfully from IPs 192.168.26.173 and 192.168.26.179 respectively.

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 DetectedLog entry 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 SNMP Trap Details windows showing request IDs, community set to public, source IPs 192.168.26.173 and 192.168.26.179, SNMPv2c trap type, and variable bindings with OIDs and values.

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 from space-000:294edb9c with severity 7 at 6/14/17 14:58:18 reports 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 from device 192.168.26.173 with SNMPv2c. Request IDs 194357516 and 1164718915. OIDs report TimeTick and Fabric Health Monitoring.

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)Log entry: ID 463, name space-000c294ed8bc, severity 3, timestamp 6/14/17 17:02:00, VIP bind issue 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)SNMP trap details for devices at IPs 192.168.26.173 and 192.168.26.179, showing Request IDs, communities, error statuses, and variable bindings including OIDs and values.

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)Log entry showing ID 394, identifier space-000294ed8bc, value 1, timestamp 6/14/17 16:39:06, and message 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)SNMP trap details with request ID, community 'public', IPs 192.168.26.173 and 192.168.26.179, and trap type SNMPv2c.

Parameter: Fabric Monitoring Process Inactive

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

Figure 59: Fabric Monitoring Process InactiveTable entry: ID 706, Name space-000c29555936, Status 1, Timestamp 6/20/17 18:59:08, Message Fabric monitoring process is 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 InactiveTwo panels showing SNMP trap details with request IDs 422199000 and 1045592590, community public, IPs 192.168.26.206 and 192.168.26.173, Trap Type SNMPv2c. Both panels display variable bindings with OIDs, data types, and values like system uptime and problem detection status.

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 LimitDatabase monitoring interface showing ID 838 with space name space-000c294ed8bc and alert: 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 LimitTwo panels showing SNMP trap details from different IPs. Left Panel: Request ID 362414777, IP 192.168.26.173, Trap Type SNMPv2c. Right Panel: Request ID 1941410565, IP 192.168.26.179, Trap Type SNMPv2c.

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: space-00c29118aa47, count 1, timestamp 6/15/17 14:58:26. Message: Device session count exceed threshold limit 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 showing trap details like Request ID 110117107, Error Status 0, IP 192.168.26.237, and SNMPv2c. Includes variable bindings like sysUpTime 0 days 07h:32m:07.78s and Device Connection value 1. Navigation buttons for raw data and trap navigation 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 AvailabilityEvent log entry: Warning detected on 6/15/17 from source space-000c294ed8bc IP 192.168.26.173 related to JBoss Hprof.

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 AvailableTwo panels show SNMP trap details from IP 192.168.26.173. Both have community public and no errors. Left panel includes system uptime and process info. Right panel notes jnxSpaceProblemDetected as yes.

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 DetectedSystem log entry with ID 644 and code space-0002911aa47. Quantity 1. Timestamp 6/14/17 19:56:49. 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 DetectedSNMP trap details showing Request ID, Community as public, IPs 192.168.26.171 left and 192.168.26.179 right, SNMPv2c, and Fabric Health Monitoring in JBoss.

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 StateMySQL database out of sync on node DB1; ID 343; Resource space-00506938252; Status 1; Timestamp 12/11/17 11:09:55.

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 display SNMP trap details; the left shows human-readable OIDs, the right shows numeric OIDs. Both share data like uptime and IP address.

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: Filesystem changes detected in JBoss node on 12/16/17 18:26:17 by AIDE monitoring.

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 showing Trap Details from a network tool with SNMP data. Left panel: OIDs in readable form like sysUpTime.0. Right panel: OIDs in numeric form like 1.3.6.1.2.1.1.3.0. Both panels include request ID 164085168, community public, IP 192.168.26.35, SNMPv2c type, and variable bindings with uptime, node IP, module, process category, and problems.

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 with ID 622 from space-000294ed8bc. Status 27. Timestamp 6/14/17 19:56:17. Message: 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 FailsTwo "Trap Details" windows in network monitoring software show SNMP trap notifications. Both have Request ID, Community "public," IP "192.168.26.173," and Trap Type "SNMPv2c." The left window includes OIDs for uptime, Fabric Health Monitoring, and Audit Log Forwarding. The right window includes sysUpTime, snmpTrapOID, and problem detection status. Used for monitoring network health and troubleshooting.

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 InactiveSystem alert: Entry ID 104 shows node space-000c295d757a with 2 inactive processes in Juniper_Slave as of 6/23/17 18:58:03.

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 InactiveSNMP trap details with Request ID 2019887467, Community public, IP 192.168.26.249, and Trap Type SNMPv2c. Includes variable bindings with OIDs, data types, and values like Fabric Health Monitoring. Buttons for navigation and raw data display are present.

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: ID 218, node space-000c29118a47, severity 5, timestamp 6/14/17 14:57:48. Message: One or more expected process is inactive in node jb2.

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 Address 192.168.26.171, Trap Type SNMPv2c, and Variable Bindings. Left panel displays OIDs for fabric health, right panel for platform-specific traps.
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 interface showing node space-0256042012000017 status, availability, and recent events. Node is active with 94.751 percent availability in 24 hours. IP 10.205.56.40 has 92.126 percent overall and 84.252 percent SNMP availability. IP 10.205.57.40 has 100 percent overall availability. Recent events include SNMP issues 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

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