To transfer billing records using TFTP, you must first configure an
external workstation to be a TFTP server. For security, the TFTP server should
be isolated from the Internet or any external networks, so that only authorized
TFTP clients, such as the Cisco CMTS router, can access the server.
To transfer the billing records, the application server must log in
to the Cisco CMTS and use the
copy command at the privileged EXEC prompt.
The
copy command needs to specify the location of
the billing record on the local filesystem and the destination server for the
TFTP transfer.
The following example shows a typical session where a billing record
on slot0 is transferred to an TFTP server with the hostname of
billserver.mso-example.com.
Router# copy slot0:CMTS01_20030211-155025 tftp://billingapp-server.mso-example.com/incoming
Address or name of remote host [billingapp-server.mso-example.com]?
Destination username [billing-app]?
Destination filename [CMTS01_20030211-155025]?
Writing CMTS01_20030211-155025
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 1102348/1024 bytes]
1102348 bytes copied in 14.716 secs (63631 bytes/sec)
Router# delete slot0:CMTS01_20030211-155025
Router# squeeze slot0:
Router#
Note |
The billing application must delete the billing record after it
has been successfully transferred, so that the Cisco CMTS can write the next
record. The
squeeze command frees up the deleted disk
space on Flash Memory and old-style PCMCIA cards (bootflash, flash, slot0,
slot1). It is not needed on the newer ATA-style PCMCIA cards (disk0, disk1,
disk2). However, because the
squeeze command takes several seconds to
complete, it should be given only when insufficient disk space exists for a new
billing record. To avoid this problem, Cisco recommends using a 64 MB (or
larger) ATA-style PCMCIA memory card, which automatically reclaims disk space
for deleted files.
|