How to Upload Files to Oracle Support

As an old Sun/Oracle upload file method has been discontinued, below are the several method on how to upload files to Oracle Support based on file size.

mos_attach

  • FTPS & HTTPS to MOS File Upload service – 200 GB max

sftp_mos

  1.     Set “ftps://transport.oracle.com” as the Host
  2.     Supply the appropriate credentials (MOS Support Portal username and password)
  3.     Leave the Port setting blank
  4.     After connecting, double-click on the Issue directory in the right (Remote) pane
  5.     Double-click the SR number’s directory in the right (Remote) pane
  6.     Locate the file to be transferred in the left (Local) pane
  7.     Drag-and-drop the file into the relevant SR directory
  • Diagnostic Assistant (DA), using MOS file utilities – 200 GB max

Diagnostic Assistant (DA)

DA 2.2 (included w/RDA/Explorer/STB 8.02) now supports uploads via https to MOS File Upload Service. Use DA via menus,explorer or the command line.

Menu

  1. Run diagnostic assistant menu:
  2. /<linux/solaris rda home>/da/da.sh menu or <win rda home>dada.cmd menuDiagnosticAssistance
  3. Start with option 3: RDA, OCM,ADR, SR Creation / Packaging, and MOS ToolsDiagnosticAssistant
  4. Next select option 4: Package, Upload Diagnostic FilesDiagnosticAssistanct
  5. Complete it with option 7: Upload File Package to SRDiagnosticAssistant
  6. You will be prompted for your SR, credentials and the file.

 

To use DA do a command line upload:

da.sh upload -p sr=<SR Number>file=path=<path to file>

To use DA to upload with explorer

explorer -w default -T DA -SR <Service Request number>

NOTE: If SR Number is not specified, the file will be uploaded to transport.oracle.com/upload/proactive/

  • Secure File Transport (SFT), part of ASR Manager – 200 GB max

# /opt/SUNWsasm/bin/sasm transport -r
Enter “1” to select:
1) transport.oracle.com
Or, enter:
https://tranport.oracle.com

  • FTP, including SFTP, is not supported

*Reference: Doc ID 1547088.2 and Doc ID 1596914.1

Advertisements

Solaris 11 ZFS Root Recovery

[SOLARIS 11 ZFS ROOT RECOVERY:

* Boot system into single user via network or CDROM.
boot net -s
boot cdrom -s

* On X86 machine, you need edit grub and append -s on kernel line OR boot CDROM with Solaris-11-Text image/media, then select option “3 shell” on “Welcome to the Oracle Solaris Installation Menu”.
* If it ask username: root/solaris or root/password

# mkdir /a /b
# zpool import -R /a -f rpool
# zfs mount –o mountpoint=/b rpool/ROOT/solaris
# vi /b/etc/shadow

*Remove the root password section, it will become look like this:
root::15356::::::

*Note that by default, the new Solaris 11 doesn’t allow blank password
*To allow empty passwords at login:

# vi /b/etc/default/login
*Switch this line “PASSREQ=YES” to “PASSREQ=NO”

*If you access the system via SSH, also check the directive PermitEmptyPasswords in “/etc/ssh/sshd_config”
PermitEmptyPasswords yes

# cd /
# umount /b
# zpool export -f rpool
# reboot

How to Force a Crash Dump When the Solaris Operating System is Hung

How to Force a Crash Dump When the Solaris Operating System is Hung.

This post describes steps for forcing a system crash dump when the Solaris system is in a hang condition. First of all, you need to drop the system into OK Prompt. For Old model which has Sun keyboard, you can press STOP+A, or for newer model / terminal, press break key sequences, example:
————-
~.
#.
#~
~#

If your console is a terminal, you can type :
“shift-break”    or
“ctrl-break”    or
“ctrl-\” (ctrl-backslash) or
“<enter>” followed by “~” and
“ctrl-break”     on Solaris Sparc,

To send a <BREAK> from Hyperterm, use <Ctrl>-<Pause> or <Alt>-<Pause>
On Hyperterminal, Ctrl-Break
————

Okay after you able to drop system to the OK prompt, you will see below PROMPT messages:

Type ‘go’ to resume
ok

All you need to do is to type ‘sync’ (without the quotes) and press Enter. The system will immediately panic. Now the hang condition has been converted into a panic, so an image of memory can be collected for later analysis. The system will attempt to reboot after the dump is complete.

 

Ref# Doc ID: 1004506.1

Enabling or Disabling MPXIO Multipathing per Port

What is MPXIO?

Solaris Multiplexed I/O (MPxIO), known also as Sun StorageTek Traffic Manager (SSTM, earlier Sun StorEdge Traffic Manager), is multipath I/O software for Solaris OS. It enables a storage device to be accessed through multiple host controller interfaces from a single operating system instance. The MPxIO architecture helps protect against I/O outages due to I/O controller failures. Should one I/O controller fail, MPxIO automatically switches to an alternate controller.

This architecture also increases I/O performance by load balancing across multiple I/O channels.

It was integrated within the Solaris operating system beginning in February 2000 with Solaris 8 release.

The file to enable or disable mpxio has been moved in Solaris 10 from /kernel/drv/scsi_vhci.conf to the bottom of the file /kernel/drv/fp.conf and /kernel/drv/mpt.conf.

The easy way to enable/disable global MPXIO On Solaris:
——————————————————————–
# vi /kernel/drv/fp.conf

mpxio-disable=”no”;

CHANGE TO ‘YES’ for Disable and ‘NO’ for Enable

Or, just simply run this command:
#stmsboot -D fp -e    >>enable MPXIO
#stmsboot -D fp -d    >>disable MPXIO

the, you will prompted to reboot the server.

But, actually Multipathing can be enabled or disabled on specific Fibre Channel Host Bus Adapter (HBA) controller ports. If you enable multipathing on a specific HBA port controller port, all supported devices connected to that controller port will be enabled for multipath operation.

The following procedure applies to both SPARC and x86 based machines:

Port Configuration Considerations

Before you start configuring the software by port, consider the following:

  • FC global and per-port multipath settings are specified in the file /kernel/drv/fp.conf.

    Per-port multipath settings have priority over the global setting. This means that if global multipathing is enabled by a specific port has been disabled for multipathing, the port will not be available in the multipathing configuration. Conversely, even if global multipathing has been disabled, specific ports may be enabled for multipathing if they are listed in the appropriate driver.conf(4) file.

  • Load balancing is controlled by the global load-balance property in /kernel/drv/scsi_vhci.conf file and is not controlled on a per-port basis.
  • If a device has more than one path to the host, all paths to the device must be configured with multipathing enabled or disabled.
  • Configuring multipathing by port enables the multipathing software to coexist with other multipathing solutions like Symantec (VERITAS) Dynamic Multipathing (DMP), or EMC PowerPath. However, devices and paths should not be shared between the multipathing software and other multipathing solutions.

To Configure Multipathing by Port

Depending on how many ports you want the multipathing software to control, you can enable or disable multipathing globally or for specified ports.

  1. Log in as root (su - root).
  2. Determine the HBA controller ports that you want the multipathing software to control.

    For example, to select the desired device, perform an ls -l command on /dev/cfg directory. The following example shows the ls -l command output.

    lrwxrwxrwx  1 root  root  50 Jan 29 21:33 c0 -> 
         ../../devices/pci@7c0/pci@0/pci@1/pci@0/ide@8:scsi
    lrwxrwxrwx  1 root  root  61 Jan 29 21:33 c1 ->
         ../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@1:scsi
    lrwxrwxrwx  1 root  root  61 Jan 29 21:33 c2 -> 
         ../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi
    lrwxrwxrwx  1 root  root  53 Jan 29 21:33 c3 -> 
         ../../devices/pci@7c0/pci@0/pci@9/LSILogic,sas@0:scsi
    lrwxrwxrwx  1 root  root  54 Apr 16 20:28 c5 ->
         ../../devices/pci@780/pci@0/pci@8/SUNW,qlc@0/fp@0,0:fc
    lrwxrwxrwx  1 root  root  56 Apr 16 20:28 c6 -> 
         ../../devices/pci@780/pci@0/pci@8/SUNW,qlc@0,1/fp@0,0:fc

    Note – Controllers c5 and c6 are ports A and B on a dual-port FC HBA. Controllers c1 and c3 are single port SAS HBA ports. Controller c2 is the internal SAS controller in a Sun FireTM T2000 server.


    Once you have determined the port, or ports, you want to explicitly enable or disable multipathing for, go to the next step.
  3. Enable or disable specific ports as follows:
    • FC HBA ports
      1. Edit file /kernel/drv/fp.conf
      2. Add the following line for each FC HBA port that is to be enabled:
        name="fp" parent="parent name" port=port-number mpxio-disable="no";

        where parent name is the port device name, and port-number is the FC HBA port number.

        For example, the following entries disable multipathing on all FC HBA controller ports except for the two specified ports:

        mpxio-disable="yes";
        name="fp" parent="/pci@6,2000/SUNW,qlc@2" port=0 mpxio-disable="no";
        name="fp" parent="/pci@13,2000/pci@2/SUNW,qlc@5" port=0 mpxio-disable="no";
      3. Add the following line for each FC HBA port that is to be disabled:
        name="fp" parent="parent name" port=port-number mpxio-disable="yes";

        For example:

        name="fp" parent="/pci@6,2000/SUNW,qlc@2" port=0 mpxio-disable="yes";
  4. Type stmsboot -u to start the reboot and configuration process.

    You are prompted to reboot. During the reboot, the /etc/vfstab file and your dump device configuration are updated to reflect any device name changes.

  5. (Optional) After the reboot, if necessary, configure your applications to use new device names as described in Multipathing Considerations.

Further reference:
Solaris SAN Configuration and Multipathing Guide

How to remove Worm Downadup Conficker

Worm:W32/Downadup.gen, W32/Conficker.worm.gen, Mal/Conficker, Worm: Win32/Conficker

Conficker, also known as Downup, Downadup and Kido, is a computer worm targeting the Microsoft Windows operating system that was first detected in November 2008. The worm uses a combination of advanced malware techniques which has made it difficult to counter, and has since spread rapidly into what is now believed to be the largest computer worm infection since the 2003 SQL Slammer.

(Wikipedia)

Continue reading

LogMeIn Hamachi: Instant, Zero Configuration VPN

logolmi.gif

logo-hamachi.gif

LogMeIn Hamachi is a VPN service that easily sets up in 10 minutes, and enables secure remote access to your business network, anywhere there’s an Internet connection. It works with your existing firewall, and requires no additional configuration. Hamachi is the first networking application to deliver an unprecedented level of direct peer-to-peer connectivity. It is simple, secure, and cost-effective.

This is my VPN screen shot:

logmein.jpg

Advantages of LogMeIn Hamachi:
•LAN over the Internet Arrange multiple computers into their own secure network, just as if they were connected by a physical cable.

•Remote Access Remote control any machine on your network with Remote Desktop.

•Files and Network Drives Access critical files and network drives.

•Zero-configuration Works without having to adjust a firewall or router.

•Security Industry leading encryption and authentication.

•Cost Effective Basic version is free to use. Premium begins at $4.95/month.

For more info, click link below:

https://secure.logmein.com/products/hamachi/vpn.asp?lang=en]]
https://secure.logmein.com/products/hamachi/download.asp
https://secure.logmein.com/r.asp?r=hamachi&t=page&u=learn

Direct download:
http://files.hamachi.cc/HamachiSetup-1.0.2.5-en.exe