Thanks Steve for the great info and reply, really appreciated! Apologies for my delay in responding, as I had to divert all my attention to our staff, ensuring they could work from home and such, due to this unprecedented times we now all are facing. I have been on a steep learning curve here with JunOS, as I have never used it before and am used to FOS and ScreenOS. Must say, I do like the rollback feature, some other stuff tho, has me scratching my head. 😉
Now for the good stuff, all is working relative to my question here, you pointed me in the right direction regarding the irb interface, this one took me a bit to get my head around. I created a new irb unit for the /25 public space, then created a vlan for this new irb unit and associated ports along with a new zone. Did something similar for the 192.168 subnet. Policies created to suit my needs and all is working as expected.
The DC had a misconfiguration on their end, that was preventing me from pinging hostnames, however IP's worked. Trying google.com was a big failure, more on this in a bit. This unfortunately took a lot of time to resolve, as they were blaming it on the "new guy" (me) in their DC that they felt did not know what he was doing. Setup a monitor on the outgoing interface and did a trace of all the traffic saved to a log file, showed the "new guy" was right afterall. For a bit, I did figure I fudged something up, being new to JunOS here.
The LB is connected to one of the ports in the VLAN and configured to handle the associated public IP's associated with any hardware or such behind it. All is working with it as well, no issues.
Now going back to pinging google.com dilemna , I was using that as my ping test originally and the hostname was failing with a "no route to host" error. I now know this is due to being associated with an IPv6 address and something the SRX does not like to do. Seems that any hostname that has an IPv6 addy, will fail on a ping with a "no route to host" error from the SRX device. My older SSG devices do not have this problem, and I am not sure at this point if I shoud even be concerned about this, or what to do to fix this.
Thanks,
Chuck