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, name space-000c29d796f5, count 1, timestamp 3/27/14 12:25:51, status message 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 Trap Details windows show SNMP trap info with Request ID 1861140816, IP 10.205.56.39, Trap Type SNMPv2c, and OIDs.

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 ThresholdRow 377: Identifier space-000c29d796f5. Value 2. Timestamp 3/27/14 11:59:48. Message: Disk usage exceeded; 63 percent free.

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 showing SNMP request 1141303069 from IP 10.205.56.39 with no errors. Community is public and trap type is SNMPv2c.

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 NormalTable entry with checkbox, ID 379, label space-000c29d796f5, count 1, timestamp 3/27/14 12:00:48, navigation controls, 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 NormalTwo screenshots of Trap Details window from an SNMP tool show SNMP traps with unique Request IDs, community string public, error status set to 0, source IP 10.205.56.39, SNMP version SNMPv2c, and Variable Bindings listing OIDs and values.

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 ExceededMonitoring interface showing alerts for CPU load thresholds exceeded with alert IDs, space names, severity levels, timestamps, and descriptions.

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 "Trap Details" windows in a network system show SNMP trap info: Request ID 1861140846, Community public, Error Index 0, Error Status 0, IP 10.205.56.39, Trap Type SNMPv2c. Variable Bindings list OIDs, data types, and values like system uptime, CPU load trigger, and high 5-minute load average. Navigation buttons and "Show Raw" option available.

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 with ID 384, space identifier space-000c29d796f5, number 1, timestamp 3/27/14 12:10:05, navigation arrows, 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 UpTrap Details interface for SNMP traps with fields like Request ID, Community, and IP Address 10.205.56.39. Trap Type is SNMPv2c. Variable bindings include OIDs like sysUpTime.0 and snmpTrapOID.0. Navigation buttons for trap analysis.

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

Figure 11: NMA is DownLog entry 382 with identifier space:000c29d796f5 shows status 1 on 3/27/14 12:09:25. Process NMA stopped. Navigation links present.

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

Figure 12: Trap Details When NMA is DownTwo Trap Details windows from a network app display SNMP trap info: Request ID 737117913, Community public, IP 10.205.56.39, and Trap Type SNMPv2c.

Parameter: Webproxy

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

Figure 13: WebProxy Is UpLog entry showing ID 390, name space-000c29d79ef5, count 1, timestamp 3/27/14 12:12:55, and description 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 window from SNMP tool showing details like Request ID 1861139988, Community public, Error Index 0, IP Address 10.205.56.39, Trap Type SNMPv2c, and Variable Bindings with OID 1.3.6.1.2.1.1.3.0.

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

Figure 15: WebProxy Is DownLog entry 386: Process space-000c29d796f5 stopped. Timestamp 3/27/14 12:12:24. Navigate with arrows.

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

Figure 16: Trap Details When WebProxy Is DownTrap Details from SNMP interface show two panels with Request ID, Community, Error Index, Error Status, IP Address, Trap Type, and Variable Bindings with OID, Type, and Value columns. Displays webproxy stopped event. Navigation options include Show Raw, Close, prev, and next.

Parameter: JBoss

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

Figure 17: JBoss Is UpSystem log entry showing ID 394, resource ID space-000c29d79ef5, status 1, timestamp 3/27/14 12:14:46, and 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 UpSNMP Trap Details interface with Request ID 1861140020, community string public, no errors, source IP 10.205.56.39, SNMPv2c, and variable bindings with OIDs. Two panels show simplified and full numeric OIDs.

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

Figure 19: JBoss Is DownLog entry with ID 391: Process Jboss stopped on 3/27/14 at 12:13:01. Navigation controls present.

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

Figure 20: Trap Details When JBoss Is DownNetwork management system showing two Trap Details windows with SNMPv2c protocol. Key info: Request ID 737110115, Community public, IP 10.205.56.39, status message Jboss stopped.

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 on 3/27/14 at 12:13:07 with ID space-000c29d796f5 and number 392.

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

Figure 22: Trap Details When Mysql Is UpScreenshots of a network monitoring tool displaying SNMP trap details with Request ID, Community, Error Index, Error Status, IP Address, and Trap Type SNMPv2c. Includes Variable Bindings with Object Identifiers OIDs, types, and values like system uptime and Mysql started message.

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

Figure 23: Mysql Is DownLog entry 398 shows space-000c29d796f5 with status 1 at 3/27/14 12:21:44. MySQL process 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 DownSNMP trap details window showing Request ID, Community, Error Index, Error Status, IP Address 10.205.56.39, Trap Type SNMPv2c, and Variable Bindings with OID, Type, and Value MySQL stopped. Includes buttons for 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 showing space-000c29d796f5 with timestamp 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 UpTrap Details windows showing SNMP trap info with Request ID 1861140052, Community public, IP 10.205.56.39, Trap Type SNMPv2c.

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

Figure 27: Postgresql Is DownTable showing a log entry: ID 389, code space-000c29d796f5, priority 1, timestamp 3/27/14 12:12:53, PostgreSQL process 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 showing Trap Details: Request ID 737120205, Community public, Error Index 0, Error Status 0, IP Address 10.205.56.39, Trap Type SNMPv2c, sysUpTime 0 days 00:12m:32.66s, PostgreSQL status 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 log entry with ID 405 showing timestamp 3/27/14 12:28:43 and 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 NormalTwo panels of a software interface labeled Trap Details for SNMP traps. Key elements: Request ID, Community set to public, Error Index and Status at 0, IP Address 10.205.56.39, Trap Type SNMPv2c. Variable Bindings table with OIDs and values; left panel shows Swap memory clear, right panel shows different OID structure. Used for network monitoring.

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: ID 410, space-000c29d796f5, 1 occurrence, timestamp 3/27/14 12:30:56, swap usage exceeded limit.

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 LimitSNMP Trap Details showing memory alert for IP 10.205.56.39. Includes Request ID 1314711189, community string public, no errors, SNMPv2c, indicating swap memory trigger and running out of swap space.

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 showing ID 41, component space-025610201100007, status 1, timestamp 3/27/14 12:44:58, and message 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 NormalScreenshots of SNMP Trap Details window with Request ID, Community as public, IP 10.205.56.39, using SNMPv2c. Left: variable bindings for CPU fan clear. Right: similar data with varied 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 ThresholdRow 280: Entry ID space-0256042012000014. Count 1. Timestamp 3/28/14 12:33:16. Alert: CPU fan too slow, speed 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 ThresholdTrap Details window displays SNMP trap info: Request ID, Community, Error Index, Error Status, IP 10.205.56.39, SNMPv2c, Variable Bindings with OIDs and metrics.

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 from space-0256102011000007 on 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 NormalTrap Details window from a network tool showing SNMP request ID, community 'public', no errors, IP 10.205.56.39, SNMPv2c, and variable bindings with OIDs.

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 with row number 60 showing identifier space-025610201100007, count 1, timestamp 3/27/14 12:58:20, and message: CPU voltage too low mV 3328.

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 ThresholdTwo screenshots of Trap Details window from an SNMP monitoring tool showing trap info like Request ID, Community, IP Address 10.205.56.39, and SNMPv2c version. Variable Bindings section lists OIDs, types, and values including CPU voltage trigger and 3312. Navigation buttons include Show Raw, prev, and next.

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, code space-0256042012000014, status 4, timestamp 3/28/14 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 NormalTwo screenshots of a Trap Details window in a network monitoring tool show SNMP trap info. Key elements: Request ID, Community, Error Index, IP Address 10.205.56.39, Trap Type SNMPv2c, and Variable Bindings with OIDs like sysUpTime.0. Navigation buttons for browsing traps are present. The screenshots differ slightly in variable bindings layout.

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-025610201100007; severity 1; timestamp 3/27/14 12:44:58; CPU temperature too high: 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 ThresholdTwo screenshots of SNMP Trap Details interface showing SNMPv2c trap with Request ID 1861140855, community public, no errors, source IP 10.205.56.39, trap type SNMPv2c. Variable bindings include sysUpTime.0 showing 0 days, 0 hours, 0 minutes, 12 seconds, CPU temperature trigger string, and Gauge value 47500. Buttons for navigation and raw data display.

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 selection, ID 642, node name 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 UpSoftware interface displaying SNMP trap details with request ID 987944205, community public, and IP 192.168.26.179 using SNMPv2c.

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

Figure 47: Junos Space Node is DownLog entry: Status code 204, space node space-000c29sd757a 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 DownTwo panels showing SNMP trap details with Request ID, Community, IP Address, Trap Type, and Variable Bindings including OID, Type, and Value. Left panel lists OIDs like 1.3.6.1.2.1.1.3.0, while the right panel shows OIDs like sysUpTime.0.

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 RemovedID 1076, Space Node Identifier space-000c2990f597, Status 1, Timestamp 6/21/17 15:33:04, Node 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 panels showing SNMP trap details with request IDs 201599757 and 1065732676. Both indicate space node removal success.

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 DetectedCheckbox with ID 846, identifier space-000c294ed8bc, number 1, timestamp 6/15/17 14:58:43, note 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 DetectedTwo panels displaying SNMP trap details: Left panel shows Request ID 1056642132, IP 192.168.26.173. Right panel shows Request ID 977942577, IP 192.168.26.179. Both include SNMPv2c trap type, public community, and variable bindings with values like Fabric Health Monitoring and JBoss.

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 with checkbox, ID 217, source space-000:294edb9c, severity 7, timestamp 6/14/17 14:58:18, and 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)Two panels showing SNMP trap details from device 192.168.26.173 using SNMPv2c and community string public. Left panel Request ID 194357516 with OIDs: TimeTick 0 days 01h:42m:35.02s, String Fabric Health Monitoring, Integer 1. Right panel Request ID 1164718915 with OIDs: TimeTick 0 days 05h:57m:28.36s, Integer yes. Navigation buttons for trap details view.

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 with VIP bind issue detected in Database Nodes on 6/14/17 at 17:02:00. Severity 3.

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 monitoring tool panels showing traps from devices 192.168.26.173 and 192.168.26.179 with details on request ID, community, error status, IP, trap type, and variable bindings.

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)Entry 394: space-000294ed8bc with status 1. Detected VIP bind issue in FMPM Nodes on 6/14/17 16:39:06.

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 IDs, community strings, error statuses, IP addresses, trap types, and variable bindings. Left panel shows IP 192.168.26.173 with metrics like time ticks. Right panel shows IP 192.168.26.179 with uptime and problem detected status.

Parameter: Fabric Monitoring Process Inactive

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

Figure 59: Fabric Monitoring Process InactiveLog entry with ID 706 for node jb1: Fabric monitoring process inactive. Timestamp: 6/20/17 18:59:08.

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 InactiveLeft panel shows SNMP trap details with Request ID 422199000, IP 192.168.26.206, Trap Type SNMPv2c, time tick 00h:09m:13s, and bindings like Fabric Health Monitoring. Right panel shows SNMP trap details with Request ID 1045592590, IP 192.168.26.173, Trap Type SNMPv2c, time tick 06h:15m:19s, and detected problem with value yes.

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 LimitAlert: Database table size exceeds 10GB for ID 838 on 6/15/17 at 14:41:36.

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 two devices: Left panel - IP 192.168.26.173, Request ID 362414777, event Fabric Health Monitoring, MySQL; Right panel - IP 192.168.26.179, Request ID 1941410555, event Fabric Health Monitoring, MySQL.

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 reports device session count exceeded in node jb2 on 6/15/17 at 14:58:26.

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 LimitSoftware interface displaying SNMP trap details with Request ID 110117107, community public, IP 192.168.26.237, SNMPv2c, and OIDs with values.

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 ID 5226 Warning on 6/15/17 at 15:40:29 from space-000c294ed8bc, IP 192.168.26.173. JBoss Hprof detected on Juniper Space platform.

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 with IP 192.168.26.173 using SNMPv2c. Left panel: Request ID 1827108907, OIDs show TimeTick and IpAddress. Right panel: Request ID 348191933, OIDs show sysUpTime and snmpTrapOID.

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 DetectedLog entry with ID 644 for space space-0002911aa47 shows Jgroup Membership issue detected on 6/14/17 at 19:56:49.

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 trap details like Request ID, community string public, IP addresses 192.168.26.171 and 192.168.26.179, SNMP version SNMPv2c, and variable bindings. Both traps relate to Fabric Health Monitoring and Cluster Issues in a JBoss system with node name ib2.

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 StateLog entry 343 for space-00506938252 reports MySQL database out of sync in node DB1 on 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 StateTrap Details panels showing SNMP traps. Request ID 1624086348, Community public, IP 192.168.26.20, Type SNMPv2c. Left panel uses descriptive OIDs, right uses numerical OIDs. Network event: Fabric Health Monitoring and MySQL Replication.

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 MonitoringLog entry showing filesystem changes detected in node jboss by Aide with timestamp 12/16/17 18:26:17.

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 MonitoringSNMP trap details in network tool screenshots showing Trap Details window with Request ID 164085168, Community public, IP 192.168.26.35, and Trap Type SNMPv2c. Variable Bindings list OIDs in human-readable and numeric formats with values like System uptime 0 days 01h:08m:05.10s, IP Address 192.168.26.35, and Node Name jboss-35. Navigation buttons for viewing options.

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 source space-000294ed8bc. Status 27 at 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 panels of SNMP Trap Details showing Request ID, Community as public, IP Address 192.168.26.173, Trap Type SNMPv2c, Error Index 0, Error Status 0, and Variable Bindings with OID, Type, and Value details. Navigation buttons for previous or next traps and raw data view options.

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 with ID 104 for process space-000c295d757a. Status 2. Timestamp 6/23/17 18:58:03. Issue: Inactive processes in 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 InactiveSNMP trap details of a network device showing request ID 2019887467, community string public, and source IP address 192.168.26.249 using SNMPv2c. Variables include OID, type, and value like Fabric Health Monitoring and Juniper_Slave. Navigation buttons include Close, Show Raw, prev, and next.

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 shows node space-000c29118a47 at 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 Trap Details with Request ID, Community as public, IP 192.168.26.171, SNMPv2c, and OIDs for fabric health and platform-specific monitoring.
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 network monitoring interface showing SNMP attributes, availability stats, node interfaces, general info, surveillance categories, notifications, 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

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