BB2-7030 User Guide – Rev. 1.0
Page 52
13.
Using
the
BB2
7030
02
as
a
BACnet
to
SNMP
Gateway
The possible reasons for using the BB2-7030 as a BACnet to SNMP gateway are fairly obvious:
Either you want to access BACnet devices from SNMP, or you want to access SNMP devices
from BACnet. The BB2-7030 allows you to access SNMP from either MS/TP or BACnet IP, and
vice versa.
Configuration begins with determining what the source of data is. If the source of data is BACnet
devices, then start by configuring the BACnet client. If the source of data is SNMP devices, then
start by configuring the SNMP client.
The BB2-7030 can be a “slave” on either the BACnet or SNMP network. If the application wants
to view BACnet data as if it was an SNMP “slave” (server or agent), configure the BACnet client
and also configure the SNMP MIB under the SNMP Agent tab. If the application wants to view
SNMP data as if it was a BACnet slave, configure the SNMP client and then address the BB2-
7030’s internal data objects from BACnet.
The BB2-7030 can be “slave” on both BACnet and SNMP sides at the same time. The BB2-7030
can also be “master” on both BACnet and SNMP sides at the same time. To be a slave on both
sides, only the SNMP MIB needs to be set up under the SNMP Agent tab. To be a master on
both sides, both the BACnet client and SNMP client need to be configured. When both clients
are configured and both sides are acting as master, you are now actively transferring data from
BACnet slaves to SNMP slaves (servers/agents) or vice versa.