Difference: AMC13DebugLog (89 vs. 90)

Revision 9013 Mar 2014 - DavidZou

Line: 1 to 1
 
META TOPICPARENT name="CmsSlhc"
Please log AMC13 test activity below, blog style (new entries at top)
Added:
>
>

2014-03-13, Dave

Testing storeConfig problems
  • SN 34 in slot 4 has IP address 192.168.1.100 (all IP address are stated for the T2, T1 is assumed 1 higher unless otherwise stated) and has that IP address in EEPROM.
    • Stored it w/ storeConfig to 192.168.230
      • Using readNVmem.py confirmed this changes
    • Cycled crate power
      • Checked the IP address using readIPs: 192.168.1.230
      • Checked the IP address stored using readNVmem: 192.168.1.230
    • Next stored 192.168.1.250 but instead just did a handle reset
      • Checked the IP address using readIPs: 192.168.1.230 (kept the old ip)
      • Checked the IP address stored using readNVmem: 192.168.1.250
    • Applied and Stored IP address of 192.168.1.222 and did handle reset
      • Checked the IP address using readIPs: 192.168.1.230 (reverted back to the old ip)
      • Checked the IP address stored using readNVmem: 192.168.1.222
      • Somehow, with a handle reset, it keeps a copy of IP address that was in the EEPROM the last time the crate was power cycled
  • This behavior seems to be present w/ all boards.
    • stored IP address is applied when the crate power is reset, however it does not get applied when doing just a simple handle reset.

2014-03-13, Dave

Experienced connectivity issues in CMS Lab, particularly with cmsssun4 and cms2. Connectivity to each other and to the outside world was spotty. Both cms2 and cmssun4 (and the other machines in CMS Lab) are connected to a D-Link switch which then connects to the outside world:

  • First noticed internet connectivity issues on cmssun4
    • Internet connection was inconsistent would periodically drop or slow down (once every few minutes)
    • Could ping to bu.edu w/ ping times of ~0.7 ms but would periodically pause and/or see ping times of ~100+ ms
  • ssh connection from cmssun4 to cms2 would periodically slow down
    • Connection did not time out usually, instead a dramatic lag would be introduced
    • Could ping to cms2.bu.edu w/ ping times of ~0.2 ms but would periodically pause and/or see ping times of ~100+ ms
  • cms2 seemed to also have problems connecting to the outside world
    • Eric experienced problems connecting to cms2 remotely in the morning
    • Could ping to bu.edu w/ ping times of ~1 ms but would periodically pause and/or see ping times of ~100+ ms
  • Plugged cms2 and cmssun4 into a new switch and plugged that switch into the original D-Link switch
    • Connection between cms2 and cmssun4 did not seem to improve (same ping stats as above)
    • Unplugged ethernet cables back to original configuration
  • Mysteriously, the connect problems seemed to have been fixed on its own.
    • Virtual machine was running during problems, but stopped and shortly after, problem was fix. May be coincidence, some test should be done.

 

2014-03-12, Eric

Guoan fixed the disk space problem through some partition-rearranging magic a few weeks ago.

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback