flyinweb's blog

通过DELL服务器的序列号，可以在其网站查询到有关该序列号对应的服务器信息，如果服务器过多，逐一查询的工作量比较大，可以通过命令行方式来查询

1、单一序列号查询：

#!/usr/bin/perl -w  
use utf8;  
binmode( STDOUT, ':encoding(utf8)' );  
use LWP::Simple;  
 
if ($#ARGV+1 != 1 ) {  
    print "\nUsage: $0 <sn>\n";  
    exit;  
}  
 
#my $sn = shift;  
my $sn = $ARGV[0];  
print "$sn\n";  
my $url = "http://supportapj.dell.com/support/topics/topic.aspx/ap/shared/support/my_systems_info/zh/cn/details?c=cn&l=zh&s=gen&~ck=anavml&servicetag=$sn";  
my $content = get $url;  
 
my %h = $content =~ m{(系统类型:).*"top">(.*?)<.*(出厂日期:).*"top">(.*?)<.*(国家和地区:).*?"top">(.*?)<};  
 
print $_, $h{$_}, "\n" for keys %h; 

输出：

[root@flyinweb dell]# ./getdellinfobysn.pl  
 
Usage: ./simple.pl <sn>  
[root@flyinweb dell]# ./getdellinfobysn.pl 1rcgw1x   
1rcgw1x  
系统类型:PowerEdge 1850  
国家和地区:China  
出厂日期:2005/12/31 

2、批量查询

可以将序列号存储在文件中，通过脚本读取每一行，然后调用上述脚本通过以下脚本来进行：

#!/usr/bin/perl -w  
# getinfobysn.pl  
use utf8;  
binmode( STDOUT, ':encoding(utf8)' );  
use LWP::Simple;  
 
open(INFILE1, "sn.txt");  
#open(OUTFILE, "+>result.txt")|| die "Cannot open the newfile: $!\n";  
 
foreach $x (<INFILE1>){  
    chomp $x;  
    print "$x\n";  
    my $url ="http://supportapj.dell.com/support/topics/topic.aspx/ap/shared/support/my_systems_info/zh/cn/details?c=cn&l=zh&s=gen&~ck=anavml&servicetag=$x";  
    my $content = get $url;  
 
    my %h = $content =~ m{(系统类型:).*"top">(.*?)<.*(出厂日期:).*"top">(.*?)<.*(国家和地区:).*?"top">(.*?)<};  
    print $_, $h{$_}, "\n" for keys %h;  
    print "\n";  
}  
 
#close  OUTFILE;  
close  INFILE1;  
exit; 

输出：

# 输出  
# [root@flyinweb dell]# ./getinfobysn.pl        
# 41G833X  
# 系统类型:PowerEdge R410  
# 国家和地区:China  
# 出厂日期:2011/3/16  
 
# HKW5Y2X  
# 系统类型:PowerEdge R410  
# 国家和地区:China  
# 出厂日期:2010/8/18 

症状：

mysql数据库无法正常启动，日志如下：

111110 14:41:22  InnoDB: Starting shutdown...
111110 14:41:28  InnoDB: Shutdown completed; log sequence number 0 103559
111110 14:41:28 [Note] MySQL: Shutdown complete

111110 14:43:06 [Note] Plugin 'FEDERATED' is disabled.
111110 14:43:06  InnoDB: Started; log sequence number 0 103559
111110 14:43:06 [ERROR] Binlog has bad magic number;  It's not a binary log file that can be used by this version of MySQL
111110 14:43:06 [ERROR] Can't init tc log
111110 14:43:06 [ERROR] Aborting

111110 14:43:06  InnoDB: Starting shutdown...
111110 14:43:11  InnoDB: Shutdown completed; log sequence number 0 103559
111110 14:43:11 [Note] MySQL: Shutdown complete

解决办法：

删除最后一个mysql-bin.x，打开mysql-bin.index 文件，删除对应的mysql-bin.x条目，重启。（未经测试）

【问题描述】：

1、Windows 7 无法访问Windows2003共享，出现“系统错误 86。网络密码不正确”，但是这些问题都是正确的，经分析问题可能出现在用户身份验证上。

2、访问共享打印机

[Window Title]
添加打印机

[Main Instruction]
连接到打印机

[Content]
Windows 无法连接到打印机。

[^] 隐藏详细信息(D)  [确定]

[Expanded Information]
操作失败，错误为 0x0000052e。

For clustering the Cluster resource name must have full access to the Virtual Cluster Names so when failover takes place DNS entries can be updated.

However if you used a underscore _ a big NO! NO! with NetBIOS and DNS names. Solution: wipe and start over.
If you used a dash -, an exceptable NetBIOS name, your still screwed and got this error. BUG in Windows 2008 R2. You can add the name manualy to the DNS, but it will not be automatic.

Following errors were recorded in event logs when it registrations fails:

场景1：

Cluster network name resource 'SQL Network Name (VirutalClusterName)' failed registration of one or more associated DNS name(s) for the following reason:
DNS signature failed to verify.

Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server
In DNS Management (dnsmgmt.msc):

1. Find the VirtualClusterName that is failing to register.
2. Right-Click Properties.
3. Select Security Tab.
4. Click Add.
5. Click Object Types.
6. Check off "Computers"; uncheck other options selected.
7. Enter in the name of the cluster (a.k.a Cluster Name Object (CNO)).
8. Click Check Names; Verify that the entry has been found.
9. Click OK.
10. Give the CNO FULL Control over this record.
11. Click OK.

场景2：

群集网络名称资源“群集名称”注册一个或多个相关联的 DNS 名称失败。原因如下:
DNS 服务器失败。

请确保与从属 IP 地址相关联的网络适配器已配置为至少可以访问一个 DNS 服务器。

相关资源：

Windows Server 2008 Troubleshooting: Event ID 1196 — Microsoft-Windows-FailoverClustering

DNS Registration with the Network Name Resource

Until Informix Dynamic Server 10.0 the number of MSC (or Miscellaneous) Virtual Processors was limited to one. With IDS 10.0 multiple MSC VPs can be configured using the VPCLASS onconfig parameter (e.g. VPCLASS msc,num=2), or added dynamically using onmode -p 1 msc.

What does that mean and why would I want to use it?
The MSC VP is a type of AIO VP, executing operating system calls on behalf of other threads. While the AIO VP mainly takes care of filesystem I/O calls the MSC VP executes some network and authentication calls like getpwnam(), gethostbyname(), gethostbyaddr() etc. (It also maintains some statistics like VP CPU usage.) The MSC VP gets used at client connection time for the operating system part of user validation, and in most cases one is sufficient.

Virtual Processor (VP) is the technical term for an Informix process. Informix forks off a handful of these VPs at engine startup to take advantage of multiple CPUs or cores and increase parallelism. Each VP is multithreaded allowing Informix to efficiently use the CPU time each process is awarded by the OS, letting ready threads do work while other threads are busy waiting on something else to finish.

There are multiple types of VPs, each performing a specific job. Some VPs are configurable (i.e. the number of VPs and what CPU they should run on, etc.) through the VPCLASS ONCONFIG parameter and some are not. The 2 VPs you need to be concerned about right now are:

• CPU - Runs all session threads and some system threads. Runs KAIO (Kernel Asynchronous I/O) if enabled. This process will consume most of the CPU cycles given to Informix by the OS and is configurable.
• AIO - Performs all I/O except for physical or logical logging if KAIO is disabled. Performs I/O to cooked chunks if KAIO is enabled and is configurable.

The Hyper-V best practice in traditional production environments is that any physical network interface used by guest virtual machines is dedicated and isolated to guest only traffic and not shared with the management operating system (host). This recommendation was made for several reasons – security is the primary reason since virtual machines are considered less trusted than the management partition isolating the network traffic reduces the risk that a malicious guest could take advantage of a remote security exploit to take over the physical machine. Following this practice also reduces the risk of a guest virtual machine saturating the network preventing the server administrator from being able to log onto the physical machine and take appropriate action. In Server 2008 (Hyper-V V1) you accomplished this by unbinding TCP (as well as any other network protocol) on the virtual adapter exposed by Hyper-V – in Server 2008 R2 we have added a new feature which be default does not create the virtual adapter on the management partition (of course there’s an option to have it the old way). In addition this functionality was pushed into the Add Roles Wizard when you create your first virtual network. Here’s some screen captures to illustrate.

I was recently asked about how to change the IP address of an Exchange 2007 cluster. Here is the information that I shared: