Critical Alarm for Nexus 7010 device

Hi Team,
We are getting Critical Alarm for the Data center device Nexus 7010 continuously from 28-Oct.
error (device hde1) in start_transaction: Journal has aborted - kernel
2012 Oct 29 10:00:18.227 DC-Core-Switch2 29 10:00:18 %KERN-2-SYSTEM_MSG: EXT3-fs
error (device hde1) in start_transaction: Journal has aborted - kernel
2012 Oct 29 10:28:37.497 DC-Core-Switch2 29 10:28:37 %KERN-2-SYSTEM_MSG: EXT3-fs
error (device hde1) in start_transaction: Journal has aborted - kernel
2012 Oct 29 10:28:42.398 DC-Core-Switch2 29 10:28:42 %KERN-2-SYSTEM_MSG: EXT3-fs
Also attaching the complete logs collected for this device and suggest if there is any Hardware related issue or some Software related issue.
Regards,
Ashutosh

Hello
hde1 is the logflash device. Looks like there were IO errors and the kernel mounted the fs read-only. You can try to reload the device and if logflash will come back up fine after the reload, its a transient issue; if the issue comes back, the logflash device most likely is damaged bad and needs to be replaced. You will need to open a service request with TAC to get it replaced.
HTH,
Alex

Similar Messages

  • Alarms for Third party devices on Cisco PI v 2.1

    Is it possible to receive alarms for third party devices in Cisco Prime Infrastructure 2.1? If so how do i configure PI to show the alarms?

    Hi,
    AFAIk, It is not possible to receive alarms for third party devices in Cisco Prime Infrastructure 2.1.
    we have very limited support of 3rd party devices in PI. third party devices only snmp polling, snmp traps and syslog will work
    Third-party support   
     ●  Ability to discover and monitor third-party (non-Cisco) switches that support RFC 1213 and wireless controllers/access points from Aruba Networks
    Thanks-
    Afroz
    ****Ratings Encourages Contributors ****

  • Ciscoview Package File for Nexus 7010

    I found an old support modules table at
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_ciscoview/device_support/table/cvsdt.html
    dated Feb 28, 2012. I cannot find one newer.
    I have LMS 4.1 and I'm trying to render a Nexus 7010 in Ciscoview. I have downloaded the latest package files. The Sup2 and Fab2 modules (N7K-SUP2 and N7K-C7010-FAB-2) show as "unsupported card".
    What packages and versions are required to recognize this card with LMS 4.1?

    The Sup2 requires 9.0 of the package file (dated 1/2/2013). You can download it here. (Click all Releases, 6.1.0, then choose the Nexus 7000 package.)
    The readme is here. It mentions the N7K-C7009-FAB2 is supported (since 7.0) but nothing about the 7010-FAB-2 so you may still be out of luck on that one.

  • Critical Alarms from LAPs in Maintenance State

    Should a critical alarm be triggered when an LAP disassociates from a WLC if it is placed in Maintenance State before it's taken offline?
    Should I delete, clear or acknowledge the critical alarm if a LAP was taken offline before it was placed in Maintenance state?
    Should I still put LAPs in maintenance state if they were taken offline before I had a chance to?
    Using Cisco Prime Infrastructure version 1.2

    I just upgraded CPI to version 2.2 and the controllers to 7.6.130 and I'm still getting the same result.
    I'm getting critical alarms for APs in Maintenance State.

  • How can I remove default alarm for events in iCal on devices ios?

    Whenever I add an event to my iCal calendar in Mounain Lion it will automatically add one default alert only on my iphone and ipad. These default alarms are not displayed on my macbook or icloud.com
    Default alarms are disabled in macbook, icloud.com, and my ios devices.
    How can I remove default alarm for events in iCal on devices ios?
    Thanks and sorry for my english.
    MacBook Pro, Mac OS X 10.8

    OK, so I have had this issue for the past several months. I think it all started when I upgraded to ML from SL and migrated my calendars and contacts to iCloud. That was a couple months ago. But now I am running 10.8.2, and about two weeks ago I upgraded my iOS devices to 6.0.1.
    I don't seem to be having any issues with events that I create now, but all those old events that were migrated to iCloud a couple months ago, many of those sound alerts on the iOS devices even though there was no alert defined when the event was originally created. I have always had alerts off by default both in iCal and on the iOS devices.
    So here's the question: is there a way to go through and disable all these spurious event alerts? I've been disabling them as the event reminders come up, but it's irritating. It would be nice if there was a way to turn them off all in one shot somehow.

  • Data Center Hall Temperature for Cisco Nexus 7010

    Hi,
    I Have a Nexus 7010 that sometimes raise an alarm about temperature thresholds that are being exceeded.... I was wondering if Cisco has a recommendation (or best practice) about the correct temperature that the Nexus need in the cold and hot hall of the data room. I know that the operative temperature of nexus is 0 - 40°C but i´m not sure if my halls are in the best temperature.

    Hi Salvador,
    As long as you keep your Data Center environment in this operative range your N7K will be fine.
    The usual is around 18°C and 24°C.
    Richard

  • In reviewing the Cisco Licensing Guide, there is a license part number for MPLS on the Nexus 7010. Part Number is N7K-MPLS1K9.

    In reviewing the Cisco Licensing Guide, there is a license part number for MPLS on the Nexus 7010.  Part Number is N7K-MPLS1K9.  Is there a corresponding part number for the Nexus 7710?

    For the benefit of others, here is what we found. The N7K was hitting the bug CSCtg95381.
    Symptom
    Nexus 7000 may punt traffic to CPU; so that the traffic may experience random delay or drop.
    Further looking, ARP is learned and FIB adjacency is in FIB adjacency table.
    Conditions
    The problem is caused by race condition. Some hosts have not responded to the ARP refresh sent by
    N7k which in turn  trigger to delete  ARP entry  due to expiry. As a result   the route delete notification is
    sent   to URIB from the process. However there is still traffic coming to   given IP address as a result  the next packet that hit glean resulting   in triggering ARP and  hope ARP is learnt from the host this time.
    Workaround
    (s):
    Clear ip route < host>.
    Not  totally explains why it was working for certain client-server  combination but yet the workaround is holding well for end-points when  implemented.
    There  would be no host route for the destination server in the adjacency  manager on N7K-01. The only thing thats there is the subnet route  pointing towards the vlan gateway address. Implementing the work-around,  a new /32 route can now be seen in the adjacency manager for the  server.
    The bug is fixed in releases starting 5.1(5). Planning to upgrade to 5.2(3a).
    Regards, Rashid.

  • Nexus 7010 bgp state change alert not triggered to NNM

    Hi ,
    BGP state change alert not triggered  to NNM on  Nexus -7010 for Monitoring.
    Details of the Device:
    Nexus 7010 :     
    Software
      BIOS:      version 3.22.0
      kickstart: version 5.1(3)
      system:    version 5.1(3)
    BGP neighbor status :
    Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
    172.16.1.2      4 65505 5089234 5194515    51359    0    0     6w2d 391
    172.16.1.3      4 65505 5044293 5146859    51359    0    0    30w4d 378
    172.31.11.3     4 15404  120744  114811    51359    0    0     1w6d 1
    172.31.42.3     4 65501 5261796 5264413    51359    0    0    2d06h 0
    Snmp trap enabled:
    snmp-server user admin network-admin auth md5 0x690c4ede8a88ba7f2de791dbe7a77f0a
    priv 0x690c4ede8a88ba7f2de791dbe7a77f0a localizedkey
    snmp-server host 172.30.0.55 traps version 2c xxxx
    snmp-server enable traps bgp
    Downloaded cisco-bgp4-mib version, bgp4-mib tried and performed snmpwalk  as given below
    nnmsnmpwalk.ovpl -c xxx 172.31.15.130 .1.3.6.1.4.1.9.9.187.0.6
    Error : No MIB objects contained under subtree
    nnmsnmpwalk.ovpl -v 2 -c xxx 172.31.15.130 .1.3.6.1.2.1.15.3.
    No MIB objects contained under subtree
    Kindly advise to resolve the issue
    Regards
    Hari

    You can set an alert for Warning State. This is feasible.
    Juke Chou
    TechNet Community Support

  • Best practices for attaching iSCSI devices

    Hello all,
    My environment: Nexus 5010 with 2148T FEX switches in the racks.
    Can (or should) I use the 2148T as the switch between clustered servers and the iSCSI SAN?  The SAN is a Dell MD3000i connected to Dell R710 servers, Win Ent 2008 R2 Server.
    Plans are to use two vlans so I have dual data paths to the SAN.  Being new to the Nexus, I'm not sure what the best practice/configuration is for that.
    Any suggestions on reading materials or best practice configurations would be appreciated!
    Thanks...
    Ted

    We recently implemented Nexus 7010s, 5020s, and 2248s in our data center. Now we would like to harden them from a security persective; are there any Best Practices available for hardening Nexus devices?
    Hi Carl,
    I dont think a specifc hardening document has been realsed but yes you can refer the generic ios based hardening and try with NX-OS which are all supported or not.
    http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080120f48.shtml
    Hope to Help !!
    Ganesh.H
    Remeber to rate the helpful post

  • How to do routing on N7K-F248XP-25E (Nexus 7010) ?

                       Hi all,
         Please educate me the following scenario : I have Nexus 7010 with 2 L3 modules, N7K-M132XP-12L and N7K-M148GT-11L. Now to increase more ports for end devices, I add in the module N7K-F248XP-25E and believe it's for Layer 2 switching only. Is there a way to do routing on these L2 modules without having to go to the L3 modules ? Thanks for all help.

    Is there a way to do routing on these L2 modules without having to go to the L3 modules ?
    No.  If you have an M1/M2 card and routing is enabled, the F2E card will "step down" and do Layer 2 work.  All Layer 3 work will be done by the M1/M2 card.

  • Nexus 7010 mgmt0 useage opinion

    As a Senior Network Engineer I have entered into a bit of a debate with our Architect about the use of the mgmt0 interfaces on the nexus 7010 switch (dual-sups, M2 and F2 linecards).
    I would like to know opinion of the Cisco support network.
    I believe the mgmt0 interface should left alone for control plane traffic only and Out Of Band management access (ie ssh).  At the moment I have made a subnet for all VDCs with the mgmt0 (vrf management) sitting in a common subnet.  The physical mgmt0 interfaces from both SUPs are connected a management hand off switch.  The mgmt0s also serves as our control plane for VPCs. The VPC peer-link however is using main interfaces of the line-cards.
    The opinions;
    - The Architect thinks we should use all the mgmt0 interfaces for snmp, ntp, tacacs netflow-analysis and switch management.
    - However, I think I should use a traditional Loopback to perform these functions within the linecards.  The mgmt0 should only be used if traditional restricted switch access has failed.
    My Basis;
    the Loopback never goes down, uses multiple paths (the OOB hand off switch could fail closing switch management access completely).  The mgmt0 should be used as a last resort of management access to CMP.
    Thoughts please - Cheers

    I see your point about wanting to mitigate the impact of losing the OOB switch. I don't think the mgmt0 interface going down is considered the level of failure that will trigger a Supervisor switchover though. That's the way I read the Nexus 7000 HA whitepaper (and what I've seen based on some limited experience with taking apart a 7k pair).
    So, no the 7k can't send you an SNMP trap or syslog message if it's configured management path is offline. Mitigation of that could be via your NMS polling the devices's mgmt0 addresses. No response = trouble in paradise. Investigation step would be to log into the 7ks using the loopback IP and local authentication since your TACACS source-interface (mgmt0) is offline and going from there.
    The handful I've built (mostly 5k setups) I go for a Cat 3k switch with dual power supplies as the OOB switch. Once one of those is setup and seen not to be DOA, it's generally going to stay up until someone goes in and uplugs it or initiates a system reload.

  • Syslog server for Monitoring Cisco devices

    I am looking for Syslog server to log all logs from Cisco devices. We have more than 800 cisco devices. Can anyone tell me what syslog server should i use to log these files.
    Thank you.

    Has anyone used the Cisco recommendation of Buliding Scalable Syslog Solutions?
    http://www.cisco.com/en/US/technologies/collateral/tk869/tk769/white_paper_c11-557812.html#wp9000318
    I used this in another organaztion and we were very successful, we currenlty use Netcool that feeds from a syslog and we get several non-actionable alarms and it's very time consuming for 13,000 devices.  I would only like to alert on 0-5 Cisco Syslog messages.  Below is the response from my Netcool Administrator (What are your thoughts?):
    From my Netcool Administrator:
    Regarding, using the Cisco syslog severity for alert control, I feel that is not the best way to control the work in Netcool.
    1. -- Cisco is not consistent with the use of this value.
        Examples:
            In this case the important message is the lower severity alert: I would consider the BGP-3-NOTIFICATION of a 6 level of Informational
            Aug  4 03:10:01 rtgara02r01m04-lb0.us.bank-dns.com 001458: Aug  4 03:10:01: %BGP-5-ADJCHANGE: neighbor 10.93.69.106 Down BGP Notification sent
            Aug  4 03:10:02 rtgara02r01m04-lb0.us.bank-dns.com 001459: Aug  4 03:10:01: %BGP-3-NOTIFICATION: sent to neighbor 10.93.69.106 4/0 (hold time expired) 0 bytes   
            This one is near the top level of serverity per Cisco but not all that severe in reality, further this syslog has a bug where the threshold is not even exceeded
            %ENVMON-1-CPU_WARNING_OVERTEMP: Critical Warning: CPU temperature 107C exceeds threshold 110C.  Please resolve system cooling immediately to prevent system damage
            This one is reporting a standard condition:
            %ILPOWER-5-POWER_GRANTED: Interface Fa0/24: Power granted
            Here is an example of a 1 where the voice group says that nothing is wrong:
            Aug  4 13:08:42 rtgcaa75u01-01.sw.us.bank-dns.com 047489: Aug  4 11:08:41: %IVR-1-APP_PARALLEL_INVALID_LIST: Call terminated.  Huntgroup \'1\' does not contain enough valid SIP end-points to proceed with a parallel call.

  • Critical Alarm with CM after uprgade

    Hi All.
    I upgraded my CM using the copy ftp install command and reloaded CM and all worked fine.
    I now noticed the following Critical alarm appears on the CM device:
    "Central Manager's secure store is initialized but not opened"
    Thanks
    Zubair

    Hi Zubai,
    When you reboot the Central Manager, you must re-enable secure store encryption manually. Disk encryption and CIFS preposition features on the remote WAE devices will not operate properly until you enter the secure store password on the Central Manager to re-enable secure store encryption.
    Please refer to the following document for more detail about re-initializing the secure store:
    http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v413/configuration/guide/other.html#wp1053890
    Best regards,
    Ahmad

  • Nexus 7010 fabric extender timing out

    Hello -
    We have a Nexus 7010 and we are testing out using the fabric extenders for a need.  We have a demo 2224 unit and have it connected to our M132XP-12 10G blade in the 7K but the FEX won't come online.  I would have figured a possible software incompatability but looking at the supported list for that as well as hardware everything seems to be in order.  This is what the status shows after it spends about 15 mins in the image download state.
    FEX: 111 Description: FEX0111   state: Offline
      FEX version: 4.2(1)N2(1a) [Switch version: 5.1(2)]
      FEX Interim version: 4.2(1)N2(1a)
      Switch Interim version: 5.1(2)
      Module Sw Gen: 21  [Switch Sw Gen: 21]
    pinning-mode: static    Max-links: 1
      Fabric port for control traffic: Eth2/20
      Fabric interface state:
        Po11 - Interface Up. State: Active
        Eth2/20 - Interface Up. State: Active
      Fex Port        State  Fabric Port  Primary Fabric
    This is looped in the log details until it times out:
    04/25/2011 15:31:41.986978: Module register received
    04/25/2011 15:31:41.987713: Registration response sent
    04/25/2011 15:31:41.987889: Requesting satellite to download image
    04/25/2011 15:32:00.105031: Module register received
    04/25/2011 15:32:00.105779: Registration response sent
    04/25/2011 15:32:00.105956: Requesting satellite to download image
    04/25/2011 15:32:20.191181: Module register received
    04/25/2011 15:32:20.191957: Registration response sent
    04/25/2011 15:32:20.192144: Requesting satellite to download image
    We ran a debug during this and these entries are displayed when looking for errors.
    2011 Apr 25 15:30:31.443745 fex: Reg resp: Failed to get card info for swcardid 132
    2011 Apr 25 15:30:35.472721 fex: Cardinfo: Unknown card id to get (132)
    2011 Apr 25 15:30:35.472753 fex: Reg resp: Failed to get card info for swcardid 132
    2011 Apr 25 15:30:41.495302 fex: Cardinfo: Unknown card id to get (132)
    I'm still doing some more searching which so far hasn't turned up much, wanted to see if anyone has some other insight??
    Thanks!

    Hi Jack -
    Thanks for the response.  Unfortunately, yes that is already complete.  I was hoping that would be an easy fix.  When we upgraded to 5.1(2) we did the 5.1 EPLD.  I ran the install all impact command noted below for the 5.1 EPLD just to make sure it didn't report anything else as needing upgrade.
    sho install all impact epld bootflash:n7000-s1-epld.5.1.1.img
    Compatibility check:
    Module  Type  Upgradable        Impact   Reason
         1    LC         Yes    disruptive   Module Upgradable
         2    LC         Yes    disruptive   Module Upgradable
         5   SUP         Yes    disruptive   Module Upgradable
         1  Xbar         Yes    disruptive   Module Upgradable
         2  Xbar         Yes    disruptive   Module Upgradable
         3  Xbar         Yes    disruptive   Module Upgradable
         1   FAN         Yes    disruptive   Module Upgradable
         2   FAN         Yes    disruptive   Module Upgradable
         3   FAN         Yes    disruptive   Module Upgradable
         4   FAN         Yes    disruptive   Module Upgradable
    Copy complete, now saving to disk (please wait)...
    Retrieving EPLD versions... Please wait.
    Images will be upgraded according to following table:
    Module  Type           EPLD      Running-Version   New-Version  Upg-Required
         1    LC  Power Manager              4.008       4.008           No
         1    LC  IO                         1.006       1.006           No
         1    LC  Forwarding Engine          1.006       1.006           No
         1    LC  SFP                        1.004       1.004           No
         2    LC  Power Manager              4.008       4.008           No
         2    LC  IO                         1.016       1.016           No
         2    LC  Forwarding Engine          1.006       1.006           No
         2    LC  FE Bridge(1)              186.006      186.006           No
         2    LC  FE Bridge(2)              186.006      186.006           No
         2    LC  Linksec Engine(1)          2.006       2.006           No
         2    LC  Linksec Engine(2)          2.006       2.006           No
         2    LC  Linksec Engine(3)          2.006       2.006           No
         2    LC  Linksec Engine(4)          2.006       2.006           No
         2    LC  Linksec Engine(5)          2.006       2.006           No
         2    LC  Linksec Engine(6)          2.006       2.006           No
         2    LC  Linksec Engine(7)          2.006       2.006           No
         2    LC  Linksec Engine(8)          2.006       2.006           No
         5   SUP  Power Manager              3.009       3.009           No
         5   SUP  IO                         3.028       3.028           No
         5   SUP  Inband                     1.008       1.008           No
         5   SUP  Local Bus CPLD             3.000       3.000           No
         5   SUP  CMP CPLD                   6.000       6.000           No
         1  Xbar  Power Manager              2.010       2.010           No
         2  Xbar  Power Manager              2.010       2.010           No
         3  Xbar  Power Manager              2.010       2.010           No
         1   FAN  Fan Controller (1)         0.007       0.007           No
         1   FAN  Fan Controller (2)         0.007       0.007           No
         2   FAN  Fan Controller (1)         0.007       0.007           No
         2   FAN  Fan Controller (2)         0.007       0.007           No
         3   FAN  Fan Controller (1)         0.007       0.007           No
         3   FAN  Fan Controller (2)        0.007       0.007           No
         4   FAN  Fan Controller (1)         0.007       0.007           No
         4   FAN  Fan Controller (2)         0.007       0.007           No

  • Nexus 7010 upgrade path

    We currently have two Nexus 7010 with 5.0(2a) as system images.
    We would need to know the correct upgrade path to 6.1(1). On the release notes it reads the path is from 4.2(8), 5.0(5) or 5.1(6) to 5.2(5) then to 6.1(1).
    Also if ISSU is possible or, because we may need to upgrade EPLD, if there is no upgrade path to do a non-disruptive upgrade.

    You probably need to dig a little deeper to get a definitive answer (sup1 or 2, type of cards, etc..) but here is a diagram in the release notes for 6.1 found here:
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/release/notes/61_nx-os_release_note.html
    If this posts answers your question or is helpful, please consider rating it and/or marking as answered.

Maybe you are looking for