There are two different, though similar ways to accomplish this.
All CAB's will have unique ID's.
The first (and simplest) method to accomplish this is to multicast the bundle from the NION so that multiple receivers in the CAB's can listen to this bundle. Setting the bundle to be a multicast bundle is done by selecting a bundle number of 1 through 256.
Bundle numbers above 256 are all unicast and what we generally recommend for point to point transmission of a bundle. However, it is possible to configure a unicast bundle to be a "multi-unicast" bundle (sounds like an oxymoron, doesn't it!) You can configure a unicast bundle to be transmitted to up to 4 receivers by using the multi-unicast feature. (if you need more than 4 receivers, it is recommended to consider multicasting the bundle if possible) You will need to use the Advanced CobraNet configuration in the NION to configure a bundle for multi-unicast operation. To enable Multi-Unicast operation, simply set the number in the "Max Unicast" column to the number of destinations you want the bundle to go. (The available settings are integers 1-4) This will allow your bundle to be sent from one transmitter to up to four receivers.
I like to think of bundles as subsnakes. You have a maximum of 8 channels available in a subsnake, but you don't have to use them all (again using Advanced CobraNet Configuration). To provide a split so the subsnake can reach more than one destination, it is easy to either multicast or multi-unicast a bundle depending on what you need to do. Of course, lots of subsnakes can be aggregated into a main trunk by linking switches together with gigabit interfaces because you have a lot of bandwidth available in the gigabit link. This can easily provide hundreds and hundreds of channels over a single connection.
Josh Millward
Burnt Orange Studios