Now good luck explaining that to support. Have you tried power-cycling it lately? Still no joy? Call comcast and ask a rep to completely remove the modem from your account and to "re-provision" it from scratch. Good luck! I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. You should get a reply here in your topic. Guess I'll just write myself off as lucky as having any internet for now Will definitely be asking for account credit once I can get through to an rep though.
Hi Taralee ,. Optional Downloads the image files from the TFTP server to the switch, and overwrites the current image. The download algorithm verifies that the image is appropriate for the switch model and that enough DRAM is present, or it aborts the process and reports an error. If there is not enough space to install the new image and keep the current running image, the download process stops, and an error message is displayed.
The algorithm installs the downloaded image on the system board flash device flash:. The image is placed into a new directory named with the software version string, and the BOOT environment variable is updated to point to the newly installed image. For filesystem , use flash: for the system board flash device. For file-url , enter the directory name of the old image. All the files in the directory and the directory are removed.
You can upload an image from the switch to a TFTP server. You can later download this image to the switch or to another switch of the same type. Use the upload feature only if the web management pages associated with Device Manager have been installed with the existing image. Uploads the currently running switch image to the TFTP server. The archive upload-sw privileged EXEC command builds an image file on the server by uploading these files in order: info, the Cisco IOS image, and the web management files.
After these files are uploaded, the upload algorithm creates the file format. You upload a switch image file to a server for backup purposes. You can use this uploaded image for future downloads to the switch or another switch of the same type.
You can copy images files to or from an FTP server. When you copy an image file from the switch to a server by using FTP, the Cisco IOS software sends the first valid username in this list:. The switch sends the first valid password in this list:. The username and password must be associated with an account on the FTP server. If you are writing to the server, the FTP server must be properly configured to accept the FTP write request from you. Use the ip ftp username and ip ftp password commands to specify a username and password for all copies.
Include the username in the archive download-sw or archive upload-sw privileged EXEC command if you want to specify a username only for that operation. If the server has a directory structure, the image file is written to or copied from the directory associated with the username on the server. For example, if the image file resides in the home directory of a user on the server, specify that user's name as the remote username.
Before you begin downloading or uploading an image file by using FTP, complete these tasks:. For more information, see the documentation for your FTP server. You can download a new image file and overwrite the current image or keep the current image. To keep the current image, follow Steps 1 to 6 and Step 8.
Optional Enters global configuration mode on the switch. This step is required only if you override the default remote username or password. Optional Changes the default remote FTP username. Optional Downloads the image files from the FTP server to the switch, and overwrites the current image. Optional Downloads the image files from the FTP server to the switch, and saves the current image.
If there is not enough space to install the new image and keep the running image, the download process stops, and an error message is displayed. The algorithm installs the downloaded image onto the system board flash device flash:. For file-url , enter the directory name of the old software image.
With the introduction of the DigitalOcean metadata service , it is possible to start configuring your servers before you even log in. In short, the metadata service is an HTTP location that your server can access during the boot process. During the initial setup, these values can be pulled down by a program called cloud-init to help configure essential services. The most powerful feature is that you can pass a script to the metadata service when you create a server using a field called user-data.
This will be run during the initial boot process and is very flexible, allowing you to accomplish whatever you can script. The most common type of script to pass in is called a cloud-config script. This is a YAML formatted file that provides simple, readable methods of setting up common configuration items by declaration. It also has the ability to run arbitrary commands for other tasks. In this guide, we will get familiar with the DigitalOcean metadata service and cloud-config files by trying out a simple example.
We will be recreating some of the steps outlined in the initial server setup for Ubuntu In order to successfully replicate the steps in the Ubuntu For our servers created with a cloud-config file, we will have to modify our goals a bit. Any information passed in through a cloud-config file is accessible to any user of the system for the entire life of the server. This introduces a number of security issues that are important to understand and address.
Some things to keep in mind are:. With these things in mind, our setup should do everything possible to avoid committing passwords, in any form, within the cloud-config file. We can adjust our goals to accommodate the specific needs of our deployment environment. Besides removing the passwords for both accounts, the most drastic change here is that the new account will be allowed to use sudo without entering an account password.
This is necessary since we are not allowing root logins and we are not setting an account password for our new user. After the new user logs in, they will have freedom to set a password for themselves securely and modify the sudo privileges to require a password, if desired. A cloud-config file is basically a YAML file that understands certain directives. YAML is a data serialization format that is meant to be very human readable, making it simple to understand and edit.
The first line of a cloud-config file must contain a special identifier so that the cloud-init program knows that the file is a cloud-config file. This looks like this:. This must be placed alone on the very first line. The cloud-config file must be provided when the server is created. This can be accomplished in a two different ways. Keep in mind that the metadata service is only available in regions where cloud 1. Additionally, the version of cloud-init needed to consume the user-data field is currently only available in Ubuntu Through the control panel interface, there is an optional check box to enable user data.
When you select this, a text box will show up where you can paste your cloud-config file:. For example, you could pass in a JSON object that looks similar to this:. Both of these methods work exactly the same in practice, so use whichever is most comfortable for you.
This is where almost all of the work will take place. To create a new user, we use the users directive. This will be contain a list of all of the new accounts that we want to create. Since we are only creating a single account, we will have a list of one.
To follow the guide we linked to, we will call this new account demo. Remember, we must start out our cloud-config files with cloud-config alone on the first line. So far, our file will look like this:. The modem has an internal IP address on Cable network. About half way through the lease period, the modem will automatically attempt to renew that lease. This message can safely be ignored. It acquires it on initial connection, and about half way through the lease period.
The other 0. Resetting the cable modem due to docsDevResetNow. Dynamic Range Window violation. The Upstream transmitters are outside of the maximum range differences 12dB — This can potentially be caused by noise on a specific upstream frequency. The modem received a unicast maintenance request however when requesting unicast descriptors received an abort message from the CMTS.
The modem will now reset its cable interface. Lost MDD Timeout. More of an informative note in the log than a warning. What may be happening is that one of the DS channels in use is not in the same fiber node, or not set up as a primary channel, and when the modem tries to lock onto that channel for example , there is no MDD being transmitted or an improper one and the MDD timer expires and the modem moves on and searches for an MDD on the next available downstream.
Some of those are TLV 5. You get those notices if the mode is not set in the modem config file, or if there is a difference between the current operation mode and what is transmitted in the MDD.
0コメント