• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Calling Cisco experts: Typical Network Flow Diagram?

kitkit201

Diamond Member
Hi folks,

Right now, I am trying to configure a network flow diagram for a client. We are moving their production servers from one co-location to another and we want them to be entirely standalone from our environment.

Right now, our configuration is roughly as follows.

Internet --> PIX --> CSS --> Pix--> LocalDirector where LD contains all our app, db and web servers.

We are going to buy a CSS and two web servers in our new environment, and reuse the PIX after having another client move over. Anyways, ideally, we want something like this..

Our plan A
Internet --> Pix --> CSS --> Gigabit Switch (vlan access-list) --> APP, WEB, DBs, Management servers.

Does Plan A's topology seem good or is there something we are missing?

Thanks
Kit
 
what do you want public and what do you want totally unreachible from the Internet?

Normally...
I---Pix---css/DMZ server----pix---LD---back end servers
 
Well, we want the Web Servers to be public and the maanagement network to be public as it will have ftp and a folder to put stuff in.

Spidey-7, Is your first and second Pix the same or one on the border and one on the backend? It seems that we are supplementing the second pix with ACLS on the gigabit switch. and using the CSS as the LD.
 
Back
Top