Yep. Could now write a small book on this platform and I haven't even deployed a mesh topology.
First, it's not a simple drop in like any other PtMP system. You will have to invest a lot of hours learning the platform before you scale it up to anything significant. But the simple steps for one AP/V5k DN and a handful of SM/V1/3k clients are as follows: You will need to get in to the V5k through 169.254.1.1 with admin/admin. I would then make sure it's on the latest version release 1.0.1. If not, download the latest from the cambium site and then upload to the radio directly as is and update it to 1.0.1 directly. Then go to the left menu bottom item to E2E Onboard controller and make it a controller and follow the steps. You can then set a IPv4 management IP on main, or secondary ethernet and/or on VLAN as well to manage it. Basically leave everything on defaults for now, it will auto-generate a IPv6 subnet to hand out to itself and other clients because Terragraph is ALL IPv6. This is very IMPORTANT, Terragraph is NATIVE IPv6. ALL TRAFFIC RUNNING THROUGH IT WILL BE TUNNELLED IN GRE LIKE TUNNELING PROTOCAL BETWEEN UNITS TO THE ENDPOINTS So even though you can assign and manage it and clients via IPv4, the protocol and traffic will all actually be talking to other units first and natively routing IPv6 between themselves. Again NOTHING layer2 passes through the units/network except through a dedicated IPv6 tunnel that the DN/E2E controller creates. This is important to note and can't be stressed enough because it impacts performance and PPS handling in/out the tunnel endpoints it creates at the "edges" of your network. Which means for this simple example, traffic in/out the GigE/SFP+ interface of the V3k client will enter/leave a tunnel, then pass through wireless to the DN then out the GigE/SFP+ of the DN as it leaves/enters the tunnel again there. Going back to config on the DN/V5k/E2E you go to configuration left side menu and set up the "Basic" info, which again leave default except you can add DNS server and time zone. THEN still in Configruation, you go to the top Nodes tab and click on the DN itself which will be the only one available for now. Here again you will see it's IPv4 config, leave it all defaults, Multi-PoP/Relay Port should be Disabled. The interesting tab is actually Radio under the DN Config: If you are testing on the bench, change IBF Transmit Power to Short Range for now, but don't forget to set it back to Long range before deploying. Also if bench testing click on Force GPS Disable for now, but don't forget to set that back right before deployment. That's pretty much it for the DN. Now, still in the DN web page, this time go to the left menu item Topology. You should see the "site" you configured I think when you set up this DN/V5k as a controller. It will have a name, Long/Lat and the DN as a device On Site. You will need the MAC address of the client V3k now, to add it to the "site". First still on the Sites tab, create a new site where the V3k will be deployed with Long/Lat, leave accuracy default and if you like you can give it elevation, I just put all of mine at 8m elevation. Then click on the next top tab to Nodes. Create a new Node and give it a name, assign it to the V3k site and add the mac address of the v3k. Type should be a CN (for now, maybe some you mesh/expand on that, but that's another "book" of information needed). That's it for Nodes. Go to the next top tab Links Create a new Link and select the V3k node, and then the DN/AP/V5k Node and which sector you want it on. Remember the DN/AP has two sectors, pointed due north, sector 1 will be on the East/Right side and sector 2 will be on the West/Left side. It will then create the Link item and should say Ignition Status Enabled on the right side of the item, if not wait about 30 seconds to see if it changes to Enabled, and if not select the three dots to the right and set Enabled. That's pretty much it for bench testing. The cool thing about this platform is that the clients pointed to it will see it and register if Ignition is Enabled and self-configure after registering. So you plug in the V3k and point it at the DN/V5k sector you assigned it to and it will register and show as Active. You can upgrade it over the DN through the upgrade tab, or you can connect to it directly and upgrade it if necessary. To set the V3k management IPv4 IP address go back to the left menu Configuration and under Nodes you will see the V3k and can assign it whatever you like. It will be pushed that config pretty quick if registered, or when it registers it will push the config. One thing about this software is that it's still a bit buggy and temperamental. Also about every change in the system tends to down THE ENTIRE SYSTEM with a few exceptions so be aware of that. If you want help with aligning the V3k client in the field, let me know. I've learned another whole semi-undocumented process for that now too. -----Original Message----- From: AF <af-boun...@af.afmug.com> On Behalf Of Nate Burke Sent: Monday, June 14, 2021 8:19 AM To: Animal Farm <af@af.afmug.com> Subject: [AFMUG] CNWave 60ghz deployment Has anybody used the CNWave 60ghz equipment yet? I got a V5000 AP and a V3000 SM and have spent about an hour so far and haven't been able to figure out the secret sauce to get them to link up. It's not just a simple AP/SM Setup it seems, lots of config want's to be done automagically, but I think somewhere you have to set the automagic up. Any pointers? The Documentation talks all about the Facebook Terragraph, and mesh setup, but I'm having trouble wrapping my head around that since I'm so used to the AP/SM Model. -- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com -- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com
