findmefast
Technical User
Referincing: thread557-1474090
burtsbees said, "My FastEthernet 0/1 interface needs to be configured to allow our 18 remote locations to connect back to us. Previously they all came in through the serial interface."
fa0/0(10.1.1.1/24)------site1(10.1.1.2)----site3(10.1.1.3)etc...
With all the routers having routes to eachother, this is all that's needed! -- Burt "
Referencing the above thread from 2008, we are in almost the exact same scenario. We have old 1721 Cisco routers over T1 at each of 18 remote sites, connecting back to a Cisco 7204 VXR,all sites are aggregrated, logically separated at this HQ router. T3 / DS3 interface (does that sound correct?) - similar to this:
controller T3 1/0
clock source line
cablelength 10
t1 1 channel-group 0 timeslots 1-24
t1 2 channel-group 0 timeslots 1-24
t1 3 channel-group 0 timeslots 1-24
t1 4 channel-group 0 timeslots 1-24
t1 5 channel-group 0 timeslots 1-24
t1 6 channel-group 0 timeslots 1-24
t1 7 channel-group 0 timeslots 1-24
t1 8 channel-group 0 timeslots 1-24
t1 9 channel-group 0 timeslots 1-24
t1 10 channel-group 0 timeslots 1-24
t1 11 channel-group 0 timeslots 1-24
t1 12 channel-group 0 timeslots 1-24
t1 13 channel-group 0 timeslots 1-24
t1 14 channel-group 0 timeslots 1-24
t1 15 channel-group 0 timeslots 1-24
t1 16 channel-group 0 timeslots 1-24
t1 17 channel-group 0 timeslots 1-24
t1 18 channel-group 0 timeslots 1-24
#Current interfaces on main HQ look something like this:
interface FastEthernet0/0
description Ethernet connection subnet mask set to class b based on design
ip address 10.1.0.12 255.240.0.0
duplex full
!
interface Serial1/0/1:0
description T1 to Site 1 CKT ID #1
ip address 10.40.253.2 255.255.255.252
service-policy output VOIP_POLICY
!
interface Serial1/0/2:0
description T1 to Site #2 CKD ID #2
ip address 10.41.253.2 255.255.255.252
service-policy output VOIP_POLICY
!
1) We want our remote site IP structure to remain the same (voip phones, voice-mail switch at site, router at site).
2) Vendor is laying fiber to all sites, handing us RJ-45-type Ethernet at each site & at HQ.
3) HQ will have 200 Mb/sec link to aggregate all sites at the new 10 Mb/sec speed (per site).
4) This will be Metro-E.
5) We still want each site to keep the router and ip structure it has: i.e.,
Sample site-router config may look like this (10.40.20.1), (10.41.20.1), etc.:
no aaa new-model
memory-size iomem 25
ip cef
!
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
no ip dhcp use vrf connected
no ip dhcp conflict logging
ip dhcp excluded-address 10.40.20.1 10.40.20.149
ip dhcp excluded-address 10.40.20.251 10.40.20.254
!
ip dhcp pool 0
network 10.40.20.0 255.255.255.0
default-router 10.40.20.1
domain-name our-domain.com
dns-server 10.1.2.112 10.1.2.110
netbios-name-server 10.1.2.112 10.1.2.110
netbios-node-type h-node
option 4 ip 10.1.2.112
option 156 ascii "ftpservers=10.1.20.18,country=1,language=1"
lease 30
!
no ip domain lookup
!
class-map match-all SHORETEL_VOIP
match ip dscp ef
!
policy-map VOIP_POLICY
class SHORETEL_VOIP
priority percent 75
class class-default
fair-queue
random-detect
!
interface FastEthernet0
ip address 10.40.20.1 255.255.255.0
speed auto
!
interface Serial0
ip address 10.40.253.1 255.255.255.252
service-module t1 timeslots 1-24
service-module t1 remote-alarm-enable
!
router eigrp 1
network 10.0.0.0
no auto-summary
!
ip forward-protocol nd
!
[NOTE: The sites are /24 and HQ is /12]
6) All site routers give out DHCP to the VOIP phones, and we hope to keep it that way
7) All sites converge here at HQ to get out to the Internet over 50 Mb line to Internet.
[note - all IOS to be 12.4 or higher - have some that are 15.x]
8) New site routers will all be 1841's, with dual 100 Ethernet
9) New site HQ router will be 2800, ditto - dual GigE Ethernet
So, how do we keep our existing IP structure at the sites, with current 1721 routers replaced by 1841 routers, HQ router 7204 replaced by 2800 and logically separate the sites back at HQ? We do not want to have to change IP structure
on 18 sites, 400 workstations, 18 site servers, etc. with our newly-arriving MetroE connections. Is is possible to do
what we are trying? If so, how do we accomplish it? Any possibility to do "internal VLANs" on MetroE? If not, what is
your best suggestion? Previous-referenced post gave a vague idea of configuring the main router with "sites"
referenced on the HQ router "site-facing" interface. Would someone please provide more detail and an example (maybe from a live similar site setup?) REMOVE ANY PRIVATE INFO as I have done!
Thanks in advance for any help!
burtsbees said, "My FastEthernet 0/1 interface needs to be configured to allow our 18 remote locations to connect back to us. Previously they all came in through the serial interface."
fa0/0(10.1.1.1/24)------site1(10.1.1.2)----site3(10.1.1.3)etc...
With all the routers having routes to eachother, this is all that's needed! -- Burt "
Referencing the above thread from 2008, we are in almost the exact same scenario. We have old 1721 Cisco routers over T1 at each of 18 remote sites, connecting back to a Cisco 7204 VXR,all sites are aggregrated, logically separated at this HQ router. T3 / DS3 interface (does that sound correct?) - similar to this:
controller T3 1/0
clock source line
cablelength 10
t1 1 channel-group 0 timeslots 1-24
t1 2 channel-group 0 timeslots 1-24
t1 3 channel-group 0 timeslots 1-24
t1 4 channel-group 0 timeslots 1-24
t1 5 channel-group 0 timeslots 1-24
t1 6 channel-group 0 timeslots 1-24
t1 7 channel-group 0 timeslots 1-24
t1 8 channel-group 0 timeslots 1-24
t1 9 channel-group 0 timeslots 1-24
t1 10 channel-group 0 timeslots 1-24
t1 11 channel-group 0 timeslots 1-24
t1 12 channel-group 0 timeslots 1-24
t1 13 channel-group 0 timeslots 1-24
t1 14 channel-group 0 timeslots 1-24
t1 15 channel-group 0 timeslots 1-24
t1 16 channel-group 0 timeslots 1-24
t1 17 channel-group 0 timeslots 1-24
t1 18 channel-group 0 timeslots 1-24
#Current interfaces on main HQ look something like this:
interface FastEthernet0/0
description Ethernet connection subnet mask set to class b based on design
ip address 10.1.0.12 255.240.0.0
duplex full
!
interface Serial1/0/1:0
description T1 to Site 1 CKT ID #1
ip address 10.40.253.2 255.255.255.252
service-policy output VOIP_POLICY
!
interface Serial1/0/2:0
description T1 to Site #2 CKD ID #2
ip address 10.41.253.2 255.255.255.252
service-policy output VOIP_POLICY
!
1) We want our remote site IP structure to remain the same (voip phones, voice-mail switch at site, router at site).
2) Vendor is laying fiber to all sites, handing us RJ-45-type Ethernet at each site & at HQ.
3) HQ will have 200 Mb/sec link to aggregate all sites at the new 10 Mb/sec speed (per site).
4) This will be Metro-E.
5) We still want each site to keep the router and ip structure it has: i.e.,
Sample site-router config may look like this (10.40.20.1), (10.41.20.1), etc.:
no aaa new-model
memory-size iomem 25
ip cef
!
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
no ip dhcp use vrf connected
no ip dhcp conflict logging
ip dhcp excluded-address 10.40.20.1 10.40.20.149
ip dhcp excluded-address 10.40.20.251 10.40.20.254
!
ip dhcp pool 0
network 10.40.20.0 255.255.255.0
default-router 10.40.20.1
domain-name our-domain.com
dns-server 10.1.2.112 10.1.2.110
netbios-name-server 10.1.2.112 10.1.2.110
netbios-node-type h-node
option 4 ip 10.1.2.112
option 156 ascii "ftpservers=10.1.20.18,country=1,language=1"
lease 30
!
no ip domain lookup
!
class-map match-all SHORETEL_VOIP
match ip dscp ef
!
policy-map VOIP_POLICY
class SHORETEL_VOIP
priority percent 75
class class-default
fair-queue
random-detect
!
interface FastEthernet0
ip address 10.40.20.1 255.255.255.0
speed auto
!
interface Serial0
ip address 10.40.253.1 255.255.255.252
service-module t1 timeslots 1-24
service-module t1 remote-alarm-enable
!
router eigrp 1
network 10.0.0.0
no auto-summary
!
ip forward-protocol nd
!
[NOTE: The sites are /24 and HQ is /12]
6) All site routers give out DHCP to the VOIP phones, and we hope to keep it that way
7) All sites converge here at HQ to get out to the Internet over 50 Mb line to Internet.
[note - all IOS to be 12.4 or higher - have some that are 15.x]
8) New site routers will all be 1841's, with dual 100 Ethernet
9) New site HQ router will be 2800, ditto - dual GigE Ethernet
So, how do we keep our existing IP structure at the sites, with current 1721 routers replaced by 1841 routers, HQ router 7204 replaced by 2800 and logically separate the sites back at HQ? We do not want to have to change IP structure
on 18 sites, 400 workstations, 18 site servers, etc. with our newly-arriving MetroE connections. Is is possible to do
what we are trying? If so, how do we accomplish it? Any possibility to do "internal VLANs" on MetroE? If not, what is
your best suggestion? Previous-referenced post gave a vague idea of configuring the main router with "sites"
referenced on the HQ router "site-facing" interface. Would someone please provide more detail and an example (maybe from a live similar site setup?) REMOVE ANY PRIVATE INFO as I have done!
Thanks in advance for any help!