rseries
25 TopicsIs there F5 Virtual Wire(vWire) variable support for vCMP or rSeries tenant?
Hey Everyone, Is there F5 Virtual Wire(vWire) variable support for vCMP or rSeries tenant? I am asking this about vCMP iSeries or rSeries 5800 as the vWire is created on the host and allocated to the tenant but for example in Virtual-wire Configuration and Troubleshooting | DevCentral there are system db variables and how are those supported in this case ? Do you configure this from the vCMP quest or Tenant or from the vCMP host or rSeries appliance ?24Views0likes0CommentsCredentialed Scanning - F5OS - Rseries
After solving the remote authentication issue previously with F5OS. My next question is related to credentialed scanning on R series appliances running F5OS. The tenable agent logs in via SSH and tries to run commands in the shell to pull system information. This has never been on issues on the iseries appliances and BIG-IP guests as they allow uses directly to the shell upon login. All linux commands run as intended. F5OS is a new beast for me to understand as it dumps you into its own OS. The shell is protected and only root at the local level is allowed access to the linux shell. This is the issue I face with credentialed scanning. Authentication works perfectly fine but the ability to run the proper commands at the appropriate level seems to be locked and it doesn't appear I can grant shell access to remote accounts. Anyone have any experience running authenticated scans on their rseries appliances with f50S?35Views0likes0CommentsHA between rSeries tenant and iSeries appliance.
According to F5 documentation, the BIG-IP system supports either homogeneous or heterogeneous hardware platforms within a device group. I want to confirm if anyone has tried to put rSeries tenants and iSeries appliances in the same cluster? Obviously, I understand they will need to be on same version and of course vlans will be same on both. If you have tried this before, what were your challenges and how did you overcome them? I am considering this approach because it makes migration easier and seamless.73Views0likes2Commentsr4600 Tenant CPU Assignment
The r4600 has 12 CPUs (by default) available for a max of 2 tenants. My initial thought was to assign 6 CPUs to each but that is not an option. 4, 8, or 12 are the only options. Question: Are these options of 4, 8, or 12 CPUs arbitrary or do they have to do with the Atom chip architecture? It seems like a waste. I can either do 4 CPUs each wasting 4 or do a 4 CPU tenant and an 8 CPU tenant. The only other option would be to purchase the license for the additional 4 CPUs to make each tenant 8 CPU. Regards, Matt71Views0likes2CommentsrSeries Management route
Hi Experts, I have a situation in rSeries where I want to define a management route for a specific IP (outside the OOB network). I'm facing a scenario where this server is outside the OOB network and cannot be reached from rSeries. I can see from the PCAP that rSeries is able to receive the ICMP request, but rSeries is not sending an ICMP reply and only an ARP request, as if it doesn't know how to reach the server IP. The following steps I tried but still fail: Adding the allowed IP address: server network and server IP with all protocols. Adding a route to the Linux kernel. Note that only the IP outside the OOB network is not reachable, and no ACL/FW in between. Thanks.88Views0likes2CommentsIssue while migrating config from 4000s to r4600
Hi All, we are trying to migrate config from 4000s to r4600. We have created UCS on 4000s but while loading it on a tenant on r4600, we got an error saying ""load sys partition all platform migrate " - failed -- 010713d0:3: Symmetric Unit key decrypt failure - decrypt failure, configuration loading error: high-config-load-failed". Before loading the UCS from 4000s device to tenant, we copied the master key to the new tenant and verified it as well. The command used to load the UCS : load sys ucs <file name> no-license platform-migrate Didn't see any other error logs in /var/log/ltm. Could someone suggest how to resolve this issue ? Please note we are using a CA device certificate and not self signed certificate for the device. Also the management IP, trunk name and number of trunk ports in the UCS are different from those on the tenant.249Views0likes5CommentsWhat is the best practice to deploy single Tenant in F5 rseries?
Hi, we are going to deploy new rseries 5k with single Tenant. What is the best practice to setup? I plan to setup like below, can someone please advise whether it is correct or not? And I have question on auto disk space and memory allocation. Thanks in advance! Allocate all the disk space to this large single tenant Allocate all the memory to this single tenant within the tenant, set "Large" to "Mgmt" module for the rest modules: LTM, GTM , ASM , set "Normal" under Resource Provisioning". Seems the system automatically allocate disk space and memory to each module. Based on the amount of disk space and memory allocated to these modules, seems there are still a lot spare diskspace and memory. Will these modules automatically share the rest spare diskspace and memory when necessary?Solved128Views0likes2CommentsHow to Get Access to BIGIP Next in RSERIES
I have imported the image of BIG-IP next to the F5OS and deployed the image and followed below article. https://clouddocs.f5.com/bigip-next/latest/install/rseries_install_next.html I executed Reset Admin Password with environment variables editing. It worked. But I only can login to BIG-IP next only using the "login" folder in postman. Browser login gives below error. SSH also not working. But I don't understand "Execute the requests Reset Admin Password" through Create Static Route "below step completely in the Guide. (I just only executed Reset Admin Password.) I need to create GUI and SSH access to BIG-IP next. What should I do next ?50Views0likes1CommentDEVICE-0202 Error while adding rSeries as a provider in CM
Hi all, we just got out rSeries Hardware and I am now trying to add it as a provider to out Central Manager instance. Unfortunately I am always getting the following error Code when trying to connect it to CM. DEVICE-0202: BIG-IP Next instance internal server error: Certificate validation failed with error: provider 1234-app123-zz.net.world.aa:8888: DEVICE-0202: BIG-IP Next instance internal server error: SSL certificate is unusable: BIG-IP Next 1234-app123-zz.net.world.aa has an unknown or unusable device certificate; explicit trust is not possible. Error: EOF. . For creating the Device Cert on the rSeries Platform I used to following KB-Article which is for the DEVICE00060 Error: https://my.f5.com/manage/s/article/K000139300 - I issued a self signed certifcate with DNS and IP as SAN Since the error didn't change I tried adding a few other things: - Adding the self signed cert to CentralManager via Applications>Certificates & Keys>import - Creating a crt signed by out Internal CA (no IP in SAN cause the CA doesn't allow that), applying it on the rSeries and uploading the chain to cm - Testing if the rSeries really uses the applied certs on port 8888 each time with openssl s_client connect which it always does But all that didn't change the error message at all. Any ideas? Thank you in advanceSolved173Views0likes4Comments