Setting up static IPs
-
- Community Administrator
- Posts: 35532
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
Setting up static IPs
One nice feature of the new Maraki firewalls is that you can now set static IPs via DHCP and TM.
The process appears to be a bit slow. I inputted in the information in TM and then re-configured the printers, but the printers ended up in the general DHCP pool. After a bunch of troubleshooting, I had to restart them to get them back to their assigned IP.
It's possible the process may be quicker if you set the printers to DHCP first and then use the lookup tool in TM to locate and select the printer. That tool doesn't scan the static area, so it won't find anything that's already manually configured with a static IP.
One tip: To find the mac address of a device on the network, open a CMD prompt and type:
arp -a 0.0.0.0
Substituting the target IP address for "0.0.0.0". I'd suggest changing the dashes into colons when copying. I'm not sure how TM will act to dashes.
The process appears to be a bit slow. I inputted in the information in TM and then re-configured the printers, but the printers ended up in the general DHCP pool. After a bunch of troubleshooting, I had to restart them to get them back to their assigned IP.
It's possible the process may be quicker if you set the printers to DHCP first and then use the lookup tool in TM to locate and select the printer. That tool doesn't scan the static area, so it won't find anything that's already manually configured with a static IP.
One tip: To find the mac address of a device on the network, open a CMD prompt and type:
arp -a 0.0.0.0
Substituting the target IP address for "0.0.0.0". I'd suggest changing the dashes into colons when copying. I'm not sure how TM will act to dashes.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.
So we can better help you, please edit your Profile to include your general location.
So we can better help you, please edit your Profile to include your general location.
- johnshaw
- Senior Member
- Posts: 2290
- Joined: Fri Jan 19, 2007 1:55 pm
- Location: Syracuse, UT
Re: Setting up static IPs
I did a little looking at the tool and found this:
IP Assignments
This tool allows you to assign IP addresses from the static IP range to specific devices by MAC address.
It appears that the assignment is supposed to be in the STATIC range of the pool rather than the DHCP? Maybe with the TM tool not really functioning today, I'm not seeing where to do the DHCP, but using static is more in line with what I've done in our stake.
IP Assignments
This tool allows you to assign IP addresses from the static IP range to specific devices by MAC address.
It appears that the assignment is supposed to be in the STATIC range of the pool rather than the DHCP? Maybe with the TM tool not really functioning today, I'm not seeing where to do the DHCP, but using static is more in line with what I've done in our stake.
“A long habit of not thinking a thing wrong, gives it a superficial appearance of being right, and raises at first a formidable outcry in defense of custom.”
― Thomas Paine, Common Sense
― Thomas Paine, Common Sense
-
- Community Administrator
- Posts: 35532
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
Re: Setting up static IPs
It is, and it does. When I was done, all of the devices were back at their old IP address, only the devices were set to 'DHCP' and it was the assignment that set the IP rather than a static setting on the device.johnshaw wrote:It appears that the assignment is supposed to be in the STATIC range of the pool rather than the DHCP?
The problem I ran into is that it appears to take time for the new assignment in TM to make it's way to the firewall. As a result, when you set the device to DHCP, it may initially be in the DHCP pool instead of the intended address. The problem will straighten out if given time (and can be speeded up by rebooting the device) without any further changes in TM. I just wanted to warn others wanting to make the change so they can save some of their hair. <grin>
Now, why would anyone want to change from device-configured static to firewall-configured assignment? Well, one of the changes is that now the ISP "Notes" in TM is limited to 400 characters. As a result, all my notes on static IP assignments were wiped out. By putting the assignments in the firewall, you're reasonably assured that your assignments are there for all to see: FM, CHQ, etc.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.
So we can better help you, please edit your Profile to include your general location.
So we can better help you, please edit your Profile to include your general location.
- johnshaw
- Senior Member
- Posts: 2290
- Joined: Fri Jan 19, 2007 1:55 pm
- Location: Syracuse, UT
Re: Setting up static IPs
Russell, thanks for doing the leg work on this. And what you describe is different than I'd expect... the term STATIC has a historical meaning in the IT world, as does DHCP Reservation. This is really good information to have and again, thanks for figuring it all out.
“A long habit of not thinking a thing wrong, gives it a superficial appearance of being right, and raises at first a formidable outcry in defense of custom.”
― Thomas Paine, Common Sense
― Thomas Paine, Common Sense
-
- Church Employee
- Posts: 69
- Joined: Mon Dec 23, 2013 1:54 pm
Re: Setting up static IPs
It is DHCP reservation. Even though a static IP and a DHCP reservation is different (configured on the device vs. on the router), they both result in a static/fixed IP assignment. Because of that, we restricted it to just the static range to keep it consistent and self documenting (if you choose to use it)
-
- Community Administrator
- Posts: 35532
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
Re: Setting up static IPs
When you go to make the assignment, you pick from a drop down list. So, I think you're stuck with assignments in the static "pool".
One thing that I'm sure is going to throw people off - when that screen comes up, it's set for the "User" network. You can only pick form 192.168.s.s addresses. There's a drop-down list in the upper right where you need to select "SP" if you want to configure the FHC printers (10.x.x.x).
One thing that I'm sure is going to throw people off - when that screen comes up, it's set for the "User" network. You can only pick form 192.168.s.s addresses. There's a drop-down list in the upper right where you need to select "SP" if you want to configure the FHC printers (10.x.x.x).
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.
So we can better help you, please edit your Profile to include your general location.
So we can better help you, please edit your Profile to include your general location.
- Mikerowaved
- Community Moderators
- Posts: 4816
- Joined: Sun Dec 23, 2007 12:56 am
- Location: Layton, UT
Re: Setting up static IPs
The delay is due to the current IP address lease still being active. When that decays to zero, the new IP assignment will take affect. I don't know what the Meraki's IP lease times are set to, but probably around 30 minutes.russellhltn wrote:The problem I ran into is that it appears to take time for the new assignment in TM to make it's way to the firewall.
So we can better help you, please edit your Profile to include your general location.
-
- Community Administrator
- Posts: 35532
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
Re: Setting up static IPs
I'm talking about a delay from TM config to the firewall. I'm sure it has to due with TM having to talk to a connector to the Meraki's cloud and the firewall getting the message. Until I re-configure the printer, there is no IP lease.Mikerowaved wrote:The delay is due to the current IP address lease still being active. When that decays to zero, the new IP assignment will take affect.russellhltn wrote:The problem I ran into is that it appears to take time for the new assignment in TM to make it's way to the firewall.
Now, if we're talking about how long from the time the printer gets a DHCP pool IP address and when it gets it's assigned IP, yes, I'm sure the lease has something to do with that. That's when you need to reboot the printer.
When I checked on the stake computer on Sunday, I saw 24 hours. Which raises an interesting question - I wonder if the 991 IP addresses in the "User" pool is going to be enough for the 5 wards that meet at our stake center? It would be interesting to see the user stats.Mikerowaved wrote:I don't know what the Meraki's IP lease times are set to, but probably around 30 minutes.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.
So we can better help you, please edit your Profile to include your general location.
So we can better help you, please edit your Profile to include your general location.
-
- Community Moderators
- Posts: 11682
- Joined: Mon Mar 17, 2008 10:27 pm
- Location: US
Re: Setting up static IPs
I would start looking for a way to reduce the lease times, including calling the GSC if necessary.russellhltn wrote:When I checked on the stake computer on Sunday, I saw 24 hours. Which raises an interesting question - I wonder if the 991 IP addresses in the "User" pool is going to be enough for the 5 wards that meet at our stake center? It would be interesting to see the user stats.
- johnshaw
- Senior Member
- Posts: 2290
- Joined: Fri Jan 19, 2007 1:55 pm
- Location: Syracuse, UT
Re: Setting up static IPs
We fixed this problem before with Cisco... round and round we go
“A long habit of not thinking a thing wrong, gives it a superficial appearance of being right, and raises at first a formidable outcry in defense of custom.”
― Thomas Paine, Common Sense
― Thomas Paine, Common Sense