Sun™ MediaCenter™ Server Administrator’s Guide Release 2.1 A Sun Microsystems, Inc. Business 901 San Antonio Road Palo Alto, CA 94303 USA 415 960-1300 fax 415 969-9131 Part No.
1997 Sun Microsystems, Inc. All rights reserved. 901 San Antonio Road, Palo Alto, California 94303 U.S.A. This product and related documentation are protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX® and Berkeley 4.
Contents 1. Introduction 1.1 Introduction 1.2 Sun MediaCenter Hardware 1.3 Sun MediaCenter Software 1.4 2. 1-1 1-1 1-2 1-4 1.3.1 Media File System (MFS) 1.3.2 Media Stream Manager 1.3.3 Content Manager 1.3.4 Web-based Tools 1-8 Video Output Interfaces 1-8 1.4.1 ATM 1-9 1.4.2 LAN 1-9 1-5 1-7 1-8 1.5 Content Preparation and Loading 1.6 Server Management 1.7 Push Model 1.8 Design Benefits 1-10 1-11 1-11 1-12 Preparing and Loading Content 2-1 2.
2.3 3. 4. 2-3 2.3.1 Packet Boundary 2.3.2 closed_gop 2.3.3 payload_unit_start_indicator 2.3.4 adaptation_field_control 2.3.5 random_access_indicator 2.3.6 PCR_flag 2-4 2.4 Content Loading 2-5 2.5 References 2-3 2-4 2-4 2-4 2-7 Monitoring the Server 3-1 3.1 Overview 3.2 Using the WebAdmin Tool 3-1 3-2 3.2.1 Invoking the Tool 3.2.2 Common Page Elements 3.3 Resource Utilization 3.4 Streaming Videos 3.5 Copy Sessions 3-9 3.6 Disk Capacity 3-12 3.
4.4 5. 6. Table of Contents Page 4.4.1 View Menu 4.4.2 Selected Menu 4-12 4-13 4-15 Sun MediaCenter Server Utilities 5-1 5.1 Setting a Title Access Control List 5.2 The smc_copy Utility 5.3 The smc_tar Utility 5-1 5-4 5-8 5.3.1 Syntax and Options 5-8 5.3.2 Content Loading 5-9 5.3.3 Copying Content 5-10 5.3.4 Remote Copying and Extraction 5.3.5 Examples 5-12 5-12 5.4 The smc_ls Utility 5-17 5.5 The smc_rm Utility 5-21 Sun MediaCenter Server FTP Daemon 6-1 6.
7. Server Output Data Format 7.1 Introduction 7.2 ATM Encapsulation 7.3 7.4 8. 7-1 7-2 7.2.1 MPEG-2 Transport Stream Packet Encapsulation 7.2.2 MPEG-2 Program Stream Packet Encapsulation 7.2.3 MPEG-1 System Stream Packet Encapsulation 7.2.4 Thomson Electronics Packet Encapsulation 7.2.5 MPEG-2 Encapsulation over Classical IP over AAL5 ATM Addressing 7-2 7-3 7-3 7-3 7-4 7.3.1 MPEG over AAL5 7-4 7.3.2 MPEG-2 over Classical IP over AAL5 Fast Ethernet Encapsulation 7-4 7-5 7.4.
9. 10. Access Control Lists 9-1 9.1 ACL Files 9.2 Permissions 9-2 9.3 Server ACL 9-2 9.4 Player ACL 9-3 9.5 Title ACL 9.6 Session ACL Troubleshooting 9-1 9-4 9-4 10-1 10.1 Symptoms and Possible Solutions/Workarounds 10.2 Error Messages 10-1 10-4 10.2.1 Server Console Messages 10.2.2 MFS Error Messages A. Setting up the SNMP Agent 10-4 10-5 A-1 A.1 The Sun MediaCenter Server MIB A.2 Enabling Management by Solstice Domain Manager A.3 Enabling Trap Handling B.
B.6 Tape Storage Format B.6.1 Tar Format B.6.2 Tapes B.7 Example B.
Preface This document, the Sun MediaCenter Server Administrator’s Guide, tells you how to set up, load content onto, and perform other administrative duties relevant to a Sun™ MediaCenter™ server.
The Sun MediaCenter Documentation Suite This manual is a companion to the Sun MediaCenter Server Installation and Configuration Manual, the Sun MediaCenter Server Programmer’s Guide and the Sun MediaCenter UltraSPARC Hardware Manual. Together these manuals are complementary of the hardware manuals shipped with the Sun products that make up a Sun MediaCenter server. These documents include manuals for the server, for the network interface (such as SunFastEthernet™ documentation), and the disk subsystem.
Appendix A “Setting up the SNMP Agent,” tells you how to make use of the SNMP agent that is shipped with the Sun MediaCenter server. Appendix B “Creating a Content Package,” describes how to prepare content if you are unable to use ftp for loading content. The Glossary lists terms from the realm of video technology, as well as terms specific to the Sun MediaCenter product. What Typographic Changes Mean The following table describes the typographic changes used in this book.
Shell Prompts in Command Examples The following table shows the default system prompt and superuser prompt for the C shell, Bourne shell, and Korn shell.
CHAPTER 1 Introduction 1.1 Introduction page 1-1 Sun MediaCenter Hardware page 1-2 Sun MediaCenter Software page 1-4 Video Output Interfaces page 1-8 Content Preparation and Loading page 1-10 Server Management page 1-11 Push Model page 1-11 Design Benefits page 1-12 Introduction The Sun MediaCenter server is a combination of standard server hardware and special software that is optimized for and dedicated to the storage and delivery of video streams.
■ a Content Manager (CM), which includes an RPC-based API that allows users to move content between servers or between a server and a client. ■ Web-based tools that allow you to configure a Sun MediaCenter server, monitor server operations, and transfer video content to a server. The Sun MediaCenter server delivers MPEG bit streams at a constant bit rate. The content of the streams are stored on an array of disks.
Control Content Sun MediaCenter Server Media Streams (Fast Ethernet or ATM) From tape, network-accessible file, or live source Fast/Wide or Ultra SCSI Media File System Files FIGURE 1-1 High-level Hardware Architecture Content is loaded onto the Sun MediaCenter server via the server ’s Content Manager, over a LAN or using 4- or 8-mm DAT tape.
1.3 Sun MediaCenter Software The Sun MediaCenter software has three major components, the Media File System (MFS), the Media Stream Manager (MSM), and the Content Manager (CM). (In addition to these, there are special network interface drivers, which are tightly coupled with the MFS.) The relationship of these modules is illustrated in FIGURE 1-2.
With the exception of the APIs for the MSM and CM, the workings of the server ’s software components are largely invisible to the user. This is particularly true of the MFS, access to which is exclusively throughout the MSM and CM.
Hot swappability The MFS supports the replacement of a failed disk while the server continues to deliver streams. Following disk replacement, you use a single command to restore data from the parity disk to the new disk and return the server to normal playback mode. The procedure for hot swapping a disk is described in Chapter 8, “Administering MFS Disks.” Efficient use of disk bandwidth The file system is designed to extract a significant portion of the available disk bandwidth (50-90%).
■ scheduler The scheduler sorts and schedules disk I/O, manages bit pump buffers, performs admission control, and schedules output driver activity. ■ bit pump The bit pump is responsible for allocating internal buffering and efficiently transferring data between the disk and the output drivers using the internal buffers. It is responsible for fine-grain scheduling and rate control of the output driver. The bit pump is dependent on the particular output driver used, whether it be for Fast Ethernet or ATM.
The MSM’s primary interface is the MSM Client API, described in the Sun MediaCenter Server Programmer’s Guide. The MSM supports playthrough, trick play, and other features of the Media File System. 1.3.3 Content Manager The CM provides for the loading of content onto a Sun MediaCenter server. Server requirements for content, such as Table of Contents files and index files (for trick play) are handled transparently by the CM.
1.4.1 ATM In an ATM environment, one or more Sun MediaCenter servers are directly connected to an ATM switch via ATM host adapters. Digital video streams are sent to clients using ATM virtual circuits. FIGURE 1-4 1.4.2 Sun MediaCenter Servers in ATM Environment LAN In the LAN environment, each Sun MediaCenter server is connected to one highspeed 100BaseT subnetwork via one or more Fast Ethernet host adapters. Digital video streams are sent to their destination(s) using LAN packets.
FIGURE 1-5 1.5 Sun MediaCenter Servers in LAN environment Content Preparation and Loading The Sun MediaCenter software specifies a format for content, described in Chapter 2, “Preparing and Loading Content.” Sun MediaCenter software uses the Content Manager for storing video content on the server. The Content Manager offers the following interfaces: ■ A set of RPCs that enable moving of content between local storage and a Sun MediaCenter server.
1.6 Server Management An SNMP agent is provided is provided with the Sun MediaCenter software. This agent includes the following MIB information: ■ current number of playing streams; ■ current aggregate bandwidth; ■ number of missed deadlines; ■ number and location of disk errors. The SNMP agent also supports the following traps: ■ Missed_Deadline ■ Admission_Failed ■ Disk_Failure See Appendix A for a description of and instructions for configuring the SNMP agent. 1.
delivery support output only. The MSM Client API has calls that allow you to specify an ultimate destination, but do not, for example, allow you to set any parameters on that destination, which would imply the ability of the receiver to confirm a setting. 1.8 Design Benefits The Sun MediaCenter server is more than simply a standard server with large amounts of memory and disk space.
CHAPTER 2 Preparing and Loading Content General MPEG Encoding Requirements page 2-1 MPEG Encoding Requirements for Trick Play page 2-2 Splice Points page 2-3 Content Loading page 2-5 References page 2-7 This chapter specifies what video content should consist of and how it should be formatted, as required by the Sun MediaCenter software. It also provides guidelines for content loading. This chapter does not tell you how to encode content.
2.2 ■ The timing information embedded in an MPEG file must exactly reflect the constant bit rate encoded in the file. Specifically, the time differences between any two consecutive PCR (SCR for Program Streams or MPEG-1 System Streams) time stamps must exactly reflect the time required to play out the number of bytes between the two PCRs (SCRs for Program Streams or MPEG-1 System Streams) at the bit stream’s specified bit rate. ■ The bit stream must be encoded at constant bit rate, between 1.
■ All trick files must be encoded at a bit rate that is less than or equal to the bit rate of the normal-speed bit stream. The Media Stream Manager supports the playing of trick play streams. See the chapter on the Media Stream Manager Client API in the Sun MediaCenter Server Programmer’s Guide for a discussion of how to play titles that have trick play streams. 2.
2.3.2 closed_gop The closed_gop is a one-bit flag that indicates the nature of the predictions used in the B-pictures immediately following the first coded I-frame following the group-ofpictures header. The closed_gop must be set to 1 to indicate that these B-pictures have been encoded using only backward prediction. 2.3.
2.4 Content Loading The preferred method of storing content on a Sun MediaCenter server is to use the Web-based CmTool. CmTool uses the Sun MediaCenter FTP daemon and the Content Manager (CM), part of the Sun MediaCenter software, to store content. The CM automatically extracts from MPEG content the information the server needs to successfully store and play that content. See Chapter 4 for information on using the CmTool interface.
■ The machine on which your content is stored does not have ftp client software. ■ For video file transfers from the server to a client machine, if your video file is smaller or equal to 2.1 GB, use smc_copy or ftp. If the file is larger than 2.1 GB, use smc_tar. ■ For video file transfers between Sun MediaCenter servers, use Cmtool or smc_copy.
2.5 References ISO/IEC 13818-1/2/3 Recommendation H.262: “Generic Coding of Moving Pictures and Associated Audio Information: Systems/Video/Audio” ISO/IEC 11172-1/2/3 “Coding of Moving Pictures and Associated Audio for digital storage media at up to 1.
2-8 Sun MediaCenter Server Administrator’s Guide • December 1997
CHAPTER 3 Monitoring the Server Overview page 3-1 Using the WebAdmin Tool page 3-2 Resource Utilization page 3-5 Streaming Videos page 3-6 Copy Sessions page 3-9 Disk Capacity page 3-12 Troubleshooting page 3-15 This chapter describes the Sun MediaCenter WebAdmin tool, a Web-based graphical user interface (GUI) for monitoring the Sun MediaCenter server. The tool is part of the software that is installed on the Sun MediaCenter server. 3.
3.2 Using the WebAdmin Tool You can run WebAdmin from the following: ■ Any browser that is fully compatible with Java Developer ’s Kit (JDK) version 1.1.1 or later (for example, HotJava™ 1.0 or later). ■ Java Applet Viewer available with JDK 1.1.3. The server that you want to monitor must have the Sun MediaCenter SUNWsmswa package installed; this software is available on the current release of the Sun MediaCenter server. The server must also be a Web server. 3.2.
FIGURE 3-1 Sun MediaCenter Page You may need to set security on your browser to allow the WebAdmin applet to connect to your local system. For the Sun HotJava browser, select “Allow all connects without warning” and “Allow access to all properties” in the Security Violation popup windows.
Once the applet loads, the Resource Utilization page is displayed: FIGURE 3-2 3-4 Resource Utilization Page Sun MediaCenter Server Administrator’s Guide • December 1997
3.2.2 Common Page Elements This section describes the items that appear at the top of each page in the WebAdmin tool. Each page is described in detail in later sections in this chapter. The Server Name field appears at the top left corner of each page and identifies the Sun MediaCenter server being monitored. The following icons appear at the top right of the pages: ■ The question mark displays online help for the WebAdmin tool.
Videos being copied Displays the number of content movement sessions on the server. Click on the icon or the link to display the Copy Sessions page, where you can view more information about the content movement sessions. See Section 3.5, “Copy Sessions,” on page 3-9. Disk Capacity Displays the status of the MFS disks. The graph shows the number of titles stored in the MFS and the percentage of available disk space being used.
FIGURE 3-3 Streaming Videos Page The top portion of the Streaming Videos page shows the number of streams that are being played on the server, the average rate of the streams (in bits per second), and the percentage of available bandwidth being used by the streams.
■ the title being viewed ■ speed (Fast-Forward, Slow Motion, Stopped, Playing, Reverse) Click on the stream icon to view more information about this stream. The Streaming Videos page shows detailed information about the stream that you selected in the Streams page; this is shown in FIGURE 3-4.
This page shows the following information about the stream being viewed: Stream Name and Direction Title and direction (fast-forward, playing, stopped, reverse, etc.) of the stream. Format Format of the content. Bit Rate Bit rate at which the stream is being played. Destination TCP/IP port or ATM virtual circuit. Playlist If this stream is part of a playlist, the titles in the playlist and the total time of the playlist are shown.
FIGURE 3-5 Copy Sessions Page The top of the Copy Sessions page shows the number of copy sessions that are active on the server.
Click on the session icon to view more information about this stream. The Session Information page shows detailed information about the content movement session that you selected in the Copy Sessions page.
This page displays the following information: State Creating or Opening Shared or Exclusive Reliable or Unreliable Status OK or error message from CM_API. Transfer Mode TCP or ATM Address TCP port or ATM address. Bytes Xfered The number of bytes already transferred. Bytes total The total number of bytes to be transferred. The bar at the bottom of page indicates the percentage of bytes transferred. The Abort This Session button allows you to stop the content transfer.
FIGURE 3-7 Disk Capacity Page A red, Failed Disk icon appears at the top of this page only if there is a failed disk in the MFS. The top portion of the Disk Capacity page shows the number of titles that are stored on the server, the amount of disk space used to store the titles, and the percentage of available disk space in the MFS being used by the titles.
The bottom portion of the Disk Capacity page displays the disks in groups, as specified by the RAID layout. Individual disks can be either Data or Parity type. The size and name of each disk are shown. Click on the disk name to view more information about the disk. The Disk Info page shows detailed information about the disk that you selected in the Disk Information page.
The top portion of the Disk Info page shows statistics about the usage of the disk. The bottom portion of the page shows any late events or disk errors. 3.7 Troubleshooting The Troubleshooting page allows you to monitor the following server components: MFS disks, network, console, and bit pump.
FIGURE 3-9 Troubleshooting Page The Troubleshooting page contains the following links: 3-16 ■ Media File System: disks displays the Disk Health page. See Section 3.7.1, “Disk Health,” on page 3-17. ■ Console Output displays Sun MediaCenter server console messages. See Section 3.7.2, “Console Log,” on page 3-18. ■ Bit Pump Statistics displays Sun MediaCenter server bit pump information. See Section 3.7.3, “Scheduler and Bitpump,” on page 3-20.
3.7.1 Disk Health This page shows the status of disks in the MFS.
The Disk Health page displays the disks in groups, as specified by the RAID layout. Individual disks can be either Data or Parity type. The name of each disk is shown, along with an icon that shows the status of the disk. Icons can be one of the following colors: ■ green is normal ■ red is failed or reconstructing Click on the disk name to view the Disk Info page for more information about the disk. See Section 3.7.1, “Disk Health” for information on the Disk Info page. 3.7.
: FIGURE 3-11 Console Log Page You can use the search function at the bottom of the page to search for a specific string. Enter in the string you want to find, then select the Search! button.
3.7.3 Scheduler and Bitpump The Bitpump page displays information about the Sun MediaCenter server scheduler and bitpump.
TABLE 3-1 describes the fields in this page. TABLE 3-1 Scheduler and Bitpump Statistics Active Active Streams Number of active streams Bandwidth Collective network bandwidth of all active streams, in bytes/sec. System Disk Bw Bandwidth of each disk (without considering seek overhead). Total Bw Total bandwidth of all data disks. Number of disks Number of data disks. Number of parity disks Number of parity disks. Number of zones Number of zones per disk.
TABLE 3-1 Scheduler and Bitpump Statistics (Continued) Admit Max Active Maximum number of streams allowed. This a fixed value. Max Bw Maximum bandwidth allowed for streams, in bytes/sec. Num Admitted Number of successful admissions. Num Failed Number of failed admissions. Total Delay Total delay for the admission of all streams since last reboot, in milliseconds. Average Delay Average admission delay, in milliseconds. Fail Num failed disks Total number of failed disks.
TABLE 3-1 Scheduler and Bitpump Statistics (Continued) bitPump bitPumpStreams Current number of bit pump streams. bitPumpBandwidth Bandwidth of the bit pump, in bits/sec. This is a fixed value. bitPumpMissedDeadlines Number of missed deadlines.
3-24 Sun MediaCenter Server Administrator’s Guide • December 1997
CHAPTER 4 Moving Content Overview page 4-1 Using CmTool page 4-2 Loading Content page 4-5 Table of Contents Page page 4-12 This chapter describes the Sun MediaCenter CmTool, a Web-based graphical user interface (GUI) that allows you to transfer content to a Sun MediaCenter server. The tool is part of the software that is installed on the Sun MediaCenter server. 4.
4.2 Using CmTool You can run CmTool from the following: ■ Any browser that is fully compatible with Java Developer ’s Kit (JDK) version 1.1.1 or later (for example, HotJava 1.0 or later). ■ Java Applet Viewer available with JDK 1.1.3. The server that you want to move content to must have the Sun MediaCenter SUNWsmswa package installed; this software is available on the current release of the Sun MediaCenter server. The server must also be a Web server. 4.2.
FIGURE 4-1 Sun MediaCenter Page You may need to set security on your browser to allow the CmTool applet to connect to your local system. For the Sun HotJava browser, select “Allow all connects without warning” and “Allow access to all properties” in the Security Violation popup windows. Once the applet loads, the Table of Contents page is displayed, with a list of content that is currently stored on the server.
FIGURE 4-2 4-4 Table of Contents Page Sun MediaCenter Server Administrator’s Guide • December 1997
4.2.2 Common Page Elements This section describes the items that appear at the top of each page in CmTool. Specific elements of each page are described later in this chapter. The Server Name field appears at the top left corner of each page and identifies the Sun MediaCenter server you are managing. The following icons appear at the top right of the pages: ■ The question mark displays online help for CmTool. ■ The house icon displays the “home” page, which is the Sun MediaCenter page.
FIGURE 4-3 Server Login Page You enter in a username and password for the Sun MediaCenter server in the Login Information page. Once you have successfully logged in to the server, you will not need to enter the login information again unless you quit CmTool or reload the page. Upon successful login, the Load Content page is displayed.
FIGURE 4-4 Load Content Page The disk space available on the server is shown in the upper right corner of the page. To load content onto the server, first specify the source where the content is located. If you select Local filesystem, you are prompted for the username and password to log in to the local system. If you select Remote Machine, you are prompted first for the name of the remote system, then for the username and password to log in to the remote system.
FIGURE 4-5 Content on Remote System To copy a title from a remote system or local filesystem, select the title or file from the scrolling list, then click the Copy selected file button. (You can also display information about a selected title or file with the View button.
You are prompted to specify a title for the content on the server, as shown in FIGURE 4-6. You can enter a name that is different from the source or use the same title. Remember that you cannot use spaces in titles. Click the Copy button (or select the Cancel button to cancel the copy operation).
You are prompted to confirm the copy operation, as shown in FIGURE 4-7. Click the smc_copy button (or select the Cancel button to cancel the copy operation).
The Session Information page, shown in FIGURE 4-8, shows the status of the content transfer. FIGURE 4-8 Session Information A message appears when the content has been successfully copied to the server. The content is now available for viewing on the Sun MediaCenter server.
4.4 Table of Contents Page This section describes the View and Selected menu options on the Table of Contents page.
4.4.1 View Menu The View menu provides options that affect the display of titles in the Table of Contents page. The following options are available: ■ Display allows you to select the attributes that you want displayed for the titles. For example, in addition to title name, you can specify that format and playtime be displayed. By default, only the title names are displayed in the Table of Contents page.
FIGURE 4-11 Sort Dialog Box To sort by one or more attributes, click on the attribute in the Available Attributes list and then click on the Add >> button. To remove an attribute from the sort list, click on the attribute name in the Sort Order list and then click on the << Remove button. Select Ascending or Descending. Click the OK button to display the specified attributes in the Table of Contents page.
4.4.2 Selected Menu The Selected menu allows you to view more information about a selected title, and to rename, delete, or play the title. Select a title in the Table of Contents page, then select the More Info option from the Selected menu. The Title Information page appears, as shown below: FIGURE 4-13 Title Information Page This page contains all available attribute information for the selected title.
4-16 Sun MediaCenter Server Administrator’s Guide • December 1997
CHAPTER 5 Sun MediaCenter Server Utilities Setting a Title Access Control List page 5-1 The smc_copy Utility page 5-4 The smc_tar Utility page 5-8 The smc_ls Utility page 5-17 The smc_rm Utility page 5-21 This chapter describes the utilities shipped with the Sun MediaCenter software. Sun MediaCenter software offers a variety of means to transfer video files. See Section 2.4 “Content Loading” on page 2-5 for a discussion of the alternatives.
When you create a new title on a Sun MediaCenter server by, for example, using smc_copy to copy a video file from one server to another, you (the copier) have read, write, and admin permissions for that title. Depending on the settings of the server ACL, other users can list your title (smc_ls) and get certain statistics on the title. However, a user besides you cannot copy your title, delete it, or append to it. To extend access for a title that you own, use the smc_settacl command.
For the -d (delete) option, stands for a comma-separated list of items of the form: u[ser]: ...where is a Solaris login name. The -s, -m, and -d options accept an asterisk in the field, so that you can specify ACL changes for all users on a server. You must use a backslash (\) with an asterisk, to prevent the shell from expanding the asterisk to mean the files in the local directory.
5.2 The smc_copy Utility The smc_copy utility copies content, specified by a title name or a local filesystem name, between a local filesystem and a Sun MediaCenter server or between two Sun MediaCenter servers. Examples of a local filesystem are the Unix filesystem (UFS) and NFS™. smc_copy offers a convenient means to load content onto a Sun MediaCenter server and to backup content from the server to a local filesystem.
filename The name of a file in the form specified by a local filesystem, such as UFS or NFS. The filename might specify an MPEG file or, for a content package, a tar file. hostname:filename The IP hostname of a machine on which filename is stored, plus the filename. You must supply an argument for source. Unless you use the -m option (for tar file input), you must also supply an argument for destination.
-t type Indicates the type of the file, either data or index. A data file is an MPEG file. An index file is a file containing splice points for switching back and forth among trick play streams. When copying a title to or from a Sun MediaCenter server, you must have appropriate permissions in the ACL portion of the copied title. (See Section 5.1 “Setting a Title Access Control List” on page 5-1 for an explanation of title ACLs.
The following command performs the same function as the preceding, except the -t and -s options are made explicit: host1% smc_copy -i -t data -s 1000 -r 1568700 heidi.mpg server1:Heidi The following command copies the title heidi from Sun MediaCenter server server1 to a Solaris machine host1: server1% smc_copy -o heidi /net/host1/export/mpeg_files/heidi.tar The preceding command copies all files associated with the title heidi.
5.3 The smc_tar Utility If you cannot use ftp to load content, as explained in Section 2.4 “Content Loading” on page 2-5, you can use smc_tar. The smc_tar command extracts a content package from a tar archival device or tar file. smc_tar parses the TOC file in the content package and stores the data and index files associated with the title, as well as the TOC file itself, into the correct locations on the Sun MediaCenter server.
the last argument in the command line if the b option is after the f option. immediately follows the option list if the b option precedes the f option. w Prompts you before overwriting already-existing content. The f argument, which precedes a source tar file or device, is required for all smc_tar commands. When writing to a tar file or device (c option), you are moving data from an MFS to a tar device.
Content Package (tar format) Input to the Media Stream Manager TOC file smc_tar --verifies TOC format --extracts index files --extracts MPEG files index files mfs_create FIGURE 5-1 MFS files (MPEG) Loading Content with smc_tar After loading content with smc_tar, you can pass a TOC file (title name) as an argument to MSM Client API functions (described in the Sun MediaCenter Server Programmer’s Guide), to play the title described by that TOC file.
Using smc_tar, you can copy files that were loaded onto the server by means other than smc_tar, such as with smc_copy or ftp. Sun MediaCenter Title tar Device smc_tar MFS or File Optional Sun MediaCenter Title MFS FIGURE 5-2 Copying a Title from a Sun MediaCenter Server As you can infer from the figure, smc_tar provides a convenient means to backup titles on a Sun MediaCenter server.
5.3.4 Remote Copying and Extraction You can run smc_tar from a Sun MediaCenter server or from a remote host that has a network connection to a Sun MediaCenter server. The syntax for the c option is: smc_tar cf : For the c option, you must have only one argument of the form <server>:<title>. <server> can be a local or remote Sun MediaCenter server and <title> can be the name of a specific title, with or without the .TOC extension.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-85.html>PAGE 85</a></h6><p>The preceding command differs from the one before it in two respects, indicated by the w and b options. The w option means that you are prompted before files of the same name are overwritten. The b option, in combination with the value of 40, specifies that smc_tar uses a block size of 40 rather than the default of 20.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-86.html>PAGE 86</a></h6><p>A useful technique for situations in which your MPEG file resides on CD-ROM is to create a symbolic link from the directory where your TOC file resides to the file on CD-ROM. You then use tar with the h option, which causes tar to follow symbolic links. The following are example commands: server# ln -s /cdrom/cdrom0/<your content>.mpg <your content>.mpg server# tar cfh - <your title>.TOC <your content>.mpg | smc_tar xf - An alternative to the preceding commands is: server# tar cf - <your title>.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-87.html>PAGE 87</a></h6><p>Examples of scripts that use smc_tar are shown below. The following script archives content to the locally-mounted /dev/rmt/0 device and writes the content titles to the UFS file SMCBackup.current-date in the current directory. #!/bin/sh # smc_backup: Script to archive multiple SMC titles to tape # # To use, type # smc_backup [title]+ # PATH="/sbin:/usr/sbin:/bin:/usr/bin:/usr/ccs/bin:/opt/SUNWsms/bin" date=`date +%Y.%m.%d` outputDevice="/dev/rmt/0" contentsFile="SMCBackup.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-88.html>PAGE 88</a></h6><p>The following script locates a specified content title from a previously-created SMCBackup.date file. It then prompts you to load the appropriate tape to restore the archived title from the locally-mounted /dev/rmt/0 device. #!/bin/ksh # smc_restore: Script to restore an SMC backup usage() { echo "usage: smc_restore [-c ContentsFile] [title]+" >&2 } printNumber() { case $1 in *1)echo "$1st";; *2)echo "$1nd";; *3)echo "$1rd";; *) echo "$1th";; esac } date=`date +%Y.%m.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-89.html>PAGE 89</a></h6><p>echo "Restore it? (yes or no) \c" read response < /dev/tty if [ $response = "yes" ]; then found=true echo "Load tape dated $date and hit return when done \c" read response < /dev/tty if mt -f ${inputDevice} rew && mt -f ${inputDevice}n fsf $((fileNumber 1)); then if smc_tar xf $inputDevice $t; then echo "$t restored" fi fi fi done if [ "$found" = "false" ]; then echo "The title you requested was not found on any backup tape" fi done 5.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-90.html>PAGE 90</a></h6><p>The other smc_ls options affect the display and sort of the title output. As a general rule, lowercase options specify the type of sort to be performed, while uppercase options specify the display of an attribute. By default, sort options turn on the corresponding display option. Options are invoked from left to right to provide the effect of a major/minor key sort. If no sort option is specified, titles are displayed using the collating rules of the native language.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-91.html>PAGE 91</a></h6><p>-r Reverse the order of the sort. This option applies across all other sort options. -S Display the play speeds for the title. For titles with multiple speeds, each available speed is listed, separated by a comma (,). Streams that have a corresponding index file are indicated by a trailing asterisk (*). This option turns off the B and D display options. -t Sort the output in the order of last modification time, with the most recentlymodified first. This option implies the -T option.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-92.html>PAGE 92</a></h6><p>The following example displays a “long listing” of the content on the local Sun MediaCenter server, sorted in order of most-recently-modified time: client% smc_ls -lt AustinPowers Jul 17 SMC_Trick Jul 17 1000,4000,8000,-4000,-8000 roc13 May 25 SMCnews_1.24Mbs May 25 SMCnews_0.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-93.html>PAGE 93</a></h6><p>The following example displays a long list of the current titles on the local server, with the output reverse-sorted by modification time (most-recently modified time last) and bitrate information displayed (instead of play speed): smc_ls -lrtB pc_test1.5 PC_TEST_1.4 Scott_and_Anne rabbit ISGs_Mariah Gisele_Kerozene v2kill YOUAINT14 smc5 ST_HISTORY Max_Headroom mnymkr2 dvd_ad Eastwood 5.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-94.html>PAGE 94</a></h6><p>5-22 Sun MediaCenter Server Administrator’s Guide • December 1997</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-95.html>PAGE 95</a></h6><p>CHAPTER 6 Sun MediaCenter Server FTP Daemon Keyword for Video-File Functions page 6-3 Video-File Attributes page 6-4 Video-File Commands page 6-5 Loading Content with ftp page 6-14 This chapter describes the Sun MediaCenter server FTP daemon. This daemon allows any ftp user—on any operating system/hardware platform—to access video files on a Sun MediaCenter server. In addition to this video server support, the daemon supports the “traditional” FTP functions described in the ftp (1) man page.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-96.html>PAGE 96</a></h6><p>PC or Workstation Sun MediaCenter Server FTP Protocol Standard FTP Functions Standard FTP Client Sun MediaCenter FTP Daemon Software FTP Functions for Video Files Unix File System Local File System FIGURE 6-1 6-2 Sun MediaCenter FTP Functions Sun MediaCenter Server Administrator’s Guide • December 1997 Media File System (Video Files)</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-97.html>PAGE 97</a></h6><p>6.1 Keyword for Video-File Functions The keyword smc: in an ftp command invokes a video-file function. So, for example, to obtain a directory listing of the video files on a Sun MediaCenter server, you enter the following command: ftp> dir smc: Title Usage Bambi cm,msm java_class FREE haircut msm, list continues to conclusion...</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-98.html>PAGE 98</a></h6><p>6.2 Video-File Attributes A piece of video content is stored as a title on a Sun MediaCenter server. The ftp video-file commands report or perform operations on titles. A title is identified by the following attributes: ■ name of the title, which usually corresponds to the name of the movie or video clip; for example, Bambi for the move “Bambi”. There is no default value for the name attribute. ■ speed associated with the file.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-99.html>PAGE 99</a></h6><p>The attribute values of the title named Bambi indicate a normal-play, forwarddirection, MPEG file that was encoded 3 Mb/sec. in MPEG-2 Program Stream format. All video-file commands require a value for the title attribute. (The value can be, with some commands, a wildcard.) Certain commands have requirements beyond this. These requirements are spelled out in the following section.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-100.html>PAGE 100</a></h6><p>All ftp commands except rename, when used with the Sun MediaCenter FTP daemon, accept the asterisk (*) as a wildcard character. When using the Solaris FTP client, you must use a backslash to escape the asterisk. Otherwise, the shell interprets the asterisk to mean all files in the current working directory. Other FTP clients, such as one you might use on a Wintel PC, might not have this requirement.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-101.html>PAGE 101</a></h6><p>6.3.1 Listing Files dir The dir command lists the names of the data and index files associated with the titles on a Sun MediaCenter server. An example of its use: ftp> dir smc: Title Usage Bambi FREE batman cm,msm java_class cm, haircut msm, list continues to conclusion...</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-102.html>PAGE 102</a></h6><p>ls Like the dir command, the ls command lists the names of the data and index files associated with the titles on a Sun MediaCenter server.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-103.html>PAGE 103</a></h6><p>Examples of mls use: ftp> mls smc:title=batman smc:title=seahunt 200 PORT command successful. 150 ASCII data connection for smc:title=batman (129.144.90.32,56451). smc:title=batman,format=MPEGTS,speed=10000,type=index smc:title=batman,format=MPEGTS,speed=10000,type=date,rate=3000000 226 ASCII Transfer complete. remote: smc:title=batman 242 bytes received in 0.045 seconds (5.2 Kbytes/s) 200 PORT command successful. 150 ASCII data connection for smc:title=seahunt (129.144.90.32,56585).</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-104.html>PAGE 104</a></h6><p>With regard to video-file attributes, when you get or mget files, (the Media File System [MFS]-to-local file system direction) those files are stored in a local file system with as many or few attributes as you specify. Conversely, when you put or mput files (the local file system-to-MFS direction), those files are stored in the MFS with the attributes that were recorded in the local file system from which the files were copied.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-105.html>PAGE 105</a></h6><p>get The get command allows you to copy a video file from a Sun MediaCenter server to a local file system. An example of its use: ftp> bin ftp> get smc:title=batman,format=MPEGTS,speed=1000,type=data,\ rate=3000000 /home/backup/batman.data 200 PORT command successful. 150 Binary data connection for smc:title=batman,speed=1000,type=data, rate=3000000 (129.144.90.32,56133) (0 bytes). 226 Binary Transfer complete. local: /home/backup/batman.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-106.html>PAGE 106</a></h6><p>6.3.2.2 Moving Multiple Titles The mget and mput commands are intended for the backup and restore of titles between the MFS and a local filesystem. You can use mput only with files that you have previously backed up with mget. For example, if you periodically use the command: ftp> bin ftp> lcd /home/backup/ ftp> mget smc:title=\* ...to back up your titles, you can use: ftp> bin ftp> lcd /home/backup/ ftp> mput \* ...to restore the backed-up titles.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-107.html>PAGE 107</a></h6><p>mput The mput command copies files from a local file system to a Sun MediaCenter server. mput allows you to copy a single video title or all of the titles that have been copied to a given directory in a local file system using the mget command. mput supports the use of the asterisk (*) wildcard character to specify all of the files in a directory. An example of its use: ftp> bin ftp> lcd /home/backup/ ftp> mput \* 200 PORT command successful.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-108.html>PAGE 108</a></h6><p>6.3.4 Deleting Files delete The delete (or del) command allows you to delete a video file from a Sun MediaCenter server. You specify only a title name for this command. An example of its use: ftp> del smc:title=Batman 250 DELE command successful. 200 PORT command successful. ftp> 6.4 Loading Content with ftp Use of ftp with the Sun MediaCenter FTP daemon is the preferred method to load content onto the server.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-109.html>PAGE 109</a></h6><p>As an example, consider that you encode the title “Batman” at 3 Mbits/sec., in MPEG Transport Stream format. You have three MPEG files, one for normal speed, one for 21 times normal speed, forward direction, and one for 21 times normal speed, reverse direction. On the encoding machine, you use the following sequence of commands to load the title on to the server: encoding_machine% ftp smc_server_one Connected to smc_server_one. 220 smc_server_one FTP server (UNIX(r) System V Release 4.0) ready.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-110.html>PAGE 110</a></h6><p>6-16 Sun MediaCenter Server Administrator’s Guide • December 1997</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-111.html>PAGE 111</a></h6><p>CHAPTER 7 Server Output Data Format Introduction page 7-1 ATM Encapsulation page 7-2 ATM Addressing page 7-4 Fast Ethernet Encapsulation page 7-5 Fast Ethernet Addressing page 7-7 Specifying Encapsulation page 7-8 Differences Among Different Types of Links page 7-9 References page 7-9 This chapter describes the format of the data that is output from the Sun MediaCenter Server. It also tells you how to specify output data encapsulation for the Media Stream Manager Client API.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-112.html>PAGE 112</a></h6><p>controlled by the Content Manager (CM). Utilities that use the CM are described in Chapter 5 and Chapter 6. The CM server and client APIs are described in the Sun MediaCenter Server Programmer’s Guide. FIGURE 7-1 illustrates the separation of data and control flows with respect to the Sun MediaCenter server.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-113.html>PAGE 113</a></h6><p>7.2.2 MPEG-2 Program Stream Packet Encapsulation The MPEG-2 Program Stream can have any packet size. The server delivers AAL-5 packets with an MPEG data size corresponding to twenty MPEG Transport packets or 3760 bytes for the Program Stream encapsulation. This encapsulation uses a larger ATM packet size than is used for MPEG-2 Transport Streams. Note – Sun is not committed to the packet encapsulation for the MPEG-2 program stream.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-114.html>PAGE 114</a></h6><p>7.3 ATM Addressing You specify the destination address with the MSMC API’s msmSetConnect() function. You fill in an instance of the MsmConnect structure before calling msmSetConnect(). This structure contains an destTiAddr field, which holds a string. This field determines the destination address to which the server delivers data. 7.3.1 MPEG over AAL5 When configured for MPEG over AAL5, the server delivers video data to a specified ATM virtual circuit over a specified server ATM port.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-115.html>PAGE 115</a></h6><p>The address is a string of the following format: host=<ip hostname>,udpport=<udpport num> The components of this address are as follows: ■ The <ip hostname> is the destination client’s IP hostname. ■ The <udpport num> is the destination UDP port number on which the client host is awaiting data. For example, the address of host=cordelia,udpport=40000 specifies that data be delivered to host cordelia at UDP port 40000.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-116.html>PAGE 116</a></h6><p>IP Port Control traffic Sun MediaCenter Server Fast Ethernet Ports video data Ethernet Switch 10/100BaseT ... Clients FIGURE 7-2 7.4.1 LAN/Enterprise Scenario MPEG-2 Transport Stream Packet Encapsulation As of the date of this publication, there is no standard for transmitting MPEG over Ethernet.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-117.html>PAGE 117</a></h6><p>7.4.2 MPEG-2 Program Stream Packet Encapsulation The MPEG-2 Program Stream is not defined to have any fixed packet size by the MPEG-2 standard. The server delivers UDP packets with payload containing MPEG data of size corresponding to seven MPEG-2 transport packets or 1316 bytes for the program stream encapsulation. This encapsulation uses the same Ethernet packet size as is used for the MPEG-2 Transport Stream. 7.4.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-118.html>PAGE 118</a></h6><p>The components of this address are as follows: ■ The <ip hostname> is the destination client’s IP hostname. ■ The <udpport num> is the destination UDP port number on which the client host is awaiting data. For example, the address of host=cordelia,udpport=40000 specifies that data be delivered to host cordelia at UDP port 40000.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-119.html>PAGE 119</a></h6><p>7.7 Differences Among Different Types of Links The following are distinctions among the ways a Sun MediaCenter server handles video output over Fast Ethernet or ATM links: 7.8 ■ As described in this chapter, MPEG streams are encapsulated in UDP/IP packets and then in Ethernet packets, when sent over Fast Ethernet links. Over ATM, MPEG streams can be encapsulated in AAL5 ATM packets or in IP packets for subsequent encapsulation in AAL5 packets.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-120.html>PAGE 120</a></h6><p>7-10 Sun MediaCenter Server Administrator’s Guide • December 1997</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-121.html>PAGE 121</a></h6><p>CHAPTER 8 Administering MFS Disks Monitoring MFS Disks page 8-1 MFS Utilities page 8-2 Replacing a Failed Disk page 8-10 This chapter tells how to monitor MFS disks and how to detect and respond to disk failures. 8.1 Monitoring MFS Disks The easiest way to monitor the Media File System (MFS) disks is to use the Sun MediaCenter WebAdmin tool.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-122.html>PAGE 122</a></h6><p>You can also use the Solstice Domain Manager (or other SNMP-conformant program) to monitor the Media File System (MFS) disks. The SNMP agent for the Sun MediaCenter server, sms-vod, has an SNMP trap, Disk_Failure, that allows for automatic notification when a disk failure occurs. This trap is particularly significant if a disk failure is followed by a reboot of the server.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-123.html>PAGE 123</a></h6><p>mfs df usage is as follows: mfs df [-kv] The mfs df command has the following options: -k Space is reported in kilobytes, rather than 64K blocks -v An option that produces “verbose” output. The two options can be used together, to obtain verbose output with space reported in kilobytes.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-124.html>PAGE 124</a></h6><p>Note in the verbose mfs df output, above, that the MFS block size (64k) is reported, as well as the disk type, which can be either data or parity. Output with the -k option is the same except that the Total, Used, and Avail data is displayed in kilobytes rather than 64K blocks. The fact that space consumed is the about the same on all disks is characteristic of the MFS, in which data is striped across all disks. 8.2.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-125.html>PAGE 125</a></h6><p>MPEGPS MPEG Program Stream packet format. MPEG1SYS MPEG-1 System Stream packet format. MPEGTCE MPEG Thomson Consumer Electronics format. The packetization of this encapsulation consists of an arbitrary number 130-byte packets. The mfs diskusg utility is useful in conjunction with mfs df. You can compare the output of mfs diskusg, the amount of space a file would consume, with the output of mfs df, which tells you the space available.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-126.html>PAGE 126</a></h6><p>mfs repair usage is as follows: mfs repair [-cs] [-Fpr] [-d /dev/rdsk/device] [-ovy] The arguments to mfs repair are described below: -c Perform consistency checking, including reclaiming unused blocks. -s Display the status of a failed drive (if any). -F Force a failure of a specified disk. -p Initiate phase-out of parity mode. (Return to normal operation from parity mode.) -r Reconstruct data on newly replaced disk drive.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-127.html>PAGE 127</a></h6><p>To find out which MFS disk has failed, you enter: server# mfs repair -s drive /dev/rdsk/c1t3d0s2 (dev 0x80009a) is FAILED mfs repair reports that the disk at c1t3d0s2 has failed. Chapter 3 of the Sun MediaCenter UltraSPARC Hardware Manual tells you that c1t3d0s2 corresponds to the third data disk in the first Multipack enclosure connected to SCSI port 1 on the server. With the server still running, you remove the defective disk and replace it with a good disk.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-128.html>PAGE 128</a></h6><p>Following this command, use the mfs repair commands described above to replace the failed disk. Use of mfs repair is appropriate only for single disk failures. Two, overlapping disk failures cause the server to panic. If you experience the failure of more than one disk, you must use smc_copy or ftp, in conjunction with the Sun MediaCenter FTP daemon, to restore your original data from backup storage.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-129.html>PAGE 129</a></h6><p>Following invocation without the -f option, mkmfs prompts you for the information required to build an MFS.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-130.html>PAGE 130</a></h6><p>The meta-file for the MFS is stored in /var/opt/SUNWsms/MFS. Use the Solaris format command to obtain the SCSI target numbers used as input for mkmfs. The preceding example assumes you use slice 2 (s2) to stand for the entire disk. Slice 2 is one of the default slice assignments in effect when you install Solaris. 8.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-131.html>PAGE 131</a></h6><p>In the output above, make note of the SCSI disk address (similar to the number c1t4d0s2). Chapter 3 of the Sun MediaCenter UltraSPARC Hardware Manual has instructions for mapping SCSI disk addresses to physical disks. 2. Open the appropriate Multipack enclosure, locate the failed disk, and remove and replace it. Documentation for your disk subsystem tells you how to replace a disk. There is no need to halt the server or reduce its load while replacing the failed disk.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-132.html>PAGE 132</a></h6><p>The procedure to replace and restore a parity disk is the same as for a data disk. A parity disk failure would be discovered while loading content. At the point of disk failure, the loading operation ceases. As with a data disk, you use the -r option to mfs repair to restore the parity disk. Note – The status of a disk as failed does not persist across a reboot.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-133.html>PAGE 133</a></h6><p>CHAPTER 9 Access Control Lists You restrict Sun MediaCenter server operations to specific users by creating access control lists (ACLs). You can create ACLs for the following: ■ Server: Allows programs to list players, titles, or states and/or create or delete players. ■ Players: Allows programs to obtain play information, control play, and/or set player access on a server.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-134.html>PAGE 134</a></h6><p>9.2 Permissions All files used for ACLs support the following syntax: <user>:<permission> For all ACL files, standard Solaris lookup mechanisms are used for user name lookup. In support of unknown UIDs, all files support: nobody:<permission> Each type of ACL file allows different permissions; the permissions are described in the following sections in this chapter. For all ACLs, permissions are independent of one another.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-135.html>PAGE 135</a></h6><p>...with the result that all users have read permission. For example, with only read permission for a Sun MediaCenter server, a user can look up titles on the server, but cannot play a stream. Each instance of the ServerAcl file must contain a line that indicates the version number of the file; this line must be the first uncommented line in the file.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-136.html>PAGE 136</a></h6><p>9.5 Title ACL Each content title has an ACL which is accessible either programmatically through the cmGetAcl() function or by the smc_gettacl utility. To create or modify permissions, use the cmSetAcl() function or the smc_settacl command. TABLE 9-3 shows the permissions that you can specify: TABLE 9-3 Permission Access Level r Title ACL Permissions User can run... Program can call... read smc_ls to obtain listing of title. smc_copy, smc_tar, and ftp to copy existing content (as in a backup).</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-137.html>PAGE 137</a></h6><p>A session ACL has a single type of permission. TABLE 9-4 Session ACL Permissions Permission Access Level User can run... Program can call... a admin CmAdmin to abort a session cmSetSessionAcl() cmClientClose() cmRpcSetTimeout() cmOpen() cmCreate() cmSessionAbort() cmSessionClose() A programmer who invokes cmClientCreate() to create a session obtains admin access to that session.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-138.html>PAGE 138</a></h6><p>9-6 Sun MediaCenter Server Administrator’s Guide • December 1997</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-139.html>PAGE 139</a></h6><p>CHAPTER 10 Troubleshooting This chapter describes tools you can use to track down problems you might have with your Sun MediaCenter server. The most useful tool you can have for modeling your server ’s behavior and for detection of problems is SunNet Manager or another SNMP-conformant management platform that allows you to read values collected by the Sun MediaCenter server’s SNMP agent in its Management Information Base (MIB). See Appendix A for a description of this MIB.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-140.html>PAGE 140</a></h6><p>Underperforming stream output Possible cause is network congestion. Use a network analyzer or your switch vendor’s diagnostics to analyze network performance. Note that your server is intended only for the storage and delivery of multimedia streams. Any processes not associated with this purpose have the potential to disrupt server output. No video displays on client Possible causes: Disk cables and/or network links not connected. If using ATM, ATM switch not configured correctly.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-141.html>PAGE 141</a></h6><p>Poor video quality Possible causes: Content is stored at a bit rate different from that at which it was encoded. Content might be poorly encoded. The destination client might not be able to keep up with the video stream. Check the bit rate of the content. The bit rate should be roughly filesize * 8/playtime, where playtime is the duration of a title, in seconds. Try another title, preferably one encoded at a lower bit rate. Try a different destination client.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-142.html>PAGE 142</a></h6><p>Unable to create title on the MFS. Likely cause: A filled MFS or a disk failure. In this situation, the Sun MediaCenter software removes all files associated with the title. Use mfs df, documented in the Sun MediaCenter Server Service Manual, to determine free space in the MFS. Use mfs repair -s, documented in the same Service Manual, to determine whether a disk has failed. If you use SunNet Manager, see if you have received the Disk_Failure trap.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-143.html>PAGE 143</a></h6><p>WARNING: stream id 107 (ba@426,3,80@) xmit error: Q size 33 Cause: Low-level software has detected a transmission error. Action required: None. Most often, higher level software can recover from such an error. However, if you receive such messages continually or if such messages are accompanied by degraded video output, contact your Sun service representative. NOTICE: ba0: qsize OK Cause: This is a Sun MediaCenter driver diagnostic message. Action required: None.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-144.html>PAGE 144</a></h6><p>10-6 Sun MediaCenter Server Administrator’s Guide • December 1997</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-145.html>PAGE 145</a></h6><p>APPENDIX A Setting up the SNMP Agent The Sun MediaCenter Server MIB page A-2 Enabling Management by Solstice Domain Manager page A-6 Enabling Trap Handling page A-9 The Sun MediaCenter software is shipped with its own SNMP agent, which is part of the SUNWsmsnm package. This agent is based on the SNMP agent shipped with the Solstice Domain Manager (SDM); the agent has been extended to support the Sun MediaCenter server.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-146.html>PAGE 146</a></h6><p>Note – A caveat on the use of the SNMP agent shipped with the Sun MediaCenter server: If you use SNMP to manage the Sun MediaCenter software, you cannot also run an SNMP agent to manage other components of your system (for example, the ATM interface). The SNMP agent reserves port 161, making that port unavailable to other SNMP agents. The SNMP agent is implemented in a daemon, snmpd, and is installed on the Sun MediaCenter server in the course of running pkgadd to add the SUNWsmsnm package.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-147.html>PAGE 147</a></h6><p>TABLE A-1 Sun MediaCenter Server MIB Definitions Group or Table Attribute Name Description admTotalDelay Total delay for the admission of all streams since last reboot, in milliseconds. admAverageDelay Average admission delay, in milliseconds. bitPump bitPumpStreams Current number of bit pump streams. bitPumpBandwidth Bandwidth of the bit pump, in bits/sec. This is a fixed value. bitPumpMissedDeadlines Number of missed deadlines.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-148.html>PAGE 148</a></h6><p>TABLE A-1 Sun MediaCenter Server MIB Definitions Group or Table Attribute Name Description diskLateTime Time at which the late event was detected, in microseconds. diskLateDuration Duration of lateness, in milliseconds. diskTable diskDeviceId Name of the disk. diskNumIOoperations Number of I/O operations for a disk. diskNumLate Number of times a disk was late. diskTotalLateness Total time late, in seconds. diskNumErrors Total number of errors for a disk. diskType “data” or “parity”.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-149.html>PAGE 149</a></h6><p>TABLE A-1 Sun MediaCenter Server MIB Definitions Group or Table Attribute Name Description sysZonesPerDisk Number of zones per disk. A zone is a region of a disk used for the storage of streams sysTimePeriodLength A fixed interval used by VOD scheduler for MFS operations. sysNumberOfBuffers Number of configured buffers. sysBufferSize Size of each buffer. sysBufferMax Maximum number of buffers used at one time. sysBufferUnavail Number of times buffers not available.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-150.html>PAGE 150</a></h6><p>The remaining attributes, those not in TABLE A-2, are counters, sizes, identifiers, and times (both durations and instants) that change according to conditions on the server. These attributes can be categorized as follows: ■ Streams and stream admission The active and admission groups. ■ Bit pump The bitPump group and the bitPumpStreamTable. ■ Disk I/O The diskError group, including the diskErrorTable; the diskLate group, including the diskLateTable; the diskTable; the failure group; the system group.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-151.html>PAGE 151</a></h6><p>3. Edit $SNMHOME/struct/elements.schema, to add lines for the Sun MediaCenter server. Use the lines for the SPARCcenter 1000 (sc1000) as a basis for the new lines for the Sun MediaCenter server (sms1000). For example: record component.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-152.html>PAGE 152</a></h6><p>6. Run: build_oid (with no arguments). This program maps names in Sun MediaCenter server MIB to new OIDs. 7. (Optional) Copy your $SNMHOME/discover.conf file to /etc/opt/SUNWconn/ snm. In the MAPPINGS section of this copy, add the line: media component.sms1000 In addition to modifying discover.conf, set the environment variable SNMDISCOVERMAP to the directory where discover.conf is located.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-153.html>PAGE 153</a></h6><p>As an example of a the SNMP agent’s capability, the following is a Quick Dump report for the bitPump attribute on a machine redoubt: Wed May 24 15:12:15 1995 [ redoubt ] : Quick Dump: sms-vod.bitPump bitPumpStreams=2 bitPumpBandwidth=8003840 bitPumpTimePeriod=5405:07:40.72 bitPumpMissedDeadlines=0 A.3 Enabling Trap Handling In addition to the six standard SNMP traps, the Sun MediaCenter server ’s SNMP agent supports three enterprise-specific traps, Admission_Failed, Missed_Deadline, and Disk_Failure.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-154.html>PAGE 154</a></h6><p>2 Missed_Deadline The Sun MediaCenter software ensures delivery of media streams at the same rate at which they were recorded. The bit pump’s missing of a deadline indicates that the machine was, at least momentarily, unable to keep up with the rate of a title. This indicates a resource conflict on the server. 3 Disk_Failure The disk subsystem sustained a failure. The failure can occur at when you are attempting to load content on the Sun MediaCenter server.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-155.html>PAGE 155</a></h6><p>APPENDIX B Creating a Content Package Content Package page B-2 The TOC File page B-3 Simplest Case TOC File page B-8 TOC File for Large Files page B-9 Index File Requirements page B-10 Tape Storage Format page B-12 Example page B-14 References page B-18 This appendix describes a content package, which is one way that content can be prepared for storage on a Sun MediaCenter server.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-156.html>PAGE 156</a></h6><p>B.1 Content Package A content package is a collection of separate MPEG streams that represent the content of a title (including audio and video) at various playback speeds. There are two types of files that together describe each of the (potentially) multiple bit streams that make up a content package: ■ the data file containing the MPEG-encoded data; ■ the index file that contains information on how a specific data file is related to the rest of the content.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-157.html>PAGE 157</a></h6><p>Content Package TOC File <asn.1 description of mpeg stream 1> <asn.1 description of mpeg stream 2> <asn.1 description of mpeg stream n> MPEG stream 1 Index File MPEG stream 2 Data File Index File FIGURE B-1 Structure of a Content Package MPEG stream N Data File Index File Data File Note – If your content consists of a single bit stream, you do not need an index file. You content package will consist of only a Table of Contents file and the single bit stream. B.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-158.html>PAGE 158</a></h6><p>A TOC file is described with the following structures: content ContentObjects ContentObjects ::= SEQUENCE { title GraphicString, version GraphicString, format GraphicsString, description GraphicStringOPTIONAL, bitstreams BitStreamObjects } BitStreamObjects ::= SEQUENCE { description GraphicStringOPTIONAL, speed INTEGER, bitrate INTEGER, indexfile GraphicString, indexsize INTEGER, datafile DataFileObjects } DataFileObjects ::= SEQUENCE { segment INTEGER, filepath GraphicString, filesize INTEGER } Some rules</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-159.html>PAGE 159</a></h6><p>B.2.1 ContentObjects The structure contains the overall information for the content package. B.2.1.1 title The title property is a string that specifies the name of the content.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-160.html>PAGE 160</a></h6><p>MPEGTCE DSS transport format wherein the server transports data in units of 130-byte packets. MPEGPS MPEG-2 program stream encapsulation wherein the server transports data in 4byte aligned packet sizes of arbitrary length. MPEG1SYS MPEG-1 system stream encapsulation wherein the server transports data in 4-byte aligned packet sizes of arbitrary length. B.2.1.4 description The description property is an optional string that allows you to enter a contentspecific comment. B.2.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-161.html>PAGE 161</a></h6><p>B.2.2.3 bitrate The bitrate property, expressed in bits/sec., specifies the bit rate at which the MPEG data file was encoded. This number also specifies the rate at which the file is to be played by the server to the network. B.2.2.4 indexfile The indexfile property is a string that specifies the pathname to the index file. The index file is an ASCII file that specifies how the bit stream being described is related to the bit stream at normal play speed.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-162.html>PAGE 162</a></h6><p>B.2.3.2 filepath The filepath property is a string specifying the pathname of the data file for this segment of the bit stream’s data. B.2.3.3 filesize The filesize property is an integer specifying the size of the data file for this segment of the bit stream’s data, in bytes. It is a 64-bit integer value. B.3 Simplest Case TOC File The following is an example TOC for a title with a single bit stream: content { title "Your title here", version "SUNW.00.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-163.html>PAGE 163</a></h6><p>The fields in the TOC file are described as follows: title A name of your choosing. After you have stored the title on the server, smc_ls returns the contents of this field. version For versions 1.0 and 1.1 of the Sun MediaCenter server software, this is always SUNW.00.01. format For MPEG-1 content, this is MPEG1SYS. For MPEG-2 content, enter MPEGPS (MPEG-2 Program Stream) or MPEGTS (MPEG-2 Transport Stream), depending on how you encoded your content. description A string of your choosing.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-164.html>PAGE 164</a></h6><p>The following is an example of a TOC file for a multi-part title: content { title “Perils of Technology”, version “SUNW.00.01”, format “MPEG1SYS”, description “History of technology, with Luddite slant“, bitstreams { description “Normal play bit stream“, speed 1000, bitrate 1660400, datafile { segment 1, filepath “Part1.mpg”, filesize 284512264 } { segment 2, filepath “Part2.mpg”, filesize 132004840 } { segment 3, filepath “Part3.mpg”, filesize 260172628 } } } B.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-165.html>PAGE 165</a></h6><p>Note – For video formatted as MPEG-2 Transport Streams, the CM automatically generates index files for titles that contain trick play streams, at the point when content is loaded onto the server. For other formats, you must generate your own index files. The index file consists of a sequence of splice points. Each splice point is of the following format: < normal play time > < file offset > Each entry in the index file represents a single splice point.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-166.html>PAGE 166</a></h6><p>B.5.2 ■ NPTs for a reverse-playing stream must monotonically decrease, from beginning to end of the index file. ■ NPT is a time offset into the content as one would view the content at normal speed, not the time at which the pictures are presented (PTS). File Offset The value in the file offset field specifies the byte offset into the MPEG-2 data file corresponding to the start of the splice point. It is a 64-bit integer value.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-167.html>PAGE 167</a></h6><p>Start of Tape Bambi.TOC Index File 1X play speed Index File 4X play speed Tape Content Package Index File nX play speed Data File 1X play speed Start of Data Files Data File 4X play speed Data File nX play speed FIGURE B-2 Tape Storage Format The TOC file must be positioned as the first file in the tar tape and must have a file extension of .TOC. Except for the file extension, the naming of the TOC file is arbitrary. In FIGURE B-2, the TOC file is named Bambi.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-168.html>PAGE 168</a></h6><p>The recommended block size of the tar format is 500 512-byte blocks, or 256,000 bytes. The default blocking factor for tar is 20 blocks, or 10,240 bytes. B.6.2 Tapes The Sun MediaCenter server supports both 4-mm and 8-mm cartridge tapes. B.7 Example This section provides an example of a content package—the TOC file and the index and data files for each bit stream—and its storage on a tape using the tar format.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-169.html>PAGE 169</a></h6><p>The content of the TOC file bambi.TOC is shown below. It contains attributes for every bit stream included in the content package for the movie “Bambi”. CODE EXAMPLE B-1 Example Content Package content { title “bambi”, version “SUNW.00.01”, format “MPEGTCE”, description “Aftermath of concentration camp survival“, bitstreams { description ““, speed -7000, bitrate 2559999, indexfile “bambi.n7x.index”, indexsize 46, datafile { segment 1, filepath “bambi.n7x.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-170.html>PAGE 170</a></h6><p>CODE EXAMPLE B-1 Example Content Package filesize 5710380 } } { description ““, speed 21000, bitrate 2559999, indexfile “bambi.21x.index”, indexsize 16, datafile { segment 1, filepath “bambi.21x.mpeg”, filesize 1905670 } } { description ““, speed 1000, bitrate 5380000, indexfile “bambi.1x.index”, indexsize 250, datafile { segment 1, filepath “bambi.1x.mpeg”, filesize 83554510 } } } The textual content of index files for various speeds are shown below.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-171.html>PAGE 171</a></h6><p>For a file bambi.1x (index file for normal-speed play): 0 496978 993956 1490935 1987913 2484892 0 258310 595010 935610 1268670 1605500 . . . 121262750 121759728 122256707 122753685 123250664 124244621 required NPT and file offset starting values 200+ entries omitted from example 82085770 82422600 82759430 83096130 83432960 83554510 Total NPT and bit steam size For a file bambi.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-172.html>PAGE 172</a></h6><p>For a file bambi.n21x (index file for twenty-one times normal speed, in reverse): 124244621 116479333 108714044 100948755 93183466 85418177 77652889 69887600 62122311 54357022 46591733 38826445 31061156 23295867 15530578 0 0 107510 239070 362960 498550 621400 750100 876980 1012570 1133860 1263210 1387490 1520610 1648140 1775930 1902680 In the preceding example, note that the NPT value in the first entry is the same as the NPT value in the last entries of the two forward-direction files, above.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-173.html>PAGE 173</a></h6><p>CCITT Recommendation X.209 (1988): Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1). Technically aligned with ISO 8825 and ISO 8825/AD 1.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-174.html>PAGE 174</a></h6><p>B-20 Sun MediaCenter Server Administrator’s Guide • December 1997</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-175.html>PAGE 175</a></h6><p>Glossary This glossary contains general, multimedia-related terms, as well as terms specific to the Sun MediaCenter product. Words and phrases in the latter category are indicated as such. access control list analog video A list of users and the associated operations they are allowed to perform. An access control list is a feature of the Media Stream Manager (MSM). Video based on a continuous electrical signal.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-176.html>PAGE 176</a></h6><p>luminance Media Stream Manager (MSM) An RPC-based API that provides users with a means of interacting with a media server without coming close to the details of media file storage and the scheduling and delivery of media streams. The MSM supports VCR-like operations such as play-a-title and fast-forward, and video-editing functions such as insert-a-title-in-a-playlist. The MSM is described in detail in the Sun MediaCenter Server Programmer’s Guide. MPEG Moving Picture Experts Group.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-177.html>PAGE 177</a></h6><p>Table of Contents (TOC) file trick play wall-clock time A fundamental component of a content package. A TOC file lists the set of index and data files that contain the bit streams that make up the movie contained by that content package. MSM clients play movies by specifying a TOC file for that movie. See Section B.2 “The TOC File” on page B-3 for a complete description. The capability for “VCR-like” functions of fast forward, fast reverse, and pause. Time of day.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-178.html>PAGE 178</a></h6><p>Glossary-4 Sun MediaCenter Server Administrator’s Guide • December 1997</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-179.html>PAGE 179</a></h6><p>Index A access control list, definition of, Glossary-1 access control list, title, 5-1 active streams, detecting number of, 3-21, A-2 admin permission, requirement for one user in title ACL, 5-3 Admission_Failed trap, A-9 alternatives for video file transfer, 2-5 analog video, definition of, Glossary-1 ASN.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-180.html>PAGE 180</a></h6><p>content requirements, 2-1 content requirements for trick play, 2-2 content, utility for listing, 5-20 ContentObjects, ASN.</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-181.html>PAGE 181</a></h6><p>loading content with smc_tar, 5-9 loading content, with smc_copy, 5-4 ls command, in ftp, 6-8 luminance, definition of, Glossary-2 M management database, saving in Solstice Domain Manager, A-8 Media File System creation of, 8-8 Media File System (MFS) features of, 1-5 Media File System bit pump, 1-7 Media File System output driver, 1-7 Media File System subsystems, 1-6 Media Stream Manager (MSM), definition of, Glossary-2 Media Stream Manager (MSM), use of, 5-1 Media Stream Manager, introduction to, 1-7 Me</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-182.html>PAGE 182</a></h6><p>playthrough, support in the MFS, 1-5 Program Association Table, encoding requirement, 2-2 Program Clock Reference, encoding requirement, 2-2 push model, description of, 1-11 put command, in ftp, 6-11 R RAID level supported by MFS, 1-2 random_access_indicator, setting for trick play, 2-4 rate attribute, for ftp, 6-4 recovery from single-disk failures, 1-5 references, used for content storage requirements, 2-7 remote copying and extraction of titles, 5-12 remove utility, 5-21 rename command, in ftp, 6-13 res</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-183.html>PAGE 183</a></h6><p>title access control list, 5-1 title ACL permissions, 5-2 title naming convention, B-5 title, setting access to, 5-2 titles, obtainiing list of on server, 5-17 titles, removing, 5-21 TOC file for large MPEG files, B-9 TOC file, example for simplest case, B-8 TOC file, parsing, 5-9 trick play streams, loading, 6-15 trick play, definition of, Glossary-3 troubleshooting, 10-1 type attribute, for ftp, 6-4 U underperforming stream output, 10-2 Unix filesystem, copying to/from using smc_copy, 5-5 V video file a</p></li><li><h6><a class="text-decoration-none text-link fw-bold" href=/manual/sun-microsystems/server-2-1/user-manual-english/page-184.html>PAGE 184</a></h6><p>Index-6 Sun MediaCenter Server Administrator’s Guide • December 1997</p></li></ul></nav></div></section></section></main><footer class=page-footer><div class="container flex-column py-3 py-sm-4"><div class="row mb-1 mb-sm-2 mb-md-5"><a href=/ class="brand offset-sm-0 col-sm-4 col-md-3 col-lg-2 offset-2 col-8 text-center text-md-start"><img class=logo-small src=/assets/img/brand-large.png alt=Manualshelf></a></div><div class=row><dl class="text-center text-sm-start col-sm-3"><dt class=fw-bold>Who We Are</dt><dd><a class=text-decoration-none href=/about>About Us</a></dd><dd><a class=text-decoration-none href=/company>Company</a></dd><dd><a class=text-decoration-none href=/careers>Careers</a></dd><dd><a class=text-decoration-none href=/terms>Terms & Privacy</a></dd></dl><dl class="text-center text-sm-start col-sm-3"><dt class=fw-bold>Resources</dt><dd><a class=text-decoration-none href=/brands>List of Manufacturers</a></dd><dd><a href=/ class=text-decoration-none>Support</a></dd><dd><a class=text-decoration-none href=/press>For the Press</a></dd><dd><a class=text-decoration-none href=/press#assets>Media assets</a></dd><dd><a class=text-decoration-none href=/faq>FAQ</a></dd></dl><dl class="text-center text-sm-start col-sm-3"><dt class=fw-bold>Get in touch</dt><dd><a class=text-decoration-none href=#>Blog</a></dd><dd><a class=text-decoration-none href=#>Email</a></dd><dd><a class=text-decoration-none href=/dmca>DMCA</a></dd></dl></div><div class=row><div class="text-center text-sm-start col-sm-4 pe-sm-0"><a href=https://www.facebook.com/pages/ManualShelf/1488826334681423 class="fs-5 text-center d-inline-block social rounded-2 align-middle text-decoration-none me-2"><i class="fab fa-facebook-f"></i></a><a href=https://www.twitter.com/ManualShelf class="fs-5 text-center d-inline-block social rounded-2 align-middle text-decoration-none me-2"><i class="fab fa-twitter"></i></a><a href=https://plus.google.com/+ManualShelf class="fs-5 text-center d-inline-block social rounded-2 align-middle text-decoration-none me-2"><i class="fab fa-google-plus-g"></i></a><a href=http://www.pinterest.com/ManualShelf class="fs-5 text-center d-inline-block social rounded-2 align-middle text-decoration-none"><i class="fab fa-pinterest-p"></i></a></div><div class="col col-sm-8 d-flex flex-column align-items-center flex-sm-row flex-wrap flex-sm-nowrap justify-content-center justify-content-sm-end"><div class="copy w-auto d-flex align-items-center justify-content-center justify-content-sm-end mt-2 mt-sm-0 me-2">ManualShelf © 2013-2025</div><select class="form-select form-select-sm w-auto mt-2 mt-sm-0"><option value=usa>USA</option></select><div></div></div><div id=pixel><script>
googletag.cmd.push(function() { googletag.display('pixel'); });
</script></div></footer><script src=/assets/js/jquery-3.3.1.min.js></script><script src=/assets/js/bootstrap.bundle.min.js></script><script src=/assets/js/jquery.autocomplete.min.js></script><script type=text/javascript>
$.extend({
redirectPost: function(location, args) {
var form = '';
$.each(args, function(key, value) {
form += '<input type="hidden" name="' + key + '" value="' + value + '">';
});
form = '<form id="s1" action="' + location + '" method="POST">' + form + '</form>';
$(document.body).append(form);
$("#s1").submit();
}
});
$(document).ready(function(){
$("#query").autocomplete({
minChars: 3,
groupBy: 'type',
paramName: 'q',
dataType: 'json',
serviceUrl: '/autocomplete',
noCache: true,
showNoSuggestionNotice: true,
noSuggestionNotice: 'Zarro results found',
onSelect: function (suggestion) {
$.redirectPost(suggestion.data.url, {highlight: encodeURIComponent(JSON.stringify(suggestion.data.hls))});
}
});
var toc = $('.toc-selector');
if (toc.length) {
var slideParams = { duration: 800, easing: 'linear' };
toc.click(function() {
$(this).toggleClass('open');
var section = $('.toc-content');
var isCollapsed = section.attr('data-collapsed') === 'true';
if (isCollapsed) {
section.slideDown(slideParams)
section.attr('data-collapsed', 'false')
} else {
section.slideUp(slideParams);
section.attr('data-collapsed', 'true')
}
});
}
});
var lastSmall = $(window).width() < 576;
$(window).resize(function() {
var newSmall = $(window).width() < 576;
if (lastSmall != newSmall) {
lastSmall = newSmall;
window.location.href = window.location.href;
}
});
</script></body></html>
