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 Up
Figure 46 shows theOID details for the trap generated when a Junos Space node is up.
Figure 46: Trap Details When Junos SpaceNode Is Up
When a Junos Space node is down, the trap shown in Figure 47 is generated:
Figure 47: Junos Space Node is Down
Figure 48 showsthe OID details for the trap generated when a Junos Space node isdown.
Figure 48: Trap Details When JunosSpace Node is Down
Parameter: Junos Space Node Removal
When a Junos Space node is removed from the fabric, the trapshown in Figure 49 is generated:
Figure 49: Junos Space Node Is Removed
Figure 50 showsthe OID details for the trap generated when a Junos Space node isremoved..
Figure 50: Trap Details When JunosSpace Node Is Removed
Parameter: JBoss Multi-Primary Detected
When there is more than one JBoss AppLogic primary node detectedin the cluster, the trap shown in Figure 51 is generated:
Figure 51: JBoss Multi-Primary Detected
Figure 52 shows the OID details for the trap generated when there is morethan one JBoss AppLogic primary node detected in the cluster.
Figure 52: TrapDetails When JBoss Multi-Primary Is Detected
Parameter: VIP Bind Issue Detected in JBoss Node(s)
When VIP Bind issue is detected in JBoss node(s), the trap shownin Figure 53 is generated:
Figure 53: VIP Bind Issue Detected InJBoss Node(s)
Figure 54 shows the OIDdetails for the trap generated when VIP Bind issue is detected inJBoss node(s).
Figure 54: Trap Details When VIP Bind IssueIs Detected In JBoss Node(s)
Parameter: Fabric Monitoring Process Inactive
When fabric monitoring process is inactive, the trap shown in Figure 55 is generated:
Figure 55: Fabric Monitoring Process Inactive
Figure 56 shows the OID detailsfor the trap generated when fabric monitoring process is inactive.
Figure 56: Trap Details When FabricMonitoring Process Is Inactive
Parameter: Tables Exceed Size Limit
When one or more tables in the MySQL database exceed the sizelimit of 10 GB, the trap shown in Figure 57 isgenerated:
Figure 57: Tables Exceed Size Limit
Figure 58 shows the OID details forthe trap generated when one or more tables in the MySQL database exceedthe size limit of 10 GB.
Figure 58: Trap Details When Tables ExceedSize Limit
Parameter: Device Session Count Exceeds Threshold Limit
When the device session count exceeds the threshold limit, thetrap shown in Figure 59 is generated:
Figure 59: Device Session Count Exceeds ThresholdLimit
Figure 60 shows the OID detailsfor the trap generated when the device session count exceeds the thresholdlimit.
Figure 60: Trap Details When Device SessionCount Exceeds Threshold Limit
Parameter: HPROF Availability
When Heap and CPU Profiling Agent (HPROF) files are detectedon a Junos Space node, the trap shown in Figure 61 is generated:
Figure 61: HPROF Availability
Figure 62 shows the OID details for thetrap generated when HPROF files are detected on a Junos Space node.
Figure 62: Trap Details When HPROF Files Are Available
Parameter: JGroup Membership Issue Detected
When the removal of a JBoss node from JGroup is detected inthe cluster, the trap shown in Figure 63 is generated:
Figure 63: JGroup Membership Issue Detected
Figure 64 shows the OID details for thetrap generated when the removal of a JBoss node from JGroup is detectedin the cluster.
Figure 64: Trap Details When JGroup MembershipIssue Detected
Parameter: MySQL In Out Of Sync State
When a MySQL database synchronization issue is detected betweennodes running the MySQL database, the trap shown in Figure 65 is generated:
Figure 65: MySQL In Out Of Sync State
Figure 66 shows the OIDdetails for the trap generated when a MySQL database synchronizationissue is detected between nodes running the MySQL database.
Figure 66: Trap Details When MySQL Is InOut Of Sync State
Parameter: File Intrusion Detection Monitoring
When changes in files or file permissions are detected, thetrap shown in Figure 67 is generated.
Figure 67: File Intrusion Detection Monitoring
Figure 68 shows the OIDdetails for the trap generated when file or file permission changesare detected in the system.
Figure 68: Trap Details for File IntrusionDetection Monitoring
Parameter: Audit Logs Forwarding Failed
When the system fails to forward audit logs to the configuredsystem log server, the trap shown in Figure 69 is generated:
Figure 69: Audit Logs Forwarding Failed
Figure 70 shows the OID detailsfor the trap generated when the system fails to forward audit logsto the configured system log server.
Figure 70: Trap Details When Audit LogsForwarding Fails
Parameter: One Or More Expected Process Are Inactive
Junos Space monitors critical process like JBoss. If any of these expected processes are inactive, the trap shown in Figure 71 is generated:
Figure 71: One or More Expected Processes Are Inactive
Figure 72 shows the OID details for thetrap generated when one or more expected processes are inactive.
Figure 72: Trap Details When One or More ExpectedProcesses Are Inactive
