As with most design issues, a lot of the answer will depend on individual
circumstances.
Including, but certainly not limited to:
Cost
Size of environment
Traffic Flow
Security Concerns
Summed up as what is your "Overall Goal"
If your primary conc
I understand your "traffic flow" perspective, but I must state that it is
not in alignment with modern data flow. That vast majority of traffic
nowadays seems to be moving toward "Enterprise applications" i.e.
"PeopleSoft", "LotusNotes", "Oracle Financials" located on hosts that serve
multiple ap
No problem with that.
Ole
Ole Drews Jensen
Systems Network Manager
CCNA, MCSE, MCP+I
RWR Enterprises, Inc.
[EMAIL PROTECTED]
http://www.oledrews.com/ccnp
-Original Message-
From: Jared Carter [ma
That sounds like an excellent strategy. There should be no problem in
skipping vlan numbers.
Just keep in mind that according to Cisco you want to keep VLAN 1 as your
management VLAN.
HTH,
Casey
>From: "Jared Carter" <[EMAIL PROTECTED]>
>Reply-To: "Jared Carter" <[EMAIL PROTECTED]>
>To: "G
What's hxhk staff?? Just wondering. (Or would I be better off not knowing
what it stands for? &;-)
You make some good points about planning and design, and the fact that
people tend to blame vendors instead of their own lack of planning. On the
other hand, there's nothing wrong with starting w
the question is like closing eye and fire a shoot to sky wishing a bird
will be hitted.
before you even ask for a guide.. you should ask yourself question like..
what kind of network resources i need to share between vlans?
the thoughput of the interexchange..
expansion.. what will be the capa
6 matches
Mail list logo
