[Cisco FAQ] - Full filesystem

One of my DNCS filesystems is full. What is the best way to start cleaning it up?

One suggeston would be to run the following command from the mount point of the filesystem to be cleaned up:
SP Video TAC Lab SR 4.2>> du -h | sort -rk 1,1 | grep -v "K" | less
929M .
9.1M ./spectrum/SS-Tools/dbpart1
9.1M ./dncs/downloads/SAIgqam/reloc
9.1M ./dncs/downloads/SAIgqam
Then move into the larger directories and run the above command again until large files that can be deleted are found. Repeat in other large directories, as needed.
Alternatively, the command below can be run repeatedly to idnetify where the filesystem space is being used:
SP Video TAC Lab SR 4.2>> du -s * | sort -n
0 lost+found
10 jdbc
14 easftp

Similar Messages

Why doesn't Cisco add full IPv6 support to the firmware of the wrvs4400n small business router?

I own a Cisco wrvs4400n. I love this router but have been unhappy that it is not ipv6 ready. I have been disappointed that Cisco has not developed/introduced a new follow-on router, an advanced version of this router adding AC wireless support and speeds, more wireless signal strength, true dual band as well as the full ipv6 for the web additional to the intranet (as they have finally added in the latest firmware update) - to name a few. What they are offering presently is embarrassingly weak. They seem to be ceding the small business arena but no one else seems to be bringing out a good product for this market either. If they would at least provide support for IPv6 on the web, I could wait until they finally wake up and develop a good follow-on wired/wireless gigabit router.
Linksys, which they sold off for whatever reason, has been developing some impressive routers by hardware measures, but their firmware does not offer access to it to control and configure it that I would expect in a SBR, like they began in the wrvs4400n. Either I need Cisco to add that ipv6 so I can at least utilise the incipient roll-out of IPv6 from my ISP for time being or finally bring out an exciting new follow-on router with all the controls of that new architecture extending what they offered in the 4400!
If anyone has information/knowledge about either of these two options, developing another firmware update with full ipv6 or developing and introducing a follow-on router, please inform me about it. I am a 1 to 6 person operation and want to move into the present, at minimum, or, preferably, future. Thank you any one who can enlighten me about this.

Voskuil67 wrote:
I have twice requested (paid) tech support for getting BB Desktop Software for Mac to work
Sorry, I don't think I understand. You have initiated a "paid" per-incident support ticket with RIM, and paid for these services, and you are not getting a call back?
When you paid for this, you should have been issued a case number or support incident file number. If you have that, you should contact RIM immediately for resolution. If you need a phone number, try 1-877-255-2377
If the above is not your situation, could you please explain further?
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

ZFS Full Filesystem - Quick Question

Folks,
With traditional UFS filesystems, when it hits 100% a message similar to below is logged in /var/adm/messages
"NOTICE: alloc: /var: file system full"
I'm wondering if zfs has a similar "NOTICE" as we have hit some 100% filesystems in the past and zfs has not logged anything to the messages file.
Is there a way to get zfs to log if a particular dataset within a storage pool hits 100%
TIA

What is a real "volume" and how would it be different from an emulation of one?
Most uses of "volume" are as a logical construction (such as Sun Volume Manager or Veritas Volume Manager). So there's not much "real" about them.
ZFS also uses physical disks to store data that is accessed via a filesystem (or block device) interface. Like the other tools, it can store redundant information to increase availability in case of hardware failures, plus many other features.
Darren

[Cisco FAQ] - Set-top box user guide?

Is there a website where I can download a user guide for my Cisco set top?

http://www.cisco.com/web/consumer/support/prod_tv_set_tops.html

[Cisco FAQ] - What is the USRM equivalent of the releaseOldSessions script that runs on the DNCS?

HOw do i tear down VOD Sessions that are older than 4 hours

NOTE: When the VOD Session Manager is a USRM, Cisco refers to this USRM as a VSM.
Here is an explanation of how the VOD Session Manager (VSM) initiates a release of VOD sessions that are older than 4 hours (configurable). The algorithm described below is similar to the releaseOldSessions script on the DNCS that many of our customers are familiar with. Both release VOD sessions that are older than 4 hours old. Also, the VSM has a retry and session audit mechanism built into its algorithm that is absent in the releaseOldSessions script on the DNCS. The main difference is that this functionality is built into the VSM, but the releaseOldSessions script must either be run manually on the DNCS or put into the DNCS crontab. The VSM will make the decision to release a VOD session base on age, typically configured for 4 hours, and then the VSM will send up to 3 teardown requests to the Edge Resource Manager (ERM). NOTE: Both the VSM and ERM are Linux servers running Cisco USRM software.
The “releaseOldSessions” algorithm is configured on the VSM in the Web UI under Applications.VodSm.Configuration as shown in the screen shot below:
Applications.VodSm.Configuration.SessionTimeout = 14,400 seconds (default, configurable)
ReleaseRetryCount = 3 (default, not configurable)
ALGORITHM: The VSM, being the VOD Session Manager, will send a session release request to the appropriate Edge Resource Manager (ERM) based on the configured “SessionTimeout”. By default this value is 14,400 seconds (4 hours, configurable). When the age of a VOD session reaches the SessionTimeout, the VSM will locate the appropriate ERM and send it a session release request for that session. If the ERM fails to acknowledge this release request, the VSM will retry the session release for the number of times configured in ReleaseRetryCount, which is 3. NOTE: Cisco Development has chosen a value of 3 for this parameter (the ReleaseRetryCount is not configurable). If after the 3rd release retry, the VSM still does not have an acknowledgement of session teardown from the ERM, the VSM will initiate a session audit of that ERM as a final attempt to tear down the session.

[Cisco FAQ] - On my D9850 I'm only getting audio, no video on some channels.

Is this an hardware issue or configuration issue?

One possibility is that you tuned to a HD service or a MPEG 4 service. some broadcaster carry SD and HD services in their transport streams.
The D9850 only support MPEG 2 SD, if you require HD or MPEG 4 you will need a D9854 or D9858 receiver depending on your application.

[Cisco FAQ] - How can I copy my recorded programs from my DVR to my PC?

Can I move copies from my DVR hard drive to my PC?

The ability to record or copy programming is categorized under specific copy protection specifications regulated by the FCC and set by the content providers.
In general, over-the-air or local broadcast programs should be set to copy freely, and allow you to make another copy for your pc or mobile device. Other subscription-based programming and premium channels may allow copying to your DVR, but might not be available to make extra copies. Additionally, PPV movies and events may be DVR recordable, but have a timeframe to view before it expires.
The copy protection on channels usually varies from provider to provider.

[Cisco FAQ] - Doctor report

Why should I run it? How should I run it? What information should I be looking for?

The Doctor Report is one of the most important tools that system operators can use to evaluate the configuration and operation of the DNCS. Output from the doctor report appears on the screen of the DNCS and is written to an output file called report._.doc in the /export/home/dncs/doctor folder.
To run the Doctor Report, type the following command in an xterm window on the DNCS:
SP Video TAC Lab SR 4.2>> /export/home/dncs/doctor/doctor -av
Best practices suggest that the Doctor Report should be run twice a day to check:
All processes are running.
System Time Messages (STMs) were delivered within the last 12 seconds.
The EUT (Entitlement Unit Table) was updated within the last 60 minutes.
All BFS carousels are up, all sessions are active and only one process per carousel.
The Doctor Report should be run once per day to verify:
No DNCS corefiles exist.
Each DNCS volume uses less than 80% of its space.
Each DNCS swap space is more than 1GB.
DNCS time is synched to an external source.
Seven days of IPG grid information is available and long descriptions are available,
The DNCS load average is consistent.
For version info and a detailed listing of all options for this utility, type the following command:
SP Video TAC Lab SR 4.2>> /export/home/dncs/doctor/doctor

[Cisco FAQ] - What are the SDV messages logged in the EventLog on the USRM?

Can you please give me the SDV messages on this EventLog?

SDV Messages in the EventLog on the USRM
Reference: Time Warner Cable Switched Digital Video Channel Change Message Interface Specification (TWC-SDV-CCMIS).
ABREVIATIONS:
Conf – Confirmation
Init – Initialization
MPN – MPEG Program Number
Rx – Message received by the USRM
SDB – Switched Digital Broadcast, aka Switched Digital Video (SDV). SDB is part of the message name in the TWC CCMIS spec.
SDV – Switched Digital Video
Sm – Session Manager
Sel – Select
SGID – Service Group ID
SID – Source ID
STB – Set-Top Box
Tx – Message sent by the USRM
TWC Channel Change Message Interface Specification (TWC-SDV-CCMIS)
Message Name in CCMIS
(appears in EventLog as)
Description / Example from the USRM EventLog
SDBInitRequest (SdvSmRxInitReq)
Sent by SDV Client to report client initialization data to the server, i.e., to register with the Server.
2012/02/20 00:08:01.831 SdvSmRxInitReq,STB=10.142.85.250,TID=0x1,SesID=38c85cdbd4da/0,SGID=7998,Ver=0
SDBInitConfirm (SdvSmInitConf )
Sent by the SDV Server to configure the Client.
2012/02/20 00:08:01.831 SdvSmInitConf,STB=10.142.85.250,TID=0x1,SesID=38c85cdbd4da/0,RC=x0
SDBProgramSelectRequest
(SdvSmRxSelReq)
Sent from a User to the SDV Server to request that a broadcast program be provided.
2012/02/21 00:00:00.206 SdvSmRxSelReq,STB=10.120.21.0,SesId=f45fd494bcaa/0,TID=0xc2,SGID=7964,Tuner=0,SID=10097,TunerUse=0x1
SDBProgramSelectConfirm
(SdvSmTxSelConf)
Sent from the SDV Server to a User in response to the SDBProgramSelectRequest.
SdvSmTxSelConf,STB=10.120.21.0,TID=0xc2,SesId=f45fd494bcaa/0,RC=OK,MPN=10097,Freq=69300
0000,Mod=16,Tsid=51247,SGID=7964
ABREVIATIONS:
Bw – Bandwitdh
Cmd – Command
Conf – Confirmation
Req – Request
RID – Resource ID (e.g., management IP address of an edge QAM)
Rm – ResourceManager
SGID – Service Group ID
SID – Source ID
STB – Set-Top Box
Sel – Select
SDV Session Setup on the USRM
/opt/usrm/linux-tools/usrmcctail
Displays Channel changes and QAM operations, combining all operations related to a single transaction together.
SDBProgramSelectRequest
(SelReq)
SDBProgramSelectConfirm
(SelConf)
ResourceManagerBandwidth Request
(RmBwReq)
ResourceManagerCreateSession
(RmCreateSession)
ResourceManagerCommandSuccess
(RmCmdSuccess)
[root@USRM01 linux-tools]# usrmcctail
++++++++++ 001ac332e0ea/0x766 ++++++++++
SelReq         2009/12/02 03:01:31.551 STB=5.134.14.212 Tuner=0 SGID=34110 SID=1350
SelConf         2009/12/02 03:01:31.551 RC=OK MPN=1014 Freq=567000000
++++++++++ 0002dea51bfc/0x1a5 ++++++++++
SelReq         2009/12/02 03:01:32.762 STB=5.173.11.94 Tuner=0 SGID=34007 SID=1519
RmBwReq         2009/12/02 03:01:32.764 BW=3750000 GDA=232.129.2.95
RmCreateSession 2009/12/02 03:01:32.765 SesId=0019b9f7e096/6266778 RID=172.30.104.6 chan0=10 EdgeIn=172.30.104.134 GDA=232.129.2.95
SelConf         2009/12/02 03:01:32.765 RC=OK MPN=1058 Freq=597000000
RmCmdSuccess   2009/12/02 03:01:32.776 Cmd=CreateSession RID=172.30.104.6
++++++++++ 001ac332e0ea/0x767 ++++++++++
SelReq         2009/12/02 03:01:33.089 STB=5.134.14.212 Tuner=0 SGID=34110 SID=1333
RmBwReq         2009/12/02 03:01:33.091 BW=15000000 GDA=232.129.2.124
RmCreateSession 2009/12/02 03:01:33.092 SesId=0019b9f7e096/6266779 RID=172.30.92.9 chan0=6 EdgeIn=172.30.93.50 GDA=232.129.2.124
SelConf         2009/12/02 03:01:33.092 RC=OK MPN=1066 Freq=597000000
RmCmdSuccess   2009/12/02 03:01:33.116 Cmd=CreateSession RID=172.30.92.9
ABREVIATIONS:
Cmd – Command
RID – Resource ID (QAM management IP address)
Rm – ResourceManager
RPC Error Codes – USRM Resource Manager
RPC Error Description – from Generic QAM Interface (GQI) Specification
RPC Error Code
GQI_NO_ERROR
0x90020000
GQI_ERROR_RPC_OUT_OF_MEMORY
0x90020001
GQI_ERROR_RPC_HARDWARE_FAILURE
0x90020002
GQI_ERROR_RPC_SESSION_NOT_FOUND
0x90020003
GQI_ERROR_RPC_MISSING_MSK
0x90020004
GQI_ERROR_RPC_SESSION_ALREADY_EXISTS
0x90020005
GQI_ERROR_RPC_INSUFFICIENT_MEMORY
0x90020006
GQI_ERROR_RPC_INSUFFICIENT_CAPACITY
0x90020007
GQI_ERROR_RPC_PROVISION_FAILURE
0x90020008
GQI_ERROR_RPC_PROGRAM_NUMBER_CONFLICT
0x90020009
GQI_ERROR_RPC_BANDWIDTH_UNAVAILABLE
0x9002000A
GQI_ERROR_RPC_SAME_GIGAIP
0x9002000B
GQI_ERROR_RPC_GIGAIP_INVALID
0x9002000C
GQI_ERROR_RPC_GIGAIP_FAILURE
0x9002000D
GQI_ERROR_RPC_GROUP_SDB_SESSION_FAILURE
0x9002000E
GQI_ERROR_RPC_INSUFFICIENT_OUTPUT_CAPACITY
0x9002000F
GQI_ERROR_RPC_ROUTE_CONFLICT_OUTPUT
0x90020010
GQI_ERROR_RPC_ROUTE_CONFLICT_INPUT
0x90020011
GQI_ERROR_RPC_ROUTE_NOT_FOUND
0x90020012
GQI_ERROR_RPC_ROUTE_ALREADY_EXISTS
0x90020013
GQI_ERROR_RPC_INVALID_MULTICAST_ADDRESS
0x90020014
GQI_ERROR_RPC_INVALID_SOURCE_ADDRESS
0x90020015
GQI_ERROR_RPC_STAT_MUX_GROUP_DEJITTER_FAILURE 0x90020016
0x90020016
GQI_ERROR_RPC_GIGE_TYPE_CONFLICT
0x90020017
Example
2010/06/08 14:56:08.097 RmCmdFail,Cmd=CreateSession,RID=10.78.193.104,Status=0x9002000a,SesId=0015c5603cd0/20587682,MPN=1028,BW=3750000,GDA=232.181.0.71

[Cisco FAQ] - How do I BACKUP and RESTORE the configuration of the RFGW1?

I would like to backup and restore my RFGW1

Go to SYSTEM tab and choose BACKUP CONFIGURATION or RESTORE CONFIGURATION
Backups of the chassis settings are also written to the associateds FTP server. The backup file is generated and consists of the IP of the chassis and the date. An example of the backup file name is shown below.
cfg_10_90_140_15_07_06_2012.gz
Settings for the FTP server are located at the bottom of the page. Click "show FTP settings".

[Cisco FAQ] - If I'm re-IPing the DNCS, what changes need to be made on the USRM?

What is the procedure to re-IP the USRM?

SOFTWARE VERSION: All USRM software releases.
If you’re just changing the IP address of the dncsatm host on the DNCS you only have to
change 2 things on the USRM:
1. The "dncsatm" host entry in /etc/hosts has be modified to reflect the new IP address of
the dncsatm interface on the DNCS.
2. The /opt/usrm/ConfigFiles/SnmpAgent.txt file must be modified if the USRM is to run in
"supervised" mode, meaning that the DNCS will provision the USRM via SNMP.
However, if you change the IP address of eth0 on the USRM, the update_persistdata script
should be used to update the “creator IP” field embedded in all of the persistdata files
on the USRM to contain the new IP address of eth0 on the USRM. So, to change the IP
address of eth0 on the USRM, you will need to:
1. Edit IPADDR, NETMASK and GATEWAY fields in the
/etc/sysconfig/network-scripts/ifcfg-eth0 file.
2. Modify the Primary USRM’s persistdata files with the update_persistdata tool and the
new IP address of eth0.
3. If you also change the IP address of eth1 on the USRM, you just need to edit the IPADDR
and NETMASK fields in the /etc/sysconfig/network-scripts/ifcfg-eth1. The IP address of
eth1 is not the “creator IP”, the IP address of eth0 is.
4. If you change the IP address of eth0 on the USRM, you must also change the IP of the USRM in the VASP List on the DNCS. Actually the IP address field in the VASP List is not editable, so you need to note the following, delete the VASP entry, and add it back with the same VASP ID and the new IP address:
   - VASP Type: SDV Server (even if the USRM is a VSM, choose VASP type "SDV Server")
   - VASP ID: x
   - IP Address:
   - Status: {Out of Service | In Service}

[Cisco FAQ] - DCM Gbe input port is not joining Multicast stream

Why does it do this and how do I fix this issue?

DCM will not join a multicast stream if the Gbe port is disabled while configuring IGMP for that port. Also when the DCM was joined but the Gbe port has been disabled for a longer time afterwards, it is necessary to reconfigure IGMP when the port is enabled. This to force the DCM again to join the multicast stream Solution : • Make sure the Gbe port is enabled • Remove and re-apply the IGMP configuration again to force the DCM to join the multicast again.

[Cisco FAQ] - What is DOCSIS 3.0 Upstream Channel Bonding?

describe what it does.

DOCSIS 3.0 required that CM must have 4 or more upstream channel transmitters. This translates into the
possibility of 100mbps+ upstream rate…
Removed DOCSIS 2.0/1.x single request-grant cycle bottleneck.
Bonded Flows allow multiple outstanding BW-REQ.
BW can be requested on any of the bonded upstream channels
Requests can be granted on any of the bonded upstream channels
Reduced upstream latency (TCP ACK) also increases DS throughput. [TCP application]
Bonds multiple, physical upstream transmit channels to form a larger, logical upstream channel.

[Cisco FAQ] - What is Wideband Downstream DOCSIS?

What does this specifically do?

Bonding of 2 or more QAM channels into Wideband channel
Uses DOCSIS 3.0 Packet Bonding to encapsulate MPEG-TS to Ethernet for transmission to EQAM
Uses existing Edge QAM (EQAM) devices deployed for VOD services
Enables ~300 Mbps downstream in current implementation
8 x 6 MHz channels @ 256 QAM
Future implementations may offer 600 Mps+ downstream
16 x 6 MHz channels @ 256 QAM

[Cisco FAQ] - What is Wideband DOCSIS?

I am not too sure how this works?

Bonding of 2 or more QAM DS channels into Wideband Downstream channel
Provides high bandwidth for DS applications
Enables up to ~300 Mbps downstream throughput
8 x 6 MHz channels @ 256 QAM
50-100 Mbps verified for Pre-EFT
4 X 6 MHz channels @ 64 QAM

[Cisco FAQ] - Full filesystem

Similar Messages

Maybe you are looking for