Juniper SSG-140 not reaching devices on VLAN

Have a Juniper SSG-140 connected to a HP PROCURVE 2530 (J9775A) and also a SSL VPN connected to the same switch.

If i configure a interface with ex. DMZ, i am able to reach the SSL VPN, but if i create a vlan on the switch, tag the SSL VPN and the SSG port i cannot reach it. (i also tagged the port on the SSG using the SUB INTERFACE.

The switch have the default VLAN with a IP configured, is this ok?

Maybe the DEFAULT_VLAN having a configured IP is causing this?
manolocruzAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

manolocruzAuthor Commented:
No one?
0
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
What does SSL VPN mean exactly? Is this another device terminating a VPN, so the SSG sees just another IP?
Maybe showing a small sketch of the relevant network participants would help much.
0
manolocruzAuthor Commented:
Is a MAG2600, another device.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

manolocruzAuthor Commented:
basically, a SSG-140 as follows:

0/0 - UNTRUST
0/1 - SW 1 - Port 1
0/2 - SW 2 - Port 1
0/3 - SW 1 - Port 3
0/4 - SW 2 - Port 3
0/5 - SW 1 - Port 5
0/6 - SW 2 - Port 5
0/7 - UNTRUST TO SSG140 (B)
0/8 - HA to SSG-140 (B)
0/9 - SW 1 Port 24

MAG 2600 SSL VPN connected on port 24 on SW 1

I bridged ports 0/3 and 0/4, created sub interface DMZ VLAN ID95, later MANAGEMENT will another VLAN here, with VLAN ID 42.

On Switch Created VLAN 95, tagged ports 3, 4 and 20.

Ports 0/1, 0/2, 0/3 and 0/4 are another bridge group, which later i will configure as TRUST and created several VLAN's, like SALES, MARKETING etc...
0
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
You certainly haven't the MAG and SSG on Sw1-24 ;-). But I get what you mean. So IF 0/9 on SSG should be the "VPN connection".

You are doing a lot of tagging, and use multiple connections to the same switch. You know that it makes things more complicated? You usually either assign a VLAN tag at each switch port or in the interfaces, but not both. You also don't need to use separate ports for different VLANs on the SSG side, as you might know - the routing info should be sufficient to separate traffic, and using too many zones gets confusing with all the rules you'll need for interzone traffic.

I'm still struggling with getting the right picture, and will need some guru meditation about that ;-).
0
manolocruzAuthor Commented:
The whole thing about vlans is to have everything in a HA configuration, we do have 2 firewalls, 2 switches and 2 MAG2600.
as the SSG's have 10 ports, we are using 2 for HA, 1 for untrust, leaving us with 6 for redundancy, 4 for the TRUST, which is the biggest traffic, 2 for management and DMZ.
TRUST cannot see or reach DMZ or management..
One thing that i noted now, is that the previous guy, configured a IP to the DEFAULT_VLAN, which i believe is wrong, ip should only be configured on the the MANAGEMENT VLAN, right?
0
manolocruzAuthor Commented:
Appreciate that!
thanks very much
0
David PiniellaCommented:
If you want TRUST to see the Management or DMZ, you're going to have to add routing to do that.

Is the IP that's been configured part of the VLAN that you're adding?
0
manolocruzAuthor Commented:
Solved!

it was a misconfiguration on SW.
0
manolocruzAuthor Commented:
for some strange reason, router wan't receiving TAG back from switch...

After a factory default on switch and reconfiguration, everything is working as it is supposed to.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
manolocruzAuthor Commented:
after contacting juniper and HP support we were able to find and solve the issue.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hardware Firewalls

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.