SummaryIf 'inbound' traffic appears to be more suited to 'outbound' and vice versa, or the 'internal' hosts are actually public IPs, the cables on the bridge might be in the reversed order
OverviewWhen cabling the Exinda, it's important to note how the cabling goes. On all bridges, the left port of the dual port pair is the LAN port, and the right is the WAN port, if the card is installed right side up (and is legible from the back). If after the Exinda is cabled, monitoring - including both graphs and the real time monitor - are reporting that internal IPs are actually 'external IPs' and vice versa, or the 'outbound' bandwidth is more suited to what should actually be 'inbound', then it is indicative of the cabling on the bridge being reversed. That is, the WAN cable going into the LAN port and the LAN cable going into the WAN port.
CauseThe monitoring on the Exinda uses the traffic going into the ports as part of the way to define directions. Traffic with sources coming into the LAN port must be internal traffic going out ('outbound') while traffic originating on the WAN port coming in must be external traffic coming in ('inbound'). The Exinda does not deep packet dive to verify that this information is right, as there are many variables that cannot be determined. For example, if the Exinda has a LAN on the subnet 10.0.20.0/24 and the connection to the WAN is going through an actual WAN link to a subnet that is still technically internal in terms of IP (10.0.30.0/24) but still 'external' in terms of the location with respect to the Exinda, the Exinda cannot differentiate the two internal subnets as they are both private IP subnets.
As a result, the 'internal' and 'external' IPs are just taken based on the port that the traffic is coming from. The same with the direction of the traffic.
When this happens, a Bridge Direction alert might be triggered. See What does the Bridge Direction alert indicate? for more information.