Updating all references to a particular object in F5 config
Hi All, I am fairly new here and I was hoping for a bit of help. I've been asked to identify all references to a particular object to update in the F5 config and I am not sure where to start. I basically need to update all references from a domain (.com) so we can replace with a (.net) , Are certificates the only place I need to identify? are there any potential objects/rules that I need to find? Is there anyway to download a copy of the config file via xml so I can parse it for any .com references? Thank you
How to configure your node server web app to be use/show on the client side??
Can anyone help me on to do it? Please I'm new on using F5 BIG-IP. Thank you in advance :) Question: How to configure my node server w/ web app locally created (Ex. File Folder w/ index.html) to be used on my F5 BIG-IP and show it specifically. Is there any video on how to configure it? Regards, Renato
Support options for Lab VE and Cloud VE
I want to confirm my understanding of technical support options available for the Lab VE license and 'Cloud' VE offerings (specifically PAYG 'utility' license referenced here). Lab VE: Comes with 1-year of eligibility for software upgrades. I'm not sure if technical support (phone or web 'ticket') is included in the Lab VE. A while back I thought I saw a post on DevCentral where someone was able to purchase an annual support contract for the lab license, though I'm not sure if that included technical support or was just follow-on upgrade eligibility. Cloud VE: The reference link notes "F5 premium support and a 30 day free trial are included in this offering." I understand this to mean that full phone and web-based technical support are available. Thanks for any clarification!
Can I expect issues to be addressed in version 12.0.0?
Hi, I am wondering if I understand the following correctly. Does the bold text imply that product defects, security fixed, diagnostics and support improvements, and new support wont be addressed in 12.0.0? I am uncertain if I should recommend for a client to wait for the long term stability release 12.1.0 before upgrading. https://support.f5.com/kb/en-us/solutions/public/5000/900/sol5903.html Beginning with BIG-IP 12.0.0, F5 has moved to an alternating Major Release/Long Term Stability Release model. For major releases (x.0.0), the Standard Support phase begins with the first customer ship date of the release and extends until the first maintenance release of the subsequent long term stability release (x.1.1) or 15 months (whichever is shorter). When either of these milestones is reached, the major release has reached its End of Software Development (EoSD) phase. For example, the BIG-IP 12.0.0 Standard Support phase will either end upon the release of 12.1.1 or after 15 months from the release of 12.0.0 (if 12.1.1 has not been released). BIG-IP ASM attack signature files are updated for major releases until the release reaches its EoSD phase. Each x.1.0 release marks the start of the long term stability release. The initial release (x.1.0) contains new features, stability improvements, and new hardware support. Subsequent maintenance releases (x.1.1 to x.1.n) address product defects, security fixes, diagnostic and supportability improvements, and new hardware support. Software Development support activities will occur only on the latest maintenance release of each long term stability release (x.1.latest) while the long term stability release is within the Standard Support phase. The Standard Support phase for the long term stability release begins with the first customer ship date of the x.1.0 release and extends for five years. BIG-IP ASM attack signature files are updated for maintenance releases until the associated long term stability release reaches its EoSD phase.Support Contracts on VIPRION
Howdy folks, I'm looking for clarity on how to properly get support contracts on VIPRION gear. Assuming the following: Hardware 1x BIG-IP VPR-C2400 VIPRION Chassis 1x F5-VPR-LTM-B2250 B2250 Blade 1x F5-ADD-VPR-BT-C2X00 Best Licensing Package It's not well documented how to properly cover these devices. It sounds like we need a service contract on all 3 items individually -- is that correct? See below: Support Contracts 1x F5-SVC-VPR-PRE-L1-3 for C2400 Chassis 1x F5-SVC-VPR-PRE-L1-3 for B2250 Blade 1x F5-SVC-VPR-PRE-L1-3 for Best Licensing Package I know this is a question for my account manager and I have sent it to the team, but I'm looking for input from the community.
Objective 5.01 - Open a support ticket with F5
The SOL135 explain that 4 main general information are required when opening a case with F5 Support. A full description of the issue, describing the symptoms, time the issue occurred for the first time A description of the impact the issue is having on your site The hours that you are available to work on the issue Remote access information, if possible. According to the SOL the above requirements apply to all versions of the LTM including 11.1 However, on the official training material for the 11.4 it includes two items which are not mentioned on this SOL135: The Serial number of the BIG-IP device requiring support Product specific information. It sounds to me that the last two requirements only applies for versions above 11.1? Any thoughts?
Getting The Most Out Of LineRate Self-Support
DevCentral is a great resource with a lot of information on all F5 products. This article is designed to help you find your way around our DevCentral LineRate forum and get answers as quickly as possible. DevCentral community does their best to provide answers to all of your questions, yet everyone's time is finite and steps here are aimed at producing best results in the least amount of time possible. Please do be mindful that many of our contributors are volunteers. By following these guidelines you are posed to get the most from networking colleagues and peers. Search First Many of the questions that are posted in the forum may have already been answered multiple times, and get the same answers each time. Before starting a new post, please try searching the forum. We also have a Knowledge Base that is part of LineRate User Documentation and can be accessed online athttps://docs.LineRateSystems.comor via web GUI on your LineRate installation accessible viahttps://:8443/doc/. Choose a good Title Title of your post should be as descriptive as possible within limitations to the entry field length. It is important to choose a good title as many folks look at the title to match their area of expertise. Posts of nature as "Help!", or "My JS code does not work" are not descriptive enough and might slow down your post response time. Provide Good Information Information you enter in the post should be written in simple language. It should be descriptive enough in what you are trying to accomplish, how you are going about towards a solution, and what question you have or issue you ran into. If applicable, post your LineRate installation platform, relevant configurations, and any customizations you have done such as third party NodeJS modules. As needed post you relevant JS code. The more relevant information posted translates to more immediate and direct answers. Tag Your Post as LineRate In addition to having tagged your post as LineRate, chose any other applicable tags, such as nodejs, scripting. Be Patient We understand your time is valuable and strive to provide answers as fast as possible. Some answers take longer to formulate due to complexities involved, please be patient and give us a chance to work through your question. Follow-up on your post Please find time to follow up on your post, either by entering a solution you might have found, or acknowledging the solution others provided. This benefits everyone that is looking for LineRate solutions. We thank you that you care. Privacy Anything you post on the forum is public. Anybody can see it. Do not post any sensitive information such as passwords, proprietary company information, or private information. Ask LineRate question To create a post and get a question on LineRate answered use the aptly named Ask a Question button. Ask a LineRate Question