This post is more than 5 years old
13 Posts
0
2287
January 25th, 2010 11:00
Disable call home for port up/down
I can sucessfully monitor my fabric via e-mail alerts but I am getting too many alerts due to port status changes. Is there a way to supress an alert each time a F port goes up or down?
Thanks
No Events found!
healyj
141 Posts
0
November 28th, 2017 07:00
Hi there,
In our efforts to clean up the forum, we came across your question / statement.
If the question / statement is still valid, not expired and you need an update please reach out again and we try to get it answered.
As for now we set it to “answered.”
Regards,
Jim
MancMan1
13 Posts
0
January 25th, 2010 12:00
I have tried this and did an admin up/down on the port. Still got an e-mail. Maybe this setting is only for SNMP traps?
Thanks
dynamox
9 Legend
•
20.4K Posts
0
January 25th, 2010 12:00
Can you go into Device Manager, Admin, Event Filters, interfaces ..and uncheck ports you don’t want to send traps when ports go up/down
This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.
If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).
dynamox
9 Legend
•
20.4K Posts
0
January 26th, 2010 06:00
MancMan1
13 Posts
0
January 28th, 2010 09:00
You define your SMTP server under call home on the MDS. So I guess it mails directly.
Thanks
MancMan1
13 Posts
0
January 28th, 2010 15:00
ConnectrixHelpe
259 Posts
0
January 28th, 2010 15:00
There is also the same option in SAN-OS at latter version of code for those who need it.
Thank you.
ConnectrixHelpe
259 Posts
0
January 28th, 2010 15:00
Just a couple questions I want to verify and I apologize if you already covered them.
I'll assume you are using MDS and Email Home directly to EMC. If so the EMC Email Home guide covers this area (see below). Please let me know the answers the above questions and if the delayed traps feature noted below would be of help to you.
Thank you.
In previous code versions Fabric Manager listens to interface traps and generates EMC Email Home email messages immediately. Link traps are generated when an interface goes to down from up or vice versa. These link traps can be initiated for both real failures and other conditions. Link traps are created are created when a scheduled server reboot happens. EMC Email Home via Fabric Manager monitors these link traps and generates an email notification on them. The alerts from servers reboots can and did created multiple invalid service requests. These invalid service requests made finding real port issues extremely difficult. A better way was needed to filter out these invalid alerts and concentrate on real port issues.
Cisco NX-OS Release 4.1(1b) and above provides the ability to generate a delayed trap so that invalid alerts for host reboots is removed or at least minimized. Delayed traps filters server reboots and avoids generating unnecessary EMC Email Home email messages. This feature is applicable only for F/FL ports. When a switch is configured to use the delayed traps feature, instead of generating the trap immediately after the F/FL port goes down, the switch waits for the specified delay timer (default = 4mins) and then sends the trap. If the port comes back up in the specified timer value, the trap is not sent. This reduces the number of emails generated and intervention of customers and EMC Support. In Cisco NX-OS Release 4.1(1b) and above, users have the ability to select the current existing feature or this new delayed trap feature. Delayed traps can be enabled using both Cisco Fabric Manager and the CLI.
AranH1
2.2K Posts
0
January 28th, 2010 15:00
Nice to hear there is a better option in NX-OS.
Currently on all my MDS switches I run 'no link-state-trap' on all interfaces except storage array ports and critical host ports. I was getting too many alerts just from random hosts rebooting.
ConnectrixHelpe
259 Posts
0
January 28th, 2010 19:00