Management Network Design - IP Addressing

Hello !
I have a basic question with IP addressing for management network. We use management IP address to identify each network element. I have come across two forms of IP addressing for management network:
1. Assign the IP address directly to an interface (if its a L2 switch, the interface is made L3 using *no switchport* command) of the network element.
2. Create a SVI i.e., define a management VLAN on each network element, assign IP to this VLAN and assign a port to this VLAN for management.
Both these designs provide IP termination on the network elements for management using standard network management protocols. I am wondering what's the difference between the two. Any significant advantage of one over the other ? Please share your thoughts.
P.S. Many vendors don't seem to support command equivalent to *no switchport* on Cisco L2 switches. I presume the reason for this is they don't have MAC addresses on L2 switch ports. Each switch has only 1 MAC address (which identifies the switch) unlike Cisco switches wherein each interface has its own MAC address and can be converted to a L3 interface.
Thanks & Regards,
Naveen

In addition to method #1 and #2 you mention, there's also the use of a loopback interface (applicable on Cisco routers) and, where available, the dedicated Ethernet management port on the device which uses its own management virtual routing and forwarding (vrf) instance, Where applicable, those two methods are the preferred ones as they have a higher degree of reliability and isolation from any routing protocols in the devices' primary routing information bases (ribs or routing tables) and, in some cases even have a dedicated CPU to isolate you from runaway main CPU utilization in the device. For routers the loopback interface is the preferred method. See page 23 of the SBA WAN Deployment Guide.
Between #1 and #2 you can make an argument either way. #1 requires a dedicated physical layer link which can be a good thing (no dependency on a shared trunk being up) or bad thing (requires using a physical port and possibly a scarce inter-floor or inter-building link). The most common method I see and one recommended by Cisco is #2 - a management VLAN SVI. See pages 19-20 of the SBA LAN Deployment Guide, for instance.
Besides the IP addressing, there's a lot of good best practices around securing the management plane and deploying centralized authentication etc. Pay attention to those aspects as well. They are covered in some of the SBA Design Guides (parent page here) as well as in the material supporting Implementing Cisco IOS Network Security, the foundation guide for CCNA Security certification.

Similar Messages

Hyper-v Management network design

Folks
I am looking into some best practices ; here is the scenario :
Multi Node hyper -V cluster
each machine had two pairs of teamed NIC cards ( 2 teams/server )
storage network is a separate SaS network and no iSCSI ; so we will have followings for remains :
Cluster network
Live Migration network
Management network
VM production traffic
Our goal is to have an efficient network , so we are going to dedicate one Teamed-NIC to our external network.
we end up having one more teamed-NIC per server to manage cluster , Live Migration and Management network.
we do have separate switches for management environment ; so what would be the best approach ?
My thought :
1-Create different virtual NICs for cluster/liveMigration and Management within Hyper-V ; these NICs will be usable
through management operating system as well.
2- Assign different IP subnets to each network
3- Connect last Teamed-NIC to management switches ; configure VLAN and QoS ; so that cluster traffic gets priority .
OR .. should I configure QoS through HyperV virtual switch ?
Any thoughts ? suggestions ?

Hi Ali,
"3- Connect last Teamed-NIC to management switches ; configure VLAN and QoS ; so that cluster traffic gets priority . "
I think you may configure Qos for your environment , please refer to following link :
http://technet.microsoft.com/en-us/library/jj735302.aspx#bkmk_1
Best REgards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Ask the Expert: Hierarchical Network Design, Includes Core, Distribution, and Access

Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about hierarchical network design.
Recommending a network topology is required for meeting a customer's corporate network design needs in their business and technical goals and often consists of many interrelated components. The hierarchical design made this easier like "divide and conquer" the job and develop the design in layers.
Network design experts have developed the hierarchical network design model to help to develop a topology in discrete layers. Each layer can be focused on specific functions, to select the right systems and features for the layer.
A typical hierarchical topology is
A core layer of high-end routers and switches that are optimized for availability and performance.
A distribution layer of routers and switches that implement policies.
An access layer that connects users via lower-end switches and wireless access points.
Ahmad Manzoor is a Senior Pre-Sales Engineer at AGCN, Pakistan. He has more than 10 years of experience in first-rate management, commercial and technical skills in the field of data communication and services lifecycle—from solution design through sales pitch, designing RFPs, architecture, and solution—all with the goal toward winning projects (creating win/win situations) of obsolete solutions. Ahmad also has vast experience in designing end-to-end data centers, from building infrastructure design to data communication and network Infrastructure design. He has worked for several large companies in Pakistan and United Arab Emirates markets; for example, National Engineer, WATEEN Telecom, Emircom, Infotech, Global Solutions, NETS International, Al-Aberah, and AGCN, also known as Getronics, Pakistan.
Remember to use the rating system to let Ahmad know if he has given you an adequate response.
Because of the volume expected during this event, Ahmad might not be able to answer every question. Remember that you can continue the conversation in the Solutions and Architectures under the sub-community Data Center & Virtualization, shortly after the event. This event lasts through August 15, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Dear Leo,
We are discussing the following without any product line, discussing the concept of hierarchical design, which will help you to take decision which model is better for you Two Layer or Three Layer hierarchical model.
Two-Layer Hierarchy
In many networks, you need only two layers to fulfill all of the layer functions—core and aggregation
Only one zone exists within the core, and many zones are in the aggregation layer. Examine each of the layer functions to see where it occurs in a two-layer design:
Traffic forwarding—Ideally, all interzone traffic forwarding occurs in the core. Traffic flows from each zone within the aggregation layer up the hierarchy into the network core and then back down the hierarchy into other aggregation zones.
Aggregation—Aggregation occurs along the core/aggregation layer border, allowing only interzone traffic to pass between the aggregation and core layers. This also provides an edge for traffic engineering services to be deployed along.
Routing policy—Routing policy is deployed along the edge of the core and the aggregation layers, generally as routes are advertised from the aggregation layer into the core.
User attachment—User devices and servers are attached to zones within the aggregation layer. This separation of end devices into the aggregation permits the separation of traffic between traffic through a link and traffic to a link, or device. Typically, it is best not to mix transit and destination traffic in the same area of the network.
Controlling traffic admittance—Traffic admittance control always occurs where user and server devices are attached to the network, which is in the aggregation layer. You can also place traffic admittance controls at the aggregation points exiting from the aggregation layer into the core of the network, but this is not common.
You can see, then, how dividing the network into layers enables you to make each layer specialized and to hide information between the layers. For instance, the traffic admittance policy implemented along the edge of the aggregation layer is entirely hidden from the network core.
You also use the core/aggregation layer edge to hide information about the topology of routing zones from each other, through summarization. Each zone within the aggregation layer should have minimal routing information, possibly just how to make it to the network core through a default route, and no information about the topology of the network core. At the same time, the zones within the aggregation layer should summarize their reachability information into as few routing advertisements as possible at their edge with the core and hide their topology information from the network core.
Three-Layer Hierarchy
A three-layer hierarchy divides these same responsibilities through zones in three vertical network layers,
Traffic Forwarding—As with a two-layer hierarchy, all interzone traffic within a three- layer hierarchy should flow up the hierarchy, through the layers, and back down the hierarchy.
Aggregation—A three-layer hierarchy has two aggregation points:
At the edge of the access layer going into the distribution layer
At the edge of the distribution layer going into the core
At the edge of the access layer, you aggregate traffic in two places: within each access zone and flowing into the distribution layer. In the same way, you aggregate interzone traffic at the distribution layer and traffic leaving the distribution layer toward the network core. The distribution layer and core are ideal places to deploy traffic engineering within a network.
Routing policy—The routing policy is deployed within the distribution layer in a three- layer design and along the distribution/core edge. You can also deploy routing policies along the access/distribution edge, particularly route and topology summarization, to hide information from other zones that are attached to the same distribution layer zone.
User attachment—User devices and servers are attached to zones within the access layer. This separation of end devices into the access layer permits the separation of traffic between traffic through a link and traffic to a link, or device. Typically, you do not want to mix transit and destination traffic in the same area of the network.
Controlling traffic admittance—Traffic admittance control always occurs where user and server devices are attached to the network, which is in the access layer. You can also place traffic admittance controls at the aggregation points along the aggregation/core edge.
As you can see, the concepts that are applied to two- and three-layer designs are similar, but you have more application points in a three-layer design.
Now the confusion takes place in our minds where do we use Two Layer and where the Three layer hierarchical model.
Now we are discussing that How Many Layers to Use in Network Design?
Which network design is better: two layers or three layers? As with almost all things in network design, it all depends. Examine some of the following factors involved in deciding whether to build a two- or three-layer network:
Network geography—Networks that cover a smaller geographic space, such as a single campus or a small number of interconnected campuses, tend to work well as two-layer designs. Networks spanning large geographic areas, such as a country, continent, or even the entire globe, often work better as three layer designs.
Network topology depth—Networks with a compressed, or flattened, topology tend to work better as two-layer hierarchies. For instance, service provider networks cover large geographic areas, but reducing number of hops through the network is critical in providing the services they sell; therefore, they are often built on a two-layer design. Networks with substantial depth in their topologies, however, tend to work better as three-layer designs.
Network topology design—Highly meshed networks, with many requirements for interzone traffic flows, tend to work better as two-layer designs. Simplifying the hierarchy to two levels tends to focus the design elements into meshier zones. Networks that focus traffic flows on well-placed distributed resources, or centralized resources, such as a network with a large number of remote sites connecting to a number of centralized Data Centers, tend to work better as three-layer designs.
Policy implementation—If policies of a network tend to focus on traffic engineering, two-layer designs tend to work better. Networks that attempt to limit access to resources attached to the network and other types of policies tend to work better as three-layer designs.
Again, however, these are simple rules of thumb. No definitive way exists to decide whether a network should have two or three layers. Likewise, you cannot point to a single factor and say, “Because of this, the network we are working on should have three layers instead of two.”
I hope that this helps you to understand the purposes of Two Layer & Three layer Hierarchical Model.
Best regards,
Ahmad Manzoor

Management VLAN Design and Implementation

Greetings, friends. I'm having trouble getting a clear picture of how a management VLAN ought to look. I just installed a Catalyst 6509-E as my core switch, and as soon as they arrive I'm going to be replacing all of our other (HP) switches with Catalyst 3560X switches. I understand the reasoning behind segregating traffic, not using VLAN1, etc., but I've never actually implemented a management VLAN--I've always just accessed the switches via the IPs assigned to them where all the client traffic flows (not VLAN1, by the way).
Is "management VLAN" simply what we as humans call a VLAN we dedicate to management activities, or is there something official in these switches to designate a "management VLAN?"
Is it best practice to include SNMP, netflow, syslog, and NTP as "management" traffic?
There's a lot of documentation talking -about- management and management VLANs, but unless I'm blind or not looking hard enough I can't seem to find any implementation whitepapers or best practices whitepapers that demonstrate setting one up on a campus LAN. Are you able to point me in the right direction to find such documentation? Is it perhaps buried in a manual somewhere that isn't explicitly labeled "Management VLAN Design and Implementation" or somesuch?
What is the best practice for accessing the management VLAN? Inter-VLAN routing + ACLs? Multi-homed PCs or servers? Additional PCs to be used as access stations?
Thank you for your wisdom, experience, and advice!
Kevin

1. Yes, you may want to keep this traffic separate of the other traffic limiting device management access to just this vlan, as this prevents eavesdropping.
2. Indeed all other housekeeping goes via this VLAN altough you could limit it to the interactive or session traffic.
3. On a campus you could think of one big VLAN spanning the campus, one a multi-site environment or where you use L3 to go to you datacenters you probably need multiple management lan's. I've seen implementations where the management traffic was kept separate and even didn't use the routing protocol in use. The whole management lan was statically routed and would work even if OSPF or BGP was down.
4. I feel a situation where the people providing support are connected on the lan giving access to the devices is probably best. A dual homed pc is a good solution I think, other customer feel the management lan should be treated as a DMZ accessible via a firewall, but the hardcore customer insist on a second pc connected to the management lan.
Points to consider are as always,
Find the single point of failure. Any device, L2 L3 firewall that could cut off management from accessing a part of the network.
Find the right balance between security, costs, easy of access for the business your in.
Cheers,
Michel

Hyper V Networking Design

I am designing a new Hyper v network with 3 nodes. Each node has 8 NICs and I want to team 2 NICs per network.
Team 1 will be the Management Network. A team will be created at the OS layer and a virtual switch will be created for the Network.
OS Management
Live migration
Heart Beat
These services will be added as interfaces on the network adaptor and will be VLAN'd. QoS will then be added to the virtual switch for the Management and Heart beat network interfaces to ensure that these services are not compromised.
The CSV network communication will managed by the virtual machine network but I may enable cluster communications on the Management network Team 1 instead.
Please advise.

Very informative reply. Helps very much :)
The other 4 ports will be for production VM traffic and storage is FC on a dual channel HBA. The over all Network design is based on Blade architecture:
Storage
1 FC HBA Dual Channel
Ethernet
2 NICS for
OS Management
Live migration
Heart Beat
4 NICs for
VM Production Traffic
Back ups are using the Native solution with agents for VM over a fibre channel network connection back to our DC.
Looking Good?
Also
What is the better approach for managing QoS on the network for hyper v 2012 r2
Create the team - Create the switch - Tag the VLAN interfaces to the team for :
OS Management
Live migration
Cluster comms
then apply Weight using Powershell
Create a management team - create a switch with the management VLAN tagged then apply the ploicy
Configuring Policy-based Quality of Service (QoS)
http://technet.microsoft.com/en-us/library/hh831689.aspx
Please advse

OVM 3.2.6 Delete Management Network

Hi there,
I was wondering if there is a way to delete unnecessary management networks. I created an extra vlan and set it as mgmt net for testing purposes. Now I would like to remove it but OVM manger doesn't let me. And it also wouldn't let me change IP addresses inside the management network.
Is there a known workaround for this?
Thanks,
Lotsie

This doesn't address your real issue, but just let me comment on the poor exception handling you mention in your previous post because I agree with you and complained about in my first reply:
The one thing I wouldn't understand is this: if it is intended to have only one management network and not modify it after the initial setup, then why does the GUI let me mark other networks as Mgmt? Also, if I can add several Mgmt networks, then why is it not allowed to delete the unnecessary ones afterwards?
Apparently, my complaint is no longer valid as it appears the developers fixed this issue way back in 3.1.1. I was in the process of setting up a similar scenario as yours in one of my labs (a 3.1.1-625 lab) and found that I was not able to create a new network I named "Test server mgmt" using the server management channel - the network wizard stopped me with the following error:
"OVMRU_0010134E: Cannot add vlan segment [network.VlanSegment (922) in Bond2 VLANs] to network [Test server mgmt] because server [myserver4] has management network [Dom0 bond0 SM].
I also encountered the same exception handling in one of my 3.2.6 labs - Oracle VM Manager does not allow people to create a second network using the server mgmt channel if one already exists.
Anyway, this doesn't help with your problem, but it does show that I learn something new every day - I can't complain about that as something we need to improve on any more :-)
Let me do a little more digging to see if I can find you an easy solution...
-Greg

Validate PIX & IPS Network Design

Attached is my network design of the PIX and the IPS in promiscuous mode (non-inline). It doesn't look sound:
1. Is it possible to set up the IPS in non-inline mode with two sensors?
2. Can the IPS direct blocking commands to the PIX through the Desktop Management console? If not, do I need to place an internal switch for the desktop console and the command/control interfaces of the PIX and IPS?
3. Other comments/suggestions?

Cisco IPS Version 5.0 Sensor can be configured either in the IPS (inline) mode or the promiscuous IDS mode. If your sensor already has more than one monitoring interface, no additional hardware is required to run Cisco IPS Sensor Software Version 5.0 in the IPS (inline) mode. IPS services require at least one monitoring interface pair (two monitoring interfaces). Cisco provides the option of upgrading sensors with a single monitoring interface to support multiple monitoring interfaces. For more information on the various IDS and IPS sensor platforms and part numbers, please refer to Cisco IPS 4200 Series Data Sheet located at: http://www.cisco.com/go/ips
http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/products_qanda_item0900aecd801e6a99.shtml

ASA Management 0/0 IP Address

hi all,
just a quick question, what's the best practice in assigning IP address on ASA's management interface? or does it have a benefit of using one?
we have a /28 public IP and was thinking i could use one on it so that we could HTTPS over the internet (or is this safe?). or maybe not waste a public IP since we have a dedicated OBM box to dial in?
or do i assign private IP address which would be on the same subnet with the 'inside' interface IP address?

Unless you have a true out of band management network or a service module (IPS, CX or SFR) managed via the the management interface, it's usually problematic to use the management interface since the ASA does not have the concept or a separate management VRF. Thus even if you have a dedicated address to assign it, return traffic "wants" to flow out one of the production interfaces per the global routing table.
Service modules have their own default gateway etc. and generally require one use the management interface.
The majority of installations I see just use one of the production interfaces (usually inside) for management, sometimes restricted to certain subnets.

I have an iphone 4 connected to my imac/itunes using a designated email address. However, I also have an 80gb ipod classic which is connected to my general email account. How can I transfer my ipod to the same account as the iphone

I have an iphone 4 connected to my imac/itunes account using its own designated email address. However, I also have an 80gb ipod classic which is connected to my general email address. How can I delete this and transfer the ipod to the same account as the iphone 4. Thankyou

iPods, iPhones, and iPads aren't tied to one particular iTunes accout/Apple ID. So there are no special instructions to follow to allow you to sync it with your newer account. Simply sync it as you would your iPhone 4.
B-rock

Office network design ideas..

Hey all, we are upgrading to a Cisco network and wanted some input on our possible network design...
Currently we have:
A Juniper SSG 140 and IDP for our firewall and IDS
3com (layer2/3) switches for our desktops
2 Dell PowerConnect 5424 switches for our servers and firewalls
2 Dell PowerConnect 5424 switches (separate network) for our SAN/VM hosts
This is what we are thinking of for our next solution
ASA 5512 for our firewall (I read we could possibly get a 25% performance speed improvement for user VPN connections?)
2 WS-C3750x-48t-e (I think this does Layer 2/3) for our desktops
2 WS-C3750x-48t-e for our firewalls/servers
2 WS-C3750x-24P-L for our SAN/VM hosts
The problem is different network services providers who are going to implement this for us are giving us different solutions
Some desktop 3560X for desktops and 4948 for servers and others are telling me 3750x for desktops and Nexus 3048 switches for SAN
Some are telling me we can keep SAN+VM+core traffic on the same switches and just separate them with VLANs while others are telling me we should get separate switches for them
Basically, we just want a improved improvement with better PERFORMANCE and REDUNDANCY (esp with our core + SAN/VM traffic) without going overboard and spending a ton of money
More thoughts:
We need Layer 2/3 switches for core + SAN
Do we need 10G ports?
Let me know your thoughts...

Hi There,
the hardware selection actually depends on the network/site topology, number of users, traffic load and more other factors
this is for IP network, for SAN do you mean iscsi, FCoE or pure FC SAN because these are different things and may change the HW selection,
in general 3560 are good fro access switches and 3750 provide same capabilities with improved performance and support for swtckwise ( 3750 is a good option especially if you planing to stack them )
for L3 it is supported on both but consider the license/image you buy with regard to the features you need
nexus for Data center switch are the best as they are design for data center switching however you need to know, port density, 1G or 10G, do you need any FC SAN, DC load/capacity, any L3 function is required and future growth then you can decide if Nexus 3K or 5K is good for you or not
N5K
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/data_sheet_c78-618603.html
N3K
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps11541/at_a_glance_c45-648255.pdf
if yo have a network topology with more details of what you need, post it here for more discussions
hope this help
if helpful rate

Need help on network design

Hi guys.
Looking for some advice on a network design.
Please tell me what you think may or may not be wrong or missing.
Here are the details:
The user count is approximately 600 (desktops, laptops and Cisco IP phones) with two locations (office and data center) connected via 100Mbps guaranteed MAN line with site-to-site VPN as backup.
Servers will all be in the Data Center.
Edge routers to be used as site-to-site VPN connection point between office and data center.
Edge router at data center also to be used to connect to 4 other remote sites.
Edge networks (router and ASA) will be used to provide internet access to equipment at their respective locations. (No routing across MAN for internet access)
Cisco 4510 to be used as user switches.
Supervisor engines will be connected via 10G fiber to core switches.
There will be 2x 10G connection for each supervisor module.
Core switches are 4500x to be stacked via VSS using 10G Twinax cables.
Core switch will also have 1G copper sfp to connect to MAN line hand-off.
There will also be a physically (for the most part) segregated network using 3750x
switches that connect back to the core. We will use 1G Fiber connections.
Here is the current kit list:
Office Network Edge
1x Cisco 3925 Router to connect to internet and vpn tunnel endpoint (CISCO3925-HSEC+/K9)
1x 2GB RAM upgrade for Cisco Router (MEM-3900-1GU2GB)
1x 1GB Compact Flash for Cisco Router (MEM-CF-256U1GB)
1x ASA Firewall w/ IPS (ASA5525-IPS-K9)
Office Network Core
2x 4500X 32 Port Switches (WS-C4500X-32SFP+) w/ IP Enterprise License
2x 1GB Fiber SFP module per 4500X switch to connect to 3750x (GLC-SX-MMD)
2x 10GB TwinAX cables to stack 4500x switches together (SFP-H10GB-CU1M)
8x 10GB Fiber SFP+ module to connect to 4510 Sup Engines (SFP-10G-SR))
1x 1GB Copper SFP to connect to MAN circuit hand-off (GLC-T)
1x 1GB Copper SFP to connect to ASA firewal (GLC-T)
Distribution
4x Catalyst 4510R+E Switches (WS-C4510R+E) w/ IP Base License
2x Supervisor 8-E per 4510 switch (WS-X45-SUP8-E)
8x 48-port PoE module per 4510 switch (WS-X4748-UPOE+E)
4x 10G Fiber SFP+ module per 4510 switch (SFP-10G-SR)
1x 2GB SD Memory card per Supervisor Engine (SD-X45-2GB-E)
Office Network Segregated
4x 3750X 48-port PoE Switches (WS-C3750X-48P-L) LAN Base License
1x 1G Fiber SFP module per 3750x switch (GLC-SX-MMD)
1x Slot module per 3750x to connect 1GB SFP modules (C3KX-NM-1G)
Data Center Edge
1x Cisco 3925 Router to connect to internet and vpn tunnel endpoint (CISCO3925-HSEC+/K9)
1x 2GB RAM upgrade for Cisco Router (MEM-3900-1GU2GB)
1x 1GB Compact Flash for Cisco Router (MEM-CF-256U1GB)
1x ASA Firewall w/ IPS (ASA5525-IPS-K9)
Data Center Core
2x 4500X 32 Port Switches (WS-C4500X-32SFP+) w/ IP Enterprise License
2x 10GB TwinAX cables to stack 4500x switches together (SFP-H10GB-CU1M)
3x 10GB Fiber SFP+ modules per 4500X switch to connect to 3850 switches (SFP-10G-SR)
1x 1GB Copper SFP to connect to MAN circuit hand-off (GLC-T)
1x 1GB Copper SFP to connect to ASA firewall (GLC-T)
1x 1GB Copper SFP to connect to segregated ASA (GLC-T)
Data Center Distribution
6x 3850 24-port PoE Switches (WS-C3850-24T-S) IP Base License
1x Slot module per 3850 switch to connect 10GB SFP+ modules (C3850-NM-2-10G)
1x 10G Fiber SFP+ module per 3850 switch (SFP-10G-SR)
Data Center Segregated
1x Cisco 2951 Router to connect to internet and vpn tunnel endpoint (CISCO2951/K9)
1x ASA 5512-X (ASA5515-K9)
Attached diagram is just a draft.

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
A 39xx is underpowered if you want to support gig VPN tunnel.
If your MAN is 100 Mbps (possibly "light" for 600 users), I would suggest running your port at 100 Mbps, not gig. (This because LAN switches don't shape, and may not be able to "see" congestion or drops within the MAN.)
You user edge (the 4500s) will be L2 or L3. If the latter, I would recommend not using a VSS core.
I would recommend not using the same Internet connection for both general Internet access and VPN.

How do I manage duplicates in my address book

How do I manage duplicates in my address book.
I am using iOS 7 and iCloud

Hi nacnud1234,
If you are having issues with duplicates when using iCloud Contacts, you may find the following article helpful:
iCloud: Resolving duplicate Contacts after setting up iCloud Contacts
http://support.apple.com/kb/ts4147
Regards,
- Brenden

High Level Network Design

Hi Guys
I am posting this because I am starting my career into network design and want some help in it. I am at present in need of a high level design overview as I need to prepare some high level network design documents. Can anyone shower some thoughts in it as how about doing this and if any there is a template for HDD so that it maybe useful.
Also I believe in keeping information as transparent as possible to the readers of the document and need someone to explain in very simple terms if at all it is possible.
Thanks a lot
Vin

Hi Vin,
I would check the Cisco SBA and Validated Design Zone as a first pass.
Lots of great design documents there.
As for how I would create a high level design - keep it simple. You just want an overview of the connectivity - e.g. for a dual-site head office with 100+ branch wan, I would only show a single branch site as a template.
Every network is different, but the more documentation you write and read the more you will define your own style.
Apologies I can't give you any of my customer's documentation - NDA's and everything!
Regards, Ash,

Management network configuration

Hi,
Oracle configuration worksheets suggest two option under table 5 : Management Network Configuration Worksheet :
Select which network is used for the database server host name. The options are :
admin network
or
client network.
1) Regarding best practice which network i should choose ?
2) If i choose "admin network" , is that mean that i will not have the option to run exadata/cluster/database command directly from the database host ?
Thanks
Edited by: Yoav on 07:02 13/05/2012

robinsc wrote:
Whenr they installed our system it took the admin host names by default. I did n't know there was a choice. So if you want to change the names at a later pointof time is there any standard way to do this or you have to live with what was there before...
Or do you just edit /etc/hosts and /etc/sysconfig/network ?
ThanksThis is a fairly recent change in the configuration worksheets. I wouldn't want to change the hostnames in a cluster, as it could lead to problems inside of grid infrastructure. When changing hostnames or IPs on an Exadata rack, you want to use the ipconf utility, not just change the values in /etc/sysconfig/...
If you change the IP on a cell without ipconf, then you could run in to trouble when patching. We've seen cells that reset to the previous IP after patching when a customer changed the IP without using ipconf.

Cisco Video Telephony Solution Reference Network Design (SRND)

Below are links to two design guides focused on video telephony and videoconferencing. The first link is goes to the NEW Video Telephony guide while the second links to the existing Videoconferencing guide that has been referenced before in a previous thread.
Cisco Video Telephony Solution Reference Network Design (SRND):
http://www.cisco.com/application/pdf/en/us/guest/netsol/ns268/c649/ccmigration_09186a008026c609.pdf
IP Videoconferencing Solution Reference Network Design (SRND):
http://www.cisco.com/application/pdf/en/us/guest/netsol/ns280/c649/ccmigration_09186a00800d67f6.pdf

Hi
As long as this is new instalation I recommend you to use SIP on all of the end points where possible and integrate with CUCM using sip trunk this will give you two main benefits
- the transformation of the called and calling number from and to CUCM will be easier
-if have end point using H323 and communicating with other end using sip the vcs will do internetworking to this call and you will need license for each internetworked call plus the media path will go through the vcs not direct between end points for internetworking
If you use sip make the end point name/sip usri as [email protected] Calls from vcs to CUCM use search rules with trsformation so if end point dial 123456 only from vcs and the default call is sip vcs will send it to CUCM as 123456@sip domain.com you need to do transformation before sending it to CUCM and send it as 123456@cucmip.
This is just in brief and also using the expersss way you can have your sip domain registered over the Internet and configure dns srv record point sip ton the vcs public ip and Internet calls can come to your end point sip name directly no need to publish ip to others to dial you
HTH
If helpful rate

Management Network Design - IP Addressing

Similar Messages

Maybe you are looking for