RE: Designing FR for 3 branches [7:16030]

2001-08-14 Thread Steve Smith

I think you are going down the right track. I always try to have a
coalition between my DLCI and my IP. We have a good sized frame network
and man does it help do be able to say " Oh, location 1 is DLCI 101 with
Wan IP x.x.x.x" This type planning will also help out when you grow and
try to track it all.

I use /30 on all my wan connections but I also figure out hw many nodes
on each locating then provision 10-20% over that depending on the
locations potential. Seems to work great for me.

Steve

-Original Message-
From: Ole Drews Jensen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 10:16 AM
To: [EMAIL PROTECTED]
Subject: Designing FR for 3 branches [7:16030]


Good morning,

I have now passed several Cisco exams, and are in a lucky situation
where I
have to establish Frame Relay connections between our main office and
three
of our branch offices.

It will not be fully meshed, but a PVC between the main office and each
branch office.

Since I've come accross much of this during my studies, I would like to
show
you my draft, and hope that some of you will throw some comments back to
me,
whether or not it's a good design or a bad design.

Our branch offices each have a branch code, and the three branch offices
I
am connecting has 1, 7 and 8.

I have planned on buying a 2610 with a WIC-1DSU-T1= for the main office,
and
1720's with WIC-1DSU-T1='s for the branches. The main office will be
768/384
(bw/cir) and the branches 256/128.

My LAN at the main office is 10.0.0.0 / 8 (total overkill, but that's
how it
was, and that has been fine with me so far).

If we take branch office 1, the setup I have drafted looks like this:

2610- Ethernet 0: 10.1.1.9 / 8
2610- Serial 0.1: 172.16.1.1 / 30
1720- Serial 0  : 172.16.1.2 / 30
1720- FastEthernet 0: 172.16.1.129 / 25

### QUESTION 1 ###

Would this be the best way of using VLSM for hierarchical design?

##

Next, I would like to match the branch office number with as much as
possible, so my idea was to skip subinterface 0.2 thru 0.6 on the 2610,
so
the next branch office setup would look like this:

2610- Ethernet 0: 10.1.1.9 / 8
2610- Serial 0.7: 172.16.7.1 / 30
1720- Serial 0  : 172.16.7.2 / 30
1720- FastEthernet 0: 172.16.7.129 / 25

### QUESTION 2 ###

Would that be a good idea, and if no - then why not?

##

At last, I would like to see if I can match the DLCI also, but I think
that
I recall 16 being the lowest number to use (is that correct?).

Therefore, the branch office connections would have DLCI 1, 7 and 8 or
21,
27 and 28 if 16 is the lowest.

### QUESTION 3 ###

Is this a good idea, and if no - then why not?

##

I appreciate any comments on this, and hope that you can help me learn
the
"no-so-much-documented" areas of study guides, so I can design this
Frame
Relay the right way from the beginning.

Thanks in advance,

Ole

~~~
 Ole Drews Jensen
 Systems Network Manager
 CCNA, MCSE, MCP+I
 RWR Enterprises, Inc.
 [EMAIL PROTECTED]
~~~
 http://www.RouterChief.com
~~~
 NEED A JOB ???
 http://www.oledrews.com/job
~~~




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=16041&t=16030
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Designing FR for 3 branches [7:16030]

2001-08-14 Thread Ole Drews Jensen

Thanks for your input Steve.
 
Have a great day,
 
Ole



~~~ 
 Ole Drews Jensen 
 Systems Network Manager 
 CCNA, MCSE, MCP+I 
 RWR Enterprises, Inc. 
 [EMAIL PROTECTED] 
~~~ 
  http://www.RouterChief.com 
~~~ 
 NEED A JOB ??? 
  http://www.oledrews.com/job 
~~~ 

-Original Message-
From: Steve Smith [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 10:44 AM
To: Ole Drews Jensen; [EMAIL PROTECTED]
Subject: RE: Designing FR for 3 branches [7:16030]



I think you are going down the right track. I always try to have a coalition
between my DLCI and my IP. We have a good sized frame network and man does
it help do be able to say " Oh, location 1 is DLCI 101 with Wan IP x.x.x.x"
This type planning will also help out when you grow and try to track it all.

I use /30 on all my wan connections but I also figure out hw many nodes on
each locating then provision 10-20% over that depending on the locations
potential. Seems to work great for me.

Steve 

-Original Message- 
From: Ole Drews Jensen [ mailto:[EMAIL PROTECTED]] 
Sent: Tuesday, August 14, 2001 10:16 AM 
To: [EMAIL PROTECTED] 
Subject: Designing FR for 3 branches [7:16030] 


Good morning, 

I have now passed several Cisco exams, and are in a lucky situation where I 
have to establish Frame Relay connections between our main office and three 
of our branch offices. 

It will not be fully meshed, but a PVC between the main office and each 
branch office. 

Since I've come accross much of this during my studies, I would like to show

you my draft, and hope that some of you will throw some comments back to me,

whether or not it's a good design or a bad design. 

Our branch offices each have a branch code, and the three branch offices I 
am connecting has 1, 7 and 8. 

I have planned on buying a 2610 with a WIC-1DSU-T1= for the main office, and

1720's with WIC-1DSU-T1='s for the branches. The main office will be 768/384

(bw/cir) and the branches 256/128. 

My LAN at the main office is 10.0.0.0 / 8 (total overkill, but that's how it

was, and that has been fine with me so far). 

If we take branch office 1, the setup I have drafted looks like this: 

2610- Ethernet 0: 10.1.1.9 / 8 
2610- Serial 0.1: 172.16.1.1 / 30 
1720- Serial 0  : 172.16.1.2 / 30 
1720- FastEthernet 0: 172.16.1.129 / 25 

### QUESTION 1 ### 

Would this be the best way of using VLSM for hierarchical design? 

## 

Next, I would like to match the branch office number with as much as 
possible, so my idea was to skip subinterface 0.2 thru 0.6 on the 2610, so 
the next branch office setup would look like this: 

2610- Ethernet 0: 10.1.1.9 / 8 
2610- Serial 0.7: 172.16.7.1 / 30 
1720- Serial 0  : 172.16.7.2 / 30 
1720- FastEthernet 0: 172.16.7.129 / 25 

### QUESTION 2 ### 

Would that be a good idea, and if no - then why not? 

## 

At last, I would like to see if I can match the DLCI also, but I think that 
I recall 16 being the lowest number to use (is that correct?). 

Therefore, the branch office connections would have DLCI 1, 7 and 8 or 21, 
27 and 28 if 16 is the lowest. 

### QUESTION 3 ### 

Is this a good idea, and if no - then why not? 

## 

I appreciate any comments on this, and hope that you can help me learn the 
"no-so-much-documented" areas of study guides, so I can design this Frame 
Relay the right way from the beginning. 

Thanks in advance, 

Ole 

~~~ 
 Ole Drews Jensen 
 Systems Network Manager 
 CCNA, MCSE, MCP+I 
 RWR Enterprises, Inc. 
 [EMAIL PROTECTED] 
~~~ 
  http://www.RouterChief.com 
~~~ 
 NEED A JOB ??? 
  http://www.oledrews.com/job 
~~~




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=16042&t=16030
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Designing FR for 3 branches [7:16030]

2001-08-14 Thread william gannon

In my experience with Worldcom , you might have trouble choosing your own
DLCI numbers.  You are likely to get assigned arbritrary numbers starting at
100+.  I have found it helps to assign the subinterface the same as the DLCI
number, it really helps in troubleshooting when you do a show frame pvc and
you can look at the subif's and know immediately what circuit it is. May not
be as helpful when you have 3 circuits, but it helps more as the number of
pvc's increase.  You can then put the office branch number in as a
description.  

-Patrick

On Tue, 14 Aug 2001 12:03:08 -0400, Ole Drews Jensen wrote:

>  Thanks for your input Steve.
>   
>  Have a great day,
>   
>  Ole
>  
>  
>  
>  ~~~ 
>   Ole Drews Jensen 
>   Systems Network Manager 
>   CCNA, MCSE, MCP+I 
>   RWR Enterprises, Inc. 
>   [EMAIL PROTECTED] 
>  ~~~ 
>http://www.RouterChief.com 
>  ~~~ 
>   NEED A JOB ??? 
>http://www.oledrews.com/job 
>  ~~~ 
>  
>  -Original Message-
>  From: Steve Smith [mailto:[EMAIL PROTECTED]]
>  Sent: Tuesday, August 14, 2001 10:44 AM
>  To: Ole Drews Jensen; [EMAIL PROTECTED]
>  Subject: RE: Designing FR for 3 branches [7:16030]
>  
>  
>  
>  I think you are going down the right track. I always try to have a
coalition
>  between my DLCI and my IP. We have a good sized frame network and man
does
>  it help do be able to say " Oh, location 1 is DLCI 101 with Wan IP
x.x.x.x"
>  This type planning will also help out when you grow and try to track it
all.
>  
>  I use /30 on all my wan connections but I also figure out hw many nodes
on
>  each locating then provision 10-20% over that depending on the locations
>  potential. Seems to work great for me.
>  
>  Steve 
>  
>  -Original Message- 
>  From: Ole Drews Jensen [ mailto:[EMAIL PROTECTED]] 
>  Sent: Tuesday, August 14, 2001 10:16 AM 
>  To: [EMAIL PROTECTED] 
>  Subject: Designing FR for 3 branches [7:16030] 
>  
>  
>  Good morning, 
>  
>  I have now passed several Cisco exams, and are in a lucky situation where
I 
>  have to establish Frame Relay connections between our main office and
three 
>  of our branch offices. 
>  
>  It will not be fully meshed, but a PVC between the main office and each 
>  branch office. 
>  
>  Since I've come accross much of this during my studies, I would like to
show
>  
>  you my draft, and hope that some of you will throw some comments back to
me,
>  
>  whether or not it's a good design or a bad design. 
>  
>  Our branch offices each have a branch code, and the three branch offices
I 
>  am connecting has 1, 7 and 8. 
>  
>  I have planned on buying a 2610 with a WIC-1DSU-T1= for the main office,
and
>  
>  1720's with WIC-1DSU-T1='s for the branches. The main office will be
768/384
>  
>  (bw/cir) and the branches 256/128. 
>  
>  My LAN at the main office is 10.0.0.0 / 8 (total overkill, but that's how
it
>  
>  was, and that has been fine with me so far). 
>  
>  If we take branch office 1, the setup I have drafted looks like this: 
>  
>  2610- Ethernet 0: 10.1.1.9 / 8 
>  2610- Serial 0.1: 172.16.1.1 / 30 
>  1720- Serial 0  : 172.16.1.2 / 30 
>  1720- FastEthernet 0: 172.16.1.129 / 25 
>  
>  ### QUESTION 1 ### 
>  
>  Would this be the best way of using VLSM for hierarchical design? 
>  
>  ## 
>  
>  Next, I would like to match the branch office number with as much as 
>  possible, so my idea was to skip subinterface 0.2 thru 0.6 on the 2610,
so 
>  the next branch office setup would look like this: 
>  
>  2610- Ethernet 0: 10.1.1.9 / 8 
>  2610- Serial 0.7: 172.16.7.1 / 30 
>  1720- Serial 0  : 172.16.7.2 / 30 
>  1720- FastEthernet 0: 172.16.7.129 / 25 
>  
>  ### QUESTION 2 ### 
>  
>  Would that be a good idea, and if no - then why not? 
>  
>  ## 
>  
>  At last, I would like to see if I can match the DLCI also, but I think
that 
>  I recall 16 being the lowest number to use (is that correct?). 
>  
>  Therefore, the branch office connections would have DLCI 1, 7 and 8 or
21, 
>  27 and 28 if 16 is the lowest. 
>  
>  ### QUESTION 3 ### 
>  
>  Is this a good idea, and if no - then why not? 
>  
>  ## 
>  
>  I appreciate any comments on this, and hope that you can help me learn
the 
>  "no-so-much-documented" areas of study guides, so I can design

RE: Designing FR for 3 branches [7:16030]

2001-08-14 Thread william gannon

In my experience with Worldcom , you might have trouble choosing your own
DLCI numbers.  You are likely to get assigned arbritrary numbers starting at
100+.  I have found it helps to assign the subinterface the same as the DLCI
number, it really helps in troubleshooting when you do a show frame pvc and
you can look at the subif's and know immediately what circuit it is. May not
be as helpful when you have 3 circuits, but it helps more as the number of
pvc's increase.  You can then put the office branch number in as a
description.  

-Patrick

On Tue, 14 Aug 2001 12:03:08 -0400, Ole Drews Jensen wrote:

>  Thanks for your input Steve.
>   
>  Have a great day,
>   
>  Ole
>  
>  
>  
>  ~~~ 
>   Ole Drews Jensen 
>   Systems Network Manager 
>   CCNA, MCSE, MCP+I 
>   RWR Enterprises, Inc. 
>   [EMAIL PROTECTED] 
>  ~~~ 
>http://www.RouterChief.com 
>  ~~~ 
>   NEED A JOB ??? 
>http://www.oledrews.com/job 
>  ~~~ 
>  
>  -Original Message-
>  From: Steve Smith [mailto:[EMAIL PROTECTED]]
>  Sent: Tuesday, August 14, 2001 10:44 AM
>  To: Ole Drews Jensen; [EMAIL PROTECTED]
>  Subject: RE: Designing FR for 3 branches [7:16030]
>  
>  
>  
>  I think you are going down the right track. I always try to have a
coalition
>  between my DLCI and my IP. We have a good sized frame network and man
does
>  it help do be able to say " Oh, location 1 is DLCI 101 with Wan IP
x.x.x.x"
>  This type planning will also help out when you grow and try to track it
all.
>  
>  I use /30 on all my wan connections but I also figure out hw many nodes
on
>  each locating then provision 10-20% over that depending on the locations
>  potential. Seems to work great for me.
>  
>  Steve 
>  
>  -Original Message- 
>  From: Ole Drews Jensen [ mailto:[EMAIL PROTECTED]] 
>  Sent: Tuesday, August 14, 2001 10:16 AM 
>  To: [EMAIL PROTECTED] 
>  Subject: Designing FR for 3 branches [7:16030] 
>  
>  
>  Good morning, 
>  
>  I have now passed several Cisco exams, and are in a lucky situation where
I 
>  have to establish Frame Relay connections between our main office and
three 
>  of our branch offices. 
>  
>  It will not be fully meshed, but a PVC between the main office and each 
>  branch office. 
>  
>  Since I've come accross much of this during my studies, I would like to
show
>  
>  you my draft, and hope that some of you will throw some comments back to
me,
>  
>  whether or not it's a good design or a bad design. 
>  
>  Our branch offices each have a branch code, and the three branch offices
I 
>  am connecting has 1, 7 and 8. 
>  
>  I have planned on buying a 2610 with a WIC-1DSU-T1= for the main office,
and
>  
>  1720's with WIC-1DSU-T1='s for the branches. The main office will be
768/384
>  
>  (bw/cir) and the branches 256/128. 
>  
>  My LAN at the main office is 10.0.0.0 / 8 (total overkill, but that's how
it
>  
>  was, and that has been fine with me so far). 
>  
>  If we take branch office 1, the setup I have drafted looks like this: 
>  
>  2610- Ethernet 0: 10.1.1.9 / 8 
>  2610- Serial 0.1: 172.16.1.1 / 30 
>  1720- Serial 0  : 172.16.1.2 / 30 
>  1720- FastEthernet 0: 172.16.1.129 / 25 
>  
>  ### QUESTION 1 ### 
>  
>  Would this be the best way of using VLSM for hierarchical design? 
>  
>  ## 
>  
>  Next, I would like to match the branch office number with as much as 
>  possible, so my idea was to skip subinterface 0.2 thru 0.6 on the 2610,
so 
>  the next branch office setup would look like this: 
>  
>  2610- Ethernet 0: 10.1.1.9 / 8 
>  2610- Serial 0.7: 172.16.7.1 / 30 
>  1720- Serial 0  : 172.16.7.2 / 30 
>  1720- FastEthernet 0: 172.16.7.129 / 25 
>  
>  ### QUESTION 2 ### 
>  
>  Would that be a good idea, and if no - then why not? 
>  
>  ## 
>  
>  At last, I would like to see if I can match the DLCI also, but I think
that 
>  I recall 16 being the lowest number to use (is that correct?). 
>  
>  Therefore, the branch office connections would have DLCI 1, 7 and 8 or
21, 
>  27 and 28 if 16 is the lowest. 
>  
>  ### QUESTION 3 ### 
>  
>  Is this a good idea, and if no - then why not? 
>  
>  ## 
>  
>  I appreciate any comments on this, and hope that you can help me learn
the 
>  "no-so-much-documented" areas of study guides, so I can design

RE: Designing FR for 3 branches [7:16030]

2001-08-14 Thread william gannon

In my experience with Worldcom , you might have trouble choosing your own
DLCI numbers.  You are likely to get assigned arbritrary numbers starting at
100+.  I have found it helps to assign the subinterface the same as the DLCI
number, it really helps in troubleshooting when you do a show frame pvc and
you can look at the subif's and know immediately what circuit it is. May not
be as helpful when you have 3 circuits, but it helps more as the number of
pvc's increase.  You can then put the office branch number in as a
description.  

-Patrick

On Tue, 14 Aug 2001 12:03:08 -0400, Ole Drews Jensen wrote:

>  Thanks for your input Steve.
>   
>  Have a great day,
>   
>  Ole
>  
>  
>  
>  ~~~ 
>   Ole Drews Jensen 
>   Systems Network Manager 
>   CCNA, MCSE, MCP+I 
>   RWR Enterprises, Inc. 
>   [EMAIL PROTECTED] 
>  ~~~ 
>http://www.RouterChief.com 
>  ~~~ 
>   NEED A JOB ??? 
>http://www.oledrews.com/job 
>  ~~~ 
>  
>  -Original Message-
>  From: Steve Smith [mailto:[EMAIL PROTECTED]]
>  Sent: Tuesday, August 14, 2001 10:44 AM
>  To: Ole Drews Jensen; [EMAIL PROTECTED]
>  Subject: RE: Designing FR for 3 branches [7:16030]
>  
>  
>  
>  I think you are going down the right track. I always try to have a
coalition
>  between my DLCI and my IP. We have a good sized frame network and man
does
>  it help do be able to say " Oh, location 1 is DLCI 101 with Wan IP
x.x.x.x"
>  This type planning will also help out when you grow and try to track it
all.
>  
>  I use /30 on all my wan connections but I also figure out hw many nodes
on
>  each locating then provision 10-20% over that depending on the locations
>  potential. Seems to work great for me.
>  
>  Steve 
>  
>  -Original Message- 
>  From: Ole Drews Jensen [ mailto:[EMAIL PROTECTED]] 
>  Sent: Tuesday, August 14, 2001 10:16 AM 
>  To: [EMAIL PROTECTED] 
>  Subject: Designing FR for 3 branches [7:16030] 
>  
>  
>  Good morning, 
>  
>  I have now passed several Cisco exams, and are in a lucky situation where
I 
>  have to establish Frame Relay connections between our main office and
three 
>  of our branch offices. 
>  
>  It will not be fully meshed, but a PVC between the main office and each 
>  branch office. 
>  
>  Since I've come accross much of this during my studies, I would like to
show
>  
>  you my draft, and hope that some of you will throw some comments back to
me,
>  
>  whether or not it's a good design or a bad design. 
>  
>  Our branch offices each have a branch code, and the three branch offices
I 
>  am connecting has 1, 7 and 8. 
>  
>  I have planned on buying a 2610 with a WIC-1DSU-T1= for the main office,
and
>  
>  1720's with WIC-1DSU-T1='s for the branches. The main office will be
768/384
>  
>  (bw/cir) and the branches 256/128. 
>  
>  My LAN at the main office is 10.0.0.0 / 8 (total overkill, but that's how
it
>  
>  was, and that has been fine with me so far). 
>  
>  If we take branch office 1, the setup I have drafted looks like this: 
>  
>  2610- Ethernet 0: 10.1.1.9 / 8 
>  2610- Serial 0.1: 172.16.1.1 / 30 
>  1720- Serial 0  : 172.16.1.2 / 30 
>  1720- FastEthernet 0: 172.16.1.129 / 25 
>  
>  ### QUESTION 1 ### 
>  
>  Would this be the best way of using VLSM for hierarchical design? 
>  
>  ## 
>  
>  Next, I would like to match the branch office number with as much as 
>  possible, so my idea was to skip subinterface 0.2 thru 0.6 on the 2610,
so 
>  the next branch office setup would look like this: 
>  
>  2610- Ethernet 0: 10.1.1.9 / 8 
>  2610- Serial 0.7: 172.16.7.1 / 30 
>  1720- Serial 0  : 172.16.7.2 / 30 
>  1720- FastEthernet 0: 172.16.7.129 / 25 
>  
>  ### QUESTION 2 ### 
>  
>  Would that be a good idea, and if no - then why not? 
>  
>  ## 
>  
>  At last, I would like to see if I can match the DLCI also, but I think
that 
>  I recall 16 being the lowest number to use (is that correct?). 
>  
>  Therefore, the branch office connections would have DLCI 1, 7 and 8 or
21, 
>  27 and 28 if 16 is the lowest. 
>  
>  ### QUESTION 3 ### 
>  
>  Is this a good idea, and if no - then why not? 
>  
>  ## 
>  
>  I appreciate any comments on this, and hope that you can help me learn
the 
>  "no-so-much-documented" areas of study guides, so I can design