[Ask] Triaging Network Engg Questions

Question

In my shop, we are embarking on a project to migrate the enterprise data warehouse infrastructure from data center A to data center B. The documentation describing the current state of the infrastructure and applications is mostly non-existent. The data warehouse team is aware of (or prefers to be on) the application layer and not at the network or physical layer.
The network engg team is asking the data warehouse team the following questions which they are unable to answer.
PHYSICAL:
How many ports will be required for all nodes and are they fiber, copper, a mix of the two?
What speed is required for the ports in bits?
Where are all nodes currently located?
What is the geo-redundant plan?
LOGICAL:
What are the security needs?
Does the traffic have CPNI considerations?
How much traffic needs to be handled by this solution and by whom? Bits per second? Traffic destination?
Which networks need access to these nodes?
Is there an application diagram that defines how the app interacts with other apps/users?
The project is stalled without crisp answers to these questions.
I am not a network engg dude so from a data warehouse standpoint, it would be great to get some knowledge pointers (*) to the network engg guys in the infrastructure so that:
1. The network engg guys can begin to understand "what is their job" (problem solving when there is NO documentation) vs
2 "What is the data warehouse team's job"
If someone can respond to the questions, describing approach (or network engg tools) to consider, under Logical and Physical that would be great.
Thanks in advance.

Answer 1

Do you have IT personal? Someone who maintains your system? No one can answer your questions without knowing your technical environment. I.e. there is no universal answer to how many ports you need.