Separating Test Environment (219 Views)
Posts: 3
Registered: ‎12-27-2013
Message 1 of 4 (219 Views)

Separating Test Environment

[ Edited ]

Currently using PRoCurve E5412


As I am implemeting a test environment I see myslef looking for complete separation from our production.

I am looking to get some logical support.

Currently the only configuration I have made are through the VLAN configs.

I have untagged to ProCurve interfaces: A12 and C12.

And made sure all other VLAN configs do not unclude these;  A12 and C12.

But I am able to still ping the production network.


What should I be looking at to complete this separation?


Forgot to mention that this is behind a watchguard firewall >  Just mentioned firewall for logical help.

I would like to put the load on the HP Procurve and not the firewall unless the firewall is needed.



Occasional Visitor
Posts: 4
Registered: ‎01-01-2014
Message 2 of 4 (176 Views)

Re: Separating Test Environment

Please list an output of the port/vlan membership so we can figure out the VLAN configuration of the switch. Also please specify what IP addresses you are using for the test environment and what addresses for the production LAN.
Posts: 3
Registered: ‎12-27-2013
Message 3 of 4 (164 Views)

Re: Separating Test Environment

Thank you for the response.

However the issue has been sovled.






Posts: 3
Registered: ‎12-27-2013
Message 4 of 4 (158 Views)

Re: Separating Test Environment

[ Edited ]

I would like to re-open this ticket.


I was able to get separation via ACL.

Clients cannot ping each other across production network and test network, visa versa.


Although clients can ping ip addresses assigned to VLANS across networks (Gateways).


Static routing is what I am going to look at next, as this is what is used.

Current static routing is a null route


Any advice would be good.


thanks,  > 


The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.