Lms 4.2 interface down alert

Hi
I receive email when an interface comes down but because i have a lot of routers with a lot of interfaces i can' tell which one came down , is there any way to include the description under the interface in the email ?
Also can i monitor the existence/not of specific route in the routing table and receive email ?
I appreciate any reply
Sent from Cisco Technical Support iPhone App

yes ,i receive the same alert but the case i have like 60 routers and lots of interfaces on every router so interfacse s0/0/0.1 is meaningless for me so i need the alert includes the description configured under the interfaces via CLI
Thanks for your reply
Sent from Cisco Technical Support iPhone App

Similar Messages

  • Unidentified traps and interface down alerts LMS 4.2

    Hi all,
    Sometimes we have unidentified traps in our log, we don't know where they come from.
    In high severity faults we see an active alert with device name “Unidentified” event name unresponsive but with a certain ip address.
    What are these alerts about? Can I filter them?
    A second issue I have is that I get interface down alerts. But when we log on to the device, there is no interface down at all. We can also ping the device from the lms server at that time. I have been told that the admin state and operational state has to be up.
    Thanks,
    Best Regards,
    Joris

    Hi Joris,
    Generic trap support is a new feature introduced in LMS 4.2 release. look at the below
    document also.
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.2/user/guide/lms_monitor/TrapFwd.html#wpxref13049
    LMS 4.2 release onwards DFM will display any unprocessed traps comming from device in
    fault monitor screen as unidentified trap under Inform alarm.
    For the other issue , it could be a DFM database issue , try to REDISCOVER those devices in
    DFM and see how it works
    Thanks
    Afroz

  • CISCO Prime Infrastructure 2.0 Link UP DOWN ALERT

    Hi,
    I want to monitor core switch link up down status and ignore all the access switch link up down. How do I do that? My core switch is nexus 7009 and my access switch is 2960s.
    I have tried configuring port group for core switch and access switch and only deploy interface health template to my core switch port group but I still receiving link down alert from my access switchport even without deploying the template to my access switch.
    Am I doing it the right way? Help please. Thank you.

    Hi Rafael,
    Here is the config:
    snmp-server community cxxx_ro RO SNMP_ACL
    snmp-server community cxxx_rw RW SNMP_ACL
    snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
    snmp-server enable traps transceiver all
    snmp-server enable traps tty
    snmp-server enable traps cluster
    snmp-server enable traps entity
    snmp-server enable traps cpu threshold
    snmp-server enable traps rep
    snmp-server enable traps vtp
    snmp-server enable traps vlancreate
    snmp-server enable traps vlandelete
    snmp-server enable traps flash insertion removal
    snmp-server enable traps port-security
    snmp-server enable traps auth-framework sec-violation
    snmp-server enable traps dot1x auth-fail-vlan guest-vlan no-auth-fail-vlan no-guest-vlan
    snmp-server enable traps envmon fan shutdown supply temperature status
    snmp-server enable traps power-ethernet group 1
    snmp-server enable traps power-ethernet police
    snmp-server enable traps fru-ctrl
    snmp-server enable traps config-copy
    snmp-server enable traps config
    snmp-server enable traps config-ctid
    snmp-server enable traps energywise
    snmp-server enable traps rtr
    snmp-server enable traps vstack
    snmp-server enable traps bridge newroot topologychange
    snmp-server enable traps stpx inconsistency root-inconsistency loop-inconsistency
    snmp-server enable traps syslog
    snmp-server enable traps mac-notification change move threshold
    snmp-server enable traps vlan-membership
    snmp-server enable traps errdisable
    snmp-server host 10.189.x.x version 2c cxxx_ro
    snmp-server host 10.189.x.x version 2c cxxx_ro
    and this is the switch interface 
    interface FastEthernet0/1
     switchport access vlan 28
     switchport mode access
     srr-queue bandwidth share 1 30 35 5
     priority-queue out
     mls qos trust cos
     no snmp trap link-status
     auto qos trust
     spanning-tree portfast
    and yes I configured that on all access port in all switches.
    Regards,
    Syafiq

  • I can no longer preview my iMessages in the pull down alerts. Any ideas

    I Can no longer preview my iMessages in the pull down alerts.  Any ideas?

    Reset the device:
    Press and hold the Sleep/Wake button and the Home button together for at least ten seconds, until the Apple logo appears.
    If that doesn't help, tap Settings > General > Reset > Reset All Settings

  • Intermittant radio interface down on 1130 APs

    I am having unified wireless installation, with WiSM on 6500 at central site and around 90 nos of 1130 APs located at remote locations ( over WAN) as well as some APs locate in the same location.
    The APs are configured in WCS, using default AP template.
    Alsomot all APs are showing minor alarms saying " radio interface threshold violated".
    In addition, a major alarm posted frequently on WCS saying "radion interface down".
    Cleints are complaining that they are loosing connectkion momentarily but connected again automatically wo WLAN. But they will have to log in to application programs in such cases.
    a.Does anybody have similar experience, and
    b. What are the best settings for 1130 APs trhat we have to do explicitly in setting up the WCS template ?
    Thanks ,

    Might be due to interference and the fact that RRM is enalbled and the ap's are changing channels causing the radios to shut down temporarily. Either set the channel or try to change the threshold.
    Here is the error info:
    http://www.cisco.com/en/US/docs/wireless/wcs/4.2/configuration/guide/wcsevent.html#wp1139158

  • VIF Bound Physcial Interface Down

    Hi Guys!
    We are trying to connect FI 6248 (UCSM 2.1.1a) to Brocade 6510 swtich(One FI to one of the two Brocade switches separately). The ports are configured as FC Uplink port and the FI's work in End-host mode. We created the service profile. After associating the SP to one of the blades the two errors occurs immediately:
    VIF <number> Bound Physical Interface Down
    VIF <number> Bound Physical Interface Down
    and this relates to the 2 vHBAs created in SP. Is this normal situation if OS isn't already installed on the host? We can't configure SAN zone from the brocade side because we don't see any WWPNs of the configured vHBAs in the SP. We see only FI's WWPNs(as I think). NPIV mode is enabled from the Brocade side. 
    Can someone explain what can cause this problem?

    Sergey,
    This is expected if there is no OS installed yet, see the possible reasons for the VIF down in this bug:
    https://tools.cisco.com/bugsearch/bug/CSCul99847
    Rate ALL helpful answers.
    -Kenny

  • Bringing an interface down using a network profile

    I use netcfg to switch between network profiles... but when I switch from a profile using ethernet to a profile using wireless, it just adds the other interface... so that both ethernet and wireless are up.
    The only way I know to bring an interface down (say, ethernet) is to edit NET_PROFILES in /etc/rc.conf and put in a profile using wireless, and do /etc/rc.d/network restart.
    But is there an easier way? Is there some sort of command I can put inside my profile which uses wireless to bring down the ethernet interface?
    Thanks.

    I'm not infront of a Linux box right now, but perhaps if you could run, as root:
    # ifconfig eth0 down;
    of course, replace eth0 with the appropriate interface you wish to take down.
    p.s. - I hope i'm not completely getting your question wrong because I feel I may be.

  • Force dialer interface down

    Can I force dialer interface down until some one dials in?
    Sent from Cisco Technical Support iPhone App

    The router is configured as a hub VPN sever for my mobiles users.
    I don't have the option for dynamic routing due to the remote end.
    Primary connection is ip for mobile users. But if they can't use ip for any reason I want them to come in via Isdn.
    The hub needs to route ip unless it sees that the remote has come in via Isdn. I have considered a gre tunnel on the Isdn but that's over heads I'd prefer to avoid.
    Sent from Cisco Technical Support iPhone App

  • Sdlc interface down very often

    Hello,
    In my customer site, SDLC device connect to 2600. IOS version is 12.0.7T. Then access AS400 through DLSW function. We showed log and found the connected interface down very often. show log as below.
    We checked AS400 log and didn't find the SDLC device inactive ever. And we check SDLC device, the device work well, user didn't find any problem??
    We don't know why always log of message showed the interface down.
    Anyone can help me??
    .Jun 23 08:29:56 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
    .Jun 23 08:29:57 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to down
    .Jun 23 08:30:01 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to up
    .Jun 23 08:30:02 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to up
    .Jun 23 08:33:06 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
    .Jun 23 08:33:07 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to down
    .Jun 23 08:33:11 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to up
    .Jun 23 08:33:12 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to up
    .Jun 23 08:36:16 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
    .Jun 23 08:36:17 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to down
    .Jun 23 08:36:21 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to up
    .Jun 23 08:36:22 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to up
    .Jun 23 08:39:25 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
    .Jun 23 08:39:26 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to down
    .Jun 23 08:39:30 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to up
    .Jun 23 08:39:31 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to up
    JSB025a#sh inter se 1/0
    Serial1/0 is up, line protocol is up
    Hardware is CD2430 in sync mode
    Description: connect to SNA pu2.1
    MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,
    reliability 255/255, txload 1/255, rxload 1/255
    Encapsulation SDLC, loopback not set
    Half-duplex enabled.
    cts-delay 0 milliseconds
    dcd-txstart-delay 100 milliseconds
    dcd-drop-delay 100 milliseconds
    transmit-delay 0 milliseconds
    Errors - 0 half duplex violation
    Router link station role: PRIMARY (DCE)
    Router link station metrics:
    slow-poll 10 seconds
    T1 (reply time out) 3000 milliseconds
    N1 (max frame size) 12016 bits
    N2 (retry count) 20
    poll-pause-timer 10 milliseconds
    poll-limit-value 1
    k (windowsize) 7
    modulo 8
    sdlc vmac: 4000.2625.01--
    sdlc addr 01 state is CONNECT (xid-poll)
    cls_state is CLS_IN_SESSION
    VS 5, VR 0, Remote VR 5, Current retransmit count 0
    Hold queue: 0/200 IFRAMEs 116636/58170
    TESTs 0/0 XIDs 40235/14460, DMs 6784/6736 FRMRs 0/0
    RNRs 7/0 SNRMs 9757/0 DISC/RDs 9733/0 REJs 0/0
    Poll: clear, Poll count: 0, ready for poll, chain: 01/01
    Last input 00:00:00, output 00:00:00, output hang never
    Last clearing of "show interface" counters 9w3d
    Queueing strategy: fifo
    Output queue 0/40, 0 drops; input queue 0/75, 0 drops
    5 minute input rate 0 bits/sec, 50 packets/sec
    5 minute output rate 0 bits/sec, 0 packets/sec
    156063821 packets input, 318338246 bytes, 0 no buffer
    Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
    11 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 11 abort
    155708948 packets output, 337016303 bytes, 0 underruns
    0 output errors, 0 collisions, 43092 interface resets
    0 output buffer failures, 0 output buffers swapped out
    106807 carrier transitions
    DCD=up DSR=up DTR=up RTS=down CTS=down

    Hi,
    I believe that your line keeps bouncing due to Data
    Carrier Detect(DCD) going down. I didn't see a copy
    of the interface config but do you have the following
    command under your interface?
    half-duplex controlled-carrier
    This in conjunction with the dcd-txstart-delay and
    dcd-drop-delay settings will cause the DCE to drop
    DCD frequently.
    These are for very specialized environments which
    probably are not what you have.
    What is your environment, with respect to the
    connection to the AS/400? Is it just a Cisco DCE
    cable connected to an AS/400 cable? Or are there
    other cables/switches/modems involved?
    If you just have the Cisco DCE cable connected to
    the AS/400's cable then you do not need that command.
    Otherwise, it is possible you have a cable or
    physical interface problem.
    Please include your interface's config if this
    information wasn't enough to resolve the problem.
    Thanks and regards,
    Ed Mazurek

  • RRI not removing routes even with outside interface down

    Hi,
    I'm having trouble with RRI and static crypto map.
    If I configure the RRI with the outside interface down the ASA doesn't create the static route to the remote subnet.
    If I bring up the interface it creates the route, but if I shutdown the interface the RRI routes never go away meaning the ASA would turn into a  black hole.
    Any suggestion on how to get it to remove the RRI routes if the interface is down?
    I tested it with two versions with the same problem:
    9.2(2)4 
    9.3(1)

    We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash ID's to help us learn more about your crash.
    #Enter about:crashes in the address bar (that's where you enter your website URL) and press Enter. You should now see a list of submitted crash reports.
    #Copy the 5 most recent crash ID's that you see in the crash report window and paste them into your response here.
    Thank you for your cooperation!
    More information and further troubleshooting steps can be found in the [[Firefox crashes]] article.

  • F0283 VIF 1 / 2 B-42/44 down, reason: Bound Physical Interface Down

    Hi
    I have some issues after migrate from CX4 SAN to VNX SAN. Everything is moved from CX4 to VNX and I have disabled FC Uplink port that is connected to CX4. Both my FI's is only connected to VNX.
    We want SAN boot on our ESXi host, and some of them is install on a boot LUN on VNX, and some other is install local at the Blade.
    My issue is that all my host shall boot from SAN. But suddenly this fails.
    I zones the host on our MDS switches, and does everything in VNX, so the host shall see its boot LUN. SAN Boot Target is changed so it sees the VNX SAN.
    In the install I see my boot LUN, and install ESXi without any issues. Remove the installation media and reboots the server.
    When it shall boot back up, it says:
    Reboot and Select proper Boot device
    or Insert Boot Media in selected Boot device and press a key.
    And i gets 8 major error messages like this:
    VIF 1 / 2 B-42/44 down, reason: Bound  Physical Interface Down
    What is wrong. I do the same thing now, as I did when I installed the hosts that is working.

    Can you try to re-ack the Server the Profile is associated to.  The error you're seeing usually means the host Iniitator interface (VIF) is down because it has no uplink to correclty pin to.  You said you shut down the ports the CX4 was previously connected to by disabling it.  Can you re-ack the blade which should re-pinn to the new/remaining uplink.
    If that doesn't correct the problem I'd look into your boot policy.  Double and triple check the boot targets entered in the profile and make sure they match the targets on the VNX, and that each one is online and logged into the MDS ("zone flogi database").  The symptoms you're seeing used to be common with Clariion arrays as they are Active/Passive.  During the installation any available path has access to the LUN for the installation, but they rebooting required the first listed target in the boot policy to be the "owner" of the LUN.  This was easily fixed by trespassing the LUN to the other Storage Processor on the array.  With VNX I'm pretty sure they are Active/Active arrays so this shouldn't matter.
    Regards,
    Robert

  • LMS 4.x Interface Availability

    I have an issue where I want to remove an interface from a device on the network, but I can't get LMS to not show it as down on the monitoring dashboard under Interface Availability. I've removed the IP from the interface and put it in admin shutdown, but it continues to show up as down in the Interface Availability chart. I also tried setting it to false under DFM for monitoring, but that didn't work. What is the correct way to remove an interface that shows down under Interface Availability that isn't actually down due to an error? It has been days since I shut down the interface.
    Thank you,
    Mark     

    Marvin,
    Thanks for the reply. So you are saying that setting the interface to false in DFM removes it from the Interface Availability report on the Monitor Dashboard for you? That would make since to me, but it is still there. I did remove and re-add a device the last time I saw this issue, but thought there has to be a better way. When setting to false under DFM didn't work, I thought maybe that was just for alert generation and not the Interface Availability dashboard widget. I hate having to reboot servers. It seems this one has to be rebooted too often to fix minor issues like this.
    Thank you,
    Mark

  • MDS 9509 - How to filter interface email alerts

    I have configured interface alert filters in the Admin/Events/Filters/Interfaces tab. In this tab I un-clicked the interfaces that I don't want to see alerts on. However, I still get email alerts on these ports that I un-clicked.

    I believe this alert filter only applies to SNMP traps, by unchecking specific port you will not be getting link up/down generic SNMP
    traps anymore.

  • Cisco Messaging Interface down

    Hi all,
    I'm having an issue on a CUCM machine running 6.0.1.2112-1. If I run the RTMT I get to see numerous of alerts saying:
    'Service status is DOWN.
    Cisco Messaging Interface...'
    The alert keeps popping up every 30 seconds.
    Can anyone tell me what the cause of this alert could be, and how it can be solved?
    With kind regards,
    Paul van den IJssel
    Digacom, The Netherlands

    Hello Paul --
    I assume that you are using Cisco Unity/Unity Connection/Unity Express for the voicemail platform. If so, you will not need the Cisco Messaging Interface service and you can deactivate it from the serviceability pages. The service is only needed for external voicemail systems that are not Cisco.
    Please let me know if you have any other questions. I hope this helps. Please rate helpful posts.
    Thanks,
    Ohamien

  • Email notifications Interface down

    Greetings!
    I've been struggling with this for most of the day. I am attempting to get email alerts when an interface goes down or up. I would like to specify the interfaces that I am monitoring. I've tried various things to accomplish this but I don't seem to be able to get it to work. Has anyone out there successfully configured this? These are things that I could easily do in Solarwinds.

    Hello,
    email alerts are a notification mode of a management software. There are a lot of software (FMS Pandora, Cacti,
    nagios...). You should configure snmp traps in your router. A collector daemon (software) and then execute some
    actions (as sending a email). If you have some experience with syslog daemon, router can send syslog messages
    (I prefer syslog to snmp traps). A syslog daemon (syslog-ng) receives the message and then react with a mail.
    Regards.

Maybe you are looking for