Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Re-segmenting my network

Original Message
Name: A_Keith (by derrylgreen)
Date: October 25, 2007 at 08:22:37 Pacific
Subject: Re-segmenting my network
OS: CiscoIOS
CPU/Ram: 36MB
Model/Manufacturer: Cisco2900
Comment:
I currently have a 10.10.0.0/16 network that I would like to re segment to 10.10.0.0/17. Currently I have about 20 work group level cisco 2900 series switches all on Vlan1 with management IP's. I'm currently looking to add VOIP on a separate VLAN with QoS. Am I right to assume that I will need to remask all network and networked devices? And that may be a little more work and require a large work window? What are the best options or practices?



Report Offensive Message For Removal


Response Number 1
Name: jefro
Date: October 25, 2007 at 14:12:08 Pacific
Subject: Re-segmenting my network
Reply: (edit)
Before I answer, let me ask what you either know or feel you need to change this for. Also what is your current useage? Any core switches?

I prefer the java web based application. The java based tools are frowned upon by cisco and may slow the switches but provide very good graphical displays of your current state.
You can print all that to a text file too.

Then you'd have to estimate what the voip would consume.

I read it wrong and answer it wrong too. So get off my case you peanut.


Report Offensive Follow Up For Removal

Response Number 2
Name: wanderer
Date: October 25, 2007 at 14:40:14 Pacific
Subject: Re-segmenting my network
Reply: (edit)
Might want to consider instead of remasking use a completely different subnet for the voip.

You can implement with no impact on your existing ip configuration.

Imagine the power if you knew how to internet search


Report Offensive Follow Up For Removal

Response Number 3
Name: Ryan (by evil_lbt)
Date: October 25, 2007 at 20:32:40 Pacific
Subject: Re-segmenting my network
Reply: (edit)
Don't use the SDM that came with your switch. The main reason is the lack of functionality.

/16 should be more than enough for any network. Why do you want to change it to /17 for? doing so will require you to change all the subnet mask on all the DHCP server. If you do not have enough documentation on your network, don't do it, else you might screw things up.


Report Offensive Follow Up For Removal

Response Number 4
Name: A_Keith (by derrylgreen)
Date: October 28, 2007 at 20:56:09 Pacific
Subject: Re-segmenting my network
Reply: (edit)
Thanks for confirming my thoughts guys, as wanderer suggested I've decided to go with a different subnet. My thoughts on it is that it will require to much to remask the current segment.

Report Offensive Follow Up For Removal




Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Re-segmenting my network

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




XP Installed to G?

exessive internet traffic

ZoneAlarm Question. Blocked Connect

Windows Live Messenger Problem

Delete $Uninstall after SP3 updates


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC