876 Configuring dial backup

We are trying to configure a Cisco 876 router to dial out via the ISDN S/T port as the primary interface. If the primary interface is disconnected for whatever reason we would like the analogue/modem connection to automatic kick in as backup through the AUX interface. Currently both the the ISDN and modem connections dial at the same time which we don't want.
I have attached a tech-support file which contains our configuration and IOS version. Is it possible to configure this router to use the ISDN to be the main connection and the analogue service to only kick in when the ISDN goes down? Appreciate any assistance.

Normally it is done with route Administrative Distance and timeout.
There are two routes to the same destination, one with low AD (e.g. 110), which is preferred, and one with high AD, manually set to e.g. 250.
When route with the lower AD goes down, traffic starts to route over route with AD250, next hop of which is backup interface. When primary link comes back up, traffic is routed over the new link, and connection on backup link times out, since there are no packets flowing.
Hope this helps.

Similar Messages

Urgent--dial backup with a PPPOE configuration

Hi all. I have a pppoe for my DSL connection. I cannot get the dial backup to work while the dsl is working.

Hi,
I think there are few problems:
1. the backup interface command should be applied under the dialer interface
2. the dialer interface will never go down unless you shut it
Let' try to configure dialer watch (http://www.cisco.com/en/US/docs/ios/12_0/dial/configuration/guide/dcdbakdw.html) or may be enhanced object tracking (http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/products_feature_guide09186a00801d862d.html).
Hope it helps, rate if does
Krisztian

Dial Backup method to use on an 1811 ISR

I am confused as to the methods available to implement Dial Backup on an 1811 ISR.
My router's WAN is connected to a cable modem via FA0.
In reading the 1811 software configuration guide (chapter 13, page 13-5), I have viewed a table listing "Dial Backup Feature Limitations".
I do not know how to interpret this table.
Is it telling me that Dial Backup on an 1811 is not possible using my "Normal IP cable modem senario"?
Any insight into this issue is gratefully appreciated.
regards

Before delving into technicalities.
Where would you dial backup to ?
Do you have the needed experience or certification to configure Cisco routers ?

Need help on dial backup with ISP

I've been googling around a couple hours and can't find a simple configuration for dial backup to an Internet Service Provider.
So far, what I've been able to find is direct dialing to routers and dial backup using ISDN.
All I need is for a router to dial. The ISP uses PAP/CHAP authentication and dynamically assigns IP addresses to dialup accounts.
I have an 1841 router with a T1 line on S0/0/0. I want it to fail over to the modem on the AUX port and use that as the new default gateway for all traffic.
Any help is appreciated.

I think you can use Dial on Demand Routing (DDR) as described here:
http://www.cisco.com/en/US/tech/tk801/tk133/tsd_technology_support_protocol_home.html
and this particular guide as well:
http://docwiki.cisco.com/wiki/Internetwork_Design_Guide_--_Designing_DDR_Internetworks#Dial_Backup_for_Leased_Lines
Basically your dial connection will not be active until certain traffic will pass through.
Now, to pass traffic only when primary is down, you can define a static floating route as explained above, which is a route with a higher admin distance than the default one, so if the normal route is up, nothing will pass to the dialer, if it's down, the route to the dialer will be used.
To detect that primary route is down, either use dynamic routing or route tracking as suggested.
I hope that helps.
Regards,
bastien.

Dial-backup - business hours limit

Hi everybody,
I´m working in a lab that includes dial-backup for a VSAT link (satellite link). This part of the lab is working excelent, dial-backup goes up when the VSAT connection is lost, and goes down when the VSAT link is recovered.
So, all is ok but... I need to grant dial-backup access only in business hours (ex: 9 am to 5 pm) and deny these the rest of the day.
I worked with time range + access list + dial-list but it didn´t work for me. I was following the steps of this link: http://www.cisco.com/en/US/tech/tk801/tk133/technologies_configuration_example09186a0080094089.shtml.
Is there other way to do this or other idea?
Regards.

Todd,
Sorry for the delay but i was on vacation. At below you´ll find the configuration, specifically highlighted in red the configuration regarding to block dial-in connections. This configuration intends to permit the dial-in connections only on business hours. I know that just is blocking IP traffic but I did not find a way to block PPP or other protocol in a low level.
Could you help me?
Thanks in advance.
Current configuration : 18107 bytes
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname central
boot-start-marker
boot-end-marker
logging message-counter syslog
no logging buffered
no logging console
enable password CVMSLoA
aaa new-model
aaa authentication ppp default local
aaa authorization exec dafault local
aaa session-id common
memory-size iomem 30
dot11 syslog
ip source-route
ip cef
ip domain name test_dbkp
no ipv6 cef
multilink bundle-name authenticated
PURPOSELY REMOVED
username alumine password 0 alumine
username senillosa password 0 senillosa
interface Loopback0
ip address 192.168.2.1 255.255.255.255
interface FastEthernet0/0
description to TELCO1
ip address 10.1.176.1 255.255.255.248
ip nbar protocol-discovery
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
analysis-module monitoring
service-policy output CUSTOMER_QoS
interface FastEthernet0/1
description to TELCO2
ip address 10.1.176.9 255.255.255.248
duplex auto
speed auto
analysis-module monitoring
interface FastEthernet0/1/0
interface FastEthernet0/1/1
interface FastEthernet0/1/2
interface FastEthernet0/1/3
interface Integrated-Service-Engine1/0
ip unnumbered Vlan1
ip nbar protocol-discovery
service-module ip address 10.1.48.253 255.255.255.0
!Application: running
service-module ip default-gateway 10.1.48.1
no keepalive
interface Vlan1
ip address 10.1.48.1 255.255.255.0
ip flow ingress
ip flow egress
ip nat inside
ip virtual-reassembly
no autostate
interface Async1
no ip address
encapsulation slip
async mode interactive
no peer default ip address
interface Async0/0/0
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/1
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/2
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/3
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/4
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/5
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/6
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/7
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode dedicated
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
router bgp 1
no synchronization
bgp log-neighbor-changes
network 10.1.48.0 mask 255.255.255.0
network 10.222.48.0 mask 255.255.255.0
network 192.168.2.1 mask 255.255.255.255
neighbor 10.1.176.25 remote-as 4
neighbor 10.1.176.25 ebgp-multihop 255
neighbor 10.1.176.33 remote-as 5
neighbor 10.1.176.33 ebgp-multihop 255
neighbor 10.1.176.41 remote-as 6
neighbor 10.1.176.41 ebgp-multihop 255
neighbor 10.1.176.49 remote-as 7
neighbor 10.1.176.49 ebgp-multihop 255
neighbor 10.1.176.57 remote-as 8
neighbor 10.1.176.57 ebgp-multihop 255
neighbor 10.1.176.65 remote-as 9
neighbor 10.1.176.65 ebgp-multihop 255
neighbor 10.1.176.73 remote-as 110
neighbor 10.1.176.73 ebgp-multihop 255
neighbor 10.1.176.81 remote-as 11
neighbor 10.1.176.81 ebgp-multihop 255
neighbor 10.1.176.89 remote-as 12
neighbor 10.1.176.89 ebgp-multihop 255
neighbor 10.1.176.97 remote-as 13
neighbor 10.1.176.97 ebgp-multihop 255
neighbor 10.1.176.105 remote-as 14
neighbor 10.1.176.105 ebgp-multihop 255
neighbor 10.1.176.113 remote-as 15
neighbor 10.1.176.113 ebgp-multihop 15
neighbor 10.1.176.121 remote-as 16
neighbor 10.1.176.121 ebgp-multihop 255
neighbor 10.1.176.129 remote-as 17
neighbor 10.1.176.129 ebgp-multihop 255
neighbor 10.1.176.137 remote-as 18
neighbor 10.1.176.137 ebgp-multihop 255
neighbor 10.1.176.145 remote-as 19
neighbor 10.1.176.145 ebgp-multihop 255
neighbor 10.1.176.153 remote-as 20
neighbor 10.1.176.153 ebgp-multihop 255
neighbor 10.1.176.161 remote-as 21
neighbor 10.1.176.161 ebgp-multihop 255
neighbor 10.1.176.169 remote-as 22
neighbor 10.1.176.169 ebgp-multihop 255
neighbor 10.1.176.177 remote-as 24
neighbor 10.1.176.177 ebgp-multihop 255
neighbor 10.1.176.185 remote-as 25
neighbor 10.1.176.185 ebgp-multihop 255
neighbor 10.1.176.193 remote-as 220
neighbor 10.1.176.193 ebgp-multihop 255
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 10.1.176.6
ip route 10.1.48.253 255.255.255.255 Integrated-Service-Engine1/0
ip route 10.1.176.0 255.255.255.0 10.1.176.2
ip route 10.1.176.24 255.255.255.248 10.1.176.10
ip route 10.1.176.40 255.255.255.248 10.1.176.10
ip route 10.1.176.64 255.255.255.248 10.1.176.10
ip route 10.1.176.72 255.255.255.248 10.1.176.10
ip route 10.1.176.88 255.255.255.248 10.1.48.16
ip route 10.1.176.152 255.255.255.248 10.1.176.10
ip route 10.1.176.200 255.255.255.248 10.1.48.16
ip route 10.1.176.208 255.255.255.240 10.1.48.16
ip route 10.1.176.248 255.255.255.248 10.1.176.10
ip route 10.2.48.0 255.255.255.0 10.1.176.2
ip route 10.3.48.0 255.255.255.0 10.1.176.2
PURPOSELY REMOVED
access-list 1 permit 192.168.150.199
access-list 1 permit 10.1.176.2
access-list 1 permit 10.1.176.6
access-list 1 permit 10.1.48.0 0.0.0.255
access-list 1 permit 10.222.48.0 0.0.0.255
access-list 101 permit ip any any time-range BUSINESS-HOURS
access-list 101 deny ip any any
dialer-list 2 protocol ip list 101
snmp-server community RTPE-T-2 RO
snmp-server community RTPE-R-2 RO
snmp-server community RTPE-W-2 RO
snmp-server location CCTE
snmp-server contact AREA C+T
snmp-server host 10.1.48.19 RTPE-T-2
snmp-server host 10.1.48.219 RTPE-T-2
control-plane
voice-port 0/2/0
voice-port 0/2/1
voice-port 0/2/2
voice-port 0/2/3
dial-peer voice 1 pots
preference 1
destination-pattern *1
port 0/2/0
dial-peer voice 2 pots
preference 2
destination-pattern *1
port 0/2/1
dial-peer voice 3 pots
preference 3
destination-pattern *1
port 0/2/2
dial-peer voice 4 pots
preference 4
destination-pattern *1
port 0/2/3
dial-peer voice 5 pots
preference 1
destination-pattern [5-7]...
port 0/2/0
forward-digits all
dial-peer voice 6 pots
preference 2
destination-pattern [5-7]...
port 0/2/1
forward-digits all
dial-peer voice 7 pots
preference 3
destination-pattern [5-7]...
port 0/2/2
forward-digits all
dial-peer voice 8 pots
preference 4
destination-pattern [5-7]...
port 0/2/3
forward-digits all
dial-peer voice 9 voip
destination-pattern 199
session protocol sipv2
session target ipv4:10.255.48.227
no vad
dial-peer voice 10 voip
destination-pattern 101
session protocol sipv2
session target ipv4:10.3.48.3
no vad
dial-peer voice 11 voip
destination-pattern 102
session protocol sipv2
session target ipv4:10.3.48.35
no vad
dial-peer voice 12 voip
destination-pattern 103
session protocol sipv2
session target ipv4:10.3.48.67
no vad
dial-peer voice 13 voip
destination-pattern 121
session protocol sipv2
session target ipv4:10.2.48.3
no vad
dial-peer voice 14 voip
destination-pattern 122
session protocol sipv2
session target ipv4:10.4.48.3
no vad
dial-peer voice 15 voip
destination-pattern 123
session protocol sipv2
session target ipv4:10.18.48.3
no vad
dial-peer voice 16 voip
destination-pattern 131
session protocol sipv2
session target ipv4:10.12.48.3
no vad
dial-peer voice 17 voip
destination-pattern 132
session protocol sipv2
session target ipv4:10.220.48.3
no vad
PURPOUSLY REMOVED
line con 0
line aux 0
stopbits 1
line 0/0/0 0/0/7
modem InOut
autoselect ppp
stopbits 1
speed 57600
flowcontrol hardware
line 66
no activation-character
no exec
transport preferred none
transport input all
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
line vty 0 4
access-class 1 in
privilege level 15
transport input telnet ssh
line vty 5 15
access-class 1 in
privilege level 15
scheduler allocate 20000 1000
time-range BUSINESS-HOURS
periodic daily 09:00 to 17:00
end

DMVPN Dial Backup

Hi,
I need to configure a DMVPN with Dial Backup, my intention is when to fall interface ADSL, my router 837 make a call to local ISP by Console port and close the DMVPN in this interface, that is possible???..Somebody has some configuration as example? Thanks.

I've been reviewing that document over and over, but it only appears to work properly with static IPs, and I will need to use DHCP. There was another document talking about RSR with DHCP, but I still couldn't get it to work properly. Here's why...
My default route is the hubs tunnel address. Then I have a /32 route for the public-facing IP of the hub, via DHCP.
The above-mentioned document doesn't function this way, because they assume that your default route is placed by DHCP. Additionally, I can't seem to find a way to work without my default route pointing the the hub tunnel address.

AS5300 RAS and Dial Backup

We have an AS5300 that currently supports 5 RAS dial-in users. I would like to expand the use of the AS5300 to also be a dial backup solution for some of our remote branch routers. These routers will be using a mixture of ISDN (BRI) and Analog (Async wic-1am) for their dial back up. I also need to run EIGRP over the dial backup links to support the remote LAN failover.
I've compiled a proposed configuration that I think might work for this solution. My main question is how will the AS5300 be able to know which Async interface to use when a remote user needing interactive session dials in versus a remote router.
Please take a look at my proposed config and give me some feedback on if you think this will work. Thanks!!

One way I would do this is to define 5 additional Dialer interfaces for the 5 RAS dial-in users and bind them to int Group-Async 1 using dialer-pool 1.
The 5 new dialer interfaces will be configured for async mode interactive.

Options: dial backup not using ISDN

This is my first post here. I hope I'm in the right place. I need to provide dial backup to one of our locations but it is too far to run an ISDN circuit to them. Mgt. says too expensive and wants a dial backup solution across a POTS line. The site was just upgraded to VOIP. We only need to allow data traffic.
We have a 2821 router running 12.4(3) version IOS. Not sure what the best option is here. Maybe another alternate way other than a modem and a POTS line. I am just looking for ideas if anyone has them. Thanks

Hello,
since cost is a concern, you could just use the AUX port (provided the device at the remote location has one) to configure a dial backup solution. This would still involve using a POTS line, but that is probably the cheapest way to get any sort of backup accomplished. Below is a configuration example. Regarding the voice traffic that should not traverse the backup connection, you would need to deny that traffic to trigger the backup, as well as to get across. In order to accomplish this, you would need to configure an access list that denies VoIP traffic, for Cisco, this would typically look like this:
access-list 101 deny tcp any any eq 1720
access-list 101 deny udp any any range 16384 32767
access-list permit ip any any
This access list then would need to be applied to the async interface (based on the configuration example given), as well as to the dialer list that triggers the backup:
interface Async65
ip access-group 101 out
dialer-list 1 protocol ip list 101
Configuring AUX-to-AUX Port Async Backup with Dialer Watch
http://www.cisco.com/en/US/tech/tk801/tk36/technologies_configuration_example09186a0080093d2b.shtml
HTH,
GP

Dial-backup in 1841 and 2801

Please, does anyone know if the AUX ports in 1841 and 2801 support dial-backup, for example, using PPP ?
Thanks,
Cleber

Hello,
TMBK they do. Check this document for configuration details:
Configuring AUX-to-AUX Port Async Backup with Dialer Watch
http://www.cisco.com/en/US/tech/tk801/tk36/technologies_configuration_example09186a0080093d2b.shtml
HTH,
GNT

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE

How to clear this ? It should auto see to DISK not to tape, i posted 2 show all below, 1st one is giving me error, & the 2nd one is working fine for another db.....
How to clear
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
RMAN> restore database preview;
Starting restore at 27-JUN-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=125 devtype=DISK
released channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/27/2012 11:45:25
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'J:\Cognoscm\%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE 'SBT_TAPE' BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'J:\COGNOSCM\%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\10\DATABASE\SNCFCOGNOSCM.ORA'; # default
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'J:\DELTEKCP\%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'J:\DELTEKCP\%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\10\DATABASE\SNCFDELTEKCP.ORA'; # default

RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'J:\Cognoscm\%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE 'SBT_TAPE' BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'J:\COGNOSCM\%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\10\DATABASE\SNCFCOGNOSCM.ORA'; # default
RMAN> restore database preview;
Starting restore at 27-JUN-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=124 devtype=DISK
RMAN-06908: WARNING: operation will not run in parallel on the allocated channels
RMAN-06909: WARNING: parallelism require Enterprise Edition
released channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/27/2012 13:22:40
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library

Configuring Rman backups from Enterprise Manager GC.

Greetings,
I am having a difficult time understanding how OEM GC 11g interacts with RMAN and am hoping someone can clarify a couple of things for me. Hopefully I am asking meaningful questions. I can make it work but am unclear as to how it is working.
1) For a particular instance under Availability -> Backup/Recovery -> Setting -> Backup Settings I configure my backup settings for RMAN. Is that analogous to issuing the CONFIGURE command from within RMAN?
2) For a particular instance under Availability -> Backup/Recovery -> Manage -> Schedule Backup There are two choices: Oracle Suggested Backup and Customized backup.
Does each of those choices use the settings defined when I configured backup settings?
Looking at the script generated by the Oracle Suggested Backup it appears that it is a very basic backup. What does it do about archive maintenance after backup.
Thanks
Bill Wagman

Hi,
to answer the questions:
1.) yes, these settings reflect the RMAN configuration settings and are used for the backup jobs that are configured via Grid Control
2.) we are using gric control to configure our backup jobs - we never used the Oracle suggested backups, they seemed to be too simple and less flexible. We preferred to build customized backups. They are easy to configure (some screens to clck through) and provides more flexibility. As an example you can decide to backup archive logs also and to delete then from disk afterwards. Also you can distinguish between full or incremental backups. I think it is uasbel and flexible enough for basic backup strategies.
Regards

Configure Dial-in

How do I configure Dial-in access using a NM-16AM card on 2621 router

Hello,
What type of logs you need to be logged?
Rating useful replies is more useful than saying "Thank you"

Trouble configuring Dial Plan in CallManager 7.1.3

Hello all.
Been trying to make my internal phones to communicate to the PSTN line through a VIC2-2FXO card on my Cisco 2911 router.
Problem is that in past tests, I managed to configure CME to direct PSTN call through an FXO card, but it was a different scenario. I had at the time a Cisco 2801 router with CallManager Express installed on its flash, and an FXO card same as this one.
I could also configure my scenario using SDM and other Cisco tools (graphical) which I can't now, because this Cisco 2911 won't accept SDM 2.5 to be installed.
Anyway, I have my phones communicating with eachother internally, both the IP phones, SIP softphones and 2 analog phones connected to the network through a VG202 voice gateway.
I'm here to ask for your help on the best way, or which steps i have to pass in order to allow my communications to be delivered to the exterior of my organization.
I already tried all that I could find, and understand, such as Route Pattern, Application Dial Rules and several others, but still no luck.
Can anyone help me with some guidelines on what I need to configure, or point me on some good documentation about this?
Thank you in advance.

Hi
Since you are using FXO ports, I would normally configure the gateway as a H.323 router. This config should be familiar to you if you have played with CME previously.
Basically you would need carry out these steps:
1) Configure dial-peers pointing to your FXO ports on the gatway (here I'm assuming you want to dial 9 for an outside line, so change the 9 if you use something different - also use whatever voice port numbers you have on your gateway):
dial-peer voice 1 pots
destination-pattern 9T
port 0/0/0
dial-peer voice 2 pots
destination-pattern 9T
port 0/0/1
2) Set the ports to use PLAR to route any incoming calls to an internal extension:
voice-port 0/0/0
connection plar 1234 (set an internal extension where I have 1234)
3) Configure dial-peers pointing to CCM for inbound calls to the number you are sending the calls to:
dial-peer voice 10 voip
session target ipv4:x.x.x.x (CCM IP address)
destination pattern 1234
codec G711a
no vad
4) In CCM, add the gateway as a H.323 gateway. Set:
Device name: IP address of the gateway.
Device Pool: something suitable or default
Inbound Calling Search Space: Set to a CSS including your internal phones, or leave at if you haven't configured partitions
5) In CCM, add a route pattern to match your dial-peer. E.g.
Pattern : 9!
Partition : a partition which your phones have in their CSS, or if you haven't configured CSS/Partitions
Gateway or Route LIst : your H.323 gateway
Leave other properties as-is for now.
This should then allow anything you dial starting with 9 to be routed to the gateway, which will then strip the 9 and send the call out.
This is a very basic setup.... there's a world of other stuff you may want to do, but it should get you started...
Regards
Aaron
Please rate helpful posts

1750 dial backup with WIC-1ENET

Does anyone have dial backup working with a DSL or CAble link on the WIC-1ENET card as the wan link?
My dial backup doesn't automatically come up when using the WIC-1ENET card. It does work correctly when I use a serial connection as the WAN link such as the WIC-1T card.
Cisco stated something about the E0 interface not sensing the change which caused the dial backup not to come up without pulling the ethernet cable out of E0.
Any help would be greatly appreciated.
Thanks

Hi
Hope this helps...
You need to run object tracking feature to enable automatic fallback.
http://www.cisco.com/en/US/partner/docs/ios/12_3/12_3x/12_3xe/feature/guide/dbackupx.html
regds

ISDN configuration for backup of backup

Hello Guys..
I have an MPLS connection where I have running BGP with service provider and I have an ISDN configured (default route with higher AD) as a Backup of that. My customer wants to implement another ISDN connection which should act the backup of backup. Could anybody help me to find a solution to make it work. I can set the priority for the dialer interface , but I am worried about the routing configuration..

Try configuring them as a multilink group:
http://www.cisco.com/en/US/tech/tk801/tk133/technologies_configuration_example09186a0080094a6c.shtml

876 Configuring dial backup

Similar Messages

Maybe you are looking for