Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Monitoring Nodes in the Fabric

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

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

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

This topic contains the following sections:

Viewing and Modifying the SNMP Configuration for a Fabric Node

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

  1. Select Administration > Fabric.

    The Fabric page appears.

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

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

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

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

    Setting

    Explanation

    Recommended Settings

    Default Value

    Enable SNMP over TCP

    Enables SNMP communication over TCP

    Note:

    By default, SNMP communication occurs over UDP.

    Cleared

    Cleared

    Monitor Web Service

    Includes monitoring the performance of the Junos Space GUI

    Note:

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

    Selected

    Selected

    Monitor All Disks

    Includes all disks on the current Junos Space server

    Cleared

    Cleared

    Monitor RAID

    Enables Net-SNMP to monitor the RAID state

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

    Note:

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

    Note:

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

    Selected

    Cleared

    Disk Usage %

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

    5

    5

    System Load (1 min)

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

    4

    4

    System Load (5 min)

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

    4

    4

    System Load (15 min)

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

    4

    4

    System Location

    Location of the fabric node

    Actual geographical or other location

    unknown

    System Contact

    E-mail address to which the system sends notifications

    E-mail address of actual person

    root <root@localhost>

    Disk Mount Path

    Disk mount path that is to be monitored

    Note:

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

    Actual path, if available

    /

    CPU Max Temp (mC)

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

    50000

    50000

    CPU Min Fan (RPM)

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

    1000

    1000

    CPU Min Voltage (mV)

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

    1000

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

Table 2 shows the configuration parameters for monitoring disk usage.

Table 2: SNMP Configuration Parameters: Monitoring Disk Usage

Monitoring Disk Usage

Parameter: Disk Usage (%)

Default: 5%

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

Figure 1: Disk Usage Threshold Is NormalSystem monitoring log entry showing ID 406, resource space-000c29d796f5, status 1, timestamp 3/27/14 12:25:51, navigation buttons, and 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 software interface panels showing Trap Details for SNMP traps with elements like Request ID, Community, Error Index, Error Status, IP Address, Trap Type, and Variable Bindings including OIDs, Types, and Values.

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

Figure 3: Disk Usage Threshold Exceeds Configured ThresholdDisk usage alert: ID space-000c29d796f5 shows 37 percent disk space used, exceeds 95 percent threshold on 3/27/14.

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 monitoring tool showing Request ID 1141303069, Community public, no errors, IP Address 10.205.56.39, Trap Type SNMPv2c, with OIDs and values for data like 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 NormalID 379 space-000c29d796f5 CPU load average is normal at 3/27/14 12:00:48 with navigation symbols.

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 Trap Details windows displaying SNMP trap info with Request ID 1141303118, IP 10.205.56.39, SNMPv2c type, and variable bindings for OID, Type, and Value.

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 ExceededCPU load average threshold alerts with ID numbers, space identifiers, numerical values, timestamps, and alert 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 from a network management system using SNMP displaying performance alerts with system metrics like uptime and a 5 min Load Average too high message.

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 UpProcess log entry with ID 384 shows process NMA started on 3/27/14 at 12:10:05 with navigation options.

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

Figure 10: Trap Details When NMA Is UpTwo screenshots of a software interface displaying SNMP trap details, showing fields like Request ID, Community, Error Index, Error Status, IP Address, and Trap Type. A table shows OID, Type, and Value details. Buttons Close, Show Raw, prev, and next are visible for navigation and actions.

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

Figure 11: NMA is DownEntry 382 shows process NMA stopped. Timestamp 3/27/14 12:09:25. Navigate with arrows. Red border suggests warning.

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

Figure 12: Trap Details When NMA is DownTrap Details windows in network monitoring app showing SNMP traps with Request ID 737117913, IP 10.205.56.39, and community public. Options for Close, Show Raw, and navigation.

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, 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 UpScreenshots of SNMP trap details showing Request ID 1861139988, Community public, IP 10.205.56.39, Trap Type SNMPv2c, indicating a web proxy start event.

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

Figure 15: WebProxy Is DownLog entry: ID 386, space code space-000c29d796f5, value 1, timestamp 3/27/14 12:12:24, status 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 "Trap Details" windows from an SNMP tool show Request ID 737109873, community "public," no errors, IP 10.205.56.39, SNMPv2c, and "webproxy stopped." Left uses mixed OIDs; right uses numeric OIDs.

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; time March 27, 2014, 12:14:46; JBoss process started.

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

Figure 18: Trap Details When JBoss Is UpTwo panels showing SNMP Trap Details. Left panel uses simplified OIDs like mib-2.1.1.0; right panel shows full numeric OIDs like 1.3.6.1.2.1.1.0. Key details include Request ID 1861140020, community public, no errors, source IP 10.205.56.39, SNMPv2c, sysUpTime 0 days 00h:00m:06.29s, and event Jboss started.

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, count 1, timestamp 3/27/14 12:13:01. Message: Process Jboss stopped. Red background suggests critical event.

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

Figure 20: Trap Details When JBoss Is DownTwo "Trap Details" windows from a network management system showing SNMP alert details like Request ID 737110115, Community public, IP Address 10.205.56.39, Trap Type SNMPv2c, and events like 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 ID 392, identifier space-000c29d796f5, priority 1, timestamp 3-27-14 12:13:07, MySQL process started.

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

Figure 22: Trap Details When Mysql Is UpSNMP trap details from device 10.205.56.39 showing identical data: Request ID 1861140036, Community public, Error Index 0, Error Status 0, SNMPv2c trap type with OID 1.3.6.1.2.1.1.3.0 as TimeTick and OID 1.3.6.1.2.1.28.0.1 as Mysql started.

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

Figure 23: Mysql Is DownLog entry with ID 398: space-000c29d796f5, status 1, timestamp 3/27/14 12:21:44. Message: Process Mysql stopped. Red background indicates a 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: Request ID 73712741, community public, error status 0, IP 10.205.56.39, SNMPv2c, OID reports Myqd stopped.

Parameter: Postgresql

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

Figure 25: Postgresql Is UpLog entry 393: 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 UpScreenshots of a network monitoring tool showing SNMP trap details from IP 10.205.56.39 with request ID, community as public, no errors, and SNMPv2c version. Variable bindings include OIDs like PostgreSQL started.

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

Figure 27: Postgresql Is DownLog entry showing ID 389 reporting PostgreSQL process stopped on 3/27/14 at 12:12:53.

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

Figure 28: Trap Details When Postgresql Is DownTwo panels showing SNMP Trap Details with Request ID 737120205, Community public, Error Index and Status 0, IP 10.205.56.39, SNMPv2c, sysUpTime 0 days 00:12m:32.66s, PostgreSQL service 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: Resource space-000c29d796f5. Status: Swap memory usage is normal on 3/27/14 12:28:43.

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

Figure 30: Trap Details When Swap Memory Is NormalTrap Details interface showing two SNMP trap panels with details like Request ID 1861140788, Community public, Error Index 0, Error Status 0, IP Address 10.205.56.39, Trap Type SNMPv2c, and Variable Bindings table with OID, Type, and Value.

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 exceeded upper limit on space-000c29d796f5. Error code 410. Occurred on 3/27/14 at 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 LimitTrap Details from SNMP monitoring tool showing Request ID 1314711189 for community public. IP 10.205.56.39, SNMPv2c. Indicates swap memory trigger 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 monitoring interface screenshot showing row 41. Identifier space-025610201100007. Status 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 NormalSNMP trap details interface showing device notifications with Request ID, Community, IP Address, Trap Type SNMPv2c, and Variable Bindings including OIDs and values like CPU fan clear.

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

Figure 35: CPU Fan Speed Is Below the Configured ThresholdLog entry with CPU fan alert: Number 280, ID space-0256042012000014, Date 3/28/14 12:33:16, Message 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 ThresholdTwo identical screenshots of Trap Details window in SNMP monitoring tool. Community set to public. Request ID 709615918. No errors. Source IP address 10.205.56.39. SNMP version SNMPv2c. Table of OIDs, types, and values.

Parameter: CPU min Voltage (mV)

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

Figure 37: CPU Voltage NormalRow 42: Unique ID space-025610201100007, Count 1, Timestamp 3/27/14 12:44:58, Message 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 windows displaying SNMP trap info; Request ID 1314711267, Community public, Error Index 0, Error Status 0, IP 10.205.56.39, Trap Type SNMPv2c, and Variable Bindings table with OIDs, Types, and Values 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 ThresholdCPU voltage issue log entry with ID 60 space identifier space-025610201100007 date 3/27/14 time 12:58:20 voltage 3328 mV.

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 SNMP monitoring tool showing SNMP trap info. Includes Request ID 1861140863, Community public, IP 10.205.56.39, Trap Type SNMPv2c, no errors, and OIDs like sysUpTime.0.

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 NormalMonitoring system interface with log entry ID 260, space reference space-0256042012000014, value 4, timestamp 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 NormalTrap Details window with SNMP trap info: Request ID, Community, Error Index and Status, IP Address 10.205.56.39, Trap Type SNMPv2c. Variable Bindings show OIDs, types like TimeTicks, String, and values like uptime 0 days 00:01:00.12. Navigation buttons include Close, Show Raw, prev, and next.

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

Figure 43: CPU Temperature Exceeds The Configured ThresholdLog entry: ID 40, Space 025610201100007, Count 1, Timestamp 3/27/14 12:44:58, CPU temperature high 51°C.

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 software windows display SNMP trap details with request ID, community string public, error index and status 0, IP 10.205.56.39, and SNMPv2c trap type. Variable Bindings list OIDs, types, and values like sysUpTime.0 and snmpTrapOID.0. Navigation buttons and options to show raw data or close the window are present.

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 UpScreenshot of a system log entry showing ID 642, space-000c294ed8bc, status 1, timestamp 6/14/17 19:54:41, and description that the space 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 showing SNMP trap details: Request ID 987944205, Community public, IP 192.168.26.179, SNMPv2c. Variable bindings include sysUpTime 0 days 06h:10m:59.53s, snmpTrapOID inxSpacePlatformTraps, inxSpaceNodeIP 192.168.26.171, inxSpaceNodeType 2. Navigation options: Show Raw, prev, next, and Close.

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

Figure 47: Junos Space Node is DownStatus log entry: Code 204, space-000c29sd757a, count 1, timestamp 6/23/17 22:45:29. Message: Space node referred by jnxSpaceNodeIP is 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, and Trap Type. Variable Bindings list OIDs, Types, and Values such as sysUpTime, IP address, and integers.

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 showing a space node removal: ID 1076, reference space-000c2990f597, timestamp 6/21/17 15:33:04, description 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 show successful removal of space nodes from IPs 192.168.26.173 and 192.168.26.179, with uptime, trap OID, node IP, object state, and node type details.

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 with checkbox, ID 846, label space-000c294ed8bc, count 1, timestamp 6/15/17 14:58:43, description Multi master issue observed in cluster.

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

Figure 52: Trap Details When JBoss Multi-Primary Is DetectedSNMP trap details for devices 192.168.26.173 and 192.168.26.179, showing request IDs, community names, IP addresses, trap types, and variable bindings, including OIDs, types, and values for monitoring and alerting purposes.

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 ID 217 from space-000:294edb9 indicating severity 7. Timestamp: 6/14/17 14:58:18. 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 with unique Request ID, error status 0, community public, source IP 192.168.26.173, SNMPv2c version, OIDs for device uptime and Fabric Health Monitoring. Navigation buttons prev, next, show raw, and close provided.

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, space-000c294ed8bc, severity 3, timestamp 6/14/17 17:02:00, VIP bind issue in Database Node(s).

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 panels with details: Request ID, Community set to public, Error Index and Status as 0, IPs 192.168.26.173 and 192.168.26.179, SNMPv2c, Variable Bindings with sysUpTime and Fabric Health Monitoring.

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 for selecting row; ID 394; Identifier space-000294ed8bc; 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 SNMP trap panels detailing Request ID, Community set to public, Error Index and Status as 0, IPs 192.168.26.173 and 192.168.26.179, SNMPv2c, and OIDs listing device uptime and event descriptions.

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: ID 706, space-000c29555936, status 1, timestamp 6/20/17 18:59:08, message 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 showing two panels with request IDs, public community, IPs 192.168.26.206 and 192.168.26.173, SNMPv2c, and variable bindings.

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 with ID 838 and space identifier space-000c294ed8bc. Entry dated 6/15/17 at 14:41:36. Message indicates 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 two devices; left panel: Request ID 362414777, IP 192.168.26.173, monitoring MySQL table size; right panel: Request ID 1941410555, IP 192.168.26.179, monitoring fabric health.

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 844: Device session count exceeded threshold 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 LimitTrap Details panels displaying SNMP network trap info: Request ID 110117107, Community public, IP 192.168.26.237, Type SNMPv2c, Error Index 0, Error Status 0. Variable Bindings include OIDs for time, IP, and fabric health.

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 AvailabilityScreenshot of network monitoring tool showing Event ID 5226 with Warning severity from system space-000c294ed8bc at 192.168.26.173 on 6/15/17 15:40:29. Event description indicates JBoss Hprof trap detected.

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 SNMP trap panels with details from device 192.168.26.173; left panel shows uptime 0 days 02h:10m:40.78s; right panel shows uptime 0 days 16h:00m:58.18s with jnxSpaceProblemDetected value 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 DetectedCheckbox for entry selection; ID: 644; Resource: space-0002911aa47; Data: 1; Date: 6/14/17 19:56:49; Issue: 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 with two panels showing trap info from IPs 192.168.26.171 and 192.168.26.179. Each includes request ID, community, trap type, and variable bindings like uptime and monitoring details.

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: ID 343, resource space-00506938252, status 1, timestamp 12/11/17 11:09:55, MySQL database out of sync in node DB1.

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 from SNMP monitoring tool showing SNMPv2c traps from device 192.168.26.20 with Request ID 1624086348. Left panel shows OIDs like sysUpTime.0, right panel shows numeric OIDs like 1.3.6.1.2.1.1.3.0. Key info includes device uptime 0 days 02h:00m:12.55s, node IP 192.168.26.20, application module Fabric Health Monitoring, process MySQL, no problems detected, node name Node1.

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 ID 199 for space-000c29c82c4a with count 1 on 12/16/17 at 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 of SNMP trap details showing SNMPv2c trap type. Fields include Request ID 164085168, Error Index 0, Error Status 0, Community public, IP Address 192.168.26.35. Variable bindings show sysUpTime 0 days 01h:08m:05.10s, snmpTrapOID jnxSpacePlatformTraps, jnxSpaceNodeIP 192.168.26.35, jnxSpaceProcess Fabric Health Monitoring, jnxSpaceProcessCategory Fabric, jnxSpaceProblemDetected yes, jnxSpaceNodeName jboss-35. Left panel shows human-readable OIDs; right panel shows 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 showing ID 622 from source space-000294ed8bc with severity 27 on 6/14/17 at 19:56:17; 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 two panels of trap details from device 192.168.26.173 with Request IDs 532070112 and 390622533. Both traps use SNMPv2c and have no errors. Left panel shows system uptime of 0 days 01h:11m:43.21s, fabric health monitoring, and audit log forwarding 1. Right panel shows system uptime of 0 days 01h:52m:56.70s, fabric health monitoring, and audit log forwarding Yes.

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 InactiveCheckbox with number 104 space-000c295d757a number 2 date 6/23/17 18:58:03 message One or more expected process is inactive 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 with request ID, community string, IP address, trap type, and no errors. Variable bindings show OIDs with types and values for network monitoring.

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 checkbox, 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 NodesTrap Details panel from SNMP monitoring tool showing Request ID 294311413, Community public, IP Address 192.168.26.171, Trap Type SNMPv2c, and Variable Bindings like sysUpTime 0 days 06h:25m:56.29s and jnxSpaceProblemDetected yes. Navigation buttons include prev, next, and Show Raw.
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 percent availability, status active, and recent SNMP 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

To install StorMan RPM:

From Junos Space Platform CLI, run the following command:

Related Documentation