sonic-buildimage/device/arista/x86_64-arista_7800_sup/chassisdb.conf

start_chassis_db=1
chassis_db_address=127.100.1.1
midplane_subnet=127.100.0.0/16

lag_id_start=1
lag_id_end=128
[ChassisDB]: bring up ChassisDB service (#5283) bring up chassisdb service on sonic switch according to the design in Distributed Forwarding in VoQ Arch HLD Signed-off-by: Honggang Xu <hxu@arista.com> - Why I did it To bring up new ChassisDB service in sonic as designed in ['Distributed forwarding in a VOQ architecture HLD' ](https://github.com/Azure/SONiC/blob/90c1289eaf89a70939e7c81e042e261947c6a850/doc/chassis/architecture.md). - How I did it Implement the section 2.3.1 Global DB Organization of the VOQ architecture HLD. - How to verify it ChassisDB service won't start without chassisdb.conf file on the existing platforms. ChassisDB service is accessible with global.conf file in the distributed arichitecture. Signed-off-by: Honggang Xu <hxu@arista.com> 2020-10-14 17:15:24 -05:00			`start_chassis_db=1`
			`chassis_db_address=127.100.1.1`
[Chassis][Voq]Configure midplane network on supervisor (#11725) Multi-asic Docker instances are created behind Docker's default bridge which doesn't allow talking to other Docker instances that are in the host network (like database-chassis). On linecards, we configure midplane interfaces to let per-asic docker containers talk to CHASSIS_DB on the supervisor through internal chassis network. On the supervisor we don't need to use chassis internal network, but we still need a similar setup in order to allow fabric containers to talk to database-chassis 2022-09-15 19:23:41 -05:00			`midplane_subnet=127.100.0.0/16`
[chassis] Set LAG Id range for 7800 chassis (#8052) Configure LAG Id range in chassisdb.conf for 7800 chassis. 2021-08-30 18:04:07 -05:00
			`lag_id_start=1`
			`lag_id_end=128`