Cool, I am able to override the DNS resolver so that cpe.tr69.management.server resolves to the IP address of my Breezeview server. I had previously firewalled off the NAT (for Layer 3 service profile) subnet from accessing the external management subnet. I poked a new hole accordingly. When I manually load the URL http://cpe.tr69.management.server:8080/ftacs/ACS the Breezeview server displays what looks like an Apache error. The requested URL /ftacs/ACS was not found on this server.
I went hunting around the Breezview server and found what looks like a config file under /opt/lte/app/lte.current/acs-server/conf.properties but the settings in this file seem to not correspond to the default URL in the CPE8000. In fact, when I looked at this config file and verified with netstat that the listener was on port 8081 instead of 8080, I ended up modifying the UE with this URL below which does work - UE shows up in Breezeview!: http://cpe.tr69.management.server: <http://cpe.tr69.management.server:8080/ftacs/ACS>8081/BreezeVIEW/tr069 # Enable ACS module in BreezeVIEW acs.enabled=true # TCP port used by the ACS, defaults to 8081 acs.port=8081 # TCP IP used by the ACS, defaults to localhost acs.ip=10.20.12.12 # BreezeVIEW ACS URL, default is /BreezeVIEW/tr069 acs.url=/BreezeVIEW/tr069 # To continue work with URL of Friendly ACS - use the /ftacs/ACS #acs.url=/BreezeVIEW/tr069 # ACS NBI URL, deafult is /soap acs.nbi.url=/soap On Tue, Oct 31, 2017 at 7:57 AM, Nathan Anderson <nath...@fsr.com> wrote: > The UEs menu *is* CPEView. That's just the marketing name that they have > chosen for that feature; I don't know that there is any place in the > software that actually says "CPEView" anywhere, but that's what it is > called in the documentation (actually, now that I look at it again, it > appears that they style it in the docs as "CPE-VIEW"). You may note that > that menu did not exist in the prior version. > > > > CPEs will not show up in there automatically. CPEs need to be told to > report in to the ACS server of your choice. Once a CPE registers with your > ACS server, it will show up as a managed device. It's not like the network > is doing this for you; ACS registration happens on a CPE-by-CPE basis, and > is initiated by the CPEs themselves. On some connectivity mediums (e.g., > WiMAX), it is possible to signal to the CPE the hostname or IP address of > the ACS server that a CPE should register itself to, often using a DHCP > option. However, LTE does not use DHCP to configure CPEs, but rather PPP > IPCP (do not be confused by the DHCP Proxy feature of the EPC: this feature > just gives the EPC a source for a pool of IP addresses that it can hand > out...it isn't actually sending the DHCP response from the server all the > way to the UE), so you have to preload the LTE CPEs with the ACS server > registration information before they go out the door. What this means is > that for already-deployed CPEs, you will have to log into them one by one > and configure the TR-069 management stuff manually. (If your ACS server > info ever has to change, you can bulk-update all currently registered CPEs > with the new info via the ACS before you flip the switch.) > > > > There is one trick you can use to simplify this onboarding process, which > is that TR-069-capable CPEs will often have it enabled with a default > hostname configured. In the case of Telrad CPEs, I believe they all come > straight from the factory with the ACS URL set to > http://cpe.tr69.management.server:8080/ftacs/ACS. If you have your own > DNS server(s), you could add management.server as a zone and then create an > A record for cpe.tr69 pointed at the IP address of your BreezeView server. > > > > StarACS is a holdover from the Alvarion days (when all software/management > components were named StarSomething, and the hardware bits BreezeSomething, > a convention presumably inherited from BreezeCom) that they kept around > because they didn't have an in-house replacement finished yet, and given > the existence now of CPE-VIEW, likely isn't long for this world...I haven't > heard one way or another but it would not surprise me if they pulled it > from sale once CPE-VIEW becomes relatively feature-complete. (For all I > know, they may have already stopped selling it.) If you need something > more than what the built-in CPE-VIEW provides, you may have to approach > Friendly Tech directly, or choose to use one of a dozen other ACS server > products available, such as the open source options FreeACS and GenieACS. > > > > -- Nathan > > > > *From:* telrad-boun...@wispa.org [mailto:telrad-boun...@wispa.org] *On > Behalf Of *Matt Lauer > *Sent:* Tuesday, October 31, 2017 3:51 AM > > *To:* telrad@wispa.org > *Subject:* Re: [Telrad] TR069 > > > > Nathan, thanks for the extensive info. My Breezeview is upgraded to 6.8 > and I can't find any indication that CPEView exists yet in the menu. In > fact, my UEs won't even show up automatically in the "UEs" menu yet. > > > > I'm definitely comfortable exploring APIs to do the types of things you > are describing. The Telrad branded StarACS lead me to question whether > there was TR-069 server built into Breezeview. We currently use Zabbix and > Cacti as well. I like your approach to bridging your data into your Cacti > system so everything is under one roof. > > > > On Mon, Oct 30, 2017 at 9:22 PM, Nathan Anderson <nath...@fsr.com> wrote: > > Oh, bother. Somehow I didn't manage to finish my sentence/thought at the > end of the 5th paragraph. Should have read: > > > > Similarly, some CPEs also have a home WiFi gateway that can be configured > by the CPE itself (has no independent management interface), and you can > push out configuration changes to the WiFi gateway via TR-069 as well. If > you decide to use those in your installs, you could thus have one standard > way of configuring both the CPEs and the home gateways of your users. > > > > --Nathan > > > > *From:* telrad-boun...@wispa.org [mailto:telrad-boun...@wispa.org] *On > Behalf Of *Nathan Anderson > *Sent:* Monday, October 30, 2017 6:21 PM > *To:* telrad@wispa.org > *Subject:* Re: [Telrad] TR069 > > > > BreezeView does have TR-069 server (ACS) built-in as of version 6.8 which > just came out. It's called CPEView and it is very much a 1.0 product, and > Telrad acknowledges this. Many features and improvements are allegedly on > the docket for 6.9. > > > > One's use-case for TR-069 is going to vary depending on your particular > requirements. What may be of value to some, others may not care about. > > > > At the very least, it can give you a handy central list of all on-line > CPEs, what eNB they are attached to, as well as the ability to push out > firmware upgrades en-masse, and to do so with a consistent interface > (upgrade procedure and experience will be the same across all CPE models > and vendors that support TR-069: just use the interface that your ACS > provides to you). > > > > You can also push out configuration changes in bulk as well, either to all > CPEs or using whatever criteria you wish (only CPEs on a certain eNB, or > only CPEs of a certain model or running a certain firmware version, or ones > which already have some other part of their configuration set to X, etc.). > > > > If your CPE has an analog voice adapter built-in that you wish to take > advantage of, you could use TR-069 to automate provisioning of the voice > component, which cannot be configured through the HSS (at least for now; > perhaps if VoLTE is supported on the EPC in the future and CPEs implement > that instead of straight SIP, then maybe this can change). Similarly, some > CPEs also have a home WiFi gateway that can > > > > To employ certain kinds of automation (e.g. the aforementioned VoIP > provisioning) may require you to programmatically interact with the ACS > using APIs that the ACS provides to you. You can certainly still do manual > provisioning with the ACS's GUI and at the very least just abstract away > the CPE's unique configuration interface that way, which may have some > value for you (again, if you have a diversity of CPE models, esp. from > different vendors), but anything more complicated than that (for example, > tying a particular IMSI/SIM to a particular SIP account using a database, > and then expecting the right credentials to get pushed out to the right CPE > automagically) would require you to implement that "glue code" yourself. > Having an API to call into is one of the features that CPEView is still > missing but which is promised in a future release. > > > > What we primarily use TR-069 for is collecting statistics from our CPEs, > like current and historical RSRPs, SINRs, and link utilization (end-user > throughput averaged over 5 minute polling intervals). This is also > something that I understand CPEView will eventually support; for now, I > believe you can only watch these KPIs in real time for one given CPE at a > time, with no option for storage. The ACS product we are using (StarACS, > which is a Telrad-branded version of Friendly Tech's ACS) doesn't itself > really support more than storage of the raw KPI data into a database table, > so using the StarACS APIs, we feed that to Cacti and have it maintain > separate RRDTool graphs for all of our CPEs. You COULD do the same thing > using SNMP, of course, but only on CPEs that actually support SNMP, and not > all of them do (TR-069 support seems more likely to be a given on LTE > fixed-install UEs). > > > > -- Nathan > > > > *From:* telrad-boun...@wispa.org [mailto:telrad-boun...@wispa.org > <telrad-boun...@wispa.org>] *On Behalf Of *Matt Lauer > *Sent:* Monday, October 30, 2017 5:27 PM > *To:* telrad@wispa.org > *Subject:* [Telrad] TR069 > > > > I am new to TR069. For the Cambium portion of our network, we are able to > make configuration file JSON templates and upload those in plain-text to > configure SMs. I understand the basic concept of "zero-configuration" for > the Telrad UE. But aside from the fact the iHSS database keeps track of the > IP assignment and the UL/DL bit rates, there must be some other compelling > reason to use TR069? Does Breezeview have a TR069 server built-in somewhere? > > > > -- > > Matt Lauer > > Solvaris, Inc. > > > > 586.453.0440 <(586)%20453-0440> p > > 248.495.3977 <(248)%20495-3977> c > > 586.453.0805 <(586)%20453-0805> f > > > > mla...@solvaris.com > > www.solvaris.com > > > _______________________________________________ > Telrad mailing list > Telrad@wispa.org > http://lists.wispa.org/mailman/listinfo/telrad > > > > > > -- > > Matt Lauer > > Solvaris, Inc. > > > > 586.453.0440 <(586)%20453-0440> p > > 248.495.3977 <(248)%20495-3977> c > > 586.453.0805 <(586)%20453-0805> f > > > > mla...@solvaris.com > > www.solvaris.com > > _______________________________________________ > Telrad mailing list > Telrad@wispa.org > http://lists.wispa.org/mailman/listinfo/telrad > > -- Matt Lauer Solvaris, Inc. 586.453.0440 p 248.495.3977 c 586.453.0805 f mla...@solvaris.com www.solvaris.com
_______________________________________________ Telrad mailing list Telrad@wispa.org http://lists.wispa.org/mailman/listinfo/telrad
