Table of Contents
Advertisement
(Step 5) Make sure that the set information is translated. hfcldd0 operates by the separate
setting of the port in (Step 2) and hfcldd1 operates by the common setting across all the adapter
ports in (Step 3.)
# ./hfcmgr -p hfcldd0
Time: xxxx/xx/xx xx:xx:xx
--------------------------------------------------------
WWPN:50000870003021e0 Device:hfcldd0 [LinkUp]
--------------------------------------------------------
：
Queue Depth
：
# ./hfcmgr -p hfcldd1
--------------------------------------------------------
WWPN:50000870003021e2 Device:hfcldd1 [LinkUp]
--------------------------------------------------------
：
Queue Depth
：
Then, delete the separately set the QueueDepth value of hfcldd0 and make sure that all the
adapter ports including hfcldd0 are operating by the commonly set value, QueueDepth 10.
(Step 6) Delete QueueDepth of hfcldd0.
Figure hfcmgr –p deleting command
# ./hfcmgr -p delete hfcldd0 qd 20
Do you execute it? (y/n) > y
Time:xxxx/xx/xx xx:xx:xx
Succeeded.
You need reboot system after remake a ramdisk image to reflect parameter changes
to the system.
# ./hfcmgr -p hfcldd0
:
Queue Depth
:
(Step 7) Reboot after updating the RAMDISK image.
(Step 8) Make sure that the set information is translated. hfcldd0 operates by the common
setting across all the adapter ports in (Step 3.).
Figure Check after deleting hfcmgr –p
# ./hfcmgr -p hfcldd0
:
Queue Depth
:
#
Figure Check after setting hfcmgr –p
Operating on 20 set by hfcldd0 port individual setting
: 20 (20)
: 10 (-)
: 20 (-)
: 10 (-)
46
hfcldd1 is operating on 10 commonly set
value to all the ports. There is no hfcldd1 port
individual set value (-).
20 is deleted but the driver is still operating on
20.
Advertisement
Table of Contents
