|
SAR |
|
P |
|
Fpipe Configuration Notes |
|
Last Updated: 2011-10-07 Issue Version 1.0 |
Introduction:
Frame-Relay is designed to provide a cost efficient method
of data communication between LANs and end points in a WAN environment. Frame-Relay
technology is based on the X.25 standard, but simplified to remove the error
correction required for transmission over analog lines. Frame-Relay places data
within variable sized frames, and transmits this data over a Permanent Virtual
Circuit (PVC).
Fpipe provides the following advantages to the Service Providers:
- Future equipment availability. Currently deployed systems in many cases lack official on-going support and equipment availability. Leveraging the 7705 SAR platform ensures continued network operation based on a modern platform.
- Increasing bandwidth requirements. Currently deployed networks are under increasing load as IP traffic usage explodes. Utilizing the 7705 SAR platform provides an easy to manage migration path towards different access technologies while providing a high-speed core architecture.
- OPEX costs. Existing systems can consume between 6 to 10 times the power, which in turn necessitates higher cooling requirements. The 7705 SAR platform can offer substantial OPEX savings compared to legacy equipment by reducing this metric.
- Additional Revenue Possibilities. The 7705 SAR platform placed in the access role close to the customer allows various value-added services to be offered in addition to carrying the existing customer traffic. (Point-to-multipoint L2/L3, IP, and or IP-VPN)
This configuration note will detail the setup of a distribution Fpipe between two 7705 SAR nodes. The CE’s will be attached to the SAP’s on the ASAP cards configured for DS1. The LMI types that can be used are ansi, itu, rev1, none. The LMI type used will be ANSI.
Setup:
Prerequisites:
- MDA/Ports are configured
- IGP/static routing/MPLS or GRE are configured
- SDPs are configured (The transport tunnels used for this setup is LDP)
Configuration:
The First Step is to configure the MDA-Mode. For the setup above, the MDA is an ASAP card, and the configuration for the MDA in node 139 is shown below. The MDA mode has to be “cem-fr-hdlc-ppp” for all nodes that have Frame-Relay configured.
*B:SAR8-139>config>card>mda# info
----------------------------------------------
mda-type a16-chds1v2
mda-mode cem-fr-hdlc-ppp
----------------------------------------------
Note: this applies to the ASAP DS3/E3 MDA’s. The serial SDI card only has one MDS-mode, and doesn’t require this step.
After configuring the MDA, the ports could be configured with Frame-Relay encapsulation type as follows:
*B:SAR8-139# configure port 1/3/16
*B:SAR8-139>config>port# info
----------------------------------------------
tdm
ds1
channel-group 1
encap-type frame-relay
timeslots 1-24
frame-relay
lmi-type ansi
exit
no shutdown
exit
no shutdown
exit
exit
no shutdown
----------------------------------------------
*A:SAR18-141# configure port 1/8/16
*A:SAR18-141>config>port# info
----------------------------------------------
tdm
ds1
channel-group 1
encap-type frame-relay
timeslots 1-24
frame-relay
lmi-type ansi
exit
no shutdown
exit
no shutdown
exit
exit
no shutdown
----------------------------------------------
Note: If the SAP port is looped back, the lmi-type has to be set to ‘none’ since the port is not connected to a CE to transmit the LMI message. The two sides (7705 SAR) can use different LMI-types, but the CE and the attached 7705 SAR have to have the same LMI-types
A DSP is configured on nodes 139 and 141. The SDP configuration for 139 is shown below:
*B:SAR8-139# configure service sdp 141
*B:SAR8-139>config>service>sdp# info
----------------------------------------------
far-end 10.10.10.141
ldp
keep-alive
shutdown
exit
no shutdown
----------------------------------------------
Next, the service has to be configured on the nodes. The Fpipe service on nodes 139 and 141 is shown below:
*B:SAR8-139# configure service fpipe 300
*B:SAR8-139>config>service>fpipe# info
----------------------------------------------
sap 1/3/16.1:100 create
exit
spoke-sdp 141:300 create
exit
no shutdown
----------------------------------------------
*A:SAR18-141# configure service fpipe 300
*A:SAR18-141>config>service>fpipe# info
----------------------------------------------
sap 1/8/16.1:200 create
exit
spoke-sdp 139:300 create
exit
no shutdown
----------------------------------------------
The SAP format is “IOM#/MDA#/port#.ChannelGroup#:DLCI”.
Verification and Troubleshooting:
Verifying that Layer 2 links are up on node 139:
*B:SAR8-139# show port 1/3/16.1 detail
===============================================================================
TDM DS0 Chan Group
===============================================================================
Description : DS0GRP
Interface : 1/3/16.1
TimeSlots : 1-24
Speed : 64 CRC : 16
Admin Status : up Oper Status : up
Last State Change : 02/08/2000 23:35:02 Chan-Grp IfIndex : 577241173
Configured mode : access Encap Type : frame-relay
Admin MTU : 1514 Oper MTU : 1514
Scramble : false
Physical Link : yes Bundle Number : none
Idle Cycle Flags : flags Load-balance-algo : n/a
Payload Fill Type : n/a Payload Pattern : N/A
Signal Fill Type : n/a Signal Pattern : N/A
Ing. Pool % Rate : 100 Egr. Pool % Rate : 100
Egr. Sched. Pol : N/A
===============================================================================
===============================================================================
Traffic Statistics
===============================================================================
Input Output
-------------------------------------------------------------------------------
Octets 1948411140 1765911121
Packets 3897950 3532951
Errors 497435 0
===============================================================================
Port Statistics
===============================================================================
Input Output
-------------------------------------------------------------------------------
Packets 3897950 3532951
Discards 0 0
Unknown Proto Discards 0
The output above shows that the port is up and the encapsulation type is Frame-Relay. The CRC size is 16 bits, this is the default value. It could be set to 32 bits. The CRC size has to match between the port and the CE connected to that port for the port to come up.
The output below shows more information specific to the frame-relay protocol, such as the LMI-type and the mode, dce/dte, along with other statistics.
*B:SAR8-139# show port 1/3/16.1 frame-relay detail
===============================================================================
Frame Relay Info for 1/3/16.1
===============================================================================
Mode : dce LMI Type : ansi
FR Interface Status : running
N391 DTE : 6 N392 DCE : 3
N392 DTE : 3 N393 DCE : 4
N393 DTE : 4 T392 DCE : 15
T391 DTE : 10
FRF-12 : Disabled
Link Identifier : N/A
Tx Status Enquiry : 0 Rx Status Enquiry : 1186
Rx Status Messages : 0 Tx Status Messages : 1189
Status Message Timeouts : 0 Status Enquiry Timeouts : 71
Discarded Messages : 0 Inv. RxSeqNum Messages : 0
===============================================================================
=================================================
Frame Relay PVCs
=================================================
Dlci State Type Creation Time
-------------------------------------------------
100 Active Static 02/08/2000 20:25:55
-------------------------------------------------
PVCs: 1
=================================================
To see more statistics regarding Frame-Relay packets through the port issue the following command:
*B:SAR8-139# show port 1/3/16.1 frame-relay dlci 100
===============================================================================
Frame Relay Info for 1/3/16.1
===============================================================================
Mode : dce LMI Type : ansi
FR Interface Status : running
N391 DTE : 6 N392 DCE : 3
N392 DTE : 3 N393 DCE : 4
N393 DTE : 4 T392 DCE : 15
T391 DTE : 10
FRF-12 : Disabled
Link Identifier : N/A
Tx Status Enquiry : 0 Rx Status Enquiry : 1198
Rx Status Messages : 0 Tx Status Messages : 1201
Status Message Timeouts : 0 Status Enquiry Timeouts : 71
Discarded Messages : 0 Inv. RxSeqNum Messages : 0
===============================================================================
=================================================
Frame Relay PVCs
=================================================
Dlci State Type Creation Time
-------------------------------------------------
100 Active Static 02/08/2000 20:25:55
-------------------------------------------------
PVCs: 1
=================================================
===============================================================================
frame-relay statistics for port "1/3/16.1" dlci "100"
===============================================================================
Input Output
-------------------------------------------------------------------------------
Frames 4012930 3647928
Octets 1998439140 1816668144
FECNs 0 0
BECNs 0 0
DE Frames 0 3647928
DE Octets 0 1816668144
Discards 0 0
Crc Discard 0 -
Aborts 0 -
Other Discard 0 -
The following displays the status of the Fpipe:
*B:SAR8-139# show service id 300 base
===============================================================================
Service Basic Information
===============================================================================
Service Id : 300
Service Type : Fpipe VLL Type : FRDLCI
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/08/2000 23:35:02
Last Mgmt Change : 02/06/2000 23:38:42
Admin State : Up Oper State : Up
MTU : 1508
Vc Switching : False
SAP Count : 1 SDP Bind Count : 1
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/3/16.1:100 frRel 1514 1514 Up Up
sdp:1023:300 S(10.10.10.141) n/a 0 1550 Up Up
===============================================================================