Showing posts with label WAN. Show all posts
Showing posts with label WAN. Show all posts

Wednesday, July 24, 2013

Frame Relay - Address Mapping

Address Mapping in Frame Relay Circuits

A router needs a method to map a DLCI to an IP address, similar to the way ARP maps a MAC address to an IP address.  This is accomplished in two ways:

  1. Inverse ARP - 
    • Default config for Frame Relay
    • provider uses LMI to send a list of DLCIs to the local router, and the local router sends Inverse ARP requests to all other DLCIs, asking for their IP address.  All DLCIs respond with IP address.  
    • If you have multiple DLCIs, your interface becomes a multipoint interface, however - Inverse ARP does not work with subinterfaces
  2. Static Mapping
    • Complete control, but more config
    • Assign IP addresses to DLCIs
    • R1(config-if)#frame-relay map ip 192.168.5.2 503 broadcast 

Frame Relay - NBMA, Split-horizon and Subinterfaces

A little more info regarding frame relay circuits:

Frame Relay is a NBMA (Non-broadcast Multi Access) network, meaning that it does not allow broadcast traffic between devices.  This will cause a problem if you use distance-vector routing protocols such as RIP, because the split-horizon loop avoidance mechanism will prevent updates from going back out the interface on which they came.  In a hub-and-spoke configuration, the spoke offices will not get updates about each other.

To avoid the split-horizon issues created in this instance, one could disable split-horizon and rely on the other loop-avoidance mechanisms (not recommended) or use subinterfaces.

Subinterfaces are logical interfaces attached to a single physical interface.  The router sees and treats them as separate interfaces, however.

Multipoint subinterfaces do not solve the split-horizon issues and are essentially useless in Fream Relay circuits.  They simply add multipoint interfaces to a logical interface, recreating all the same issues as a physical subinterface.  Meh...

Point-to-point subinterfaces allow a single, physical interface to hold multiple ports.  They are created using a "dot" - instead of Serial 0/0 we now have Serial 0/0.10.  Each subinterface can connect a PVC of its own, and the router treats each like a different port.




Tuesday, July 23, 2013

PPP authentication and compression

PPP is a simple encapsulation to configure on Cisco routers, with the ability to add multiple features once enabled.  TO start, the only configuration necessary is to enter into the interface configuration mode and type:

R1(config-if)#encapsulation ppp

Do that on both sides of your WAN link and you're good to go.

The CCNA exam requires feature configuration for PPP links, however, and mainly CHAP authentication.  CHAP is an authentication method that sends MD5 hashes of a shared password between configured peers.  The configuration steps are:

  1. Configure a hostname for both routers
  2. Create a user on each router with the hostname of the peer, being certain the hostname is case-correct.  Also be certain that the password is identical for both peers.  As stated above, username and password are both case sensitive
  3. Enable ppp encapsulation on the interfaces of both peers
  4. Enable CHAP authentication on both peers
Voila, that's it.  Before you enable authentication on both sides, a debug will show:

 R2(config)#
*Mar  1 00:09:57.055: Se0/0 PPP: Authorization required
*Mar  1 00:09:57.075: Se0/0 PPP: No authorization without authentication
*Mar  1 00:09:57.075: Se0/0 CHAP: I CHALLENGE id 1 len 23 from "R1"
*Mar  1 00:09:57.091: Se0/0 CHAP: Unable to authenticate for peer
*Mar  1 00:09:58.051: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0, changed state to down


And the other troubleshooting step would be to show the brief interface statistics:

R2#sho ip int brie
Interface       IP-Address   OK? Method Status      Protocol
FastEthernet0/0 10.2.1.1        YES manual up       up 
Serial0/0       192.168.2.2     YES manual up       down
FastEthernet0/1 10.20.1.1       YES manual up       up 
Serial0/1       192.168.3.1     YES manual up       up 


Here you see on Serial0/0 that we have a status "up" and Protocol "down" which is the classic case of layer 1 being satisfactory but layer 2 is the problem.  This is always an issue with the L2 protocol, whether it is a mis-matched encapsulation type or misconfigured authentication or compression.

Compression

Configuring compression on a PPP connection is quite simple, also.  The caveat is that you need to do it on both ends or the link will once again fail (you will see this with an up/down status on the connected interfaces).  

Monday, July 22, 2013

Random thoughts on WAN connectivity

Reviewing WAN connectivity this morning.  Here are some items of interest to me...

T1 interfaces use an RJ-48 connector.  While looking like an RJ-45, the RJ-48 uses STP cabling, a different pinout and voltages.  Don't be fooled!


PPP replaced SLIP and offers encrypted authentication and support for protocols other than TCP/IP.

ATM is cell switched while Frame Relay is packet switched.

PPP Sub-layers:
  1. ISO HDLC:  common ground for devices using PPP, enables base features of PPP
  2. LCP (Link Control Protocol):  Where all PPP features are enabled.  These are:
    • Authentication - PAP or CHAP
    • Compression
      • Stacker - replace continuous streams with codes
      • Predicter - replace data with indexed codes
    • Multilink - bundle multiple lines into a single management, load-balanced line
    • Callback - security method to dial remote users back at a predefined number
  3. NCP (Network Control Protocol):  common interface for L3 protocols