Fully Redundant Network

Hello everyone,I
have some rack space in a colo and would like to know if what I have in
mind is actually correct and perhaps if there is a better way to do it.I
want to setup full redundancy in terms of the LAN and WAN. I have 2
drops from the datacenter for redundant internet connection.I have 2 managed dell switches (cisco oem from what i understand) and 2 ASA 5505's.I
have just a simple ESX environment and my boxes have NIC Teaming setup
already, which seems to be the ideal configuration for redundant
network.I plan to have 2 VLan's, 1 for WAN and 1 for LAN on each switch (2 total).I understand that I will want to have HSRP setup, but I am not sure how to go about that or if the 5505 is even able to do HSRP.So
I will have just 1 subnet and just have all servers and SAN connected
to 2 switches and each ASA on 1 switch with HSRP, sound right?It sounds like i need hsrp for both wan and lan.Did i forget anything? Thanks a ton for all the help!
Hi,
It will be helpful if you can provide the scehmatic diagram of the current setup and we can guide the best design with the expected one any how what i have understand with the above comments is you have two internet links with two routers,two switches,two ASA5505 and all servers are having two NIC with teamiung configured.
To have simple redudant network configure two vlans in switches one with external where your router and ASA 5505 interface will be connected and anothere with local lan where another port of ASA 5505 will be connected an will act as gateway for local servers.
To have redundancy for internet links alos configure HSRP in router local interface with tracking configuration so that one links goes down traffic will be shifted to other one without any delay,for that you need to configure a defualt route towards the vip of HSRP of router in ASA 5505.
Check out the below link on HSRP with tracking configuration on routers
http://www.networkstraining.com/cisco-router-hsrp-configuration/
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094e8c.shtml
and on ASA 5505 you need to configure two vlan as mentioned and for local and external interface configure a cluster setup with HSRP in ASA 5505
Check out the below link for ASA 5505
http://www.articlesbase.com/networks-articles/stepbystep-configuration-guide-for-the-cisco-asa-5505-firewall-803076.html
http://www.cisco.com/en/US/docs/security/asa/asa80/configuration/guide/asacfgIX.html
Hope to Help !!
Remember to rate the helpful post
Ganesh.H

Similar Messages

Switch and Router Redundant Network

I am trying to learn as much as possible about networking and cisco. I trying to build the following network to practice redundancy. I set up HSRP on my routers because it the only protocol available on packet tracer. The following setup works but how would I go about adding the vlans to switch ALPHA and switch BETA. I would like to use access list for security, for example Sales can't access Accounting but Accounting can access sales. I can do that with one layer 3 switch but how do I do it with 2? Do I add the same VLans to both switches? Should the configurations to both switches be exactly the same? Because I tried that and for some reason the Vlans could not communicate unless I changed the interface to dot1q and trunk mode. I thought it be easier to change all interfaces at one time but when I tried that STP failed. I tried setting only the interfaces being used to dot1q and trunk mode on one switch it worked but as soon as I did it for the other STP failed again. Read layer 3 switches can have HSRP but seems like a waste of a switch. Ive looked online and can't seem to figure it out. So my question is how do I set this up, I would like to add hosts and a server later but I can't even get this to work. Hopefully someone can help me out with this as I find it very interesting and am eager to figure it out.

Ok thanks again John. I will set that up as soon as I can. But the issue I was having don't know if its because of HSRP not configured but when I did identical configs on both switches I couldn't ping between Vlans unless I changed the interface, for example the interfaces between Sales to Alpha then Alpha to Marketing, using the command
Switch(config-if)#int f0/?
Switch(config-if)#switchport trunk encapsulation dot1q
Switch(config-if)#switchport mode trunk
for both interfaces.
It worked ok until I did the same thing for the interfaces between Alpha and Beta then STP turned off and everything started blinking. But I had to because I couldn't get to Accounting without doing that to Beta since STP blocks ports and sends traffic through Beta also.The I tried using the same command on all the interfaces for Vlan switches Sales, Marketing, Acc instead of Alpha or Beta to try something different and same thing happened. Not sure if you know why its happening? Wrong interface encapsulation or mode on either side? needed HSRP?
Basically if I change all interfaces on Alpha and Beta to dot1q and trunk mode STP fails or if I change all the interfaces and the bottom switches to dot1q and trunk mode everything also fails.
I guess I try what you said first if it fails I show you what I'm talking about.
Thanks,
John

Channel Bonding? Oracle RAC with multiple redundant network

We are planning on setting up on Oracle RAC 10g on Linux.
We have redundant switches, so I would like to set up the network to have some version of network redundancy.
Under windows, it is called 'teaming'. Linux is 'channel-bonding'
I just want to make sure if I setup the channel-bonded interfaces, it will be supported with RAC. Has anyone done this before??
-Andy

we are running our RAC on NIC bonding. Although we need to do some more testing to be real sure as to the functionality of the bond.
Metalink Note:298891.1 would be a good place to start.
hth,
-S

Secure redundant network, how would you do this?

I'm just kind of curious what people think of this. I interned at the local county about a year ago. I noticed something that kind of bugged me. They have all their 911 dispatch stuff done on computers. They have this setup called computer aided dispatch I think it has a lot to do with like records of individuals, etc. Which all seemed quite critical.
I didn't like the setup much though because they had 3 systems I'm pretty sure all went to the same switch and there was only a single server for this software, it used tape backups which if they had to use offsite one would then be 2 days old. (I guess the software vendor set all this up. besides a fiber which would have split off for other county offices.)
For me I saw so many possible issues with that I think may be why they are changing vendors now.
It would cost $$ but this would be my...

Hi everyone,I have a user connecting to a Server 2008 R2 RDP server. He can connect no problem, but there is quite a bit of latency which I do not understand. He pings to the server at around ~60ms. I have another server on the same site (Server 2012 R2) and he does not experience the same latency. I've connected another Windows 8.1 computer to the Server 2008 R2 box and CANNOT replicate the issue.He appears to be the only one.I've temporarily disabled his AV, windows firewall, disabled local visualization settings (and on the server). I've configured RDP to 56k settings in the Experience tab which changed absolutely nothing.I've also run the netsh commands everyone seems to suggest with this issue.Any recommendations or things to try?EDIT: I've also updated his wireless drivers. I don't have the laptop in hand to try the local...

Default security policy 802.1x

Folks,
I just installed a 2100 controller and added a WLAN. I noticed that the default L2 security policy is 802.1x which is using WEP 104 keys. My question is where do we define the wep key on the controller. does that mean no client will be able to connect to the AP, unless he adds the key to the SSID?

Does 802.1x always require a radius server? With a fully redundant network implementation I could see a Windows Radius server being the weakest link.
For port security for a project I am working on I am searching for the best solution. I will shutdown unused ports. Allow only one mac-address (need to learn how to do this). I am also researching the cost effectiveness of implementing 802.1x security.
James

HP Photosmart C5580 , I need a network driver for windows 7 64 bit.

hello all ,
this is the only driver supplied by HP for my printer and Windows 7 64bit :
ftp://ftp.hp.com/pub/softlib/software11/COL30128/mp-74904-1/PS_AIO_04_C5500_NonNet_Full_Win_WW_130_1...
as you can see it is listed as "NonNet" and as it is such I am unable to print from ANY other computer in my house , I have been trying o solve this for months , Complete reinstalls of drivers (hundreds of times) and complete reinstalls of Operating systems , this will not work.
(also , the only OS's supported under this drivers listing are the Windows 7 family only , could this be the problem?)
What I have running now:
Main PC , Windows 7 64bit ( the printer is installed here with above and only driver , all software and buttons work and prints as it should)
XP MCE Laptop (sees the printer , installs it , shows it as ready , will NOT print)
Vista Ultimate 32bit ( sees the printer , installs it , shows it as ready , will NOT print)
Vista Home Pro (sees the printer , installs it , shows it as ready , will NOT print)
I am at a total loss other then this driver just is not right , maybe because its not a network driver?? I don't know but I am out of things to try , I have tried adding the port , finding the printer through the ip yada yada on all the PC"s , nothing works
PLEASE if anyone has an answer or direction for me to go , please help.
thanks , have a wonderful day.

I'm not on a wireless netowrk , I have a fully wired network...still no printing (from other computers) if the C5580 is hooked to my Windows 7 64Bit PC
I had to put the C5580 printer and drivers on one of my Vista PC's (in another room) and now all the PCs (even the windows 7 64bit) prints to that pc , the ONLY problem with that is I need that printer/scanner on my Windows 7 64 PC and need the other PCs to print to it , because I need the scanner and software in here.

SMB networking issue in 10.5.2 - detailed analysis and cry for help

I am a computer technician for a medium-sized company. Our setup in the company is mainly Windows-based, using Active Directory and Windows Server 2003 on our file servers, with a fully Gigabit network. We also have about a dozen Macs, mostly Mac Pros but some PowerMac G5s and a few MacBooks here and there.
In the past few weeks, we've started seeing an issue on some of the computers relating to transferring large files from the Macs to the file server. This generally only applies to files over 1GB in size, but sometimes it can even happen with files of a few hundred megabytes. What is happening is that when the Mac starts up, the first couple of times a user will transfer a file of this size to the server over SMB, it will act normally. Eventually (usually anywhere from the third to the seventh transfer of a file that size) a file transfer will stall out. It doesn't stop completely, but it begins transferring painfully slowly. We're talking maybe 100 or 200KBps, and it never speeds up again. If you cancel out that transfer, any subsequent transfers will do the same thing.
Here are the things we've determined through almost a week of testing this issue:
*It doesn't matter what file or what kind of file we're copying, what server we're copying it to, or what folder on the server it is being copied to
*The issue is relatively random as far as which file or transfer number will trigger it, but it is repeatable in that it inevitably will happen
*It doesn't appear to be a third-party product, hardware or software, that is causing this. It's happening on Mac Pros, G5s, a MacBook, and a MacBook Pro, none of which have very much overlap in terms of third-party things installed
*Using clean and basic installs, we've tested under controlled circumstances found that the problem does not manifest itself in Tiger or even Leopard 10.5.1
*The problem doesn't seem to be affected by the time of day at all, in that when it happens, it consistently does it whether morning, afternoon, evening, or overnight; subsequently, it does not appear to be affected by cross traffic on the network or peak network usage
*Using a quick AppleScript, we made a file transfer happen repeatedly over time; on Tiger and Leopard 10.5.1, the transfers were able to run uninterrupted for as much as 12 hours at a time without the problem manifesting itself, but with Leopard 10.5.2, the problem would occur under the same conditions within 10 to 15 minutes
*We have ruled out any faulty hardware by connecting the test machine directly to our main switch
*All the PCs on our network, in many different configurations, are performing the same types of transfers just fine
*Using Ethereal, we can see that when a transfer starts stalling out, you'll start seeing a more than usual number of duplicate ACKs on the connection
*We're not really sure what this means, but it is worth noting that doing the same types of transfers under the same conditions using curl never manifested the issue
*After the problem has manifested itself, rebooting the machine clears up the issue, but it will come back steadily
I think that's pretty much everything we've figured out, which leads us to believe that this is a problem that started happening in 10.5.2. We've eliminated as many variables as possible, so I feel very comfortable with that conclusion. The issue now, then, is finding a fix. Yes, we could just use 10.5.1, but there are so many good bug fixes in 10.5.2 that we'd like to not miss out on. We have tried several fixes on both our server side and on the Mac side, but nothing has helped.
I doubt that this is something that will get resolved, but I'm posting it here just hoping to see others having the same issue so maybe it will get noticed. Any suggestions, though, are very welcome.
Message was edited by: Josh R. Holloway

There have been some other posts suggesting that Apple might have messed up some default TCP configuration parameters in 10.5.2. It might be instructive to compare the result of:
sysctl -a | grep tcp
on otherwise similar 10.5.1 and 10.5.2 systems.

Data Center Redundancy

Hi, dear experts!
I) My Input data is (read please, or see attach):
- I have one active data center (main office), one backup data center (backup office), and several branch offices and many corporate internet users
- Each of the offices has redundant internet connection: Main office via ISP1 and ISP2, backup office via ISP3 and ISP4.
- Standby data center duplicates corporates services (such as Exchange, Sharepoint, FileStorage).
- Main office and backup office are long-distanced from each other (about 800 km), and interconnected via 1Gb fiberoptic.
II) My tasks are:
1. Provide redundant network connection for local ofiice users to corporate services.
2. Provide redundant network connection for branch offices and internet users to corporate services.
III) My ideas are:
1. Accordingly to the 1-st task. Here I suppose to use load balancers in redundant configuration.
2. Accordingly to the 2-nd task. To my mind there are two scenarios.
2.1 First scenario. To built a DMVPN topology using main and backup offices as a hubs, and branch offices as a spokes.
2.2 Second scenario. To by provider independet IPv4-adress block and ASN, to advertise main and backup office networks in internet.
IV) My questions are:
-What scenario according to the 2-nd task is better: using a DMVPN-topology or using an ASN-redundancy?
-Is it possible to avoid assymetric routing problems in case of using a an ASN-redundancy?
Thank you!

I think Global loadblancer device will solve your both issue or there is an other solution for 2nd question,
to use BGP confedration, that means use two private ASN internaly one in each DC, and put them both DC in one confedration, use one public ASN with all your ISP's.
Regards,

Which network effective route for KM repository ?

Our portal (Knowledge Management) server is located (at Location A) physically far apart from our remote offices (Location B) due to which we are concerned of network bandwidth, latency delays while accessing huge files of 40 / 60MB from a DB repository in portal (Location A) over the WAN from Location B.
Will creating an FSDB, or DBFS portal repository pointing to a remote file share at remote offices (Location B) eliminate the long network path ?
User at Location B requests for a resource in portal FSDB OR DBFS repository. Will the resource (40MB file) be retrieved directly from Location B remote share to the user at Location B or will it traverse from Location B to Location A (Portal) & then back to Location B (remote user), thus creating a redundant network path ?

Hi Muhammed,
There would always be latency and performance related issues when users are accessing files or applications over the WAN. The issues would be more conspicuous when large files in KM are accessed from a DB repository over WAN connections. One way to handle this is through SAP's Accelerated Application Delivery . This tool address the issues of latency and/or performance which are of concern when applications are accessed from remote locations.
Refer the following links to get an idea about Accelerated Application Delivery:
[http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b08443bc-75fd-2a10-3da0-8ef1d4f7c622]
[http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60336bbb-e87c-2b10-6aac-b1c834f907dc?QuickLink=index&overridelayout=true]
You can also leverage third party tools like Akamai to achieve the same result.
Regards,
Prathamesh

CMTS uBR10k with redundant wan interfaces

Hello,
I have a config question for those who's working with the uBR10k.
I have a 10k with 2x wan uplink cards (ESR-HH-1GE) GigabitEthernet3/0/0 and
GigabitEthernet3/1/0
Those links are connected to 2x cat2960G (.1Q trunk between them) where each
c2960 has an ASA5520 connected, running active/passive failover-mode.
What i would like to do is to make L2 redundans from the 10k to the ASA(s).
I have multi vrf and vlans (subinterfaces, because 10k doesnt support vlan
interface) on the 10k.
Is this possible at all or do i have to create a subinterface on each
Ge-interface (per vlan), in that vlan & vpn, create 2 interfaces on the ASA
(per vlan), in that and then do some dynamic L3 routing ? (i hope not, this
will almost x2 my ASA config) :-(
Martin
Denmark

The uBR10K is the way to go if they want a fully redundant configuration.You will need a uBR10K with a 1+1 MC5x20 configuration (one for supporting the customer traffic, with a second one as a backup). In addition, you will need the following components in dual-redundant configuration: PREs, Gig Es, Power supplies and TCC+ cards.

The dreaded: The network address is invalid error - SQL 2014 Cluster on Server 2012 R2

Trying to setup an SQL 2014 Failover cluster on Windows Server 2012 R2 (two nodes). Every time I get to the assign a SQL server Network Name piece of the setup I get the following error message:
The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid.'
This happens whether I use the Advanced cluster installation procedures or the normal installation. I have tried the following based on anything I can find on the web:
1) Removed the clustered MTDTC role.
2) Deleted the NIC Team (4 1GB NICs). Deleted all but 1 NIC from the server device manager.
3) Shutdown the second node.
4) Lanman Server registry change posted someplace on this forum that does not stick on reboot
None of the above, separately or in combination, has worked to allow SQL 2014 to be installed as a cluster role.
There is no virtual machines added to the cluster. This is not a VMware installation. It is straight Windows 2012 R2 with a two node cluster (setup identically).
Any ideas, suggestions, comments?
Thanks,
-Andrew

Hi Alberto and Lydia,
The cluster was verified, there are only warnings related to a lack of redundant network paths as the cluster verification doesn't recognize a team of 4 nics are redundant. I updated AD to include the permissions detailed in the link Lydia provided,
still no go.
I'm not sure how to attach the installation logs to this message forum other than as text in the message, so here you go:
Summary:
Overall summary:
Final result:                  User cancelled
Exit code (Decimal):           -2068380094
Exit facility code:            1207
Exit error code:               1602
Exit message:                  User has cancelled.
Start time:                    2015-03-24 09:55:25
End time:                      2015-03-24 10:01:04
Requested action:              CompleteFailoverCluster
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for ComponentUpdate: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.
Cluster properties:
Machine name: SUN-PIE-CS-01
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Machine name: SUN-PIE-CS-02
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Data Quality Client                      1033                 Standard
Edition     12.0.2000.8     No         Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Machine Properties:
Machine name:                  SUN-PIE-CS-01
Machine processor count:       16
OS version:                    Windows Server 2012
OS service pack:
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  Yes
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Package properties:
Description:                   Microsoft SQL Server 2014
ProductName:                   SQL Server 2014
Type:                          RTM
Version:                       12
SPLevel:                       0
Installation location:         \\sun-server2\data\Software\Microsoft\SQL 2014\x64\setup\
Installation edition:          Standard
User Input Settings:
ACTION:                        CompleteFailoverCluster
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASLOGDIR:                      Log
ASSERVERMODE:                  MULTIDIMENSIONAL
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
CONFIGURATIONFILE:
CONFIRMIPDEPENDENCYCHANGE:     false
ENU:                           true
FAILOVERCLUSTERDISKS:          <empty>
FAILOVERCLUSTERGROUP:          SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES:    <empty>
FAILOVERCLUSTERNETWORKNAME:    sun-pie-mt-01
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS:              false
INSTALLSQLDATADIR:             <empty>
INSTANCENAME:                  MSSQLSERVER
QUIET:                         false
QUIETSIMPLE:                   false
SAPWD:                         <empty>
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSYSADMINACCOUNTS:           <empty>
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
UIMODE:                        Normal
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150324_095524\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Full-Text and Semantic Extractions for Search
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Data Quality Services
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services - Native
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Integration Services
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Setup Support Files
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity SDK
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Writer
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Documentation Components
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Browser
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150324_095524\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
    Message:
        User has cancelled.
    HResult : 0x84b70642
        FacilityCode : 1207 (4b7)
        ErrorCode : 1602 (0642)
    Stack:
        at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
        at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
        at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)

Network Vaults and Mirrored Drives

I just updated my server with a mirrored (Raid 1) drive and I was looking forward to putting an Aperture vault on the drive. Of course Aperture doesn't support network drives for vaults (yes, yes, I should have checked first...)
anyone out there find an alternative workflow that works for them. I still like the idea (and redundant) network drives backing up my pictures.
thx!
Dual G5, 15" MacBook Pro Mac OS X (10.4.8)

Hi (I also from Seattle),
I also have a mirrored network drive. At the time I put Aperture 1.0 on my Quad G5, I couldn't put the Library on the network account, nor a vault. Now, I think I can at least use referenced files on the network account...but I choose not to. I don't know if the managed library can reside on the network drive. I don't think it can.
Regardless, the Library on the RAID might be nice in case of drive failure, but for the vault, I wouldn't trust it. If the library is corrupted, or files get deleted, I instantly replicate the error to the mirrored drive. Same for the vaults.
So instead, I have a pair of backups (Vaults) that I rotate off-site. I intend on having a third. It's easy, and fast. I don't keep the vaults connected all the time--I've had bad luck with drive failure in the past, so I take them online only for the task. Like I said, it's quick and easy. I have a 140 GB Library. The vault updates take a few minutes each time. I vault the library every time I add new images or make substantial changes.
Having tried a variety of ways of backing up, I'm really pleased with what Apple's come up with so far. Of course for those who need a network workflow, there's much to be desired...
BTW, I run my laptop with a Portable Home Directory. Of course, it can't run Aperture. If it did, I'd be exporting the projects I needed to work on to my home directory, and then it would be synched to the Laptop and back.

Connecting redundant servers to redundant CSS

Hi,
I'm quiet new with CSS configurations and currently working on an assignment to get two servers (with both a redundant network connection) connected directly to a redundant CSS configuration. I have tried a box-to-box redundancy configuration but i'm having some problems with the fallback and inside connectivity. When i look at all the configuration guides and tips then there's always a switch connected between the CSS and the servers. Before i ask for help with this config i want to know if the design that they've put me up with can work! Attached there's a picture of the design. The servers have teaming enabled with fail-over option. When the primary CSS fails, the secondary CSS will take over. The primary link of the server will fail and perform a fail-over to the secondary link. I have my doubts that this design will work.
I hope that someone can get me started :)
Kind Regards,
Daniel

We have seen too many issues in the past with servers using redundant interfaces.
We always end up recommending not to use such a solution and to insert at least 1 switch between the CSS and the servers.
Gilles.

Another issue with Mac+PC & Airport Express network

Okey here's my problem. Yesterday i got my very first Mac (iBook 12") and i'm very happy about the computer in general. I also have Airport Express wireless base station. My other computer is table-PC and it has Planet WL-8314 PCI wireless card in it. I have ADSL-modem that i used with ethernet connection.
Now i want to connect Airport Express to ADSL so that both computers could get wireless internet connection and PC could be able to connect to speakers with Airtunes.
iBook connects to Airport Express very easily. No question there. But my Windows XP (service pack 2) PC is driving me crazy. I have configured the network using the admin utility from iBook. I've tried fully open network, use mac-address, WEP and WPA, but nothing works. I've installed Airport Express applications to windows as well but it doesn't connect.
Here is my current settings (Hope i can translate them correctly to english, i'm using finnish).
Encryption: WPA2 Personal
Encryption type: WPA OR WPA2
Connection: Ethernet
DHCP is in use
Share IP-addresses "checked"
by sharing one IP-address (DHCP and NAT) (use 192.168.1.1. addressing)
As i said i've disabled encryption, used mac-addresses and even made it fully public but nothing helps.
When i configure Airport Express from iBook my PC shows the network and does recognize the name of the network correctly and even if there is an encryption in use or not. If i'm using WPA and trying to connect, my PC asks for password but when i give the correct password it just stays stuck - nothing happens. The same thing when i try to connect without any encryption and passwords. It just tries and tries and tries... and fails.
This feels pretty hopeless. And the weird part is that yesterday i got it work for maybe an hour or so. Then Windows crashed and when it loaded again the same settings did not work anymore. So there are really weird things happening. And that period when it was working the admin utility worked in PC as well.
So any ideas what i could do. I'd really apreciate any help that can guide me to make my network fully work. So far it works perfect only with iBook - well better than nothing .
iBook G4 Mac OS X (10.4.3)

The connection i managed to establish last night didn't last very long. When i restarted Win XP, the connection was lost again. Anyway now i think i have solved the problem. All i had to do was to not set Windows XP take control over wireless network configure. This was done through unchecking one option. Then i could open wireless network adapter's own configuration tool and establish a connection to Airport Express wireless network.
So basically i had to punch Windows XP's native tools down in order to get the connection work at all. It just amazes me why such feature exists if it doesn't work.. Anyway i'm happy now and hope this discussion with myself in this thread might help some other as well .
iBook G4 Mac OS X (10.4.3)

Redundant Switch Configuration

I'm trying to setup two Catalyst 3750X-48T-L switches to support redundant networking. Most pieces of equipment will have two Ethernet interfaces, each on separate subnets.
So far, I've got the switches configured as separate VLANs, connected together with stack cables as shown below. I can propagate Ethernet traffic in each subnet/VLAN independently. However, I cannot get packets routed across the VLANs/subnets.
I'm looking for guidance on what additional steps are needed. Do I need to define each port as a trunk connection?

If you want to route between the vlans then you need to have L3 vlan interfaces (SVIs) on the switches.
So for each vlan you need to create an SVI and assign it an IP address from the IP subnet used for that vlan.
Then you set the default gateway of the clients in that vlan to the be the SVI IP address.
Note - if your switches are stacked you only need to create the SVIs on the stack master.
Edit - haven't used 3750-X switches so you many also need to enable IP routing using the "ip routing" command.
Jon

Fully Redundant Network

Similar Messages

Maybe you are looking for