Networking & Communications
A common problem in mobile networks is a lack of Ethernet ports at telecom sites or IP addresses on the network. A SiteBoss can be equipped with a four-port or eight-port Ethernet Layer 2 switch. This solves several problems:
More “smart” controllers are being added to sites and site routers don’t have the physical ports to accommodate them. The SiteBoss adds additional Ethernet ports for expansion at the site.
IP address management is complicated by the addition of networked devices at sites. The SiteBoss provides a separate network for attached devices with IP addresses served from the SiteBoss by DHCP. Only the IP address of the SiteBoss needs to be added to the network conserving scarce IP addresses.
Many operators have network security concerns, and the SiteBoss can perform as the single approved secure device on the network, with non-approved devices on the separate network created by the SiteBoss.
In telecom sites where there is no Ethernet connectivity the SiteBoss can use alternate connectivity types:
Asentria has a range of wireless modems available as options in the SiteBoss.
Fiber Connections (SFP)
Asentria SiteBoss units can support an SFP connection for cases where only fiber connectivity is available.
Network Secure Remote IP Access
The primary methods for secure remote IP access are listed below. This function most often enables someone within the NOC to communicate securely to the SiteBoss unit, and then pass through the SiteBoss unit to communicate to other equipment at the site.
Ethernet to Ethernet (or Serial)
In some cases intelligent devices (eg. HVAC, generator, or rectifier smart controllers) are not considered secure enough to be placed directly onto a network, and can be directly connected to the internal Ethernet or serial ports on a SiteBoss for access.
Wireless Modem to Ethernet (or Serial)
A wireless modem option can be used to connect to the SiteBoss, and then connect through the SiteBoss unit to any attached Ethernet or serial based device.
Many of the most interesting applications relate to the SiteBoss’ onboard scripting language, and the new RESTful API. The SiteBoss is connected to all major site sub-systems, and can make decisions based on complex logic. Two brief examples are listed below, but there are many new possible applications using these functions.
Site Hardening Example – A SiteBoss recognizes AC main power is lost to a site. The SiteBoss doesn’t start generator unless battery charge is below a certain level, and site temperature is above a certain level, extending diesel fuel and site life.
Energy Efficiency Example – A SiteBoss with integrated HVAC card is controlling HVAC at sites. Using the RESTful API network wide changes to set points can be made, and even made continuously, to optimize HVAC at sites and across the network. Via the API, telemetry data on HVAC performance across the entire network can be retrieved and analyzed.
Sending SNMP traps based on recognizing any of a wide variety of faults is one of the most common uses for a SiteBoss unit.
SNMP OID Creation
If polling of the SiteBoss is preferred to SNMP traps, the SiteBoss also has OID’s corresponding to all measured values that can be polled. New OID’s can be created to create new values at the site.
Allows SNMP agents to poll devices that are connected to the SIteBoss, but which are not on the same network as the agent. A means of keeping smart controllers that aren’t considered fully secure off the primary network.
SNMP Trap Capture
SNMP traps can be sent from local devices at a telecom site directly to the SiteBoss. The SiteBoss can then take various pre-set actions based on the trap received, or information contained within the traps.
SiteBoss can poll specific OID’s from other SNMP devices, and build internal files of that data that can be used by our alarming or scripting functions.
- ASCII to SNMP
- MODBUS to SNMP
- XML to SNMP
- HTML to SNMP