Technology Manager 2.0 Release

Discussions about Internet service providers (ISPs), the Meetinghouse Firewall, wired and wireless networking, usage, management, and support of Meetinghouse Internet
lajackson
Community Moderators
Posts: 8528
Joined: Mon Mar 17, 2008 9:27 pm
Location: US

Re: Technology Manager 2.0 Release

Postby lajackson » Wed Nov 02, 2016 7:40 am

So far, I have positioned myself under each WAP with WiFi connected, then turned them off one at a time until my WiFi signal dropped. I labeled that one in TM, turned it back on, and moved to the next. The last one in each building was easy since I was just verifying that I got the first ones right.

Low tech, but it worked. The hardest part (other than the guess work) was making sure I was attached to the closest WiFi access point when I tripped the switch.

russellhltn
Community Administrator
Posts: 26021
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Re: Technology Manager 2.0 Release

Postby russellhltn » Wed Nov 02, 2016 10:31 am

Mikerowaved wrote:When you're done walking around, compare the MAC addresses you recorded with the list in TM.

Doesn't work. The wired side and wireless side have different MAC addresses.

Also, a tip: In WiFi Analyzer, you can do a long press on a AP and save a alias for it. So now you can have it show "East Hallway" instead of yet another "LDS Access".

Also, a warning to others: turning off the AP works as long as you test that for ALL of them. (Not just all of them in TM.) Otherwise, you might have the hidden AP situation I ran into. In that case, the AP you turn off in TM may not be the right one.

You can check how many you have by going to the main page for the firewall, click on "Get Connected Devices". Wait for the "plug" icon to come up to the left of the line for the "User" zone. Click on the plug. Type in "Cisco" in the search box. Count the lines. Unless you've got a managed Cisco switch, the number of lines should match the number of APs in the building (including the one built-into some models of the firewall.)
Have you searched the Help Center? Try doing a Google search and adding "site:lds.org/help" to the search criteria.

So we can better help you, please edit your Profile to include your general location.

bookofnorman
New Member
Posts: 5
Joined: Thu Jul 18, 2013 4:52 am

Re: Technology Manager 2.0 Release

Postby bookofnorman » Fri Nov 04, 2016 6:03 am

who is given what permissions in 2.0? can the technology specialist do everything the FM manager can? what about the mechanics?

User avatar
Biggles
Senior Member
Posts: 1165
Joined: Tue May 27, 2008 4:14 am
Location: Watford, England

Re: Technology Manager 2.0 Release

Postby Biggles » Fri Nov 04, 2016 6:45 am

The answer to your question about what the STS and the FM manager can and can't do is described in the initial post https://tech.lds.org/forum/viewtopic.ph ... 87#p160787 to this thread. I would hasard a guess that the mechanics will have the same access as the FM manager.

The Help Centre notes about TM haven't been updated yet, to reflect the recent changes. I actually sent feedback about this earlier today.

CleggGP
Church Employee
Church Employee
Posts: 118
Joined: Mon Jul 28, 2014 12:55 pm

Re: Technology Manager 2.0 Release

Postby CleggGP » Fri Nov 04, 2016 1:41 pm

bookofnorman wrote:Can the technology specialist do everything the FM manager can? what about the mechanics?

On a stake level currently an STS and FM (and Assistant FM) can do similar things in TM. This includes view network information, edit ISP information, enable/disable WiFi, label WAPs, refresh the firewall configuration, and reboot the firewall. On the satellite network they can view satellite information, change language channels, and temporarily mute receiver video. An FM can also activate/deactivate/reassign/replace a satellite receiver.

Currently FM mechanics can view network information, edit ISP information, enable/disable WiFi, label WAPs, refresh the firewall configuration, and reboot the firewall.

russellhltn wrote:[Wireless access points have different wired and wireless] addresses.

In new TM feature (available later next week) will show both the MAC and WiFi address for each WAP on the "Access Points" tab.

CleggGP
Church Employee
Church Employee
Posts: 118
Joined: Mon Jul 28, 2014 12:55 pm

Re: Technology Manager 2.0 Release

Postby CleggGP » Tue Nov 08, 2016 3:08 pm

CleggGP wrote:[A] new TM feature ... will show both the MAC and WiFi address for each WAP on the "Access Points" tab.

FYI. A TM update was released today that includes a new feature that lists both MAC and WiFi addresses for WAPs, which may help people identify and label AP locations in TM.

jamiep39
New Member
Posts: 41
Joined: Fri Jan 17, 2014 7:48 pm

Re: Technology Manager 2.0 Release

Postby jamiep39 » Wed Nov 09, 2016 5:29 pm

Biggles wrote:Unfortunately not available for Apple products.


I ended up using the Fing network scanner on my iPhone. All of my APs have power injectors mounted in a row in the closet so I just scanned the network for the APs, found one of the APs in the list, pinged it, and unplugged the LAN side of the power injector one at a time until the ping stopped replying. Then I labeled that one and moved on to the next. Saved a lot of time having to wait for them to reboot by just unplugging the LAN. I did 7 APs in about 10-15 minutes.

User avatar
Mikerowaved
Community Moderators
Posts: 3584
Joined: Sun Dec 23, 2007 12:56 am
Location: Layton, UT

Re: Technology Manager 2.0 Release

Postby Mikerowaved » Wed Nov 09, 2016 9:57 pm

jamiep39 wrote:I ended up using the Fing network scanner...

Yes, Fing is a terrific tool. So you were labeling the cables in the wire closet. How were you determining which area of the building each WAP covered?
So we can better help you, please edit your Profile to include your general location.

jamiep39
New Member
Posts: 41
Joined: Fri Jan 17, 2014 7:48 pm

Re: Technology Manager 2.0 Release

Postby jamiep39 » Fri Nov 11, 2016 1:55 am

Mikerowaved wrote:
jamiep39 wrote:I ended up using the Fing network scanner...

Yes, Fing is a terrific tool. So you were labeling the cables in the wire closet. How were you determining which area of the building each WAP covered?


The cables were already labeled. It was the physical location to mac address that I had to figure out.


Return to “Meetinghouse Internet”

Who is online

Users browsing this forum: No registered users and 1 guest