Nexus 7010 - L3 SVI stuck down

Have an interesting dilemma...two 7010s, were working previously, but not in production yet.  One had to be powered off to switch to 220V for the PSUs.  The other stayed up the entire time.  After bringing the other switch back online, the L3 VLAN interface we had setup to do the peer-keepalive is stuck down/down.  The physical link (1Gb SFP on an F1 32-port SFP blade) is up though.  Configuration looks good.  Tried rebooting, shut/no shut, delete/re-create, etc.  Nothing is working...
Does anyone have any ideas?  Tried searching in the bug tool, but didn't see anything that really stuck out for this situation...have never seen anything like it if a link is up.
SJ

Hi Scott,
I'm going to ask a few scoping questions here.
1. is this VLAN used to make the layer3 keep-alive (L3KA) link?
2. if so, is the VLAN on the L2 peer-link (L2PL)?
A quick and easy way to set up VPC on N7K is to use a layer3 port, in a separate VRF...I use VRF L3KA for ease of management.  I'm not a big fan of lengthy/wordy VRF-ids :-)  if you're using multiple VDCs do something like vdc1-L3KA, vdc2-L3KA etc.
L3KA is loosely analagous to a starter motor on a car, it has to come up before the L2PL can initialize.  If the L3KA is a L3 VLAN interface on the L2PL it'll never initialize.
JD

Similar Messages

  • 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

  • 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.

  • Nexus 7010 with F3 line modules. The modules are not "powering on" ?

    Hi,
    Just tried installing a new Nexus 7010, With a couple of F3 line modules.
    I cant seem to figure out how to get them to come online.
    They flash with red LED and from a "show module" they show as powered down.
    Its a fresh nexus install, What could I be missing here? Do I need to "provision them somehow?
    Thanks
    L

    Hi,
    Its 6. something  ( Im not in front of it right now )
    And im certain its these ones.
    http://www.cisco.com/c/en/us/products/collateral/switches/nexus-7000-series-switches/datasheet-c78-730273.html
    They are 48 port , 1/10G fiber. with "8 port groups.."
    No idea if this helps at all.
    Its a new install,
    It contains the default VDC and an admin user. No other config has been done.

  • Port-channel L2 problem with Fabric Interconnect and Nexus 7010

    Hi,
    i using port-channel from both fabric interconnect to N7k with 3 cables per Fabric Interconnect.
    but, my problem is when i creating port-channel, Fabric Interconnect don't support mode ON dan rate-mode share in Interface 10G Nexus 7010.
    I was trying :
    1. I using non dedicated port in Nexus 7010.
          - rate-mode share
          - channel-group 1 mode active
          - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    2. I using non dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode on
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
    3. I using dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    4. I using dedicated port in Nexus 7010
         - rate-mode dedicated
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up and running well.
    but, the problem is my costumer do not want using a dedicated rate-mode. if i using dedicated mode the only available port is 8 interfaces instead of 32 ports. i want to using rate-mode share in nexus 7010.
    is there any way to configuring port-channel using mode on in fabric interconnect ? i was trying using CLI to create port-channel in Fabric interconect but i cannot configure the channel group protocol.
    i attach the topology of N7K with Fabric interconnect.
    regards,
    Berwin H

    Hi Manish,
    the issue was solved, i was fix it last week.
    the solution is:
    i enable the license grace-priode (since my license is Enterprise so cannot create VDC) then i create a VDC (ex: VDC 2)  so i allocate the interface on all module
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin-top:0cm;
    mso-para-margin-right:0cm;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0cm;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    N7K-M132XP-12 to VDC 2. after that i delete VDC 2 then all interface back to VDC 1 (default vdc). then i enable the rate-mode share in dedicated port and bundle into port-channel and its working.
    i dont know why it must move to VDC first then it will working, maybe cisco can explain the reasons.
    So here the result of my port-channel :
    SVRN7KFARM-HO-01# show port-channel summary
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            S - Switched    R - Routed
            U - Up (port-channel)
    Group Port-       Type     Protocol  Member Ports
          Channel
    1     Po1(SU)     Eth      LACP      Eth1/1(P)    Eth1/2(P)    Eth1/3(P)
                                         Eth1/4(P)    Eth1/25(P)  
    2     Po2(SU)     Eth      LACP      Eth1/9(P)    Eth1/10(P)   Eth1/11(P)
                                         Eth1/12(P)   Eth1/26(P)  
    3     Po3(SU)     Eth      LACP      Eth1/17(P)   Eth1/18(P)  
    4     Po4(SU)     Eth      NONE      Eth10/32(P)  Eth10/34(P)  Eth10/35(P)
                                         Eth10/36(P)
    Thanks.
    Berwin H

  • The sleep button on my ipod touch is stuck down. i cannot turn on or charge. any ideas?

    the sleep button on my ipod touch is stuck down and i cannot turn it on or charge it. any ideas?

    You will need to get that serviced.
    Basic troubleshooting steps 
    17" 2.2GHz i7 Quad-Core MacBook Pro  8G RAM  750G HD + OCZ Vertex 3 SSD Boot HD 
    Got problems with your Apple iDevice-like iPhone, iPad or iPod touch? Try Troubleshooting 101
     In Memory of Steve Jobs 

  • 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

  • My iPod lock button is stuck down. How do I get it out?

    Okay, so I went to turn my iPod on and found my lock button was stuck down into the housing of the iPod, I cannot get it out and cannot turn my iPod on. Should I just buy a new iPod or is there a way of repairing it?

    Contact (Google) a third-party iPod repair service and get it serviced.
    Basic troubleshooting steps  
    17" 2.2GHz i7 Quad-Core MacBook Pro  8G RAM  750G HD + OCZ Vertex 3 SSD Boot HD 
    Got problems with your Apple iDevice-like iPhone, iPad or iPod touch? Try Troubleshooting 101

  • 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.

  • Question about Nexus 7010.

    Hello everybody,
    Just a quick question, how do you restore a running-config (or a Nexus .bin file) to a Nexus 7010. Is it thesame process as the IOS base scenario. Please explain and help. Thank you in advance.
    --chie                  

    Copy tftp: running-config should work. See below there are other options as well.
    NX7K02-agg# copy ?
      bootflash:      Select source filesystem
      core:           Select source filesystem
      debug:          Select source filesystem
      ftp:            Select source filesystem
      log:            Select source filesystem
      logflash:       Select source filesystem
      nvram:          Select source filesystem
      running-config  Copy running configuration to destination
      scp:            Select source filesystem
      sftp:           Select source filesystem
      slot0:          Select source filesystem
      startup-config  Copy startup configuration to destination
      system:         Select source filesystem
      tftp:           Select source filesystem
      usb1:           Select source filesystem
      usb2:           Select source filesystem
      volatile:       Select source filesystem
    NX7K02-agg# copy tftp: ?
      bootflash:      Select destination filesystem
      debug:          Select destination filesystem
      log:            Select destination filesystem
      logflash:       Select destination filesystem
      nvram:          Select destination filesystem
      running-config  Copy from source to running configuration
      slot0:          Select destination filesystem
      startup-config  Copy from source to startup configuration
      system:         Select destination filesystem
      usb1:           Select destination filesystem
      usb2:           Select destination filesystem
      volatile:       Select destination filesystem
    NX7K02-agg# copy tftp: running-config

  • Disruptive ISSU 6.1.4a- 6.2.8 on Nexus 7010 sup1 because of LACP timers.

    Hi all.
    The problem.
    Today I updated my Nexus 7010 sup1 from 6.1.4a to 6.2.8.
    I want did it in ISSU mode, but after impact check I got this:
    Compatibility check is done:
    Module  bootable          Impact  Install-type  Reason
         1       yes  non-disruptive       rolling  
         2       yes  non-disruptive       rolling  
         3       yes  non-disruptive       rolling  
         4       yes  non-disruptive       rolling  
         5       yes      disruptive         reset  Some LACP ports not in steady state or operating in 'rate fast' mode.
         6       yes      disruptive         reset  Some LACP ports not in steady state or operating in 'rate fast' mode.
         7       yes  non-disruptive       rolling  
         8       yes  non-disruptive       rolling  
         9       yes  non-disruptive       rolling  
        10       yes  non-disruptive       rolling  
    Additional info for this installation:
    Service "lacp" in vdc 1: LACP: Upgrade will be disruptive as 6 switch ports and 0 fex ports are not upgrade ready!!
          Issue the "show lacp issu-impact" cli for more details.
    (modified the impact to <Hitful>  for module <6>)
    Do you want to continue with the installation (y/n)?  [n] y
    I went on with yes and update script reboot both sups after updated all modules.
    It was quite a surprise for me (yes I know I must see word "disruptive" opposite my sups 5 and 6). Because I already had done two ISSU updates on two nexuses (from 5.1.* ->5.2.7 and 5.2.7 -> 6.1.4a) and didn`t have any trouble with LACP timers. Is it a new feature of the 6.* train?
    I have another Nexus that I want to update. And it also has same problem with LACP timers.
    show install all impact give me the same disruptive result because of LACP.
    Can I somehow suppress such ISSU behavior? In case of LACP. I don`t have vPC, just ordinal PC.
    It is a way better if some LACP interfaces flap in process, than an almost 14 minutes of all 7010 chassis reboot that I had.
    Although problem with LACP timers is that they must be the same on the switch side and on the other side. And in case of switches, linux boxes or HP VCs changing LACP timers isn`t a big problem. IT is a biggg problem in case of the Windows Server.
    sh lacp interface ethernet 8/13
    Interface Ethernet8/13 is up
      Channel group is 13 port channel is Po13
    Local Port: Eth8/13   MAC Address= 40-55-39-23-1e-c1
      System Identifier=0x8000,  Port Identifier=0x8000,0x80d
      Operational key=12
      LACP_Activity=active
      LACP_Timeout=Long Timeout (30s)
    Neighbor: 0x1
      MAC Address= ac-16-2d-a4-f2-54
      System Identifier=0xffff,  Port Identifier=0xff,0x1
      Operational key=17
      LACP_Activity=active
      LACP_Timeout=short Timeout (1s)
    They must be the same and equal 30s for successful ISSU

    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.

  • MGTM0 Interface only in Admin VDC in Nexus 7010

       Hi guys,
          I created two new VDCs in a Nexus 7010 (NX-OS 6.2.6) and I can see the MGTM0 interface only in the Admin VDC
          I wanted to see the MGTM0 in all VDCs.
        Does someone get this problem too ?
        My Best Regards,
        Andre Gustavo Lomonaco

     Hi Reza,
          Thanks for your reply.
          If the user run the setup wizard, the interface mgtm0 will be created in VDC.
          If the user don't run the setup wizard, the interface mgtm0 will not be created and you will need
          to only use the interface mgtm 0 command to create the interface.
          Thanks a lot

  • TS1248 trackpad stuck down on intel macbook pro

    Any advice on help for my trackpad which is stuck down, 5 year old computer and has had no misuse

    Try removing the battery. You have to make sure that your have your computer plugged into the mains, and that it doesn't become disconnected whilst you are using it without the battery installed.
    Place the laptop back onto a flat surface (without the battery installed, but still plugged into the mains), and see if the fault has been rectified.
    What happens, is that, over time, the heat generated by the MacBook Pro warps and distorts the battery casing. The battery is housed over the trackpad circuitry, so that as the battery casing warps, it presses up against the circuitry and causes all sorts of mayhem.
    If you discover that this is the cause of your problem, the only remedy is to replace the battery.

Maybe you are looking for