HiPath 4000 V6 SNMP Error Trap

[Flame8888]

Hi
I am currently running HiPath 4000 V6. SNMP is enabled. Error traps are reporting to the IP address configured.

I am currently running an FBUS SET600 ISDN device on a STMD3 board. When the board loses connectivity to the terminal placing it in UNACH state/ error condition ie. Layer 1 down, I want the HiPath 4000 to send an error trap to the SNMP server that I have setup.

Does anyone know what FXXXX alarm is used to report this particular event? I tried running through the alfe tool and read all error messages and events but cannot find any events relating to this particular scenario. in short when a terminal goes down, layer one error, I would like an event triggered.

Regards
Flame8888

 

[sbcsu]

I don't know if it will send ISDN errors out as an SNMP message but try this.

Plug in your ISDN phone and test to see if it is working
DEL-HISTA;
ADD-HISTA:10000,DEACT;
Unplug the phone
STA-HISTA:SEARCH;
you should see the error there in the history
If you don't see any error after a while then its possible that the error has been deactivated.
Check to see if that is so by
DIS-SIGNL:LOCKMSG;

 

[Flame8888]

I have checked Hista and there are two fault messages:
F5454 and F5453 coming up for this error condition.

SNMP error traps are enabled for these two i.e. F5454 and F5453. However no traps are generated to SNMP server. These only appear in Hista.

Is there something else I need to turn on? I've also tried to reboot H4K Assistant, still the behaviour persists.

 

[sbcsu]

Are ANY traps sent to the SNMP server?

 

[Iamnothere]

Did you import the MIBs that are provided inside the V6 system?

 

[Flame8888]

sbcsu
Yes, SNMP errors are sent to the SNMP server, most prominent are F4057 (DBAR errors). In the HISTA file, F5453 is the one I am also worried about which does not appear in the SNMP Server messages. I have also tried to disable and enable the SNMP service under base admin to see if it helps, still no luck. Version identification: RMX R1.12.7/Assistant R1.13.2/ Platform R1.12.0.

Iamnothere
Yes, MIBs were imported from HiPath 4000 SNMP configurator and configured on the SNMP server.

 

[Iamnothere]

I will have a look today. Will post if I discover anything.

 

[Iamnothere]

Sorry - I completely forgot about this. I will do my best to check today. Due to various issues, in recent months my availability to view Tek-Tips has been diminished. I read some of the postings this morning. Nice job SBCSU!

 

[sbcsu]

Thanks Iamnothere?

Original Poster can you please see if any of the fault messages are locked
DIS-SIGNL:LOCKMSG;

 

[Iamnothere]

In the Assistant -> Diagnostics -> Fault Management -> SNMP Configurator -> Fault Trap Configuration screen:
the Fault Codes F5454 and F5453 appear on the RIGHT side of the screen in the "Enabled fault traps" window, correct?
And you have clicked "Save configuration", correct?

The "FM_SNMP" process may not restart, as it should, when the "Save configuration" button is clicked. Therefore I suggest that you manually reset the SNMP process.
First, access your V6 system's Linux by logging in as "root" user at the Linux console.
Then use the ssh command to login to the Assistant Linux/virtual machine.
Do this by following this format: ssh -l engr IP_Address_of_Assistant (that's a -lower case "L")
Assistant's Linux/virtual machine should prompt you for the "engr" password - enter it. You should now be inside the Assistant virtual machine.
Type the following:
procadmin -l (again a -lower case "L"). Do you see the process for Fault Management/SNMP (FM_SNMP) with a status of ACTIVE? You may need to scroll up/down. Does the date/time for that FM_SNMP process indicate that the SNMP service restarted when you last clicked the "Save configuration" button?
If not, type these two commands to terminate/start the FM_SNMP process:

procadmin -t -g FM_SNMP (switches OFF the SNMP service)
<wait one minute>
procadmin -s -g FM_SNMP (switches ON the SNMP service)
Now type procadmin -l just to verify that the FM_SNMP service is once again ACTIVE.
Type "exit" to back-out of the Assistant virtual machine.
Type "exit" to back-out of the 4K system's Linux.
Now check and see if the F5454/F5453 traps are showing up on your SNMP trap server.
If not, someone else with more SNMP experience will need to provide assistance.
DO NOT PLAY AROUND INSIDE THE Assistant Virtual Machine or in the system's Linux. DANGEROUS!

 

[Flame8888]

Thanks sbcsu and iamnothere

Sbcsu: no entries under signl:lockmsg;

Iamnothere: will try restarting the service in virtual machine. I'll let you know happens.