Design Workshop

Internet Edge Solution 1

Existing Solutions
• LAN Design
Design Notes for Internet Edge
General Design Notes: Services/Solutions

• Data Center Facilities • General Best Practices

• Reliability: Hardware, Power, Connections • Security Best Practices
• Network Management: NMS, Diagrams, Docs
• Naming Std: <cmp>-<dev-id>-<rm>-<loc>-<st/co>

• VLAN Std: Data, Voice, Server, Mgmt, Other

• IP Address Std: 10.X.Y.H
• Subnets: Users (4), Guests (4), Mgmt
Internet Edge
3 – Solutions
Internet Edge Solution
Internet Edge
3 – Solutions
Step 1 – Scalability
Step 1-1: Topology for Internet Edge
Design Diagram
Step 1-2: Layer 2 / Layer 3 Topology
Step 1-2: Layer 2 / Layer 3 Topology
Step 1-2: Layer 2 or Layer 3 Topology
Step 1-2: Layer 2 or Layer 3 Topology
• Layer 3 connection between LAN Core and Edge Router
Design Diagram
Design Notes
General Design Notes: Services/Solutions

• Data Center Facilities • General Best Practices

• Reliability: Hardware, Power, Connections • Security Best Practices
• Network Management: NMS, Diagrams, Docs • Routing
• Naming Std: <cmp>-<dev-id>-<rm>-<loc>-<st/co>

• VLAN Std: Data, Voice, Server, Mgmt, Other

• IP Address Std: 10.X.Y.H
• Subnets: Users (4), Guests (4), Mgmt
Internet Edge
3 – Solutions
Step 2 – Reliability
Step 2-1: Redundancy Model
Step 2-1: Redundancy Model
• Redundancy Components:
• Edge Router
• ISP cloud

• Internet Connectivity:
• Inbound
• Outbound
Step 2-1: Redundancy Model
• Outbound:

• Inbound:
Step 2-1: Redundancy Model
• Two ISP using Single Edge Router (or Firewall) Redundancy:
Step 2-1: Redundancy Model
• Two ISP using Single Edge Router (or Firewall) Redundancy:
Step 2-1: Redundancy Model
• Two ISP using Single Edge Router (or Firewall) Redundancy:
Step 2-1: Redundancy Model
• Through Primary ISP:
• Web Server: 192.168.10.10  6.6.6.6

• Through Secondary ISP

• Web Server: 192.168.10.10  60.60.60.60
Step 2-1: Redundancy Model
• Redundancy critical:
• Not recommended to use this model.
• When using a high number of
connections to your public facing
servers (web, email).
• Require transparent/quick failover.

• Redundancy not critical:

• Update DNS records for public facing
servers when a failure occurs.
• Open support ticket with ISP to resolve
issue.
• No DNS dependency

• Considerations:
• Edge router still SPOF in the solution.
Step 2-1: Redundancy Model
• DNS Dependency

• Client/Server (on Internet) connecting to internal server using:

• Domain Name (e.g. routehub.net)
• IP Address (e.g. 4.2.2.2)
Step 2-1: Redundancy Model
• DNS Dependency: Yes, using
domain name
• Most common
• Relies on DNS
(www.routehub.net  4.2.2.2)
• Not recommended for Two ISP
using Single Edge Router
Redundancy
Step 2-1: Redundancy Model
• DNS Dependency: No, using
IP address
• Not common
• Relies on IP address within the
application/program used by
the client/server.
• Recommended for Two ISP
using Single Edge Router
Redundancy
Step 2-1: Redundancy Model
• Two ISP using Single Edge Router (or Firewall) Redundancy:
Step 2-1: Redundancy Model
• Two ISP using Dual Edge Router Redundancy

When to use:
• Business Size: this option can be used for
Small, SMB, and some Medium-sized
networks.
• Public Addressing: uses different Public IP
subnets from each ISP. A single Public IP
subnet cannot be used between two different
ISPs.
• DNS dependencies not required
Step 2-1: Redundancy Model
• Redundancy critical:
• Not recommended to use this model.
• When using a high number of
connections to your public facing
servers (web, email).
• Require transparent/quick failover.

• Redundancy not critical:

• Update DNS records for public facing
servers when a failure occurs.
• Open support ticket with ISP to resolve
issue.
• No DNS dependency
Step 2-1: Redundancy Model
• Two ISP using Dual Edge Router Redundancy

Services Required:
• Network Address Translation (NAT)
• IP Service Level Agreements (SLA)
• First Hop Redundancy Protocol (HSRP,
VRRP, GLBP)
Step 2-1: Redundancy Model
• Full Redundancy with BGP Multi-Homing

When to use:
• Business Size: this option is common for medium,
large-sized networks, hosting, to service providers.
• Public Addressing: uses a single (or multiple)
customer owned Public IP subnets between all ISP
clouds. For the Public subnet(s), you need to obtain
them through the ARIN website.
• DNS Dependency: YES, users/server can use the
DNS domain name or a dedicated IP address for
accessing services within the internal network using
this redundancy option.
Step 2-1: Redundancy Model
• Technical Requirements:
Step 2-1: Redundancy Model
1. Two ISP using Single Edge Router (or Firewall) Redundancy
2. Two ISP using Dual Edge Router Redundancy
3. Full Redundancy with BGP Multi-Homing
Step 2-1: Redundancy Model
Step 2-1: Redundancy Model
1. Two ISP using Single Edge Router (or Firewall) Redundancy
2. Two ISP using Dual Edge Router Redundancy
3. Full Redundancy with BGP Multi-Homing

X
Step 2-1: Redundancy Model
1. Two ISP using Single Edge Router (or Firewall) Redundancy
2. Two ISP using Dual Edge Router Redundancy
3. Full Redundancy with BGP Multi-Homing

X X
Step 2-1: Redundancy Model
• Full Redundancy with BGP Multi-Homing

Services Required:
• BGP (IP Routing)
• IP Routing (OSPF, EIGRP) or First Hop
Redundancy Protocol (HSRP, VRRP)
Design Diagram
Design Notes
General Design Notes: Services/Solutions

• Data Center Facilities • General Best Practices

• Reliability: Hardware, Power, Connections • Security Best Practices
• Network Management: NMS, Diagrams, Docs • Routing, BGP
• Naming Std: <cmp>-<dev-id>-<rm>-<loc>-<st/co> • FHRP

• VLAN Std: Data, Voice, Server, Mgmt, Other

• IP Address Std: 10.X.Y.H
• Subnets: Users (4), Guests (4), Mgmt
Step 2-2: Other Reliability Service(s)
Step 2-3: Hardware Considerations
Design Notes
General Design Notes: Services/Solutions

• Data Center Facilities • General Best Practices

• Reliability: Hardware, Power, Connections • Security Best Practices
• Network Management: NMS, Diagrams, Docs • Routing, BGP
• Naming Std: <cmp>-<dev-id>-<rm>-<loc>-<st/co> • FHRP

• VLAN Std: Data, Voice, Server, Mgmt, Other

• IP Address Std: 10.X.Y.H
• Subnets: Users (4), Guests (4), Mgmt
Internet Edge
3 – Solutions
Step 3 – Performance
Step 3: Bandwidth for WAN Interface

WAN facing interface

LAN facing interface
Step 3-1: Determine Internet Performance
• Performance for WAN interface on Edge router component
Step 3-1: Determine Internet Performance
• 500 users (HQ)
• 100 users (all RS)

• Moderate Performing:
• 400 users (HQ)
• 100 users (RS)

• High Performing:
• 100 users (HQ)
Step 3-1: Determine Internet Performance
• Services:
• Email, Web Browsing
• Basic File Downloads

• Bandwidth rate per user:

• 130kbps
Step 3-1: Determine Internet Performance
• Services:
• Email, Web Browsing
• Large Downloads
• Cloud Services

• Bandwidth rate per user:

• 384kbps
Step 3-1: Determine Internet Performance
• Moderate Performing Users:
• 400 Users (HQ) x 130kbps = ~52Mbps
• 100 Users (RS) x 130Mbps = ~13Mbps

• High Performing Users:

• 100 Users (HQ) x 384kbps = ~38Mbps

• 52Mbps + 13Mbps + 38Mbps = ~100Mbps

Design Diagram
Step 3-2: Determine Bandwidth Technology
• Based on Internet Performance Calculations:
Design Resources: RFI Checklist
• Service Provider
• Tier Provider
• Reliability (SLA – Availability)
• Performance (SLA – Latency and Packet Loss)
• Security
• Support (Customer Service)
• Installation and Repairs (Maintenance)
• Pricing
• Services
• Length of Contracts
• Case Studies
Step 3-2: Determine Bandwidth Technology
• Example: Internet Performance ~3Mbps
Step 3-2: Determine Bandwidth Technology
• Our Design: Internet Performance of ~100Mbps
Design Diagram
Step 3-3: Bandwidth with LAN/Data Center
• Our Design: Internet Performance of ~100Mbps
Step 3-3: Bandwidth with LAN/Data Center
Design Diagram
Internet Edge
3 – Solutions
Step 4 – Security
Step 4: Security for Internet Edge
Design Notes
General Design Notes: Services/Solutions

• Data Center Facilities • General Best Practices

• Reliability: Hardware, Power, Connections • Security Best Practices
• Network Management: NMS, Diagrams, Docs • Routing, BGP
• Naming Std: <cmp>-<dev-id>-<rm>-<loc>-<st/co> • FHRP

• VLAN Std: Data, Voice, Server, Mgmt, Other • Solutions: Firewall

• IP Address Std: 10.X.Y.H

• Subnets: Users (4), Guests (4), Mgmt
Internet Edge
3 – Solutions
Step 5 – Network Management
Step 5: Network Management for Internet Edge
Design Notes
General Design Notes: Services/Solutions

• Data Center Facilities • General Best Practices

• Reliability: Hardware, Power, Connections • Security Best Practices
• Network Management: NMS, Diagrams, Docs • Routing, BGP
• Naming Std: <cmp>-<dev-id>-<rm>-<loc>-<st/co> • FHRP

• VLAN Std: Data, Voice, Server, Mgmt, Other • Solutions: Firewall

• IP Address Std: 10.X.Y.H • NM : SNMP, Log, NTP, VTY ACL, Netflow

• Subnets: Users (4), Guests (4), Mgmt

Internet Edge
3 – Solutions
Step 6 – Flexibility
Step 6: Flexibility for Internet Edge
Internet Edge
3 – Solutions
Step 7 – Design Aspects
Step 7-1: Other Services
Design Notes
General Design Notes: Services/Solutions

• Data Center Facilities • General Best Practices

• Reliability: Hardware, Power, Connections • Security Best Practices
• Network Management: NMS, Diagrams, Docs • Routing, BGP
• Naming Std: <cmp>-<dev-id>-<rm>-<loc>-<st/co> • FHRP, Multicast, IPv6

• VLAN Std: Data, Voice, Server, Mgmt, Other • Solutions: Firewall

• IP Address Std: 10.X.Y.H • NM : SNMP, Log, NTP, VTY ACL, Netflow

• Subnets: Users (4), Guests (4), Mgmt

Step 7-2: IP Subnets

• IPv4:
• Small/SMB networks: /29 or a single Public IP address
• SMB/Medium networks: /28 or /29
• Medium/Large networks: /24 and higher

• IPv6 (Global):
• /48 IPv6 prefix
Step 7-2: IP Subnets
• Two ISP using Dual Edge Router Redundancy
Design Notes
General Design Notes: Services/Solutions

• Data Center Facilities • General Best Practices

• Reliability: Hardware, Power, Connections • Security Best Practices
• Network Management: NMS, Diagrams, Docs • Routing, BGP
• Naming Std: <cmp>-<dev-id>-<rm>-<loc>-<st/co> • FHRP, Multicast, IPv6

• VLAN Std: Data, Voice, Server, Mgmt, Other • Solutions: Firewall

• IP Address Std: 10.X.Y.H • NM : SNMP, Log, NTP, VTY ACL, Netflow

• Subnets: Users (4), Guests (4), Mgmt, Public,

Transit (IE_LAN)
Internet Edge
3 – Solutions
Step 8 – Hardware
Hardware for Edge Router
• Business Size: Medium
• Gigabit Ethernet for LAN and WAN interfaces
• Internet Performance: ~100Mbps
• BGP Routing with Dual ISP
• Services: Routing, BGP, FHRP, Network Management, Multicast,
IPv6
Hardware Consolidation Options
Hardware Consolidation Options
Hardware Options
Hardware for Edge Router

GOOD BAD
• Medium network • Pricing
• GE support
• Performance support
• L3 services support
Hardware for Edge Router

GOOD BAD
• Medium network • N/A
• GE support
• Performance support
• L3 services support
Hardware for Edge Router

GOOD BAD
• GE support • Small & SMB network
• Performance support • Not ideal for BGP
• L3 services support
Hardware for Edge Router

GOOD BAD
• GE support • Large-sized networks
• Performance support
• L3 services
Hardware for Edge Router

Cisco ISR G2 3900 or 2900 Series

Hardware for Edge Router
• Cisco 3945 Integrated Services Router
• Cisco 3945E Integrated Services Router
• Cisco 3925 Integrated Services Router
• Cisco 3925E Integrated Services Router
Hardware for Edge Router
Hardware for Edge Router
Hardware for Edge Router
Hardware for Edge Router

• NAT, ACL, QoS, VPN

• Typical Internet based traffic
• Packet Byte size (64Bytes, 1500Bytes)
Hardware for Edge Router
• Bandwidth Supported?
Hardware for Edge Router
• Cisco Services Performance Engine (SPE)
Hardware for Edge Router
• Portable Product Sheets for Routing Performance
Hardware for Edge Router
Hardware for Edge Router
Hardware for Edge Router

• Initial Performance: 100Mbps

• Future Performance: 250Mbps – 300Mbps
Hardware for Edge Router
• Cisco ISR G2 3925
Hardware for Edge Router
• Cisco Build and Price for Routers
• https://apps.cisco.com/ccw/cpc/guest/home.do
Design Diagram
Design Notes for Internet Edge
General Design Notes: Services/Solutions

• Data Center Facilities • General Best Practices

• Reliability: Hardware, Power, Connections • Security Best Practices
• Network Management: NMS, Diagrams, Docs • Routing, BGP
• Naming Std: <cmp>-<dev-id>-<rm>-<loc>-<st/co> • FHRP, Multicast, IPv6

• VLAN Std: Data, Voice, Server, Mgmt, Other • Solutions: Firewall

• IP Address Std: 10.X.Y.H • NM : SNMP, Log, NTP, VTY ACL, Netflow

• Subnets: Users (4), Guests (4), Mgmt, Public,

Transit (IE_LAN)
Internet Edge Solution 1
Completed