EIGRP within data center

I am looking for best practice advice. In a network I have two Nexus 5548UP switches that are connected together with a port channel.  I have created a layer 3 link over the port channel using vlan 1152 192.168.150.8/30. A management vlan has been also been created on the switches with vlan 211 172.30.211.0/24. A Cisco ASA firewall is connected to the Nexus1 switch and has the inside intereface configured with an IP from the management network. A Cisco Router is connected to the Nexus2 switch and the LAN interface is also configured with an IP from the management network. EIGRP has been configured on all 4 devices. On the Nexus switches all svi's have been configured with the passive-interface command with the exception of the Vlan 1152 SVI's and the Vlan 211 SVI's. I am using the vlan 211 SVI IP for my EIGRP router-id. With this configuration the Nexus switches are neighbored twice with each other on both the 192.168.150.8.0/30 network and the 172.30.211.0/24 network. I would like to reduce that down to where they only neighbor using the layer 3 192.168.150.8.0/30 network but if I put the vlan 211 svi's in passive mode then it will break the neighborship with my ASA and router. To overcome this issue would I be better creating loopback interfaces to use as my router id and also making the links between my switch and ASA plus switch and router layer 3? Is there a better way to do this? I have attached two images, the first being the original design and the second being the proposed design. I have also provided the neighbor show commands from original design which lists all the neighbors being formed.
Nexus1# sh ip eigrp neighbor
IP-EIGRP neighbors for process 100 VRF default
H   Address                 Interface       Hold Uptime SRTT   RTO Q Seq
                                            (sec)         (ms)       Cnt Num
3   172.30.211.1            Vlan211         14   6w6d      3    200   0   439537
2   172.30.211.2            Vlan211         14   6w6d      2    200   0   439536
1   192.168.150.10          Vlan1152        14   6w6d      1    200   0   439535
0   172.30.211.20           Vlan211         14   11w5d     1    200   0   293289
slondc1#

for high availability - I run HSRP.
No single point of failure - I have redundant etherchannels between core and distribution.
Quick convergence - I have manually configured STP root's and secondarys. I also run RPVST
I have a failover pair of PIX535's - with a static route point to the inside IP of the failover pair, if one fails, the other picks up. I have also configured statefull failover - so no connections are lost.
We run EIGRP - mainly from legacy networks, but it runs smooth. We have tweaked the hello/hold timeres, to 1 and 3. We also summarise out to the remote sites (no need to fill up routiong tables, just takes cpu cycles)
All routing protocols have their merits - you just need to choose one you are comfortable with, that you can troublshoot and you know really well. I don't think it's a good idea to implement a routing protocol in a D/C that you are not 100% with.
HTH.

Similar Messages

Deploying Cisco Overlay Transport Virtualization (OTV) in Data Center Networks

Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about how to plan, design, and implement Cisco Overlay Transport Virtualization (OTV) in your Data Center Network with Cisco experts Anees Mohamed Abdulla and Pranav Doshi.
Anees Mohamed Abdulla is a network consulting engineer for Cisco Advanced Services, where he has been delivering plan, design, and implementation services for enterprise-class data center networks with leading technologies such as vPC, FabricPath, and OTV. He has 10 years of experience in the enterprise data center networking area and has carried various roles within Cisco such as LAN switching content engineer and LAN switching TAC engineer. He holds a bachelor's degree in electronics and communications and has a CCIE certification 18764 in routing and switching.
Pranav Doshi is a network consulting engineer for Cisco Advanced Services, where he has been delivering plan, design, and implementation services for enterprise-class data center networks with leading technologies such as vPC, FabricPath, and OTV. Pranav has experience in the enterprise data center networking area and has carried various roles within Cisco such as LAN switching TAC engineer and now network consulting engineer. He holds a bachelor's degree in electronics and communications and a master's degree in electrical engineering from the University of Southern California.
Remember to use the rating system to let Anees and Pranav know if you have received an adequate response.
Because of the volume expected during this event, Anees and Pranav might not be able to answer each question. Remember that you can continue the conversation on the Data Center, sub-community forum shortly after the event. This event lasts through August 23, 2013. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hi Dennis,
    All those Layer 2 extension technologies require STP to be extended between Data Centers if you need to have multiple paths between Data Centers. OTV does not extend STP rather it has its own mechanism (AED election) to avoid loop when multiple paths are enabled. It means any STP control plane issue, we don't carry to the other Data Center.
    OTV natively suppresses Unknown Unicast Flooding across the OTV overlay. Unknown unicast flooding is a painful problem in layer 2 network and difficult to troubleshoot to identify the root cause if you don't have proper network monitoring tool.
   It has ARP optimization which eliminates flooding ARP packets across Data Center by responding locally with cached ARP messages. One of the common issues I have seen in Data Center is some server or device in the network sends continuous ARP packets which hits Control plane in the Aggregation layer which in turn causes network connectivity issue.
The above three points proves the Layer 2 domain isolation between data centers. If you have redundant Data Centers with Layer 2 extended without OTV, the above explained layer 2 issue which happens in one Data Center carries the same failure to the second data center which creates the question of what is the point of having two different Data Centers if we can not isolate the failure domain.
OTV natively supports HSRP localization with few command lines. This is a very important requirement in building Active/Active Data Center.
Even though your question is related to L2TP, OTV deserves the comparison with VPLS and those comparison will also be applicable for L2TP. The below link explains in detail...
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/white_paper_c11-574984.html
Thanks,
Anees.

Ask the Expert: Scaling Data Center Networks with Cisco FabricPath

With Hatim Badr and Iqbal Syed
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about the Cisco FabricPath with Cisco technical support experts Hatim Badr and Iqbal Syed. Cisco FabricPath is a Cisco NX-OS Software innovation combining the plug-and-play simplicity of Ethernet with the reliability and scalability of Layer 3 routing. Cisco FabricPath uses many of the best characteristics of traditional Layer 2 and Layer 3 technologies, combining them into a new control-plane and data-plane implementation that combines the immediately operational "plug-and-play" deployment model of a bridged spanning-tree environment with the stability, re-convergence characteristics, and ability to use multiple parallel paths typical of a Layer 3 routed environment. The result is a scalable, flexible, and highly available Ethernet fabric suitable for even the most demanding data center environments. Using FabricPath, you can build highly scalable Layer 2 multipath networks without the Spanning Tree Protocol. Such networks are particularly suitable for large virtualization deployments, private clouds, and high-performance computing (HPC) environments.
This event will focus on technical support questions related to the benefits of Cisco FabricPath over STP or VPC based architectures, design options with FabricPath, migration to FabricPath from STP/VPC based networks and FabricPath design and implementation best practices.
Hatim Badr is a Solutions Architect for Cisco Advanced Services in Toronto, where he supports Cisco customers across Canada as a specialist in Data Center architecture, design, and optimization projects. He has more than 12 years of experience in the networking industry. He holds CCIE (#14847) in Routing & Switching, CCDP and Cisco Data Center certifications.
Iqbal Syed is a Technical Marketing Engineer for the Cisco Nexus 7000 Series of switches. He is responsible for product road-mapping and marketing the Nexus 7000 line of products with a focus on L2 technologies such as VPC & Cisco FabricPath and also helps customers with DC design and training. He also focuses on SP customers worldwide and helps promote N7K business within different SP segments. Syed has been with Cisco for more than 10 years, which includes experience in Cisco Advanced Services and the Cisco Technical Assistance Center. His experience ranges from reactive technical support to proactive engineering, design, and optimization. He holds CCIE (#24192) in Routing & Switching, CCDP, Cisco Data Center, and TOGAF (v9) certifications.
Remember to use the rating system to let Hatim and Iqbal know if you have received an adequate response.
They might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Data Center sub-community Unified Computing discussion forum shortly after the event. This event lasts through Dec 7, 2012.. Visit this support forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hi Sarah,
Thank you for your question.
Spanning Tree Protocol is used to build a loop-free topology. Although Spanning Tree Protocol serves a critical function in these Layer 2 networks, it is also frequently the cause of a variety of problems, both operational and architectural.
One important aspect of Spanning Tree Protocol behavior is its inability to use parallel forwarding paths. Spanning Tree Protocol forms a forwarding tree, rooted at a single device, along which all data-plane traffic must flow. The addition of parallel paths serves as a redundancy mechanism, but adding more than one such path has little benefit because Spanning Tree Protocol blocks any additional paths
In addition, rooting the forwarding path at a single device results in suboptimal forwarding paths, as shown below, Although a direct connection may exist, it cannot be used because only one active forwarding path is allowed.
Virtual PortChannel (vPC) technology partially mitigates the limitations of Spanning Tree Protocol. vPC allows a single Ethernet device to connect simultaneously to two discrete Cisco Nexus switches while treating these parallel connections as a single logical PortChannel interface. The result is active-active forwarding paths and the removal of Spanning Tree Protocol blocked links, delivering an effective way to use two parallel paths in the typical Layer 2 topologies used with Spanning Tree Protocol.
vPC provides several benefits over a standard Spanning Tree Protocol such as elimination of blocker ports and both vPC switches can behave as active default gateway for first-hop redundancy protocols such as Hot Standby Router Protocol (HSRP): that is, traffic can be routed by either vPC peer switch.
At the same time, however, many of the overall design constraints of a Spanning Tree Protocol network remain even when you deploy vPC such as
1.     Although vPC provides active-active forwarding, only two active parallel paths are possible.
2.     vPC offers no means by which VLANs can be extended, a critical limitation of traditional Spanning Tree Protocol designs.
With Cisco FabricPath, you can create a flexible Ethernet fabric that eliminates many of the constraints of Spanning Tree Protocol. At the control plane, Cisco FabricPath uses a Shortest-Path First (SPF) routing protocol to determine reachability and selects the best path or paths to any given destination in the Cisco FabricPath domain. In addition, the Cisco FabricPath data plane introduces capabilities that help ensure that the network remains stable, and it provides scalable, hardware-based learning and forwarding capabilities not bound by software or CPU capacity.
Benefits of deploying an Ethernet fabric based on Cisco FabricPath include:
• Simplicity, reducing operating expenses
– Cisco FabricPath is extremely simple to configure. In fact, the only necessary configuration consists of distinguishing the core ports, which link the switches, from the edge ports, where end devices are attached. There is no need to tune any parameter to get an optimal configuration, and switch addresses are assigned automatically.
– A single control protocol is used for unicast forwarding, multicast forwarding, and VLAN pruning. The Cisco FabricPath solution requires less combined configuration than an equivalent Spanning Tree Protocol-based network, further reducing the overall management cost.
– A device that does not support Cisco FabricPath can be attached redundantly to two separate Cisco FabricPath bridges with enhanced virtual PortChannel (vPC+) technology, providing an easy migration path. Just like vPC, vPC+ relies on PortChannel technology to provide multipathing and redundancy without resorting to Spanning Tree Protocol.
Scalability based on proven technology
– Cisco FabricPath uses a control protocol built on top of the powerful Intermediate System-to-Intermediate System (IS-IS) routing protocol, an industry standard that provides fast convergence and that has been proven to scale up to the largest service provider environments. Nevertheless, no specific knowledge of IS-IS is required in order to operate a Cisco FabricPath network.
– Loop prevention and mitigation is available in the data plane, helping ensure safe forwarding that cannot be matched by any transparent bridging technology. The Cisco FabricPath frames include a time-to-live (TTL) field similar to the one used in IP, and a Reverse Path Forwarding (RPF) check is also applied.
• Efficiency and high performance
– Because equal-cost multipath (ECMP) can be used the data plane, the network can use all the links available between any two devices. The first-generation hardware supporting Cisco FabricPath can perform 16-way ECMP, which, when combined with 16-port 10-Gbps port channels, represents a potential bandwidth of 2.56 terabits per second (Tbps) between switches.
– Frames are forwarded along the shortest path to their destination, reducing the latency of the exchanges between end stations compared to a spanning tree-based solution.
    – MAC addresses are learned selectively at the edge, allowing to scale the network beyond the limits of the MAC addr

Data Center Network Design

I'm looking at a couple options for a small network in a data center. I seem to be getting hung up on all the different options. One of the options I'm looking at is end or row using both 2960Ss and Blade Center chassis switches with each physical server dual homed into a 2960, each ESX server dual homed into a blade switch and each of the switches with a Layer 2 10Gb uplink (20 total with etherchannel) to one of two 4900Ms. The 4900Ms would then have a layer 2 uplink between them to accomodate VLANs that span the access layer switches. This would be an inverted U topology. That's simple enough, and maybe that is where I should leave it, but there is the now available stacking feature of 2960s that has me wondering if there is another option available with dual homing a stack. Is there such a beast? Would it be better to stack 2960s, or even 3750s, so as to make each end of row with 2 redundant switches appear as one logical stack, and then uplink that stack to an aggregate multilayer switch such as a pair of 4900Ms? Or might that limit me to keeping VLANs within a stack and end or row?
thank you,
Bill

Hi Bill-
First, I personally would not use the 2960S for the data center, no matter the size. That switch was purposely built for user access and has some limitations. Also, depending on what you need to accomplish will determine your design. I recently did a design similar to what you are describing. We ended up putting 3750X's at the top of rack as a stack. This allows for etherchannel to your servers with both server NICs being active. From there we uplinked to a pair of 6509's in VSS. From a layer 2 point of view this was about as simple as it gets; 1 switch connected to another switch connected to a server. No spanning tree! If you can't afford stackable switches, you may want to look at routing at the top of rack. However you will lose functionality like moving VLAN's between racks, relying on server NIC software for active/passive links and the moving of VM's could be limited.

Ip addressing for data center

can you suggest me which pool we use for data center public or private,which is best one

You will encounter conflicts ONLY if you are connecting to a network that is using your same address space. See more below.
The private IP addresses that you assign for a private network (inter-office LAN, Internet Service Provider customer bases, campus networks, etc) should fall within the following three blocks of the IP address space:
10.0.0.1 to 10.255.255.255, which provides a single Class A network of addresses, which would use subnet mask 255.0.0.0.
(theoretically up to 16,777,215 addresses, good for VERY large enterprises like internet service providers or other global deployment)
172.16.0.1 to 172.31.255.254, which provides 16 contiguous Class B network addresses, which would use subnet mask 255.255.0.0.
(theoretically up to 1,048,576 addresses, good for large enterprises like colleges and governmental organizations)
192.168.0.1 to 192.168.255.254, which provides up to 2^16 Class C network addresses, which would use subnet mask 255.255.255.0.
(theoretically up to 65,536 addresses, widely used by default in consumer/retail networking equipment)
Explanation of Subnet masks, Network classes, and other technical info is readily available on the internet.

EU data center

I can not connect to my BC account, web mail, loading pages is mission impossible
What's going on?
I do not see any information on the BC Status
Do others have problems with the EU data center?
14:35:00 hours, the problem appears to be resolved
Message was edited by: terradomus

Hi,
There wasn't any noted EU related center issue of late.
However if you are still experiencing some troubles and nothing is noted on the status page please reach out to direct support so they can help confirm. If not related then they'll help investigate what could be causing within your site.
Kind regards,
-Sidney

Data Center Interconnect using MPLS/VPLS

We are deploying a backup data center and need to extend couple of Vlans over the backup data center.These two DC's which are interconnected by a fibre link which we manage and terminates on the ODC2MAN and ODCXMAN.We run MPLS on these devices ODC2MAN and ODCXMAN(Cisco 6880) as PE routers. I configured OSPF between these devices and advertised their loopbacks.
I need configuration assistance on my PE (odcxman and odc2man) to run the VFI and the VPLS instances.The vlans on the ODCXAGG need to extend to the ODC2AGG.
Also, I am looking for the configuration assistance such that each core devices should have 3 eigrp neighbors.
For example:
ODC2COR1 should have Eigrp neighbors with ODCXCOR1, ODCXCOR2 and ODC2COR2 and my VPLS Cloud should be emulated as a transparent bridge to my core devices such that it appears that ODC2COR1 is directly connected to ODCXCOR1 and ODCXCOR2 and have cdp neighbor relation. I have attached the diagram.Please let me know your inputs.

Hello.
If you are running Active/Backup DC scenario, I would suggest to make network design and configuration exactly the same. This includes platforms, interconnectivity types and etc.
Do you know what is the latency on the fiber between these two DCs?
Another question: why do you run 6880 in VSS, do you really need this?
Q about the diagram: are you going to utilize 4 fibers for DC interconnection?
PS: did you think about OTV+LISP instead of MPLS?

Scheduled system maintenance on US data center - November 23rd 2014

To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our US data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours and will take up to 8 hours to complete. During the maintenance procedure, creating and updating content, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available. Additionally, during the 8 hours maintenance procedure, all sites on the US data center will experience 4 sessions of 15 minutes downtime. Except for the 4 scheduled downtime sessions, the website front-ends will not be impacted by the maintenance.
Maintenance schedule:
Start date and time: Sunday, November 23rd, 3:00 AM EST (check data center times)
Duration: We are targeting a 8 hours maintenance window
Customer impact:
Partner registration, Trial site creation, Adobe Muse publish, APIs, FTP and some admin section will not be available through the entire maintenance window on all data centers
All websites and services on US data center will experience 4 sessions of 15 minutes downtime sometimes within the maintenance window
Creating or updating content on sites located on US data center will be unavailable during the maintenance procedure
For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
Thank you for your understanding and support,
The Adobe Business Catalyst Team

agents will be online for update from console.
Method 1: Update the protection agents from the Data Protection Manager Administrator Console
Open the Data Protection Manager Administrator Console.
Click the Management tab, and then click the
Agents tab.
In the Protected Computer
list, select a computer, and then click Update on the Action pane.
Click Yes, and then click
Update Agents.
Note You may have to restart the computer after you install the agent upgrades.
Method 2:Update the protection agents on the protected computers
Obtain the update protection agent package from the following directory on the System Center 2012 R2 Data Protection Manager server:
<var>Data_Protection_Manager_installation_location</var>\DPM\DPM\Agents\RA\4.2.1217.0
The installation packages are as follows:
For x86-based updates: i386\1033\DPMAgentInstaller_KB2904687.exe
For x64-based updates: amd64\1033\DPMAgentInstaller_kb2904687_AMD64.exe
Run the appropriate DPMAgentInstaller.exe package on each protected computer, based on the architecture of the agent.
Open the Data Protection Manager Administrator Console on the System Center 2012 R2 Data Protection Manager server.
Click the Management tab, and then click the
Agents tab. Select the protected computers, update the information, and then verify that the agent version number is 4.2.1217.0
Have a nice day !!!

Scheduled system maintenance on EU data center - October 26th, 2014

To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our EU data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours and will take up to 6 hours to complete. During the maintenance procedure, creating and updating content, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available. Additionally, all sites on the EU data center will experience a 20 minutes downtime sometimes during the maintenance window. Except for the scheduled 20 minutes downtime, the website front-ends will not be impacted by the maintenance.
Maintenance schedule:
Start date and time: Sunday, October 26th, 9:00 AM UTC (check data center times)
Duration: We are targeting a 6 hours maintenance window
Customer impact:
Partner registration, Trial site creation Muse Publish, APIs, FTP and some admin section will not be available through the entire maintenance window on all data centers
All websites and services on EU data center will experience a 20 minutes downtime sometimes within the maintenance window
Creating or updating content on sites located on EU data center will be unavailable during the maintenance procedure
For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
Thank you for your understanding and support,
The Adobe Business Catalyst Team

Congrats to Alan! Only one article, but it's a good one!
System Center Technical Guru - October 2014
Alan do Nascimento Carlos
ALM and IT Operations - Management 360 with System Center Operations Manager
in 06 Steps
Ed Price: "Lots of images. Great job breaking up the steps! Could benefit from a TOC and References. Great article!"
GO: "Thanks for the only article. great btw. :-)"
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Scheduled system maintenance on US data center - March 15th 2015

To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our US data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours for the region and will take up to 6 hours to complete. During the maintenance procedure, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available for sites on all data centers (including EU and AU). Additionally, during the 6 hours maintenance procedure, all sites on the US data center will experience 2 sessions of 1 minute downtime. Except for the 2 scheduled downtime sessions, the website front-ends will not be impacted by the maintenance.
Maintenance schedule:
Start date and time: Sunday, March 15th, 6:00 AM UTC (check data center times)
Duration: We are targeting a 6 hours maintenance window
Customer impact:
Partner registration, Trial site creation, Adobe Muse publish, APIs, FTP and some admin sections will not be available through the entire maintenance window on all data centers
All websites and services on US data center will experience 2 sessions of 1 minute downtime sometimes within the maintenance window
For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
Thank you for your understanding and support,
The Adobe Business Catalyst Team

Congrats to Noah and Mr. X!
System Center Technical Guru - March 2015
Noah Stahl
Make System Center Orchestrator Text Faster than a Teenager using PowerShell
and Twilio
Ed Price: "Wow, I love the breakdown of sections. As Alan wrote in the comments, "Wow! Great article!""
Mr X
How to educate your users to regularly reboot their Windows computers
Ed Price: "I love the table and use of code snippets and images! Great article!"
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Welcome to the Solutions and Architectures Data Center & Virtualization Community

Welcome to the Solutions and Architectures Data Center & Virtualization Community. We encourage everyone to share their knowledge and start conversations related to Data Center and Virtualization Solutions and architectures.All topics are welcome, including Servers – Unified Computing, Data Center Security, Data Center Switching, Data Center Management and Automation, Storage Networking, Application Networking Services and solutions to solve business problems.
Remember, just like in the workplace, be courteous to your fellow forum participants. Please refrain from using disparaging or obscene language or posting advertisements.
Cheers,
Dan Bruhn

Hi,
I have a question...
I going to install two Nexus 7009 with three N7K-F248XP-25 modules on each one, I am planning to create 3 VDC, but at the initial configuration the system does not show the ethernets ports of these modules, even with the show inventory and show module I can see tah the modules are recognized and its status is OK. There is something that I have to do before start to configure these modules...? enable some feature or license in order to see the ports with show running CLI...?

Welcome to the Enterprise Data Center Networking Discussion

Welcome to the Cisco Networking Professionals Connection Network Infrastructure Forum. This conversation will provide you the opportunity to discuss general issues surrounding Enterprise Data Center Networking. We encourage everyone to share their knowledge and start conversations on issues such as Mainframe connectivity, SNA Switching Services, DLSw+, managing SNA/IP and any other topic concerning Enterprise Data Center Networking.
Remember, just like in the workplace, be courteous to your fellow forum participants. Please refrain from using disparaging or obscene language or posting advertisements.
We encourage you to tell your fellow networking professionals about the site!
If you would like us to send them a personal invitation simply send their names and e-mail addresses along with your name to us at [email protected]

Hi together,
Since the release of SAP NetWeaver 2004s to 'Unrestricted Shipment' as of 6th of June 2006, we have renamed the forum 'SAP NetWeaver2004s Ramp-Up' to 'BI in SAP NetWeaver2004s'.
The forum should continue to adress BI issues particular to the release SAP NetWeaver 2004s. Please post general BI, project, etc. question to the other existing BI forums.
The SAP NetWeaver BI organisation will also use this forum to communicate / roll-out information particular to the release of SAP NetWeaver 2004s (in addtion to the FAQs and other material on the SAP Service Marketplace and information in other areas of the SDN).
Cheers
SAP NetWeaver BI Organisation

Windows server 2012 Data Center with VDI configuration error message ( The remote session was disconnected because there are no remote desktop license servers available)

Dears,
I have two windows server 2012 Data Center and I configured (Virtual Desktop Interface)VDI on it's.
All my clients connected on both of servers by used Remote Desktop sessions ,5 months since.
Currently,when the clients is connected on the both of servers they received the following error:
"The remote session was disconnected because there are no remote desktop license servers available to provide license"
Kindly note, I installed windows Licenses Server Data Center on the both of servers.
Regards.

Hi,
Please let us know if you have purchased RDS CALs and install it in your RD licensing server.
Also, on RD Session host servers, please make sure that you have specified the license mode and point them to the RD licensing server.
Remote Desktop Services Client Access Licenses (RDS CALs)
http://technet.microsoft.com/en-us/library/cc753650.aspx
RD Licensing Configuration on Windows Server 2012
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
Hope this helps.
Jeremy Wu
TechNet Community Support

When trying to start my Windows server 2008 R2 Data Center, I am getting "ramdisk device creation failed due to insufficient memory",

I have the following:-
VMWare workstation version 9 , with windows server 2008 R2 data center installed.
- I have installed the windows 2008 R2 inside the VM using an iso image.
- The host is windows 7.
I use to work well with the VM, but after adding a new VM to the same workstation . I start getting the following error when starting my old VM
ramdisk device creation failed sue to insufficient memory.
And on the windows boot manger screen they mentioned to :-
inset my windows installation dis and restart my PC.
click “repair your computer”
but not sure if this will fix the problem , baring in mind that the RAM assigned to the VM
is 24 GB & 80 GB hard disk.
The error is
Link.
so can any one advice what is causing this error?
Thanks

You might start by checking the RAM.
http://windows.microsoft.com/en-US/windows7/Diagnosing-memory-problems-on-your-computer
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Please shed some light on Data Center design

Hi,
    I want you guys to recommend what the design should be. I'm familiar with HP blade system. Let me clarify the existing device.
1. HP Blade with Flex Fabric. It supports FCOE.
2. MDS SAN switch for the storage
3. Network Switch for IP network.
4. HP Storage.
    HP Blade has 2 interface types for IP Network(Network Switch) and Fiberchannel(SAN).
   What is the benifit for using Nexus switch and FCOE for my exising devices. What should be a new design with Nexus switch? Please guide me ideas.
THX
Toshi

Hi, Toshi:
Most of these chat boards have become quite boring. Troubleshooting OSPF LSA problems is old news. But I do pop my head in every now and then. Also, there are so many other companies out there doing exciting things in the data center. You have Dell, Brocade, Arista, Juniper, etc. So one runs the risk of developing a myopic view of the world of IT by lingering around this board for too long.
If you want to use the new B22 FEX for the HP c7000 blade chassis, you certainly can. That means the Nexus will receive the FCoE traffic and leverage its FCF functionality; either separate the Ethernet and FC traffic there, or create a VE-port instantiation with another FCF for multihop deployments. Good luck fighting the SAN team with that one! Another aspect of using the HP B22 is the fact that the FEX is largely plug and play, so you dont have to manage the Flex Fabric switches.
HTH

EIGRP within data center

Similar Messages

Maybe you are looking for