OSPF Graceful Restart

Hi all! i´m Juan from Argentina.
I´m studing to my CCIE WR R&S Exam, and i have a dude with GR in OSPF:
When a router needs to boot, or switch the RP, sends a ospf-graceful to his neighbors.
When his neighbors receives his graceful-lsas:
     1- What will they do?
          a) they don´t down the neighbor relationship.
          b) they sends again his own lsa?
          c) they gives to the graceful router,a grace period to maintain the relationship?
Thanks to all, but i don´t understand this topic,
Thanks
Juan

Juan,
Check out the following URL for more information on OSPF Graceful restart.  Your answer is in there.
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/gr_ospf.html
Thanks,
Bryan

Similar Messages

  • Graceful Restart of Apache Causes JRun Connector Protocol Error

    Can anyone shed some light on how I can get Apache to do a
    graceful restart without causing a JRun Connector Protocol error.
    If I run a ColdFusion page that basically loops through a set
    of numbers and then issue a "kill -SIGUSR1 `cat
    /var/run/httpd.pid`" command then I receive the following error:
    Server Error
    The server encountered an internal error and was unable to
    complete your request.
    JRun Connector Protocol Error.
    Can anyone shed some light on how I can avoid this error?
    Thanks,
    John

    And what happens on Apache 1.3?
    Thanks in advance,
    Lopato

  • How do I gracefully restart Apache?

    Is there any way to gracefully restart Apache? On a standard setup I would normally run this command:
    <pre>sudo apachectl graceful</pre>
    But the Apache 2 that comes with OS X Server 10.5 does not gracefully restart with this command. Instead it will interrupt all open connections stopping all downloads. I'm assuming this is because Apache is handled by launchd which doesn't support graceful restarts. Is there any way to get around this problem?

    I decided maybe there's a man page that will point in the right direction:
    http://developer.apple.com/documentation/Darwin/Reference/Manpages/man1/launchct l.1.html
    This is a complete stab in the dark. Launchd can receive commands from launchctl. but the launchctl command syntax is not the same as say apachectl. Try this command:
    launchctl submit -p apachectl graceful
    Let me know if that really performs a graceful restart. I'm a big fan of the graceful restart myself, and would hate to see that option not available from the commandline.

  • How Do I do graceful restarts or configtests of SUNW.apache Resources?

    I have created a scalably clustered Apache resource group using the SUNW.apache resource type.
    I can not find any documentation as to how to perform configtest and graceful (restart) operations.
    Can anyone detail for me, or point me to documentation on how these standard Apache functions are invoked in this environment?
    Thanks in advance!
    John
    [email protected]

    I have created a scalably clustered Apache resource group using the SUNW.apache resource type.
    I can not find any documentation as to how to perform configtest and graceful (restart) operations.
    Can anyone detail for me, or point me to documentation on how these standard Apache functions are invoked in this environment?
    Thanks in advance!
    John
    [email protected]

  • HT201236 "graceful" restart key combination

    Hi there, I'd like to do a "graceful" restart, but there Control-Command-Power button combination is listed twice in here. Do you know how to do it?

    OS X: Keyboard shortcuts - Apple Support
    Two keys:
    Control-Power button
    Show the restart / sleep / shut down dialog
    Three keys:
    Command-Control-power button
    Force the Mac to restart

  • RSVP graceful restart support in 12000 router

    Hi,
    It seems like the router is not supporting graceful restart full mode.
    If you have to GSR's that are connected to each other, will it be possible to setup graceful restart and work together with SSO?
    I have tried but with no success, if it's should work, have somebody any config example?
    /Niklas

    Thanks,
    I will contact our sales.
    Means helper-mode that the router can help the other side to recover a RP failure situation?
    The other router must also support full-mode?
    BR Niklas

  • BGP and Graceful-restart

    Hello colleagues!
    I'm trying to figure out some details regarding BGP GR functionality.
    The basic concept is pretty simple, but I cannot find answer to my question:
    How BGP peers knows when SSO-performing router switches to standby supervisor?
    BGP peers should somehow distinguish real supervisor fail from some other fails.
    I think it's very important, because if not so - when 'other fail' occurs BGP peer will keep routes during `Restart Timer` that equal to 120 sec by default. It may cause a blackhole.
    Also such a big pause (dead timer + restart timer) is not acceptable for HA infrastructure.
    Does really BGP Peers each time when BGP TCP session timed out (no matter why) keeps routes during `Restart Timer`? Or how Restarter notify its peers?
    On the other hand - when I simulate termination of the BGP session (add route to the neighbor to Null0 at the Restarter), peer just wait for the holdtime and does not mark routes as stale after. In other words it does not start NSF process. What should happen to start that process in the context of neighbors?
    If the BGP session is lost during the RP switchover, the NSF-aware BGP peer marks all the routes associated with the NSF-capable router as stale; however, it continues to use these routes to make forwarding decisions for a set period of time. This functionality means that no packets are lost while the newly active RP is waiting for convergence of the routing information with the BGP peers.
    After an RP switchover occurs, the NSF-capable router reestablishes the session with the BGP peer. In establishing the new session, it sends a new graceful restart message that identifies the NSF-capable router as having restarted.
    http://www.cisco.com/en/US/docs/ios/12_2t/12_2t15/feature/guide/ftbgpnsf.html
    Regards, Konstantin.

    I think I figured it out...
    When new supervisor becomes active it receives BGP keepalives from BGP peers but ongoing TCP session is unknown for the new supervisor. That's why it abort the session with TCP RST.
    This RST is a trigger to its peer to mark old routes as `stale` and continue NSF process as documented.

  • NSR, NSF and graceful restart

    Hello all,
    I have understand the difference between NSF and NSR. NSF supports forwarding without traffic loss during a brief outage of the control plane. Whereas NSR allows for the forwarding of data packets to continue along known routes while the routing protocol information is being refreshed following a processor switchover.
    Would like to know
    1. Working principle of Graceful restart.
    2. Do we need to enable gracefule restart along with NSF abd NSR?
    3. What is the advantage of enabling Graceful restart with NSR?
    4. If possible, please explain what is checkpointing and mirroring?
    Thanks
    Hari

    Hi Hari,
    Ah I think I provided a lot of that detail in your other discussion you started.
    To sume up:
    1) GR assists in not declaring a peering down (grace period) while the control plane is converging.
    while this is happening the FIB maintains its forwarding table as it knew it was before the convergence. this is also called "headless routing"
    2) NSF is by default in XR/A9K because of its distributed architecture. It mainly is composed of the SSO functionality, and yes GR will definitely help but not mandated.
    NSR is a separate option to maintain a routing peering by syncing state and seq numbers between active and standby control plane.
    4) checkpointing is the concept of making snapshots of data and synchronizing or saving that to a particular location. Mirroring, yeah that is something you look at when you shave in the morning, or it is just the same as checkpointing really. Checkpoints are usually done in batches, at least that is what the concept refers to.
    regards
    xander

  • Graceful vs Forceful Dgraph restart

    Hi,
    I would like to know if there is any dgraph flag in endeca which would decide the type of restart configuration of the dgraph. That is, it could either start forcefully or gracefully. Graceful restart of dgraph is when it serves the existing request before restarting and forceful type is when dgraphs is restarted by terminating the request.
    Please let me know.
    Thanks

    Thanks for the reply. I know the machine isn't getting its power killed like a normal outage -- the system log snippets I posted shows that it is getting a shutdown command.
    I thought the whole point of linking the UPS and the Mac Pro via USB cable, and having UPS power options integrated into OS X, was that the operating system could do a normal, graceful system shutdown based on information received from the UPS unit. It correctly receives the time or percentage of battery power remaining, and displays that on the menu bar -- it should be a simple matter for the OS to monitor this and perform a regular shutdown when certain thresholds of battery power are reached, correct?
    If OS X doesn't do this, is there an easy way to script this? Have an Applescript monitoring program, that checks the UPS status and does a graceful restart when the UPS battery life remaining gets too low?

  • Restarting Stanby database after host crash

    Ok here is the scenario . . .
    the host for my Physical Standby database crashes . . . you know the janitor kick the plug out . . .
    How do I gracefully restart the Physical Standby database . . .
    My concern/paranoia/fear is that during the restating of the Physical Standby database that it does NOT opens as the new Primary database.
    I guess what I am looking for is the steps it takes to "restart" the Physical Standby and make sure it is in "managed standby".
    Edited by: user10260925 on Apr 6, 2010 12:54 AM

    A physical or logical standby will never open itself as a primary. If you have Fast-Start Failover configured then the Observer will make it a Primary if the requirements for the failover have been met. Otherwise you would have to manually enter the failover commands to make it a Primary database.
    As of 10g Release 1 if you do a STARTUP on a Physical standby it will open the database in read only mode if possible (i.e. the apply had been terminated cleanly). If, as would be in your case, the apply was terminated in the middle of applying then the open would fail until redo apply had been restarted and cleaned up after itself. In any case, in 10g (10.1 and 10.2) restarting the apply would close the physical standby before starting the apply. As of 11g it will not close the standby as that is what is called Active Data Guard, the Apply running while the standby is open read only.
    Now, to answer your last question, getting it into managed recovery again. If you use the Broker it will take care of that for you. If you do not use the Broker then you need to execute the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE.... command manually.
    Larry

  • Restart-VM

    From the W2012 Host computer I want to schedule a restart of one of the VM. I have it working via this command however the 'force' syntax is not a graceful restart...
    Powershell.exe Restart-VM BNRVM1 -Force
    I would rather do a graceful restart and remove the -Force syntax and instead enter a Y when the prompt is trying to confirm that I want to restart.
    Can someone please advise on what the syntax is to have a Y entered instead of the -Force

    Hi Bnrtech,
    In addition, I found this function, which can help us to Gracefully Restart Virtual Machines on Hyper-V, please note I haven't tested:
    function Restart-VM {
    <#
    .SYNOPSIS
    Restarts one or more virtual machines by performing an orderly shutdown and startup sequence.
    .DESCRIPTION
    Restarts one or more virtual machines by performing an orderly shutdown and startup sequence.
    Shadows the built-in Restart-VM, which does not contain the same functionality.
    .PARAMETER Name
    A string array containing the name(s) of the virtual machine to restart.
    .PARAMETER ComputerName
    The name(s) of the computer(s) that host(s) the target virtual machine(s). If not specified, the local host will be used.
    .PARAMETER AsJob
    Places the restart operation in a job and returns immediately.
    Cannot be included with Passthru.
    .PARAMETER Force
    If the virtual machine is not running integration services, or if the integration services do not respond promptly, performs a Turn Off operation.
    If not specified, only virtual machines with responding integration services will be restarted.
    .PARAMETER VM
    The virtual machine object to be restarted.
    .PARAMETER Timeout
    Maximum number of seconds to wait for the target system to shut down gracefully before performing a Turn Off operation. Default is eternity.
    If multiple virtual machines are specified, each has its own separate timer.
    .PARAMETER ForceTimeout
    Number of seconds to wait for a forced turn off to work before assuming the worker process is hung. Default and minimum is 5 seconds.
    If multiple virtual machines are specified, each has its own separate timer.
    Has no effect if Force is not also specified.
    .PARAMETER Passthru
    Causes the script to emit a virtual machine object that represents the VM that was restarted.
    Cannot be included with AsJob.
    .OUTPUTS
    None by default.
    If -Passthru is specified, Microsoft.HyperV.PowerShell.VirtualMachine.
    If -AsJob is specified, System.Management.Automation.PSRemotingJob.
    .NOTES
    Author: Eric Siron
    Copyright: (C) 2014 Altaro Software
    Version 1.0.1
    Authored Date: November 15, 2014
    1.0.1 revision: November 26, 2014: Minor fix to timeout logic.
    .LINK
    http://www.altaro.com/hyper-v/free-script-restart-vm/
    .EXAMPLE
    C:\PS> Restart-VM svtest
    Description
    Restarts the virtual machine named test on the local host.
    .EXAMPLE
    C:\PS> Restart-VM svhungsystem -Force
    Description
    Restarts the virtual machine named svhungsystem on the local host even if it is not responding.
    .EXAMPLE
    C:\PS> Get-VM -Name svtrouble | Restart-VM -Force -ForceTimeout 30
    Description
    Forces the virtual machine named svtrouble to shut down, but extends the maximum wait time from 5 seconds to 30 seconds.
    .EXAMPLE
    C:\PS> Restart-VM svserver1, svserver2 -ComputerName svhv1 -Timeout 60
    Description
    Restarts VMs named svserver1 and svserver2 on Hyper-V host svhv1. If either does not shut down within 60 seconds, it is forcefully turned off.
    .EXAMPLE
    C:\PS> Get-ClusterVM | Restart-VM
    Description
    Using the output of Get-ClusterVM (another free script from Altaro), restarts all cluster VMs.
    #>
    [CmdletBinding(DefaultParameterSetName='ByName', SupportsShouldProcess=$true)]
    param(
    [Alias("VMName")]
    [Parameter(ValueFromPipeline=$true, ValueFromPipelineByPropertyName=$true, ParameterSetName='ByName', Mandatory=$true, Position=1)]
    [String[]]$Name,
    [Alias("VMHost")]
    [Parameter(ValueFromPipelineByPropertyName=$true, Position=2, ParameterSetName='ByName')]
    [String[]]$ComputerName = @(, $env:COMPUTERNAME),
    [Parameter(ValueFromPipelineByPropertyName=$true)]
    [Switch]$AsJob,
    [Parameter(ValueFromPipelineByPropertyName=$true)]
    [Switch]$Force,
    [Parameter(ValueFromPipeline=$true, ValueFromPipelineByPropertyName=$true, ParameterSetName='ByVM')]
    [Microsoft.HyperV.PowerShell.VirtualMachine[]]$VM,
    [Parameter(ValueFromPipelineByPropertyName=$true)]
    [UInt32]$Timeout = 0,
    [Parameter(ValueFromPipelineByPropertyName=$true)]
    [UInt32]$ForceTimeout = 5,
    [Parameter(ValueFromPipelineByPropertyName=$true)]
    [Switch]$Passthru
    BEGIN {
    ### Globals ###
    $JobList = @()
    ### Script blocks ###
    $RestartScript = {
    param(
    [Parameter(Position=1)][Object]$VMObject, # deserialized and cannot be used as a VM object
    [Parameter(Position=2)][UInt32]$Timeout,
    [Parameter(Position=3)][UInt32]$ForceTimeout,
    [Parameter(Position=4)][Switch]$Force,
    [Parameter(Position=5)][Switch]$Passthru
    ### Constants ###
    New-Variable -Name VMStateRunning -Value 2 -Option Constant
    New-Variable -Name VMStateTurnedOff -Value 3 -Option Constant
    New-Variable -Name MinimumForceTimeout -Value 5 -Option Constant
    ### Functions ###
    function TurnOff {
    param(
    [Parameter()][Object]$VMObject, # deserialized and cannot be used as a VM object
    [Parameter()][UInt32]$Timeout,
    [Parameter()][ValidateSet("Shutdown", "TurnOff")][String]$Mode
    switch($Mode)
    "Shutdown" {
    Stop-VM -ComputerName $VMObject.ComputerName -Name $VMObject.Name -Force
    "TurnOff" {
    Stop-VM -ComputerName $VMObject.ComputerName -Name $VMObject.Name -Force -TurnOff
    $TimeoutCounter = 0
    $Continue = $true
    while($Continue)
    Start-Sleep -Seconds 1
    $Continue = ((Get-WmiObject -Namespace root\virtualization\v2 -Class Msvm_ComputerSystem -ComputerName $VMObject.ComputerName -Filter "Name = '$($VMObject.VMId.Guid.ToString().ToUpper())'").EnabledState -ne $VMStateTurnedOff)
    if($Timeout -and $Continue)
    $TimeoutCounter++
    if($TimeoutCounter -ge $Timeout)
    $false
    return
    $true
    if($ForceTimeout -lt $MinimumForceTimeout) { $ForceTimeout = $MinimumForceTimeout }
    $ForceRequired = $true # this will be set off if a graceful shutdown is successful
    $StopAttempted = $false
    # output from get-vm isn't always reliable, ask WMI if the VM is on
    if((Get-WmiObject -Namespace root\virtualization\v2 -Class Msvm_ComputerSystem -ComputerName $VMObject.ComputerName -Filter "Name = '$($VMObject.VMId.Guid.ToString().ToUpper())'").EnabledState -eq $VMStateRunning)
    # The VM is on. Check for the shutdown integration service.
    $ShutdownIntegrationStatus = Get-VMIntegrationService -Name "Shutdown" -ComputerName $VMObject.ComputerName -VMName $VMObject.VMName
    if($ShutdownIntegrationStatus.Enabled)
    if($ShutdownIntegrationStatus.PrimaryOperationalStatus -eq "Ok")
    $StopAttempted = $true
    if(TurnOff -VMObject $VMObject -Timeout $Timeout -Mode "Shutdown")
    $ForceRequired = $false
    else
    Write-Warning "Graceful shutdown for $($VMObject.Name) was unsuccessful."
    if($Force -and $ForceRequired)
    $StopAttempted = $true
    Write-Verbose -Message "Attempting to turn off (hard shut down) $($VMObject.VMName) on $($VMObject.ComputerName)"
    if(-not(TurnOff -VMObject $VMObject -Timeout $ForceTimeout -Mode "TurnOff"))
    Write-Warning -Message "Unable to turn off $($VMObject.VMName)"
    if($ForceRequired -and -not $Force)
    Write-Warning -Message "VM $($VMObject.VMName) can only be restarted with the -Force switch"
    # start the VM if the script tried to turn it off and its status is off
    if((Get-WmiObject -Namespace root\virtualization\v2 -Class Msvm_ComputerSystem -ComputerName $VMObject.ComputerName -Filter "Name = '$($VMObject.VMId.Guid.ToString().ToUpper())'").EnabledState -eq $VMStateTurnedOff)
    Start-VM -ComputerName $VMObject.ComputerName -Name $VMObject.Name
    if($Passthru)
    # just passing the object back will return a deserialized object. allow the calling thread to retrieve the object
    [String]::Join(",", ($VMObject.Computername, $VMObject.Name))
    elseif($StopAttempted)
    Write-Error "VM $($VMObject.Name) cannot be started because it was not successfully turned off"
    PROCESS {
    if($Name -eq $null -and $VM -eq $null)
    throw("Must select at least one virtual machine to restart.")
    if($AsJob -and $Passthru)
    throw("AsJob and Passthru cannot be specified together")
    # if submitted by VM object, use as-is. otherwise retrieve VM objects
    if(-not $VM.Count)
    $VM = @()
    foreach($VMHost in $ComputerName)
    foreach($VMName in $Name) # $Name is the input parameter for virtual machine name(s)
    try
    Write-Verbose -Message "Checking for $VMName on $VMHost"
    $VM += Get-VM -ComputerName $VMHost -Name $VMName -ErrorAction Stop
    catch
    Write-Verbose -Message "No VM with the name $VMName is present on host $VMHost"
    foreach($VMObject in $VM)
    Write-Verbose -Message "Performing restart of $($VMObject.Name) on $($VMObject.ComputerName)"
    if($PSCmdlet.ShouldProcess("$($VMObject.Name) on $($VMObject.ComputerName)", "Restart"))
    $JobList += Start-Job -ScriptBlock $RestartScript -Name "Restart-VM-$($VMObject.ComputerName)-$($VMObject.Name)-$($VMObject.VMId)" -ArgumentList $VMObject, $Timeout, $ForceTimeout, $Force, $Passthru
    END {
    if($JobList)
    if($AsJob)
    $JobList
    else
    $ResultsArray = @()
    Wait-Job -Job $JobList | Out-Null
    foreach($Job in $JobList)
    $ResultsArray += Receive-Job -Job $Job
    $JobList | Remove-Job
    if($Passthru)
    foreach($Result in $ResultsArray)
    try
    $VMItem = $Result.Split(",")
    Get-VM -ComputerName $VMItem[0] -Name $VMItem[1] -ErrorAction Stop
    catch
    ; # really nothing to do about it
    else
    $ResultsArray
    Refer to:
    http://www.altaro.com/hyper-v/free-script-restart-virtual-machines-hyper-v/
    If there is anything else regarding this issue, please feel free to post back.
    Best Regards,
    Anna Wang
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Office 2013 Initiates Restart Remote Desktop Session Host

    We have a Windows Server 2008 R2 Remote Desktop Session Host that gracefully restarted on it's own today, logging off all of the users.  When it came back online I found the following event log:
    The process msiexec.exe has initiated the restart of computer ESDTS01 on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found
     Reason Code: 0x80030002
     Shutdown Type: restart
     Comment: The Windows Installer initiated a system restart to complete or continue the configuration of 'Microsoft Office Standard 2013'.
    I discovered that a new user had opened Outlook, and msiexec went through a configuration and prompted to restart the computer.  The user had clicked Yes, which prompted the server to restart.
    I can't seem to replicate the issue with a new user profile, and it seems to only have happened randomly with two users. What can I do to stop this?

    Hi,
    To my knowledge, this is not an Office specific issue, any updates that require a reboot might cause the issue. You might either want to disable the automatic Updates or disable the ability of non-admins to restart the system with a Group Policy.
    However, this is out of scope of this forum, I'd suggest you to seek assistance in the forum of
    Windows Server. Thanks for your understanding.
    Below links might be helpful, you might want to have a look:
    http://serverfault.com/questions/306133/how-can-i-prevent-terminal-server-users-from-restarting-the-server-after-an-auto
    http://superuser.com/questions/190448/disable-restart-after-update-prompt-for-server-2008-r2
    (Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee
    the accuracy of this information.)
    Thanks,
    Ethan Hua CHN
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Trouble with VRF traffic on ASR9000

    Hi We have a trouble to established  neighbord and pass tables from Cisco 7600 to ASR9000 when configure a vrf between both devices.
    the configuration on cisco 7600 is:
    router bgp 2006
    bgp router-id 172.16.110.97
    bgp log-neighbor-changes
    bgp graceful-restart restart-time 120
    bgp graceful-restart stalepath-time 360
    bgp graceful-restart
    neighbor 172.16.14.6 remote-as 64512
    address-family ipv4
      no synchronization
      redistribute connected
      neighbor 172.16.14.6 activate
      no auto-summary
    exit-address-family
    the configuration on Cisco ASR9000 (A) is:
    hostname ED_MEX_1
    logging console informational
    telnet vrf GW ipv4 server max-servers 15
    telnet vrf default ipv4 server max-servers 5
    cdp
    vrf GW
    description "CONEXION-GW"
    address-family ipv4 unicast
      import route-target
       64512:2006
      export route-target
       64512:2006
    vrf CAMPUS
    address-family ipv4 unicast
      import route-target
       64512:64513
      export route-target
       64512:64513
    interface GigabitEthernet0/2/0/19
    vrf GW
    ipv4 address 172.16.14.6 255.255.255.252
    interface Bundle-Ether202
    vrf CAMPUS
    ipv4 address 172.16.19.6 255.255.255.252
    router bgp 64512
    address-family vpnv4 unicast
    neighbor 172.16.14.5
      remote-as 2006
      address-family vpnv4 unicast
    neighbor 172.16.19.5
      remote-as 64513
      address-family vpnv4 unicast
    vrf GW
      rd 64512:2006
      address-family ipv4 unicast
       redistribute connected
       redistribute static
       route-policy pass-all in
       route-policy pass-all out
    vrf CAMPUS
      rd 64512:64513
      address-family ipv4 unicast
       redistribute connected
       redistribute static
       route-policy pass-all in
       route-policy pass-all out
    when we try to look the routing tables on ASR9000 only have the local connected network L and C on table
    RP/0/RSP1/CPU0:ED_MEX_1#sho route vrf all
    Wed May 15 11:07:29.268 UTC
    VRF: GW
    Codes: C - connected, S - static, R - RIP, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
           i - ISIS, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, su - IS-IS summary null, * - candidate default
           U - per-user static route, o - ODR, L - local, G  - DAGR
           A - access/subscriber, - FRR Backup path
    Gateway of last resort is not set
    C    172.16.14.4/30 is directly connected, 01:25:10, GigabitEthernet0/2/0/19
    L    172.16.14.6/32 is directly connected, 01:25:10, GigabitEthernet0/2/0/19
    VRF: CAMPUS
    Codes: C - connected, S - static, R - RIP, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
           i - ISIS, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, su - IS-IS summary null, * - candidate default
           U - per-user static route, o - ODR, L - local, G  - DAGR
           A - access/subscriber, - FRR Backup path
    Gateway of last resort is not set
    C    172.16.19.4/30 is directly connected, 00:22:05, Bundle-Ether202
    L    172.16.19.6/32 is directly connected, 00:22:05, Bundle-Ether202
    the diagram is this:
    thanks for your comments
    Best Regards

    Hi
    thanks for you cooperation the final configuration on devices that working is this:
    vrf GAT
    address-family ipv4 unicast
      import route-policy pass-all
      import route-target
       64512:2006
      export route-policy pass-all
      export route-target
       64512:2006
    interface GigabitEthernet0/2/0/19
    vrf GAT
    ipv4 address 172.16.14.6 255.255.255.252
    route-policy pass-all
      pass
    end-policy
    router bgp 64512
    bgp router-id 172.16.161.1
    address-family ipv4 unicast
    address-family vpnv4 unicast
    vrf GAT
      rd 64512:2006
      address-family ipv4 unicast
       redistribute connected
       redistribute static
      neighbor 172.16.14.5
       remote-as 2006
       address-family ipv4 unicast
        route-policy pass-all in
        route-policy pass-all out
    Regards

  • Assistance Needed: Inter-VRF Routing with MP-BGP

    hello everyone,
    I've been trying to solve a problem for over a day regarding inter-vrf routing using MP-BGP and I can't seem to figure a few things out.
    I have Cisco 1921 which has VRF-JLAN and VRF-JGLOBE with 3 interfaces configured as (g0/0 = vrf JLAN, g0/1=no vrf, g0/2 = dot1q trunk to 2960S). vrf JLAN is a restricted network for users access, dns server, e.t.c. vrf JGLOBE is for Video server and global routing table belongs to Wifi Access. I've been able to seperate all the network and I can route traffic out to the Internet from vrf JLAN and the global route table but where I'm having issues is getting vrf JGLOBE to route traffic using the Global route table.
    For example: vrf JLAN should not be accessed by either Global or vrf JGLOBE. JGLOBE should be able to access vrf JLAN dns server but it should route its internet traffic via Global route table (g0/1). Last JLAN should be able to access 2 networks from the Global route table.
    I've attached my config and diagram so you can better understand what I'm trying to achieve. More light to solving this problem would be much appreciated.
    ip vrf JGLOBE
     rd 65001:2
     export map WIFI
     route-target export 65001:2
    ip vrf JLAN
     rd 65001:1
     import ipv4 unicast map C-GLOBAL
     route-target export 65001:1
     route-target import 65001:1
     route-target import 65001:2
    interface GigabitEthernet0/0
     description LAN-ACCESS-INTERNET [TO Nexthop FIREWALL]
     ip vrf forwarding JLAN
     ip address 192.168.4.3 255.255.255.248
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip flow ingress
     ip flow egress
     ip inspect INTERNET-FW out
     ip virtual-reassembly in
     load-interval 30
     duplex auto
     speed auto
    interface GigabitEthernet0/1
     description GLOBAL-Wifi-INTERNET [TO Nexthop - FIREWALL]
     ip address 192.168.5.3 255.255.255.248
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip flow ingress
     ip flow egress
     ip inspect GLOBAL-FW in
     ip inspect GLOBAL-FW out
     ip virtual-reassembly in
     load-interval 30
     duplex auto
     speed auto
    interface GigabitEthernet0/2
     no ip address
     duplex auto
     speed auto
    interface GigabitEthernet0/2.3
     description Users LAN
     encapsulation dot1Q 3
     ip vrf forwarding JLAN
     ip address 192.168.30.1 255.255.255.240
    interface GigabitEthernet0/2.4
     description Video Server
     encapsulation dot1Q 4
     ip vrf forwarding JGLOBE
     ip address 10.6.40.1 255.255.255.0
    router ospf 1 vrf JLAN
     router-id 10.6.6.10
     redistribute bgp 65001 subnets
     network 0.0.0.0 255.255.255.255 area 0
    router ospf 2 vrf JGLOBE
     router-id 10.5.7.10
     redistribute bgp 65001 subnets
     network 0.0.0.0 255.255.255.255 area 0
    router bgp 65001
     bgp router-id 10.4.6.4
     bgp log-neighbor-changes
     bgp graceful-restart restart-time 120
     bgp graceful-restart stalepath-time 360
     bgp graceful-restart
     address-family ipv4
      redistribute connected
     exit-address-family
     address-family ipv4 vrf JGLOBE
      redistribute connected
      redistribute ospf 2
     exit-address-family
     address-family ipv4 vrf JLAN
      redistribute connected
      redistribute ospf 1
     exit-address-family
    ip dns view vrf JGLOBE default
    ip dns view vrf JLAN default
    ip route 0.0.0.0 0.0.0.0 192.168.5.1
    ip route vrf JGLOBE 0.0.0.0 0.0.0.0 GigabitEthernet0/1 192.168.5.1
    ip route vrf JLAN 0.0.0.0 0.0.0.0 192.168.4.1 name LAN_INET
    ip prefix-list GLOBAL-INET seq 5 permit 0.0.0.0/0
    ip prefix-list SERVER-NET seq 5 permit 10.6.40.2/32
    ip prefix-list WIFI-NET seq 5 permit 10.254.0.0/22 le 32

    Hi Matt
    Yes the X/32 routes needs to be present in the VRF Routing-Table and if they are to be learnt statically then the MP-iBGP config for that particular VRF address-family has to redistribute static routes as well.
    Regards
    Varma

  • BGP NSF

    Hello,
    1. Is NSF supported for BGP routing protocol? If so how to enable that?
    2. Can we configure both NSF and NSR for a same instance of IGP routing protocol? If so, which will have top priority(whether NSF or NSR)?
    Thanks
    Hari

    Hi Hari,
    because the a9k provides for a total distributed architecture, whereby the control plane is separated from teh forwarding, there is natively already NSF, so for that you dont have to configure anything.
    You can read up more on that topic if you like when you google asr9000 route scale architecture.
    NSR, that is bascially to keep a peering alive, while the standby sending the actual TCP packets (to keep the seq numbers in sync) is something that you configure separately via:
    rotuer bgp 100
    nsr
    Assisting in NSF can be the fucntionality of graceful restart (to maintain the session before declaring it down), and NSF is also implemented by nature via the functionality of SSO (stateful switchover).
    The concept of NSR is tricky and important, I have a write up for you here:
    The NSR implementation in XR relies on the use of the Standby RP. If the
    process were to fail/crash on the Active RP, unless control is passed to the
    Standby RP, NSR operation will not work - in effect it will then revert back to
    either Graceful-restart (if enabled) or a full process restart (peer down/adj
    down etc.). The process on the Active RP cannot recover state from the Standby
    RP. If you were to have a situation where the Active RP were to crash, then NSR
    functionality will kick-in as control will be passed to the Standby RP.
    The question is, do you only want NSR to occur in the event of an RP failure
    (which should be a rare occurrence)? If the answer is 'yes', then do no enable
    the configuration 'nsr process-failures switchover'. If the answer is 'no' and
    the customer understand that an RP failover is expected in the circumstances,
    then enable 'nsr process-failures switchover'. For some customer, the very idea
    of an RP failover is just 'bad' - for others, they are comfortable with this
    form of operation.
    There are only a few SPs using NSR today, since for many, the key driver has
    been BGP NSR which was only delivered in rls 3.8.0. We do have customers who
    are in service with NSR for OSPF and LDP and BGP - we have a good number of
    customers who are using ISIS with NSF CISCO (which is actually NSR), which was
    delivered back in rls 3.3.x. They do use the 'nsr process-failures switchover'
    since the RP failover is considered to be too rare an event.
    Without 'nsr process-failures switchover' enabled, NSR will only come into
    effect should the RP crash or an RP failover be manually triggered.
    Enabling this config will result in a failover being initiated if BGP, TCP, LDP
    or OSPF were to crash. Since an FO is immediately triggered to preserve NSR, a
    core-dump of the crashed process will not be available. If diagnosing such a
    crash is more important for the customer, then this knob should not be turned
    on.
    xander

Maybe you are looking for