Forum Discussion
adding pool members in cli
I am trying to figure out what i am leaving out. I am creating a fqdn node, creating a pool, and then adding the fqdn node to the pool. when i do this through the cli the pool only returns one ip address, when there should be two ip addresses listed in the pool members.
When i create the pool in the gui and add the fqdn node, then the pool shows two ip address for the pool members.
so what am i missing when trying to do this through the cli
Below are the cli commands i am using.
create ltm node AWPRMIPSAPRCH-RKE2-CP-91229EFA47358335.ELB.US-GOV-WEST-1.AMAZONAWS.COM fqdn {name MIPSAPRCH-RKE2-CP-91229EFA47358335.ELB.US-GOV-WEST-1.AMAZONAWS.COM autopopulate enabled interval 0}
create ltm pool MIP-METRONOME-443-PL monitor tcp
modify ltm pool MIP-METRONOME-443-PL members add { AWPRMIPSAPRCH-RKE2-CP-91229EFA47358335.ELB.US-GOV-WEST-1.AMAZONAWS.COM:443
3 Replies
I tried, the thing is this box with the problem has not updated the ASM signatures.
My lab device with v12 and updated ASM sig does not even have that
buffer overflow sig anymore, but onlyattempt 1
and so on.attempt 27 28
- Lior_Rotkovtic1Historic F5 Account
not even here ? : Security ›› Options : Application Security : Attack Signatures : Attack Signature List
also, try accepitng the request from the request log - where it got block. this should disable the signautre so that it will not block
This sig is fired for this one uri in one parameter in json request, the problem with disabling it is it will disable the sig everywhere globally right?
And yes
is not even in the big sig list.Generic buffer overflow attempt 1
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com