Managing the Media Flow Controller Disk Cache (CLI)
95
Media Flow Controller Administrator’s Guide
Media Flow Controller Configuration Tasks (CLI)
DM2_MGMT_STATE_IMPROPER_UNMOUNT and
DM2_MGMT_STATE_IMPROPER_MOUNT = "soft disk error, try to clear"
DM2_MGMT_STATE_CACHE_RUNNING = "cache running";
DM2_MUST_FORMAT = “Disk Cache Enable Failed - Disk Cache must be formatted before
enabling”
DEFAULT = "unknown state, please try again a little later";
When a disk cache error is displayed, a first step to take is bringing down the disk and bringing
it back up; to do, first find cache names, then act on the problem cache:
show media-cache disk list
media-cache disk <cache_name> status inactive
media-cache disk <cache_name> status active
media-cache disk <cache_name> enable
Replacing Bad Disks
In order to replace a bad disk, first disable and inactivate the disk, and then add a new disk.
This procedure uses dc_bad for the disk name; replace appropriately.
1.
Discover the bad disk’s name.
show media disk list
2.
Disable the bad disk by name.
media-cache disk dc_bad cache disable
3.
Make the bad disk inactive.
media-cache disk dc_bad status inactive
4.
Pull the drive, put in a new drive and mount the new disk.
media-cache disk mount-new
5.
Find the inactive disk’s name.
show media-cache disk list
6.
Activate the new disk.
media-cache disk dc_new status active
7.
Format the new disk; takes approximately five minutes.
media-cache disk dc_new format
8.
Enable the new disk.
media-cache disk dc_new cache enable
Important!
This procedure will not work when adding a new disk or disks to a Juniper
Networks VXA Series to a slot that was never configured. In such a case, please follow the
instructions in the VXA Series hardware guides for adding a new disk using the Adaptec Utility
or see
“Inserting New Disks into a VXA Series Media Flow Engine” on page 95
.
Inserting New Disks into a VXA Series Media Flow Engine
The task
“Replacing Bad Disks” on page 95
is incorrect for VXA Series hardware when adding
one or more new disks to a slot that was never used (configured) before because Media Flow
Controller only searches for new disks at manufacture time. Use this procedure instead.
Содержание MEDIA FLOW CONTROLLER 2.0.4 -
Страница 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Страница 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Страница 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Страница 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Страница 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Страница 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...