2012年10月12日 星期五

您所輸入的網路介面卡IP位置已經被指派給另一個介面卡XXX的問題


這問題源自於發生在將A Server端用 VMware vCenter Converter 將OS做成 vmdk 的映像檔然後掛載在VM上。因為轉換後網卡不同了,因此原本在A台主機上的網卡上設定10.10.10.22 (example) 到了VM 上的VM-A主機上要再設定相同的IP時會出現下列的錯誤訊息  

英譯: This network adapter is already assigned to another adapter XXXXXXX on this compuetr"
中譯: 您輸入的網路介面卡IP位置已經被指派給另一個介面卡 XXXXXXX


以前有時候運氣很好,從控制台把隱藏網卡叫出來刪掉就好了....但這次居然找不到? 搞了很久發現有更簡單的方式
解決方式:
1. 開始 ->執行 ->輸入regedit (打開登錄檔編輯器)
2.尋找下列機碼位置
HKEY_LOCAL_MACHINE\SYSTEMCurrent\ControlSet\Services\Tcpip\Parameters\Interfaces

在Interfaces 機碼底下放著都是設定網卡的資訊,你可以點選每一個來看,
但是哪一個才是我想要的呢?

因為看不出來所以才每一個都點開來看,就應該會發現有一個居然已經有10.10.10.22 ,這表示這個資料夾就是已經消失在VM系統中的舊網卡,因此把此把對應的做邊資料夾機碼刪掉後,你在去修改一次IP就會發現很神奇的可以儲存了。













2012年7月17日 星期二

VMware-用 vmkfstools Clone一個新的VM OS

因為沒有安裝 Vcenter的關係所以在要不斷的複製出新的VM OS其實是很麻煩的(沒辦法滑鼠點點就完成 XD )

解決方法:

1. 每次都建立一個新的設定檔然後用光碟片安裝OS  <<(當然不建議嚕)


2.先做成一個Sample OS , 然後用 vmkfstools 來做clone


指令如下:
vmkfstools -i /vmfs/(volumes name)/(Storage name)/(folder name)/(file name).vmdk -d thin
/vmfs/(volumes name)/(Storage name)/(folder name)/(file name).vmdk







Vmkfstools 參數如下:


OPTIONS FOR FILE SYSTEMS: 



vmkfstools -C --createfs [vmfs3|vmfs5]
               -b --blocksize #[mMkK]
               -S --setfsname fsName
           -Z --spanfs span-partition
           -G --growfs grown-partition
   deviceName

           -P --queryfs -h --humanreadable
           -T --upgradevmfs
   vmfsPath

OPTIONS FOR VIRTUAL DISKS:

vmkfstools -c --createvirtualdisk #[gGmMkK]
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick]
               -a --adaptertype [buslogic|lsilogic|ide]
           -w --writezeros
           -j --inflatedisk
           -k --eagerzero
           -K --punchzero
           -U --deletevirtualdisk
           -E --renamevirtualdisk srcDisk
           -i --clonevirtualdisk srcDisk
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick|
                                rdm:<device>|rdmp:<device>|
                                2gbsparse]
               -N --avoidnativeclone
           -X --extendvirtualdisk #[gGmMkK]
               [-d --diskformat eagerzeroedthick]
           -M --migratevirtualdisk
           -r --createrdm /vmfs/devices/disks/...
           -q --queryrdm
           -z --createrdmpassthru /vmfs/devices/disks/...
           -v --verbose #
           -g --geometry
           -I --snapshotdisk srcDisk
           -x --fix [check|repair]
           -e --chainConsistent
   vmfsPath

OPTIONS FOR DEVICES:

           -L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|readresv] /vmfs/devices/disks/...
           -B --breaklock /vmfs/devices/disks/...


2012年5月18日 星期五

Cisco Aironet1262N-快速連接GUI

最近剛入手 Cisco Aironet 1262N 的 無線Access Point ,很開心的把它拿出來,這體積還真的有點大
老實說我也是第一次碰到這種脫離SOHO的無線AP

但....要怎樣連接到GUI??

連接GUI 介面方法:

1.使用DHCP 進行IP配法: 如果有架設DHCP Server 網路一插上去就 BVI1 Interface就會自動派發到IP,所以查一下DHCP Server 對照一下Cisco Aironet背面的MAC Address就可以知道是哪個IP了。

2.使用Consol介面指定BVI1 介面IP /Mask 及Gateway


EWSW01#
EWSW01#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
EWSW01(config)#int BVI1
EWSW01(config-if)#ip add
EWSW01(config-if)#ip address 10.10.11.203 255.255.255.224
EWSW01(config-if)#no sh
EWSW01(config-if)#exit

EWSW01(config)#ip default-gateway 10.10.10.254



這樣一來就可以連到Cisco Aironet 的GUI 介面,是不是很簡單呢.....

2012年5月15日 星期二

Cisco Aironet 設定 SSH


Configure Secure Shell (SSH) on an Access Point

CLI Configuration
In this section, you are presented with the information to configure the features described in this document
with the use of CLI.Step−by−Step Instructions
In order to enable SSH−based access on the AP, you first must configure the AP as an SSH server. Follow
these steps in order to configure an SSH server on the AP from CLI:
Configure a host name and domain name for the AP.
AP#configure terminal

!−−− Enter global configuration mode on the AP.

AP<config>#hostname Test
!−−− This example uses "Test" as the AP host name.

Test<config>#ip domain name abc.com
!−−− This command configures the AP with the domain name "abc.com".
1.
Generate a Rivest, Shamir, and Adelman (RSA) key for your AP.
Generation of an RSA key enables SSH on the AP. Issue this command in global configuration mode:

Test<config>#crypto key generate rsa rsa_key_size
!−−− This generates an RSA key and enables the SSH server.
Note: The recommended minimum RSA key size is 1024.
2.
Configure user authentication on the AP.
On the AP, you can configure user authentication to use either the local list or an external
authentication, authorization, and accounting (AAA) server. This example uses a locally generated list
in order to authenticate the users:

Test<config>#aaa new−model


!−−− Enable AAA authentication.
Test<config>#aaa authentication login default local none
!−−− Use the local database in order to authenticate users.

Test<config>#username Test password Test123
!−−− Configure a user with the name "Test".

Test<config>#username ABC password xyz123
!−−− Configure a second user with the name "ABC".

This configuration configures the AP to perform user−based authentication with the use of a local
database that is configured on the AP. The example configures two users in the local database, "Test"
and "ABC".
3.
Configure the SSH parameters.
Test<config>#ip ssh {[timeout seconds] | [authentication−retries integer]}
!−−− Configure the SSH control variables on the AP.
4. Note: You can specify the timeout in seconds, but do not exceed 120 seconds. The default is 120.
This setting applies to the SSH negotiation phase. You can also specify the number of authentication
retries, but do not exceed five authentication retries. The default is three.
GUI Configuration
You can also use the GUI in order to enable SSH−based access on the AP.
Step−by−Step Instructions
Complete these steps:
Log in to the AP through the browser.
The Summary Status window displays.
1.
Click Services in the menu on the left.
The Services Summary window displays.
2. Click Telnet/SSH in order to enable and configure the Telnet/SSH parameters.
The Services: Telnet/SSH window displays. Scroll down to the Secure Shell Configuration area. Click
Enable beside Secure Shell, and enter the SSH parameters as this example shows:
This example uses these parameters: EXAMPLE
♦ System Name: Test
♦ Domain Name: abc.com
♦ RSA Key Size: 1024
♦ Authentication Timeout: 120
♦ Authentication Retries: 3
3. 4. Click Apply in order to save the changes.
Verify
Use this section to confirm that your configuration works properly.
The Output Interpreter Tool ( registered customers only) (OIT) supports certain show commands. Use the OIT to
view an analysis of show command output.
show ip ssh Verifies if SSH is enabled on the AP and enables you to check the version of SSH that
runs on the AP. This output provides an example:
•
show ssh Enables you to view the status of your SSH server connections. This output provides an
example:
•
Now, initiate a connection through a PC that runs third−party SSH software and then make an attempt to log
in to the AP. This verification uses the AP IP address, 10.0.0.2. Because you have configured the user name
Test, use this name in order to access the AP through SSH:Troubleshoot
Use this section to troubleshoot your configuration.
If your SSH configuration commands are rejected as illegal commands, you have not successfully generated
an RSA key pair for your AP. Refer to the Troubleshooting Tips section of the document Configuring Secure
Shell for a list of possible reasons for this problem.Disable SSH
In order to disable SSH on an AP, you must delete the RSA pair that is generated on the AP. In order to delete
the RSA pair, issue the crypto key zeroize rsa command in global configuration mode. When you delete the
RSA key pair, you automatically disable the SSH server. This output provides an example:
Related Information
• Configuring Secure Shell
• Configuring the Access Point for the First Time
• Secure Shell (SSH) Support Page
• Wireless Support Page
• Technical Support & Documentation − Cisco Systems
Contacts & Feedback | Help | Site Map
© 2009 − 2010 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of
Cisco Systems, Inc.
Updated: Nov 05, 2008 Document ID: 68789