* [service] Restart SwSS Docker container if orchagent exits unexpectedly
* [dhcp_relay] Use STATE_DB to determine whether interfaces are ready
* Supervisor now autorestarts rsyslogd upon unexpected exit
* Add other critical processes to event listener
* Make supervisor-proc-exit-listener script global, have it read from 'critical_processes' file inside container
* Add SwSS to 'WantedBy=' option of services which should be started along with SwSS
seen issues to build dockers using aufs in ubuntu 18.04
Immedidate dockers are exported to docker file and then
imported into sonic image. Thus, whether using vfs or aufs
as the storage driver does not matter for the immediate build.
Signed-off-by: Guohan Lu <gulv@microsoft.com>
Need to build NTP 4.2.6 locally due to a Bug in NTP 4.2.6.
Changes:
1.) Remove 'apt-get ntp' step from build_debian.sh.
2.) Add NTP package as part of base image in slave.mk.
3.) NTP Makefile for Sonic Build System rules/ntp.mk.
4.) NTP Source Makefile src/ntp/Makefile.
5.) Patch to fix the issure src/ntp/patch.
Signed-off-by: Praveen Chaudhary<pchaudhary@linkedin.com>
* [src/ntp/Makefile]: DSC file URL points to sonic storage.
Signed-off-by: Praveen Chaudhary<pchaudhary@linkedin.com>
* [src/ntp/Makefile]: Changes to build with sonic blob.
518ff41 2019-01-28 | Revert "Fix the ipv6 address lost issue with current config CLI (#331)" (HEAD, origin/201803) [Guohan Lu]
Signed-off-by: Guohan Lu <gulv@microsoft.com>
cde2966 2018-06-26 | * Reduce severity of log 'vty connect from' from INFO to DEBUG (#21) (HEAD) [pavel-shirshov]
Signed-off-by: Guohan Lu <gulv@microsoft.com>
* [Dell] sensors.conf files for S6100/Z9100
Addded sensors.conf file for S6100/Z9100 switches.
sensorsd daemon can able to write syslogs when alarms are raised for any specific attribute.
Added alarm supprot for onboard sensors.
Tuned return values of attributes to avoid "Bad Adddress" proc errors.
Exported SMF version.
* Converted TAB to Spaces
* uodate sai and sdk for fix some bug and add some filt to device/accton and ingrasys for support different sfp module and hw version
* update device config for support s9230 R0B and update port_config.nps and ini
* update device file
* fix some code error
* fix init chip config data error
* Fix redis-py version
Signed-off-by: Qi Luo <qiluo-msft@users.noreply.github.com>
* Update submodule sonic-py-swsssdk: Fix redis-py version to 2.10.6
Signed-off-by: Qi Luo <qiluo-msft@users.noreply.github.com>
* 8113744 2018-11-18 | Force key/value convertion to str before send to redis lib (#39) (HEAD, origin/master, origin/HEAD) [Taoyu Li]
Signed-off-by: Guohan Lu <gulv@microsoft.com>
* update sfputil, port indext start from 1
* DX010 update SKUs port config index
Port index in port_config.ini now start from 1.
* Seastone-DX010-10-50 port config update
* Seastone-DX010-50 port config update
* Seastone-DX010 port config update
* Update dx010 sfputil plugin
* Implement lpmode set function.
* Implement transceiver reset function.
* Python code style format.
* Remove new line at the end of port_config.ini
*New line cause parsing error in sfputilbase.
* Add get_transceiver_change_event method
*This needed by new sfputilbase implement.
* Fix unintended line breaks
Auto negotiating console speed could cause sonic to lock on a wrong
speed under rare conditions. The only way to come out of the wrong
speed is to issue line break or restart console service with forced
speed, or reboot sonic.
Lock down the console speed to avoid these situations.
Signed-off-by: Ying Xie <ying.xie@microsoft.com>
Flashes used for the 7050QX-32 and 7050QX-32S have a fw issue.
The best option to solve the problem is to upgrade to a newer firmware.
However this can only be done while in memory and take 10 seconds.
Adding an upgrade mechanism is possible but would need more
consideration as flashing the firmware and reformating the flash will
exceed the fast-reboot requirements.
A quick mitigation is to align the ext4 partition that we create on
these vfat based system on a 4k boundary.
Here we chose 1M instead but it's the same.
Newer version of sfdisk do this automatically but the one in SONiC
today doesn't have this behavior.
This workaround will only reduce the pace of the flash health
degradation. The only long term fix is to flash the firmware.
