Forum Discussion
SSL Orchestrator and Layer 2 Service Integration
Hi RedBaron,
Did you assign a Self IP to the VLAN? That will cause them to not appear in the Services screen when creating a Layer 2 Service. Creating the vlan name and tag in F5OS is all that is required. You do not need to make any other network changes in the Tenant.
- RedBaronOct 07, 2025Nimbostratus Kevin, I finally got to talk to you ! Anyway, here's the dilemma, 2 rSeries with a single tenant each in HA mode. Building the orchestrator requires the interface mapping, VLAN name and tag, mac address bank, and verify the listeners at the rSeries level as you know. Inside the tenant, same VLAN name and tag number manually entered, identical to the rSeries entries. Building the topology, no issues, however, once we deploy it....kaboom, interfaces up, services down on both. We walked line by line in the configuration, rebuild it 3 times, and still the same issue. One thing I discovered was that the active node, the interception rule field was completely empty !, the standby is fully populated, but the service is still down ! Weird. No changes needed, just need to make this layer 2 service work so we can provide the customer with full functionality of the system built. Somehow, the services don't seem to work, red red, but the interfaces up. Another thing, the services are not even generated arp entries on both tenants cli prompt. Strange things indeed ! - RedBaronOct 07, 2025Nimbostratus BTW, no self IP on the layer service VLAN. IPs only on external, internal, floaters, and HA VLANs 
- KevinGallaugherOct 07, 2025Employee Hi Red Baron, I don't know what would cause this strange behavior. You should open a case with Technical Support. Kevin 
 
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