Wave2 AP（1800,2800,3800）サポートパッチについて

Kunitaka Matsumura · ‎2017-04-26

概要
インストール手順
WLC Softwareの要件
Prime Software の要件
補足：作業ログ

概要

Wave2 APをMSE 8.0 でサポートする為のパッチのインストール手順について説明します。
適用対象 MSE のバージョンは 8.0.140.0 です。
このパッチの適用により、クライアント、RFID タグのトラッキングが AP1800、2800、3800 を利用時に可能になります。
※ 8.0.140.9 にはこのパッチの修正は含まれておりますので、8.0.140.9 へ適用する必要はございません。

パッチファイル名：Wave2APsPatch-201704051742.tar.gz

以下の CCO サイトより入手できる 8_0_140_0_Wave2APsPatch.zip に同封されています。
'Download Software, Mobility Services Engine Virtual Appliance'
https://software.cisco.com/download/release.html?mdfid=284294864&flowid=31242&softwareid=282487503&release=10.3.0&relind=AVAILABLE&rellifecycle=ED&reltype=latest
( All Releases より、8.0.140.0(ED) を選択して下さい。)

インストール手順

root ユーザで MSE にログインしパッチファイルを /opt/installers フォルダにコピーし tar.gz ファイルを展開します。
cd /opt/installers
tar zxvf Wave2APsPatch-201704051742.tar.gz
cd /opt/installers/Wave2APsPatch
README ファイルに従ってパッチを適用します。
/etc/init.d/msed stop
./install-patch.sh
/etc/init.d/msed start
./vendordata-schema-change.sh

作業ログは補足に記載してあります。

WLC Softwareの要件

RFID タグをトラッキングする要件がない場合、WLC の変更は必要ありません。
RFID タグをトラッキングする要件がある場合、 WLC Software 8.3.112.2 / 8.3 次期メンテナンスリリース / 8.4 にアップグレードが必要です。
※ 8.3.112.2 の入手にはサービスリクエストのオープンが必要となります。

Prime Software の要件

1800, 2800, 3800 をサポートしているバージョンであれば問題ありません。
注意事項：本パッチを適用後、MSEのバージョン番号（8.0.140.0）は変更されません。

補足：作業ログ

1. MSEの状態確認

[root@mse ~]# /etc/init.d/msed status
STATUS:
Health Monitor is running
UDI: PID: AIR-MSE-VA-K9 , VID: V01, SN: mse_8f4f0dac-2739-11e7-81cb-005056b0
703b
Disk Capacity: 170G
Disk Space used: 5.3G
Drive Type: Spinning Disk Drive
Server Uptime: 0 Days, 1:05 Hours
Number of Reboots: 2
-----------------------------
Retrieving MSE Services status.
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJ configured for FIPS mode
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCE turning on FIPS...
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCEProvider version 2.0520150519 loading...
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - Executing Java version = 1.7.0_45

MSE services are up, getting the status

-------------
Server Config
-------------

Product name: Cisco Mobility Service Engine
Version: 8.0.140.0
Health Monitor Ip Address: 1.1.1.1
High Availability Role: 1
Hw Version: V01
Hw Product Identifier: AIR-MSE-VA-K9
Hw Serial Number: mse_8f4f0dac-2739-11e7-81cb-005056b0703b
HTTPS: null
Legacy Port: 8001
Log Modules: -1
Log Level: INFO
Days to keep events: 2
Session timeout in mins: 30
DB backup in days: 2

-------------
Services
-------------

Service Name: Context Aware Service
Service Version: 8.0.1.116
Admin Status: Enabled
Operation Status: Up

Service Name: WIPS
Service Version: 3.0.8193.0
Admin Status: Disabled
Operation Status: Down

Service Name: Mobile Concierge Service
Service Version: 5.0.1.28
Admin Status: Disabled
Operation Status: Down

Service Name: CMX Analytics
Service Version: 3.0.1.80
Admin Status: Disabled
Operation Status: Down

Service Name: CMX Connect & Engage
Service Version: 1.0.0.36
Admin Status: Disabled
Operation Status: Down

Service Name: HTTP Proxy Service
Service Version: 1.0.0.1
Admin Status: Disabled
Operation Status: Down

--------------
Server Monitor
--------------

Server start time: Sat Apr 22 19:00:22 JST 2017
Server current time: Sat Apr 22 19:01:35 JST 2017
Server timezone: Asia/Tokyo
Server timezone offset (mins): 540
Restarts: 1
Used Memory (MB): 112
Allocated Memory (MB): 989
Max Memory (MB): 989
DB disk size (MB): 5170

-------------
Context Aware Service
-------------

Total Active Elements(Wireless Clients, Tags, Rogue APs, Rogue Clients, Interfer
ers, Wired Clients): 0
Active Wireless Clients: 0
Active Tags: 0
Active Rogue APs: 0
Active Rogue Clients: 0
Active Interferers: 0
Active Wired Clients: 0
Active Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired C
lients, Tags) Limit: 100
Active Sessions: 0
Wireless Clients Not Tracked due to the limiting: 0
Tags Not Tracked due to the limiting: 0
Rogue APs Not Tracked due to the limiting: 0
Rogue Clients Not Tracked due to the limiting: 0
Interferers Not Tracked due to the limiting: 0
Wired Clients Not Tracked due to the limiting: 0
Locally administered clients Not Tracked due to filtering: 0
Total Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired Cl
ients) Not Tracked due to the limiting: 0
[root@mse ~]#

2. パッチファイルをMSEにコピー

コマンドラインか MSE の GUI メニューを使ってください。

2-a. コマンドラインの場合

[root@mse ~]# cd /opt/installers/
[root@mse installers]# sftp ftp@192.168.xxx.yyy <<< 適当なサーバを準備してください。
Connecting to 192.168.xxx.yyy…
The authenticity of host ‘192.168.129.49 (192.168.xxx.yyy)’ can’t be established.
RSA key fingerprint is 8b:4d:f4:fb:ac:5b:4a:6e:ed:0e:11:50:10:a2:59:c1.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘192.168.xxx.yyy’ (RSA) to the list of known hosts.
ftp@192.168.xxx.yyy’s password:
sftp>
sftp> get Wave2APsPatch-201704051742.tar.gz
Fetching /Wave2APsPatch-201704051742.tar.gz to Wave2APsPatch-201704051742.tar.gz
/Wave2APsPatch-201704051742.tar.gz 100% 9159KB 8.9MB/s 00:01
sftp> quit

[root@mse installers]# ls -al
total 5282604
drwxr-xr-x 3 nobody nobody 4096 Apr 22 19:07 .
drwxr-xr-x 9 root root 4096 Apr 22 18:59 ..
-rwxr-xr-x 1 nobody nobody 45 Apr 22 17:45 aeroscout.tar.gz
-rwxr-xr-x 1 nobody nobody 2814635162 Sep 1 2016 CISCO-MSE-L-K9-8-0-140-0-64bit.bin
-rwxr-xr-x 1 nobody nobody 2580005154 Sep 12 2016 Database_Installer.11.2.0.4.tar.gz
drwxr-xr-x 4 nobody nobody 4096 Apr 22 17:47 dbinstaller
-rwxr-xr-x 1 nobody nobody 451 Sep 1 2016 MSE_PUB.pem
-rwxr-xr-x 1 nobody nobody 256 Sep 1 2016 signhash.bin
-rwx—— 1 root root 9379216 Apr 22 19:07 Wave2APsPatch-201704051742.tar.gz

2.b GUIの場合

SYSTEM ＞ MAINTENANCE ＞ Download Software

3.パッチファイルを展開

[root@mse installers]# tar xvf Wave2APsPatch-201704051742.tar.gz
Wave2APsPatch/
Wave2APsPatch/server-eng.jar
Wave2APsPatch/server-eng.jar.sha256
Wave2APsPatch/algo.jar.sha256
Wave2APsPatch/install-patch.sh
Wave2APsPatch/algo.jar
Wave2APsPatch/README
Wave2APsPatch/vendordata-schema-change.sh

4. 展開されたディレクトリィに移動してファイルを確認

[root@mse installers]# cd Wave2APsPatch
[root@mse Wave2APsPatch]# ls
algo.jar README vendordata-schema-change.sh
algo.jar.sha256 server-eng.jar
install-patch.sh server-eng.jar.sha256

READMEファイルの内容
[root@mse Wave2APsPatch]# more README
Patch
-----
Support for Wave APs

Applicable MSE version
----------------------
8.0.140.0

Contents
--------
install-patch.sh Script to install the patch
vendordata-schema-change.sh Script to change vendordata schema.
algo.jar Algorithm jar supporting new Wave2 APs
server-eng.jar CAS service main jar file
algo.jar.sha256 checksum (sha256) of the algo.jar
server-eng.jar.sha256 checksum (sha256) of server-eng.jar
README This file

Instructions to apply patch
===========================
1. Stop MSE services.
2. Execute install script as given below
./install-patch.sh
3. Start MSE services.
4. Verify that MSE services are Up using
getserverinfo
5. Execute schema change script as given below
./vendordata-schema-change.sh
6. Verify that clients/tags are detected on Wave APs.

5．パッチを適用する前にMSEのサービスを停止

[root@mse Wave2APsPatch]# /etc/init.d/msed stop
Stopping MSE Platform
Apache Service is running…will not stop it
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJ configured for FIPS mode
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCE turning on FIPS…
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCEProvider version 2.0520150519 loading…
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - Executing Java version = 1.7.0_45

Shutting down framework and services ……
Framework and services successfully shutdown. Shutting down database …..
MSE platform shutdown complete

6. パッチをインストール

[root@mse Wave2APsPatch]# ./install-patch.sh
Installed patch …
Patch installed successfully.
[root@mse Wave2APsPatch]#

7. MSEのサービスを起動

[root@mse Wave2APsPatch]# /etc/init.d/msed start
Starting MSE Platform

Flushing any pending data from Admin Process read and write pipe.
Starting Apache HTTPD Server
Apache Server is already running. Skipping restart.
Starting Health Monitor, Waiting to check the status.
Health Monitor successfully started
Starting Admin process…
Started Admin process.
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJ configured for FIPS mode
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCE turning on FIPS…
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCEProvider version 2.0520150519 loading…
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - Executing Java version = 1.7.0_45

Database started successfully. Starting framework and services …
Database started successfully. Starting framework and services ………………………….
Framework and services successfully started

8. MSEのサービスの起動を確認

[root@mse Wave2APsPatch]# /etc/init.d/msed start
Starting MSE Platform

Flushing any pending data from Admin Process read and write pipe.
Starting Apache HTTPD Server
Apache Server is already running. Skipping restart.
Starting Health Monitor, Waiting to check the status.
Health Monitor successfully started
Starting Admin process...
Started Admin process.
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJ configured for FIPS mode
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCE turning on FIPS...
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCEProvider version 2.0520150519 loading...
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - Executing Java version = 1.7.0_45

Database started successfully. Starting framework and services ...
Database started successfully. Starting framework and services ...............................
Framework and services successfully started

[root@mse Wave2APsPatch]# getserverinfo
Health Monitor is running
UDI: PID: AIR-MSE-VA-K9 , VID: V01, SN: mse_8f4f0dac-2739-11e7-81cb-005056b0703b
Disk Capacity: 170G
Disk Space used: 5.3G
Drive Type: Spinning Disk Drive
Server Uptime: 0 Days, 1:17 Hours
Number of Reboots: 2
-----------------------------
Retrieving MSE Services status.
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJ configured for FIPS mode
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCE turning on FIPS...
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCEProvider version 2.0520150519 loading...
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - Executing Java version = 1.7.0_45

MSE services are up, getting the status

-------------
Server Config
-------------

Product name: Cisco Mobility Service Engine
Version: 8.0.140.0
Health Monitor Ip Address: 1.1.1.1
High Availability Role: 1
Hw Version: V01
Hw Product Identifier: AIR-MSE-VA-K9
Hw Serial Number: mse_8f4f0dac-2739-11e7-81cb-005056b0703b
HTTPS: null
Legacy Port: 8001
Log Modules: -1
Log Level: INFO
Days to keep events: 2
Session timeout in mins: 30
DB backup in days: 2

-------------
Services
-------------

Service Name: Context Aware Service
Service Version: 8.0.1.116
Admin Status: Enabled
Operation Status: Up

Service Name: WIPS
Service Version: 3.0.8193.0
Admin Status: Disabled
Operation Status: Down

Service Name: Mobile Concierge Service
Service Version: 5.0.1.28
Admin Status: Disabled
Operation Status: Down

Service Name: CMX Analytics
Service Version: 3.0.1.80
Admin Status: Disabled
Operation Status: Down

Service Name: CMX Connect & Engage
Service Version: 1.0.0.36
Admin Status: Disabled
Operation Status: Down

Service Name: HTTP Proxy Service
Service Version: 1.0.0.1
Admin Status: Disabled
Operation Status: Down

--------------
Server Monitor
--------------

Server start time: Sat Apr 22 19:11:47 JST 2017
Server current time: Sat Apr 22 19:13:33 JST 2017
Server timezone: Asia/Tokyo
Server timezone offset (mins): 540
Restarts: 2
Used Memory (MB): 117
Allocated Memory (MB): 989
Max Memory (MB): 989
DB disk size (MB): 5170

-------------
Context Aware Service
-------------

Total Active Elements(Wireless Clients, Tags, Rogue APs, Rogue Clients, Interferers, Wired Clients): 0
Active Wireless Clients: 0
Active Tags: 0
Active Rogue APs: 0
Active Rogue Clients: 0
Active Interferers: 0
Active Wired Clients: 0
Active Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired Clients, Tags) Limit: 100
Active Sessions: 0
Wireless Clients Not Tracked due to the limiting: 0
Tags Not Tracked due to the limiting: 0
Rogue APs Not Tracked due to the limiting: 0
Rogue Clients Not Tracked due to the limiting: 0
Interferers Not Tracked due to the limiting: 0
Wired Clients Not Tracked due to the limiting: 0
Locally administered clients Not Tracked due to filtering: 0
Total Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired Clients) Not Tracked due to the limiting: 0
[root@mse Wave2APsPatch]#

9. スキーマの変更

[root@mse Wave2APsPatch]# ./vendordata-schema-change.sh
vendordata schema change: SUCCESS
[root@mse Wave2APsPatch]#

10. 動作の確認

Wave2 対応パッチの適用は以上です。
PI の MAPに Client 等が表示されることを確認してください。

[サンプル表示]

ychikara · ‎2017-05-02

情報の提供、ありがとうございます。

Wave2APsPatch-201704041214.tar.gz

のパッチファイルですが、入手するための方法をご教示いただけますでしょうか？

2017/5/2追記：いただいたご回答とのつながりを見やすくするために、本文を変更させていただきました

satwatan · ‎2017-05-02

SR にてご提供させていただきますので、必要の際にはお手数ですが SR オープンいただけますでしょうか。

宜しくお願い致します。

ychikara · ‎2017-05-02

ご回答ありがとうございました！

SRでの対応となる旨承知いたしました。