Exchange failover DR testing

Hey guys, i have a problem
wih my Exchange testing
Exchange configuration:
3 Sites
2 Hub cas servers in Site1
2 Mailbox (DAG) in Site1
1 Mailbox+CAS (also in same DAG) in
HotSite
1 Witness Server in Site3
1 Database mounted in Hotsite with a test client.
Heres the problem:
Manual failover from Site1 to HotSite works without issue, however we did some testing by switching off the both NICs for LAN and DAG on the mailbox servers at Site1 expecting Hotsite to become the active one, and then things got weird.
From the exchange point of view all the servers were "disconnected" and database at the Hotsite is "dismounted"
From the client point of view (outlook) the clients who were on the databases originally mounted in Site1 are "connected" but can't send or receive mail. The test client who was originally mounted in Hotsite that is supposedly "dismounted"
is also connected but keeps getting the message that the administrator has made changes, please restart outlook.
We're accustomed to this message whenever we failover to HotSite but now it kept popping up every few seconds as if it were failing over and then back again. Could it have something to do with the FileShare witness being a separate site at
a separate location
Any ideas? thanks

check the Datacenter Activation Coordination Mode which will result to occur automatic failover over the datacenter
you can verify them using - Get-DatabaseAvailabilityGroup -Identity <DAGName> | fl
ref: http://technet.microsoft.com/en-us/library/dd979790(v=exchg.150).aspx
Exchange Queries

Similar Messages

Exchange Failover - Outlook Doesn't Work with 1 Server

Hi,
Wondering if someone could help.
We have 3 Exchange 2010 servers with all roles installed. All at SP3 RU6. DAG set up between all 3 servers for all mailbox databases. Manual failover is enabled. MB1 holds all copies. Outlook 2010 with all latest updates being
used by end clients.
MB1 - Main Physical Server – All Active Copies – No Issues
MB2 – Secondary Physical server – Passive – Problem Server
MB3 – VM for use in the worst case scenario – Passive – No issues
We simulated MB1 failing. We can get MB2 to take ownership of the databases manually. OWA works fine, mail flow works fine but whenever we open Outlook it either fails to connect and continues to say “Server is unavailable, Retry, Work Offline,
Cancel” or the inbox loads but it loads old mail from a month+ ago (I actually this this may be a cached mode setting that’s being taken from somewhere even though cached mode is disabled) and sits at “Offline”. If I do the “Test E-mail Auto configuration”
then everything passes fine but we can’t get the client to go online at all.
If I fail everything over to MB3 then it all connects up ok and works fine. I stuck MB1 back online with mailboxes being active on MB2 and Outlook pointing to MB1 and it works fine. The only thing that appears to be broken is when Outlook points
to MB2 only.
Thanks

We don't have a CAS array set up. We want the fail over to be fully manual and only fail over to another server when mb1 is in a completely failed state and won't be back up and running withing a set time frame. We can get everything working
on MB3 and only Outlook doesn't work when everything is on MB2. Outlook also doesn't work if databases are on another server and DNS is pointing Outlook to MB2 (again MB3 works fine).

Failover Cluster testing - not working

Hello
We are trying to perform failover testing on OC4J clusters. We have two nodes clustered. On each node we have installed SOA suite - four OC4J instances (home, oc4J_soa, oc4j_wsm, and oc4j_esbdt).
This is how we are performing the test:
We have deployed servlet on both oc4j_soa with different application names but with same context-root. We have observed following behavior.
1) In mod_oc4j.conf file , we have "Oc4jSelectMethod roundrobin:local".
So when we hit http://<loadbalancer>/<context-root-for-servlet> it works fine in roundrobin fashion. We have set the HTML page title as node name in servlets.
And so we see Node 1 title one time and Node 2 title the other time.
2) Now if I undeploy the servlet from Node 1 and hit http://<loadbalancer>/<context-root-for-servlet> It doen't work one time (gives HTTP 500 error) and it works the other time.
ie. it is still sending one request to Node 1 and other request to Node 2.
well, it should not do this right ? if my application is down/not available on Node 1 , all request should go to Node 2.
3) Also what i have observed is , when we hit the Nodes' http url directly instead of going through the loadbalancer it crisscross the requests.
ie. http://NODE 1/<context-root-for-servlet> - this one always goes to Node 2
and http://NODE 2/<context-root-for-servlet> - always goes to Node 1
This is something weird.
Anybody has any idea , please ? I am not sure why are we getting unexpected behavior mentioned 2) and 3 )
Please let me know if you need anything about config details.
Thanks
/Mishit

2) I hope there is a Hardware LBR front ending this architecture ... If yes then HW LBR have intelligent death detection mechanisms where in if Node 1 crashes it stops serving requests to the failed node until it is back online .... so this setting is more at the LBR then at mod_oc4j.conf
3) If load balancing is configured correctly, I dont think u shud be getting this issue..
To test load balancing you can do as below:
- Ensure Virtual host configuration is done in Apache of both nodes
- Ensure Virtual host entry is added to /etc/hosts
Like on Node 1 /etc/hosts
<Node 2 IP> <Virtual hostname>
Similarly on Node 2 /etc/hosts
<Node 1 IP> < Virtual hostname>
- Give Virtual URL to your LBR guy and he will do the settings in LBR
- Bring down node 1 keeping node 2 alive & check below:
http://<virtualURL>/contextroot
http://<node2>/contextroot
- Similarly bring down node 2 keeping node 1 alive & check below:
http://<virtualURL>/contextroot
http://<node1>/contextroot

Instlaling exchange 2013 for testing purposes

i would like to start testing exchange 2013. That why i installed a virtual member server on my workstation but i am confused concerning the network cards.
What should i do, add an extra network card that connects through nat to my isp?

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Bindings in IIS on Exchange 2010 causing Test-outlookwebservices to fail on Autodiscover

Exchange 2010 is coexisting with Sharepoint 2013 Foundation.
Exchange 2010 have 2 internal IP's (1 for Exchange and 1 for Sharepoint).
Under IIS we had set up binding on port 443 to 1st IP, and second IP was used to bind it to 80 port for SharePoint. That kind of configuration gave as an error for: outlookwebservices, for Autodiscover, which is logical because both IP's have an A record
which points to servername.domain.com.
This are our configuration for EWS internal/external URL's and AUTODISCOVER internal/external URL'S:
EWS URL's
InternalUrl                     :
https://mail.domain.com/ews/exchange.asmx
ExternalUrl                     :
https://mail.domain.com/ews/exchange.asmx
AUTODISCOVER URL's
InternalUrl                     :
https://mail.domain.com/autodiscover/autodiscover.xml
ExternalUrl                     :
https://mail.domain.com/autodiscover/autodiscover.xml
This are the error messages for: Test-outlookwebservices
RunspaceId : 5ee30248-5bec-436f-808a-c56180a8a6d9
Id         : 1113
Type       : Error
Message    : When contacting
https://SRVNAME.domain.com:443/autodiscover/autodiscover.xml received the error Unable to
              read data from the transport connection: An existing connection was forcibly closed by the remote host.
RunspaceId : 5ee30248-5bec-436f-808a-c56180a8a6d9
Id         : 1113
Type       : Error
Message    : When contacting
https://SRVNAME.domain.com:443/autodiscover/autodiscover.xml received the error An existi
             ng connection was forcibly closed by the remote host
The "workaround" solution, because Sharepoint only goes thru PORT 80 on this server was chosing bindings 443 to all the ips (then Test-Outlookwebservices goes thru), but doing that we are unable to use anything else on port 443 on that server in
the future.
I was wondering if changing InternalNLBBypassUrl in our scenario would be a possible workaround or there would be no effect on this scenario?
Set-WebServicesVirtualDirectory -Identity "Contoso\EWS*" -InternalNLBBypassUrl
https://mail.domain.com/ews/exchange.asmx
With best regards,
bostjanc

Hi Bostjan,
This was working fine before, Is it the first time we are facing the problem.
Make sure that all the exchange services are started.
Did you select the proper certificate at the Organization level and check the permission settings.
For the Autodiscover, please access
https://localhost/Autodiscover/Autodiscover.xml on the CAS. The 600 error code will be displayed.
Try to find the Error by running the Below cmdlets.
Get-ExchangeCertificate | FL
Get-WebServicesVirtualDirectory –Server ServerName | FL
Get-AutodiscoverVirtualDirectory –Server ServerName | FL
Get-ClientAccessServer
| FL
Than press Ctrl+right click the Outlook icon in the System Tray, select Test E-mail AutoConfiguration, uncheck Use Guessmart and Secure Guessmart Authentication, click Test button.
If found the problem is related to web services and basic authentication than try with the below cmdlet and the
Link
Set-WebServicesVirtualDirectory -identity "BOXEDUC-EXC1\EWS (Default Web Site)" -externalurl https://mail.domain.com/ews/exchange.asmx -internalurl https://mail.domain.com/ews/exchange.asmx -BasicAuthentication:$True
Mark as Answer/Helpful Post if it helps
Regards.
Naren Neelam, Messaging Consultant, ITBigBang (P) Ltd Www.ITBigBang.Com | Hire Us for Messaging Consulting

Exchange 2010 SP3 - Test-OutlookConnectivity Failures

Test-OutlookConnectivity -Protocol TCP gives success on all tests. If I run Test-OutlookConnectivity -Protocol HTTP, I get failures on all . I'm trying to figure out why. We have a single CAS array in our main site with two servers.
We have a third server in our COLO location and there is no CAS for that site. Outlook Anywhere is not enabled.
If I run "Test-OutlookConnectivity -Protocol HTTP" at the main site, I get this error message:
Fatal Autodiscover failure EXPR = <Null>.
    + CategoryInfo          : OperationStopped: (Microsoft.Excha...onnectivityTask:TestOutlookConnectivityTask) [Test-
   OutlookConnectivity], FatalAutodiscoverException
    + FullyQualifiedErrorId : F70A1ED2,Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask
    + PSComputerName        : ex1.domain.local
I get different messages altogether when I run tests from the COLO site. For both protocols I get the message:
An error occurred while trying to access mailbox EX2.domain.local, on behalf of user o2bancorp.local\extest_49ce0203
32a04
Additional information:
[Microsoft.Exchange.Data.Storage.WrongServerException]: The user and the mailbox are in different Active Directory sit
es..
    + CategoryInfo          : OperationStopped: (Microsoft.Excha...onnectivityTask:TestOutlookConnectivityTask) [Test-
   OutlookConnectivity], CasHealthStorageErrorException
    + FullyQualifiedErrorId : 6A829B37,Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask
It seems to me that we don't have something setup properly in our environment. I think the reason that the lead Exchange admin does not have a CAS array defined for the COLO site is that some of our business locations that are part of the COLO site
and he doesn't want the Exchange server there servicing client requests except for in a DR scenario. He also has also had all receive connectors disabled. I enabled the two default receive connectors on the COLO Exchange server.

Hi Hollisorama,
Base on my knowledge, this command is used to test end-to-end Outlook connectivity scenario for Outlook Anywhere, however outlook anywhere is disabled in your environment. It is the reason why you will get error message when running the command.
I recommend you refer to the following article to enable outlook anywhere, and then test connectivity again:
Enable Outlook Anywhere
Best regard,
Niko Cheng
TechNet Community Support

Exchange 2013 Sp1 Test-PopConnectivity issues in coexistence

I'm having issues with Pop3 in a coexistence environment with 2007. The 2013 roles are split- cas servers and mailbox servers.
If I run "Test-PopConnectivity -ClientAccessServer:cas01 -MailboxCredential:(Get-Credential domain\test.exchange) |fl"
I get the error "Service MSExchangePOP3 was not found on <mailboxserver>" and a DR Watson is created.
Ok I know there is a front end and a back end component to Pop3. This error is expecting to find the front end component on a mailbox server? So is it just an issue because the roles are split or is it to do with proxying through the CAS not being enabled?
Pop3 does not use a send connector- just a receive connector right? So how would it Proxy- if it does
Confused
Tony

Hi,
Is “cas01” the front end server?
Did you use the exchange 2013 MailboxCredential to test the Pop Connectivity?
Make sure the pop is enalbed for users and the pop services are started.
Proxy and redirection for POP and IMAP:
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Thanks,
Simon Wu
TechNet Community Support

Exchange Failover Cluster Resource

Hi,
Can someone help confirm if amending the Exchange 2010 DAG Cluster Resource to include an empty role with just a shared IP is supported?
This is not for any an exchange function but for a backups to target an active member, in the event of a failure.
Thanks

Hello msadiq,
As you have Veritas Cluster I suggest you speak to Symantec. We only support Sun/Oracle Cluster.
Regards,
Steve

Exchange 2013 DLP Testing - Allowing Social Security numbers

I've created a DLP policy to block SSN's. The problem is it only looks for the word "SSN". The rule in the DLP is looking for SSN's. It blocks the email if I have the letters "SSN" in it with a fake social, but if
I remove the letters "SSN" it allows it to send. Is there a way to tune how it reads sensitive info?
ST

The Xml defines that. You could create your own if needed:
http://technet.microsoft.com/en-us/library/jj674704(v=exchg.150).aspx
Developing sensitive information rule packages
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Testing failover, how to reproduce ORA-24505: transaction status unknown

Database Version:11.2.0.2 psu 2
RAC 2-node
SUSE 11
Dataguard fast start failover
During testing of failover to the standby database we had a problem with taf, oracle reported an error 24505, the application trapped the error ignored it and then failed by attempting to re-insert the same data and recieving a primary key violation. My understanding is that this is one of the possible errors when using TAF and the application should trap the error and then determine if the transaction was completed before either replaying the transaction or continuing. We have raised this as a bug withthe application developers, however we need to reliably test for this condition and due to the nature of the problem we can not reliable reproduce the error condition and setting up the system to execute the failover makes repeatedly testing and hoping to encounter the error impractical.
Is there a method to force this error condition for both possible states? i.e. failover and force an ORA-24505 to be returned with the transaction having completed and also return ORA-24505 withthe transaction having rolledback.
Chris

We have arleady raised an SR, I am curious however as to how others test these types of issues as some of the taf errors are very rare.

It is there an alternative to the Test-SystemHealth powershell cmdlet for Exchange 2013?

Hello
The Powershell cmdlet Test-SystemHealth, that was available on Exchange 2010, is no longer available on Exchange 2013.
Test-SystemHealth cmdlet gathered data about the Microsoft Exchange system and analyzed the data according to best practices.
Are there any alternatives to this for Exchange 2013?
Thanks!

Haven't really played with it too much, but check out Get-ServerHealth
http://technet.microsoft.com/en-us/library/jj218703(v=exchg.150).aspx
Looks to have replaced Test-SystemHealth.

How to test if Spam protection with Forefront for Exchange 2010 works

Hi there.
Installed forefront for exchange 2010 on Exchange Edge server.
We have tested virus protection with creating EICAR, but the question is, is there a way to check if SPAM Works fine, and how to?
with best regards
bostjanc

Hi bostjanc,
Since this is an issue on the Forefront side, I suggest ask Forefront Forum for help so that you can get more professional suggestions. For your convenience:
https://social.technet.microsoft.com/Forums/forefront/en-US/home?forum=FOPE
However, based on my knowledge, use the EICAR antivirus test file is the only built-in method to check whether the Anti-Spam configured correctly.
You can try to send some test spams to your Exchange server for testing, even if this is a stupid method : )
Thanks
Mavis Huang
TechNet Community Support

Redundancy/failover testing

My company is a relatively small enterprise (about 800 people scattered across 45-50 branches) and we are planning on setting up a periodic failover/redundancy testing schedule for our routers. Basically, we want to test the secondary WAN links at our branch offices and test our redundancy in our data centers.
I'm sure there is plenty of documentation out there in regards to best practices, but what I find has more to do with a full DR test of a enterprise's systems, as opposed to a simple failover test of an office's WAN link.
Does anyone have good suggestions for how often you should run these tests? My original thinking is to do this every quarter, but this would involve some travel for us and our resources are slim. The branch offices can be done remotely without any issue, but our DR site (which is actually used for some production traffic) would probably require one of our staff to be on site during a redundancy test.
Thanks!

Yep, that's what I did now.
But keep in mind this is not really explained, even if crossing all the documentations.
There is no document explaining what behaviour to expect in Jabber in case of redundancy of all the UC components.
For the CUCM, it's not clear, and nothing is mentionned in case of MRA.
IM&P is documented, but nothing for MRA.
Expressays states about redundancy, but the behaviour to expect is not. Same for XMPP federation, no idea.
UnityConnection as well, nothing is explained.

Tests pass, but iPhone won't autodiscover Exchange 2010.

I have some Exchange 2007 and one Exchange 2010 I am responsible for. As far as I can tell I have ActiveSync and AutoDiscover setup properly. Running the tests here confirms this. With an iPhone I am able to do the "one step autodiscovery" on the Exchange 2007 servers but the Exchange 2010 does the "two step setup" where it fails to get the server name and it has to be put in by hand.
I'm curious if something was changed in 2010 AutoDiscover that breaks iPhone (3G 3.1.2). More likely I have got something misconfigured.
All the DNS names point to the same server, the SSL certificate supports all the names.
Here is my ActiveSync test results against the 2010 server.
Testing Exchange ActiveSync
Exchange ActiveSync was tested successfully
Test Steps
Attempting AutoDiscover and Exchange ActiveSync Test (if requested)
Successfully tested AutoDiscover for Exchange ActiveSync
Test Steps
Attempting each method of contacting the AutoDiscover Service
The AutoDiscover Service was successfully tested.
Test Steps
Attempting to test potential AutoDiscover URL https://pepper.net/AutoDiscover/AutoDiscover.xml
Failed testing this potential AutoDiscover URL
Test Steps
Attempting to resolve the host name pepper.net in DNS.
Host successfully resolved
Additional Details
IP(s) returned: 69.85.246.35
Testing TCP Port 443 on host pepper.net to ensure it is listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with remote host
Exception Details:
Message: No connection could be made because the target machine actively refused it 69.85.246.35:443
Type: System.Net.Sockets.SocketException
Stack Trace:
at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
at Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.PerformTestReally()
Attempting to test potential AutoDiscover URL https://autodiscover.pepper.net/AutoDiscover/AutoDiscover.xml
Testing AutoDiscover URL succeeded
Test Steps
Attempting to resolve the host name autodiscover.pepper.net in DNS.
Host successfully resolved
Additional Details
IP(s) returned: 69.57.51.22
Testing TCP Port 443 on host autodiscover.pepper.net to ensure it is listening and open.
The port was opened successfully.
Testing SSL Certificate for validity.
The certificate passed all validation requirements.
Test Steps
Validating certificate name
Successfully validated the certificate name
Additional Details
Found hostname autodiscover.pepper.net in Certificate Subject Alternative Name entry
Testing certificate date to ensure validity
Date Validation passed. The certificate is not expired.
Additional Details
Certificate is valid: NotBefore = 11/25/2009 1:15:23 PM, NotAfter = 11/26/2011 3:33:48 AM"
Attempting to send AutoDiscover POST request to potential autodiscover URLs.
Successfully Retrieved AutoDiscover Settings by sending AutoDiscover POST.
Test Steps
Attempting to Retrieve XML AutoDiscover Response from url https://autodiscover.pepper.net/AutoDiscover/AutoDiscover.xml for user [email protected]
Successfully Retrieved AutoDiscover XML Response
Additional Details
AutoDiscover Account Settings
XML Response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/mobilesync/responseschema/2006">
<Culture>en:us</Culture>
<User>
<DisplayName>test user</DisplayName>
<EMailAddress>[email protected]</EMailAddress>
</User>
<Action>
<Settings>
<Server>
<Type>MobileSync</Type>
<Url>https://webmail.pepper.net/Microsoft-Server-ActiveSync/</Url>
<Name>https://webmail.pepper.net/Microsoft-Server-ActiveSync/</Name>
</Server>
</Settings>
</Action>
</Response>
</Autodiscover>
Validating Exchange ActiveSync settings
ActiveSync URL https://webmail.pepper.net/Microsoft-Server-ActiveSync/ was successfully validated
Attempting to resolve the host name webmail.pepper.net in DNS.
Host successfully resolved
Additional Details
IP(s) returned: 69.57.51.22
Testing TCP Port 443 on host webmail.pepper.net to ensure it is listening and open.
The port was opened successfully.
Testing SSL Certificate for validity.
The certificate passed all validation requirements.
Test Steps
Validating certificate name
Successfully validated the certificate name
Additional Details
Found hostname webmail.pepper.net in Certificate Subject Alternative Name entry
Testing certificate date to ensure validity
Date Validation passed. The certificate is not expired.
Additional Details
Certificate is valid: NotBefore = 11/25/2009 1:15:23 PM, NotAfter = 11/26/2011 3:33:48 AM"
Testing Http Authentication Methods for URL https://webmail.pepper.net/Microsoft-Server-ActiveSync/
Http Authentication Methods are correct
Additional Details
Found all expected authentication methods and no disallowed methods. Methods Found: Basic
Attempting an ActiveSync session with server
Testing an ActiveSync session completed successfully
Test Steps
Attempting to send OPTIONS command to server
OPTIONS response was successfully received and is valid
Additional Details
Headers received: Allow: OPTIONS,POST
MS-Server-ActiveSync: 14.0
MS-ASProtocolVersions: 2.0,2.1,2.5,12.0,12.1,14.0
MS-ASProtocolCommands: Sync,SendMail,SmartForward,SmartReply,GetAttachment,GetHierarchy,CreateCollection,DeleteCollection,MoveCollection,FolderSync,FolderCreate,FolderDelete,FolderUpdate,MoveItems,GetItemEstimate,MeetingResponse,Search,Settings,Ping,ItemOperations,Provision,ResolveRecipients,ValidateCert
Public: OPTIONS,POST
Content-Length: 0
Cache-Control: private
Date: Fri, 05 Feb 2010 05:11:05 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
Attempting FolderSync command on ActiveSync session
FolderSync command completed successfully.
Additional Details
Number of Folders: 11
Attempting initial sync (no data) for Inbox folder
Completed Sync Command successfully
Additional Details
Status: 1
Attempting to test GetItemEstimate command for Inbox Folder
Successfully received GetItemEstimate Response from Server
Additional Details
Estimate: 2 messages
Attempting to test Sync of Inbox Folder
Completed Sync Command successfully
Additional Details
Number of items synchronized: 2

http://www.experts-exchange.com/Apple/Hardware/iPhone/Q_24933916.html
Demazter:
Check the security tab of the users in AD and see if inherit permissions is checked.
had a similar problem with my first migration to Exchange 2010 and it was down to a security permission on the Active Directory User account.
In Active Directory Users and Computers right click on the user and select properties then under the security tab and advanced make sure the box is checked for inheritable permissions.
=========================
dmlavigne1:
Demazter is right for existing users that have been upgraded from previous versions of Exchange. If you create a new user in Exchange 2010 IPhone sync will work without additional steps.
When I went to check the security tab in AD, it was not visible. I had to click the View menu then place a check beside Advanced Features.
When I checked the inheritable box, IPhone Sync worked for that existing user.
Note, I checked other users in my AD with mailboxes and some of them had this already checked. The only two that didn't have this box checked were the users that were using the IPhone syncing and were upgraded from Exchange 2007.

MDS 9509 Failover Testing failed

We tried to do a failover to test the HA environment for the upcoming upgrade to 2.0(1b), only with no succes. We're currently running on 1.2(1b) and want to upgrade non-disruptively to the new firmware.
can anybody tell me what went wrong? Thanks in advance.
Switch CLI Output:
==================================
SSW-97-001# show module
Mod Ports Module-Type Model Status
1 16 1/2 Gbps FC Module DS-X9016 ok
2 16 1/2 Gbps FC Module DS-X9016 ok
3 16 1/2 Gbps FC Module DS-X9016 ok
4 16 1/2 Gbps FC Module DS-X9016 ok
5 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 active *
6 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 ha-standby
Mod Sw Hw World-Wide-Name(s) (WWN)
1 1.2(1b) 3.0 20:01:00:0d:ec:02:34:80 to 20:10:00:0d:ec:02:34:80
2 1.2(1b) 5.0 20:41:00:0d:ec:02:34:80 to 20:50:00:0d:ec:02:34:80
3 1.2(1b) 5.0 20:81:00:0d:ec:02:34:80 to 20:90:00:0d:ec:02:34:80
4 1.2(1b) 5.0 20:c1:00:0d:ec:02:34:80 to 20:d0:00:0d:ec:02:34:80
5 1.2(1b) 4.0 --
6 1.2(1b) 4.0 --
Mod MAC-Address(es) Serial-Num
1 00-0c-30-da-09-6c to 00-0c-30-da-09-70 JAB0749066Y
2 00-0c-30-da-2c-88 to 00-0c-30-da-2c-8c JAB075107B2
3 00-0c-30-da-2c-60 to 00-0c-30-da-2c-64 JAB075107FW
4 00-0c-30-da-78-38 to 00-0c-30-da-78-3c JAB08040ACU
5 00-0c-30-d9-f5-60 to 00-0c-30-d9-f5-64 JAB0747055Q
6 00-0c-30-d9-f4-d0 to 00-0c-30-d9-f4-d4 JAB0747059P
* this terminal session
SSW-97-001# conf t
Enter configuration commands, one per line. End with CNTL/Z.
SSW-97-001(config)# system switchover warm
SSW-97-001(config)# exit
SSW-97-001# show module
Mod Ports Module-Type Model Status
1 16 1/2 Gbps FC Module DS-X9016 ok
2 16 1/2 Gbps FC Module DS-X9016 ok
3 16 1/2 Gbps FC Module DS-X9016 ok
4 16 1/2 Gbps FC Module DS-X9016 ok
5 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 active *
6 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 standby
Mod Sw Hw World-Wide-Name(s) (WWN)
1 1.2(1b) 3.0 20:01:00:0d:ec:02:34:80 to 20:10:00:0d:ec:02:34:80
2 1.2(1b) 5.0 20:41:00:0d:ec:02:34:80 to 20:50:00:0d:ec:02:34:80
3 1.2(1b) 5.0 20:81:00:0d:ec:02:34:80 to 20:90:00:0d:ec:02:34:80
4 1.2(1b) 5.0 20:c1:00:0d:ec:02:34:80 to 20:d0:00:0d:ec:02:34:80
5 1.2(1b) 4.0 --
6 1.2(1b) 4.0 --
Mod MAC-Address(es) Serial-Num
1 00-0c-30-da-09-6c to 00-0c-30-da-09-70 JAB0749066Y
2 00-0c-30-da-2c-88 to 00-0c-30-da-2c-8c JAB075107B2
3 00-0c-30-da-2c-60 to 00-0c-30-da-2c-64 JAB075107FW
4 00-0c-30-da-78-38 to 00-0c-30-da-78-3c JAB08040ACU
5 00-0c-30-d9-f5-60 to 00-0c-30-d9-f5-64 JAB0747055Q
6 00-0c-30-d9-f4-d0 to 00-0c-30-d9-f4-d4 JAB0747059P
* this terminal session

Some log messages:
Feb 11 01:17:39 switch1.int.bon.nl : Feb 11 02:17:38 cet: %KERN-2-SYSTEM_MSG: mts: HA communication with standby timedout
Feb 11 01:17:39 switch1.int.bon.nl : Feb 11 02:17:39 cet: %PLATFORM-5-MOD_REMOVE: Module 6 removed
Feb 11 01:17:41 switch1.int.bon.nl : Feb 11 02:17:41 cet: %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console from pts/0 (192.168.44.1)
Feb 11 01:17:49 switch1.int.bon.nl : Feb 11 02:17:49 cet: %SYSMGR-3-OPERATIONAL_MODE_WARM: Operational redundancy mode set to warm (error-id 0x401E0017).
Feb 11 01:17:53 switch1.int.bon.nl : Feb 11 02:17:53 cet: %MODULE-5-STANDBY_SUP_OK: Supervisor 6 is standby

Exchange failover DR testing

Similar Messages

Maybe you are looking for