Re: OpenSM: reporting traps 129, 130, 131

2009-11-13 Thread Hal Rosenstock
On Thu, Nov 12, 2009 at 3:36 PM, Sasha Khapyorsky sas...@voltaire.com wrote: On 11:38 Thu 12 Nov     , Hal Rosenstock wrote: We've cared for several years now (babbling port policy was introduced into the master on 7/6/07) but this issue still persists. Are you saying no reports for these

Re: OpenSM: reporting traps 129, 130, 131

2009-11-12 Thread Hal Rosenstock
On Sun, Nov 8, 2009 at 9:37 AM, Yevgeny Kliteynik klit...@dev.mellanox.co.il wrote: Hi Sasha, I noticed that OpenSM doesn't send InformInfo on traps 129/130/131. This is what osm_trap_rcv.c is doing: 322: static void trap_rcv_process_request(IN osm_sm_t * sm, 323:                            

Re: OpenSM: reporting traps 129, 130, 131

2009-11-12 Thread Sasha Khapyorsky
On 08:46 Thu 12 Nov , Hal Rosenstock wrote: Any particular reason why there's no reporting of these traps? AFAIK it's been this way for at least the last 5 or 6 years. Yes, this is what I found too tracking down git/svn history. A practical consideration in changing this is that

Re: OpenSM: reporting traps 129, 130, 131

2009-11-12 Thread Sasha Khapyorsky
On 11:38 Thu 12 Nov , Hal Rosenstock wrote: We've cared for several years now (babbling port policy was introduced into the master on 7/6/09) but this issue still persists. Are you saying no reports for these traps until the trap rate is obeyed ? If existing trap rate filtering in OpenSM