* [DHCP Relay]: Support new <DhcpRelays> minigraph tag; support multiple VLANs
* Don't start dhcrelay in quiet mode so as to get startup output in syslog
* Update sonic-cfggen tests to support new '<DhcpRelays>' tag
* <DhcpRelays> tag is only present for VLANs which require a DHCP relay agent -- only parse if present
* Don't attempt to configure a DHCP relay agent for VLANs without specified DHCP servers
* Modify to work with Taoyu's minigraph/DB changes (#942)
* Reduce number of DHCP servers in sonic-cfggen unit tests from 4 to 2
* Remove isc-dhcp-relay sample output file from sonic-cfggen test, as we no longer generate that file
* Update Option 82 isc-dhcp-relay patch to load all interface name-alias maps into memory once at start instead of calling sonic-cfggen on each packet we relay
* Remove executable permission from Jinja2 template
* Set max hop count to 1 so that DHCP relay will only relay packets with a hop count of zero
* Replace tabs with spaces
* Modify overlooked sonic-cfggen call, use Config DB instead of minigraph
* Also ensure > 1 VLAN requires a DHCP relay agent before outputting to template
* Generate port name-alias map file using sonic-cfggen and parse that in lieu of parsing port_config.ini directly
* No longer drop packets with hop count > 0; Instead, drop packets which already contain agent info
* [build]: sonic-utilities package now depends on swsssdk; add build dependency
* Now building sonic-utilities Python package in wheel format
* Update sonic-utilities submodule
* Change output wheel name to match proper format
* Make supervisor controlled one-shot program autorestart 0 time, so the status will become FATAL instead of EXITED if failure happens
Signed-off-by: Qi Luo <qiluo-msft@users.noreply.github.com>
* Make swssconfig.sh strictly exit on any failure
Signed-off-by: Qi Luo <qiluo-msft@users.noreply.github.com>
* Tune startretries, tested in supervisor 3.3.2-1
Signed-off-by: Qi Luo <qiluo-msft@users.noreply.github.com>
The current DEVICE_NEIGHBOR format doesn't support multiple different
ports connecting with same neighbor. Thus the lldpd.conf file is not
generated correctly, causing missing information for LAG members.
This fix reverts the data structure in the previous version of
minigraph parser - using local port as the key and remote port/device
as the value of the map. Sample format is:
DEVICE_NEIGHBOR['Ethernet124'] = {
'name': 'ARISTA04T1',
'port': 'Ethernet1/1'
}
The corresponding unit test in test_cfggen is updated.
Add one more unit test for lldpd.conf.j2 verification.
Signed-off-by: Shu0T1an ChenG <shuche@microsoft.com>
Use ipv4_loopback_addresses variable to store all IPv4 loopback addresses.
The source IP for encapsulation is chosen from one of the addresses.
The destination IPs for decapsulation is the list of the addresses.
Signed-off-by: Shu0T1an ChenG <shuche@microsoft.com>
* Add timestamp suffix to the dirty images version string
This will allow to build different debug images without
having to update BUILD_NUMBER variable before the build
* Changed timestamp format to YYYYMMDD.HHMMSS
* Add S8900-64XC SFP QSFP CPLD kernel module.
* Fixed QSFP function call in i2c_utils.sh.
* Add QSFP monitor service for SFP and QSFP SI.
Signed-off-by: Wade He <chihen.he@gmail.com>
change hwmon kernel modules installation order on S8810-32Q/S8900-54XC/S8900-64XC/S9100-32X
change hwmon kernel modules installation order in i2c_utils.sh and update related fancontrol file
Check the hwmon kernel module insertion order in /sys/class/hwmon/hwmonX.
w83795 should be in /sys/class/hwmon/hwmon1, and jc42 should be the last one.
change hwmon kernel modules installation order on S8810-32Q/S8900-54XC/S8900-64XC/S9100-32X
* Fixing a couple of issues to enable FRR to run with latest SONiC code.
* Adjusting FRR's jinja template to meet latest sonic-cfgen requirements. Basically, i'm just extending #448 changes into FRR.
* Eliminate FRR's integrated-config file to prevent daemons from bypassing their own config files. FRR daemons now default to an integrated-config file for config-parsing purposes. But we are still interested in having each daemon looking in their specific config file (bgpd.conf, zebra.conf, etc). So here i'm just deleting this integrating-config file to prevent FRR from running from a bogus config-file.
* Allows interactive session with the slave docker-container after conclusion of the building process.
Proposed changes provide a more direct access to the building pipeline,
by allowing users to launch consecutive compilation tasks from the same
slave container.
* Revert "snmpd ignores unavailable disks (#607)"
This reverts commit d70e973496.
* Disable snmpd module disk_hw, so no syslog messages about unavailable disks
Signed-off-by: Qi Luo <qiluo-msft@users.noreply.github.com>
* Strip white spaces
Signed-off-by: Qi Luo <qiluo-msft@users.noreply.github.com>
With the fixes in /etc/network/interfaces file, host interfaces
could be added into the corresponding LAGs automatically. Thus,
the logic of checking if port initialization is ready is no longer
needed.
Signed-off-by: Shu0T1an ChenG <shuche@microsoft.com>
* Framework to plugin Organization specific scripts
* Framework to plugin Organization specific scripts
* Framework to plugin Organization specific scripts
* add getopt option to organization script
- What I did
Update Ingrasys submodule for S8900-54XC QSFP reset function.
- How I did it
Add reset init scripts in S8900-54XC init function.
- How to verify it
Used the command "sfputil reset Ethernet48" to verify reset function.
If no error occurs, it is passed.
- Description for the changelog
Update Ingrasys submodule for S8900-54XC QSFP reset function
- A picture of a cute animal (not mandatory but encouraged)
Existing dockers has paths mounted according to the HWSKU. When HWSKU
changes, these dockers need to be destroyed and recreated with the
correct paths mounted.
* [Ingrasys] update port_config.ini and sfputil for ingrasys platforms
- What I did
Update port_config.ini on S8810-32Q/S8900-54XC/S8900-64XC/S9100-C32 platforms
- How I did it
Update alias field and add port field in port_config.ini
- How to verify it
Check with the "sfputil show eeprom" command. If no error occurs, it is passed.
- Description for the changelog
Update port_config.ini on S8810-32Q/S8900-54XC/S8900-64XC/S9100-C32 platforms
* [Ingrasys] remove debug message in sfputil.py on S8810-32Q
- What I did
remove debug message in sfputil.py on S8810-32Q
- How I did it
remove print in get_low_power_mode() and set_low_power_mode()
- How to verify it
There should be no debug message when executing "sfputil show lpmode"
and "sfputil lpmode on Ethernet0"command.
- Description for the changelog
remove debug message in sfputil.py on S8810-32Q
- A picture of a cute animal (not mandatory but encouraged)
