BBMD - Revision history

BACnetEd at 16:13, 9 January 2024

2024-01-09T16:13:05Z

← Older revision		Revision as of 09:13, 9 January 2024
Line 1:		Line 1:
	BBMD - BACnet Broadcast Management Device		'''BBMD - BACnet Broadcast Management Device'''


	Broadcasts are usually blocked by IP routers. In this case, discovery mechanisms such as Who-Is broadcasts cannot reach devices on other IP Subnets. This restriction is overcome by placing a BBMD in each of the IP Subnets.		Broadcasts are usually blocked by IP routers. In this case, discovery mechanisms such as Who-Is broadcasts cannot reach devices on other IP Subnets. This restriction is overcome by placing a BBMD in each of the IP Subnets.

BACnetEd at 16:12, 9 January 2024

2024-01-09T16:12:45Z

← Older revision		Revision as of 09:12, 9 January 2024
Line 1:		Line 1:
	BBMD - BACnet Broadcast Management Device		BBMD - BACnet Broadcast Management Device

			Broadcasts are usually blocked by IP routers. In this case, discovery mechanisms such as Who-Is broadcasts cannot reach devices on other IP Subnets. This restriction is overcome by placing a BBMD in each of the IP Subnets.


			BBMDs are devices (usually 'virtual', it, part of another BACnet Device of Router) that are responsible for receiving a broadcast on an IP Subnet, transferring it using a unicast other BBMDs on other IP Subnets, which then rebroadcast on those IP Subnets.


	In the "Old Days" all BBMDs had to have identical BBMD Distribution Tables. (BDTs), and only one active BBMD per IP subnet.		In the "Old Days" all BBMDs had to have identical BBMD Distribution Tables. (BDTs), and only one active BBMD per IP subnet.


	Now you are allowed multiple active BBMDs per subnet, but the BDTs must not have any identical peer IP entries (to avoid broadcast loops). ( J.4.3. "BBMD Concept", paragraph 2, of the spec )		Now you are allowed multiple active BBMDs per subnet, but the BDTs must not have any identical peer IP entries (to avoid broadcast loops). ( J.4.3. "BBMD Concept", paragraph 2, of the spec )

BACnetEd: Created page with "BBMD - BACnet Broadcast Management Device In the "Old Days" all BBMDs had to have identical BBMD Distribution Tables. (BDTs), and only one active BBMD per IP subnet. Now you are allowed multiple active BBMDs per subnet, but the BDTs must not have any identical peer IP entries (to avoid broadcast loops). ( J.4.3. "BBMD Concept", paragraph 2, of the spec ) So far so good. For full coverage of a given network, all subnets need a BBMD (or multiple) that point to every ot..."

2024-01-09T16:09:43Z

Created page with "BBMD - BACnet Broadcast Management Device In the "Old Days" all BBMDs had to have identical BBMD Distribution Tables. (BDTs), and only one active BBMD per IP subnet. Now you are allowed multiple active BBMDs per subnet, but the BDTs must not have any identical peer IP entries (to avoid broadcast loops). ( J.4.3. "BBMD Concept", paragraph 2, of the spec ) So far so good. For full coverage of a given network, all subnets need a BBMD (or multiple) that point to every ot..."

New page

BBMD - BACnet Broadcast Management Device

In the "Old Days" all BBMDs had to have identical BBMD Distribution Tables. (BDTs), and only one active BBMD per IP subnet.

Now you are allowed multiple active BBMDs per subnet, but the BDTs must not have any identical peer IP entries (to avoid broadcast loops). ( J.4.3. "BBMD Concept", paragraph 2, of the spec )

So far so good. For full coverage of a given network, all subnets need a BBMD (or multiple) that point to every other BBMD in the network, so broadcasts can percolate from any subnet to all other subnets.

BUT the specification allows you to deliberately leave out connections to avoid forwarding broadcasts where they are not required. ( J.4.3. "BBMD Concept", paragraph 2, of the spec )