Frame Relay configuration for ccie lab

-
==========================================================================
Frame Relay router

!
interface Serial0/0/0
 description *** static DCE connection to s1 Prasit
 no ip address
 encapsulation frame-relay
 clock rate 2000000
 frame-relay intf-type dce
 frame-relay route 150 interface Serial0/1/0 130
 frame-relay route 170 interface Serial0/2/0 180
!
interface Serial0/1/0
 description *** static DCE connection to s0 spicy
 bandwidth 1000000
 no ip address
 encapsulation frame-relay
 tx-ring-limit 100
 tx-queue-limit 100
 transmitter-delay 10
 frame-relay intf-type dce
 frame-relay route 130 interface Serial0/0/0 150
 frame-relay route 140 interface Serial0/2/0 160
!
interface Serial0/2/0
 description *** static DCE connection to s1 Aton
 ip address 192.168.22.1 255.255.255.0
 encapsulation frame-relay
 frame-relay intf-type dce
 frame-relay route 160 interface Serial0/1/0 140
 frame-relay route 180 interface Serial0/0/0 170
!

==========================================================================

BR2
interface Serial0/2/0
 ip address 172.16.26.3 255.255.255.0
 encapsulation frame-relay
 no fair-queue
 clock rate 2000000
 frame-relay interface-dlci 160
 frame-relay interface-dlci 180
 !

==========================================================================

BR1
!
interface Serial0/0/0
 ip address 172.16.26.2 255.255.255.0
 encapsulation frame-relay
 no fair-queue
 frame-relay interface-dlci 150
 frame-relay interface-dlci 170
!

==========================================================================

HQ
!
interface Serial0/0/0
 ip address 172.16.26.1 255.255.255.0
 encapsulation frame-relay
 no fair-queue
 clock rate 2000000
 frame-relay interface-dlci 130
 frame-relay interface-dlci 140

Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Administr
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C
Read more