IBM DS3200 and DS3400 SAN Reset - Syswipe

How to Reset - IBM DS Storage Area Network Appliances. NAS and SAN are becoming the standard for both Datacentres and Business. In the Web Hosting and Remote Storage they are invaluable. The IBM DS3200 range can provide 6gbps transfer rate to server. VALU run DS3200 and the 3400's for backup and cloning purposes. Time to time we may need to expand the array or create new LUNS, this can be a tricky thing as SAN's are a beast of their own.

Recently we needed to expand an array from 700GB to 1.4TB, the array build went horribly wrong, the IBM software would not let us delete the old array or logical drives, as we had an exact copy of the SAN data, we decided to reset the IBM DS3200 sub system, this leaves the IP as normal, and allows us to rebuild the arrays correctly.

The option RESET is not available in the storage manager, yet, in the storage manager for the DS4000-series this was available.

To reset a DS4000-series use the command sysWipe on both controllers and sysReboot afterwards, these commands are done through the serial port.

1. Login into the serial port shell of the controller.

2. Type the following: ld </Debug

2. Type the command: safeSysWipe

3. Next run the command sysReboot.  This will reboot the controller.

4. Repeat steps 1-3 on the second controller.

To reset Sub System, from the Enterprise screen of the DS3000 DSM, go to the script editor and type (paste) the following :-

clear storageSubsystem configuration;

Verify and execute, this will reset the configuration of the storage array. IP address will remain the same.

If you want to run it from the DOS window, CD to the directory with the SMCLI executable , run SMCLI and add the IP address of the array you wan to reset and then run the same command. (You may need to use the “-c” switch after SMCLI  in this case.  The windows wont close , so a ctl C will be needed  once you are sure the array has reset !

If needed you can place the :- “clear storageSubsystem configuration;” into a file and run it from the dos windows using SMCLI –f <ip address> -f filename.

You will need to reset the controller IP address manually. The default IP Addresses are 192.168.128.101 and 102.

How to Move or Migrate Blackberry Database and Server.

We have a number of customers wishing to migrate their Blackberry Services to the their Dedicated Servers they have hosted with us. This is an easy process.

Options: Move Database to different location.

Open SQL management Studio, backup database. Or stop SQL, copy Database to the new location.

Shutdown Server.

Start SQL, Detach Database, Attach Database, choosing the new location as the data and log files.

Done.

Migrate Blackberry to new Server/location

Depending if you have a different machine/netbios name on the new server the process is a little different.

Same Netbios Name - Same as above to get a copy of your Database, install blackberry as usual. When install is fully complete, stop SQL server, rename current Blackberry .ldf and .mdf files. Copy the OLD server files to the same location, add Network service permissions, to both, full. Restart SQl.

Different Netbios Name:

Same as Above, but license will not work until you run these SQL queries against the database:

use BESMgmt

update ServerConfig set ServiceName = <name_of_destination_server> where Id = 1

go

use BESMgmt

update ServerConfig set MachineName = <name_of_destination_server> where Id = 1

Restart SQl and BB Server Services or simply reboot the machine.

If you have issues with the above command this can be changed in the Database table dbo.ServerConfig

If you are using groupwise, the above will copy most settings, you will meed to save your trusted key before turning off old BB server.

The Key Generator is in the Installation Directory.

Configure Trusted Application Permissions - Blackberry for Novell Groupwise  

Verify your Groupwise Primary Domain

• Open ConsoleOne, right click the primary domain in your Groupwise system and then click Properties.
  
• Click the Groupwise -> Identification tab. The UNC path value points to the location of your Groupwise primary domain database.
  
• Install the trusted application key generator
  
• Log in with a Novell administrator account that has supervisor rights to the GroupWise system.
• Copy the folder that contains the trusted application key generator located on the BlackBerry Enterprise Server product CD to the BES machine.
• Create the trusted application key.
• The trusted application key allows the BlackBerry Enterprise Server(s) to communicate with the GroupWise mail server. One key is generated for each GroupWise mail server.
• In the key generator application directory, double click Generate_GW_Trusted_App.exe.
• Type the Groupwise Domain Path that points to the location of the GroupWise primary domain database (for example, \\server\volume\GWDomain\).
• Click Generate.
• Click Yes. The generated key is populated in the Trusted Application Key field.
• Click Yes to create a configuration file that contains the trusted application key information.
• Save the Generate_GW_Trusted_App.ini file.

If errors occur during key generation, the error messages are logged in Generate_GW_Trusted_App.ini.

• Verify that the BlackBerry Enterprise Server is a trusted application
• In ConsoleOne, select your GroupWise system.
• On the Tools menu, select GroupWise System Operations > Trusted Applications.
• Verify that RIMBES appears on the list.

Blog: Troubleshoot the MS POP3 Connector.

An amount of our customers use POP3 to their email servers, such as exchange. Using POP3 connectors can be difficult to troubleshoot. Below is a guid of what steps to perform if you have issues.

Re-register the POP3 Connector event sink in Microsoft Internet Information Services (IIS). To do this, click Start, click Run, type %programfiles%\microsoft windows small business server\networking\pop3\imbreg.exe, and then click OK. 

Test your email using Telnet.

C:\>telnet exchangeserverIP 25

Telnet>helo <cr>

Telnet> mail from:youremail@xxxxxxxxxxxxxx

Telnet>rcpt to:youremail@xxxxxxxxxxxxxx

Telnet>data <cr>

Telnet> test test test <cr>

Telnet> test test test <cr>

Telnet>. <cr>

Troubleshoot the SMTP delivery process

The POP3 Connector may download e-mail messages from the remote POP3 server, but those e-mail messages may not be delivered to the user. In this scenario, no files remain in the Incoming Mail folder or the Failed Mail folder. To troubleshoot this issue, follow these steps:

Examine the contents of the PickUp folder. If no files appear in this folder, Windows tried to deliver the e-mail message to the recipient. At this point, the e-mail message is outside the boundaries of the POP3 Connector. In this scenario, follow these steps:

Examine the SMTP queues on the Windows Small Business Server-based computer. 

Enable e-mail message tracking on the Windows Small Business Server-based computer. 

Please check out our email hosting.

Network tools are very useful to gain information about your Network or to check its performance.

A set of tools for detecting network health and retrieving information about a particular IP address or hostname. Using some of the features like, advanced NSLookup, DNS tool and Network Lookup with a trace can tell you alot!

Some of the tools available, IP Tools, Network Tools, Online Tools, Whois, Ping, Reverse Look Up, Anti Spam.

You can use the Network Tools from this website.

http://network-tools.com

Web Hosting Support.