In the event of a kernel panic or freeze, critical logs may not be written to /var/log/messages making it difficult to troubleshoot the root cause.  Serial console logging can be configured to capture any kernel messages dumped to the console. Before beginning this procedure, stop the HDB processes on all hosts.  A reboot will be required to complete the procedure. Configure SUSE for console access Modify /etc/inittab Edit /etc/inittab to set the default runlevel to 3 (disables x-windows on startup). change id:5:initdefault: to id:3:initdefault: Uncomment and modify the S0 line to match: S0:12345:respawn:/sbin/agetty -L 115200 console vt102 Modify grub boot menu Edit /boot/grub/menu.lst Comment out gfxmenu #gfxmenu (hd0,0)/message Add these lines near the top of the file (before the grub entries): serial --unit=0 --speed=115200 terminal --timeout=8 serial console Copy the default boot entry, creating a new one before the default entry.  Add `console=tty0 console=ttyS0,115200` to the end of the kernel options.  Changes to the default grub entry are highlighted in red here: ###Don't change this comment - YaST2 identifier: Original name: linux### title Serial -- SUSE Linux Enterprise Server 11 SP1 - 2.6.32.12-0.7     kernel (hd1,0)/vmlinuz-2.6.32.12-0.7-default root=/dev/rootvg/lv_root resume=/dev/rootvg/lv_swap splash=silent crashkernel=256M-:128M showopts console=tty0 console=ttyS0,115200     initrd (hd1,0)/initrd-2.6.32.12-0.7-default Modify /etc/securetty Add the following lines to the end of the file to allow root login via console: console ttyS0 xvc0 Configure UCS Create Serial-over-LAN Policy Under Servers->Policies->root->Serial over LAN Policies: Create a new policy. Enable the State and choose Speed: 115200. Create IPMI Policy Under Servers->Policies->root->IPMI Access Profiles: Create a new policy. Create a new user with Admin role.  This will be the username/password you use to ssh to the console port. Create BIOS Policy Under Servers->Policies->root->Sub-Organizations->T01->BIOS Policies: Create or edit a BIOS Policy.  Under the Server Management tab, modify the console redirection settings: Console Redirection: serial-port-a Flow Control: none BAUD Rate: 115200 Terminal Type: Platform Default Legacy OS Redirect: enabled (or Platform Default) Apply the Policies to the Service Profile Template Under Servers->Service Profile Templates->root->Sub-Organizations->T01->Service Template T01-ServiceProfileTmpl: Under Policies tab: Click `Change Serial over Lan Policy` Select: Use an Existing Serial over LAN Policy Serial over LAN Policy: sol-115200 (the one created in an earlier step). Under BIOS Policy, select the BIOS Policy created in an earlier step Under IPMI Access Profile Policy, select the IPMI Policy created in an earlier step. Identify the Blade Management IPs: Under Admin->Communication Management->Management IP Pool->IP Address: Record the IPs (192.168.76.x) associated with each blade.  Check the service profiles to identify which host is running on each blade. Reboot Reboot the nodes to apply the changes to the service profiles. Setup Console Logging Session Open a console session to begin logging output.  SSH using the username/password created in the IPMI access profile to the blade mgmt IP of the server. To log the output to a file, here are a few options: Open the ssh session from an ssh client with logging enabled (putty, securecrt, etc.) Start a script session from a linux machine and then connect via ssh ... View more

Build rpm with --target sletc11sp1 ... View more

Performing a Factory Reset There are multiple methods available to perform a factory reset: When logged in with HIGH privileges (admin).  Gnome Control Center -> Device Settings -> Advanced -> Factory Reset G-key - Hold the 'g' key on the keyboard while the device is booting. Touch /etc/NEED_FACTORY_RESET What Happens During a Factory Reset Summary The following items are reset to defaults: User passwords (admin, thinuser, guest) Time Zone & Time Server Configuration Cached INI file(s) User Customizations Installed Printers Network Manager Settings Update.mode = Both, Update.preserve_changes = No, Force Update = No G-Key Reset set to 1 (Allowed) Registry (Persistent and Saved) Full Reset Process A factory reset occurs during the boot process.  When the device is signalled to perform a factory reset (using one of the above methods), the `/etc/init.d/boot.factory_reset` script is run. Here's a breakdown of that script: Command(s) Explanation rm -fr /etc/userlevel/home mkdir /etc/userlevel/home Reset /etc/userlevel/home Reset passwords Reset Time Zone Reset Time Server Reset Registry Delete Cached INI Delete Cached User Information Delete monitors.xml Delete Cached INI Reset Update Preferences Delete printers Reset Network Manager settings Enable g-key reset ... View more

In a default installation of VXC-M, all discovered devices are placed in the default view ("All Devices"). Built-in Views/Groups Built-in Views already exist for Platform, OS, and other attributes. Custom Views/Groups Custom Views allow an administrator to manually assign devices to groups, and apply different packages and configurations to each group. Create a New View Give your View a name Create a New Group Type Add your new group type to your View Change your current Device Manager View Drag devices into the appropriate groups Default Device Configurations by View/Group Once your views are created, you can create a DDC and attach it to the View. Create a new DDC Select your View from the dropdown Select your OS, Memory Size, and Image Add packages for the specified group Repeat this process for all groups Select when you want the DDC to be applied Click Finish Now, according to the timing you selected, the devices will pull the appropriate packages. Troubleshooting If a device is not pulling the appropriate packages: Verify that that the device has checked in Check the Package History for the device Check for currently scheduled updates Reset to Factory Defaults      As a last resort, you can reset the VXC to factory defaults. ... View more