ProxySG-restart issue

I need a solution

Hi Team,

We have noticed that proxy has restarted multiple times due to the bug. We have noticed below logs in the sysinfo.

Minicontext produced on: 2018-05-14 01:12:06+00:00UTC
Minicontext version: 1.5
ProxySG Appliance: Version 6.5.10.4.203460
Architecture: x86_64
Kernel: Multiprocessor
System image flags: Customer, Optimized, Non-GDB, 64-bit

Hardware exception code: 0x0
Software exception code: 0x10005
Page fault linear address: 0x0
Process group: “PG_UNKNOWN”
Process: “ATA Clock” in “” at .text+0x0

Minicontext produced on: 2018-05-13 12:24:32+00:00UTC
Minicontext version: 1.5
ProxySG Appliance: Version 6.5.10.4.203460
Architecture: x86_64
Kernel: Multiprocessor
System image flags: Customer, Optimized, Non-GDB, 64-bit

Hardware exception code: 0x0
Software exception code: 0x10005
Page fault linear address: 0x0
Process group: “PG_UNKNOWN”
Process: “ATA Clock” in “” at .text+0x0

We have noticed that the above bug:

Bug# 194940 – The ProxySG experienced a software restart at 0x10005 in process group “PG_UNKNOWN” in process “ATA Clock”.

But this issue has been fixed the version 6.5.5.1 but we are already running the version 6.5.10.4.

Please suggest us to fix this issue and provide the most stable veresion in this code.

Proxy Version: 6.5.10.4

Model: 600-20

Thanks,

Ram.

0

Related:

Isilon Supportability part 2: SNMP Trap List

<Note: the pictures will get clear when you click them…..>

In my original plan, SNMP trap list will be discussed in some posts later . However, I got a few asks on this topic and some are quite urgent requests. So I decided to move this up for this dedicate topic.

What’s SNMP Alert

In case you don’t understand what’s SNMP alert is, spend several minutes on this section and it won’t waste your time. If you are quite familiar with it, just skip to the next section.

The SNMP provides a standardized interface to query network devices for information. This can include uptime, descriptions, locations, and device specific information. For OneFS, the device specific information includes cluster and node data, disk health and much more.

There are two parts to the OneFS implementation of SNMP as listed below:

  1. SNMP monitoring – it’s for query requested information of the Isilon cluster in a synchronization way and usually it’s for monitoring purpose
  2. SNMP trap – It’s an asynchronous way for the customers to subscribe for a subset of events.

This post will only cover the SNMP trap. The SNMP monitoring will be discussed in later posts.

How SNMP Alert works

As explained in the previous post https://community.emc.com/people/v_shen/blog/2018/04/27/hello-world, OneFS sends traps when CELOG events occur, sending them through configured SNMP trap channels. Internally SNMP traps are sent by process snmpinform or snmptrap with appropriate parameters to a 3rd party SNMP management console in the client side.

SNMP.png

Isilon OneFS SNMP Trap List

I’ve uploaded a SNMP trap list for OneFS 8.1.1.0 at SNMP Trap List for OneFS 8.1.1.0

This lists all the SNMP traps supported in 811 and how they are mapped to the event groups. (between SNMP OID and Event Group ID)

temp.jpg

With the combination of this SNMP trap list and Event Reference (https://support.emc.com/docu84283_OneFS-8.1.0-Event-Reference.pdf?language=en_US), you can get a very detailed information of each SNMP trap.



Example:



To get the detailed info on a specific SNMP trap – e.g. diskPoolUsageCrit, find this in the list attached and note down the ID which in this example is 100010015

temp2.jpg

Then query this ID in the Event Reference guide, then you can get the details for this trap as below:

temp3.jpg

Thanks for your time and leave me any comments or email me if you have any questions. (vincent.shen@dell.com)

Related:

QRadar – SNMP Trap based on QID Rule

Hi all,

I’m trying to make QRadar send me alerte via SNMP Trap when occures a system error but I’m having issues while configuring it…

For instance, I would like to be warned when the system is loosing events based on a rule logging this specific QID. My rule is quite simple and goes like this : and when the event QID is one of the following (38750060) Event pipeline dropped events. I hit “SNMP Alerte” on the next page and done.

Then I’m flooding QRadar but I’m not receiving the alerte which is very special because I’m receiving a notification on the Web interface (one again, it’s freak because I disabled all the other rules sending notification…).

I sure that :

  1. My network is well configurated
  2. My SNMP server/client also
  3. My custom Trap Profil too because I’m receiving other TRAPs.

My questions are :

  • Did I made a mistakes in my rule ?
  • How the system is creating this notification (rule or other thing…?) ?

Did I missed something else ?
Thanks for you help

Related:

Traps

I need a solution

 
while these messages sent via trap, I would like to better understand the message, what specific event is the same as critical?
 

18/10/2017 14h10min13s GMT-03:00

SERVIDOR  Unknown alert received from device SERVIDDOR of type GnSNMPDev. Device Time 328+15:21:45. (Trap type 1.3.6.1.4.1.3417.2.12.2.6.3) Trap var bind data: OID: 1.3.6.1.2.1.1.3.0 Value: 2839450531 OID: 1.3.6.1.6.3.1.1.4.1.0 Value: 1.3.6.1.4.1.3417.2.12.2.0.3 OID: 1.3.6.1.4.1.3417.2.12.1.1.1.0 Value: Health Monitor (CRITICAL): Health Check Status is ‘CRITICAL’ System     GnSNMPDev 0x10801 10
 

18/10/2017 14h10min5s GMT-03:00

SERVIDOR An event occurred for model ‘SERVIDOR’ of type ‘GnSNMPDev’ for which no event format file exists. System     GnSNMPDev 0xfff00173 10
0

Related:

AgentBuilder – SNMP Event Specific trap not received in the correct group

Hi,
I’m working on a AgentBuilder agent that contain many SNMP Event attributes groups.
My agent must receive traps with known specific enterprise Oid and from all other, so I have 1 group “All Traps” for all traps, and some groups for specifics traps with custom OiD.

For example, if I test the custom group “HTTP trap” alone, It receive the trap correctly, but when I test the full agent my spécific trap is received in the group “All Trap” and not in the “HTTP trap” group. If I remove “All Traps” from my agent and I test again the trap is well received in “HTTP trap”.

I’ve tried to separate custom group with subnode, the problem is still the same.
If I put “All_trap” in a single subnode, my customs groups well receive specifics trap, but “All trap” don’t receive nothing.

Oid filter look like this : 1.3.6.1.4.1.16077.2-2

Thx

Related:

Smarts SAM: trap-notify.conf file returns the following error when starting the service – TrapConfiguration::Trap-Configuration: Expected assignment for property ‘Destinations’, got: ‘= { {“xxx252”, 162, “V1”},’

Article Number:494241

Article Title and Link for Registered Users: Smarts SAM: trap-notify.conf file returns the following error when starting the service – TrapConfiguration::Trap-Configuration: Expected assignment for property ‘Destinations’, got: ‘= { {“xxx252”, 162, “V1”},’

Affected Product(s): Smarts Service Assurance Manager,Smarts,Smarts Service Assurance Manager 9.4,Smarts Service Assurance Manager 9.3

Article Summary:The following has been inserted in the trap-notify.conf file: serverName = “xxx92:9001/AGGR-SA”11:46:07 Destinations = { {“xxx252”, 162, “V1”}, Upon starting the Trap Notifier Adapter, we get the following errors in the log file: [December 2, 2016 1:31:33 PM GMT+02:00 +577ms] t@1503405680 sm_notify ASL_MSG-*-ASLP …

Article Last Updated:January 09, 2017

Please note that this abstract is machine-generated. Registered users should click the above link to view the entire knowledge article from Dell EMC Online Support, otherwise please contact Dell EMC Customer Service for further assistance.

Related:

  • No Related Posts