I assume it's the upside-down "Y" thing (formerly) made by Cisco?
They have had a number of issues.
At one point, they cross-checked the address with the GPS coordinates,
and if the GPS coordinates weren't within 1/4 or so of the address, they
would refuse to connect. I thought they fixed this, but really don't
know. Addresses in our area are very haphazard, and the "location" of
the street address is often off by more than a mile (I think our street
address is almost 2 miles off the mark).
If you are NATting in the SM, there are some issues WRT address resolution.
Older Canopy firmware (prior to 13.4) either breaks (or doesn't break)
packets on boundaries that are "acceptable" to the AT&T femtocell.
We have had the best luck by putting the SM in bridge mode.
They also take a horrendous amount time to "sync up" with the network
(sometimes hours). Make sure they are close to a window so they can
obtain a GPS fix.
bp
<part15sbs{at}gmail{dot}com>
On 7/1/2015 8:57 AM, That One Guy /sarcasm wrote:
Did AT&T make some change to their microcells? We have customers
callin in alot with their microcells no longer working. I initially
thought it was because we moved some customers to some IP space we
borrowed from our upstream. But we have had a couple that didnt change
and one that actually is triple NAT.
We dont support these things at all, we just make sure their on a
public and tell them to call AT&T to recommend a compatible router and
provide configuration instruction so its not a support issue im
concerned about, just curious if others are seeing this.
We did change from static routing to OSPF, but I cant imagine that
would have had any impact since the customers are still traversing the
same path
--
If you only see yourself as part of the team but you don't see your
team as part of yourself you have already failed as part of the team.
