?
Solved

Best Practices

Posted on 2013-06-03
2
Medium Priority
?
232 Views
Last Modified: 2013-06-11
Hi All,

If you have a hardware refresh project in place and have Layer 3 switches in production that are using static IP addresses (Virtual Chassis mostly) and a few single non VC switches with only 48 ports, if you have ample IP addresses available in your "management" IP range, how would you manage the static IP addresses and DNS names?  Just looking for the leanest approach. All clients are using DHCP. I was thinking of using different IP addresses and using a temporary DNS name by just using the same DNS Entry and appending it with -temp.  Seems like a lot of different ways to approach this.


Thanks,

R
0
Comment
Question by:rotarypwr
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 3

Accepted Solution

by:
corower earned 750 total points
ID: 39218463
so far i have seen both that DNS bears meaningful info, or is skipped alltogether. the choice is up to you. with L3 (and active routing) i assume, having an meaningful DNS record (both A and PTR) is nice. i think, if you use these IPs only in "management" subnet, and it is not routable, not shown to outside world and, basically, accessed by you only, there is no big need to build up whole DNS structure - some entries in your management-gw hostsfile will definately help. and this depends on size of your network, ofcourse. i have several rather small sites, like under 10 units of networking hardware, i am really lazy and usually i can memorize every IP address in these nets (and, after all, they're sticked right on the front panel of each switch and router), and i have some nice maps with IPs on them,  meanwhile in most campus- and metro-sized networks there are hundreds of switches, routers and bridges, and one would be happy to have both nicely drawn maps and meaningfull names. so, the choice is yours. if you're comfortable with IPs and are not going  to share troubleshooting with others, leave naked IPs. otherwise create DNS records :)
0
 
LVL 22

Assisted Solution

by:eeRoot
eeRoot earned 750 total points
ID: 39220864
It would be best to have a VLAN with an IP range outside of the normal network to keep the network management isolated, but how you assign those IP's and names is up to the network admins.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the hope of saving someone else's sanity... About a year ago we bought a Cisco 1921 router with two ADSL/VDSL EHWIC cards to load balance local network traffic over the two broadband lines we have, but we couldn't get the routing to work consi…
Shadow IT is coming out of the shadows as more businesses are choosing cloud-based applications. It is now a multi-cloud world for most organizations. Simultaneously, most businesses have yet to consolidate with one cloud provider or define an offic…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Suggested Courses

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question