BGP ipv6 Implementation

We started to test dual-stack bgp implementation. although we established neighbour over ipv6, seems still we couldnt advertise our networks on internet and we couldnt reach anywhere over ipv6 address.
Here our related configs and outputs;
router bgp 3xxx
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 2A02:E0:0:xx::1 remote-as 34xxx
neighbor x.x.x.x remote-as 34xxx
neighbor x.x.x.x remote-as 91xx
maximum-paths 4
address-family ipv4
exit-address-family
address-family ipv6
  neighbor 2A02:E0:0:xx::1 activate
  neighbor 2A02:E0:0:xx::1 prefix-list v6in in
  neighbor 2A02:E0:0:xx::1 prefix-list v6out out
  network 2001:67C:xxxx::/48
  no synchronization
exit-address-family
ipv6 prefix-list v6in seq 5 permit ::/0 le 128
ipv6 prefix-list v6out seq 5 permit 2001:67C:xxxx::/48
interface GigabitEthernet0/2
ip address 92.45.xxx.x 255.255.255.252
no ip redirects
no ip proxy-arp
ip flow ingress
load-interval 30
duplex auto
speed auto
media-type rj45
negotiation auto
ipv6 address 2A02:E0:0:xx::2/126
ipv6 enable
7200-1_KULE#sh bgp ipv6 unicast
BGP table version is 4, local router ID is 212.156.xx.xx
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*> ::/0             2A02:E0:0:xx::1                        0 34xx 34xx 130xx 94xx i
What we supposed to do ?
Best regards.

Yes, we have three  C class networks and one of them is used for firewall side.
May i ask aother question?
On ipv4 bgp conf. we use route maps for coming and outgoing traffic on 3 different metro ethernet internet connections. We have 3 c class ipv4. so we configured load sharing for each networks between net connections. We use local-pref, weight or as path prepend.
Could we do the same thing for ipv6 connections ? We have ::/48 . for example we want to use ::/56 and share networks on internet lines. 
Best regards

Similar Messages

  • IPv6 implementation on WLC ( 7.2.103) along with ISE

    Has any one done the ipv6 implementation on Wireless Network with user Authentication for guest access using ISE 1.1.
    My customer has following componets in the wireless network .
    1. WLC  5508 with 7.2.103 version
    2. ISE 1.1
    Please forward the steps required for integrating ISE as CWA  guest portal for ipv6 .

    The Cisco Identity Services Engine, Release 1.1, is not compliant with IPv6.

  • "sh ip bgp ipv6" or "sh bgp ipv6"

    Hi All,
    im trying to clarify some confusion with where this is going in terms of show commands for bgp
    when i first played with ipv6 bgp in 12.3 years back, the only way to view bgp v6 items was via "sh bgp ipv6", and this as far as i recall was meant to be the way forward for v4 too, and 'sh ip bgp' was to be removed in future ios releases.
    Now im looking at SRE5 in the lab, and a 'sh bgp ipv6' gives me not output saying its deprecated, and 'show ip bgp ipv4' shows me all v4 and v6 bgp neighbour sessions.
    if anyone can anyone shed some light on this it would be great since its a tad confusing, even more when you add vpnv4 to the mix.
    thanks
    Mark

    Mark,
    Let me try to answer your question like this.
    As far as I know. Both commands are still valid (check int recent 15.2.1T release).
    R2#show bgp ipv6 unicastBGP table version is 2, local router ID is 192.168.23.2Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,              r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-FilterOrigin codes: i - IGP, e - EGP, ? - incomplete   Network          Next Hop            Metric LocPrf Weight Path*> 2001:DB8:2::/64  ::                       0         32768 iR2#show ip bgp ipv6 unicastBGP table version is 2, local router ID is 192.168.23.2Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,              r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-FilterOrigin codes: i - IGP, e - EGP, ? - incomplete   Network          Next Hop            Metric LocPrf Weight Path*> 2001:DB8:2::/64  ::                       0         32768 i
    What is deprecated is the command without "unicast" added.
    R2#show ip bgp ipv6% Incomplete command.R2#show bgp ipv6BGP table version is 3, local router ID is 192.168.23.2Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,              r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-FilterOrigin codes: i - IGP, e - EGP, ? - incomplete   Network          Next Hop            Metric LocPrf Weight Path*> 2001:DB8:2::/64  ::                       0         32768 i% NOTE: This command is deprecated. Please use 'show bgp ipv6 unicast'
    I'm not aware of anything specific to SRE that would cause it to be different.
    Can you make share same outputs from your devices?
    M.

  • IPv6 in a big corporate

    Hi,
    does anybody here have a practical experience with IPv6 implementing within a big corporate network?
    Let's say the corporate has got several thousands of sites, some of them in Europe, others in Asia and Americas.
    20 Data Centers are used for the Internet connectivity.
    So what kind of IPv6 addresses should it use?
    As all IPv6 documents are saying "Don't think about ULA and NAT, use GUA!", it should try to get PI (Provider Independent) addresses, I guess?
    Looking to RIPE web pages (http://www.ripe.net/ripe/docs/ripe-452) I found only an info it's necessary to have a contract with a LIR to get some PI addresses but no details :-(
    How big could such a block be? /32?
    But is it possible to use one PI address block worldwide?
    I don't think so, as ISPs in America would not accept prefixes provided by RIPE, I'm afraid?
    So the corporate should try to get a PI block from each RIR (RIPE, APNIC, ARIN, ...)?
    Even then with /32 PI per continent available, it would be necessary to advertise only some more specific subnet from each DC probably?
    Let's say /36?
    But would /36 be accepted by the ISPs connecting the DCs to the Internet?
    And propagated to the neighboring ASes?
    I've been told /32 is the maximum prefix length accepted? (But using an IPv6 looking glass I can see lots of /48s among the current IPv6 BGP prefixes within the Internet?).
    So it would be necessary to use a single ISP per continent?
    Even when all mentioned above would work, it would be necessary to advertise the default route into the corporate network a very sophisticated way to ensure all /36 clients would use the correct DC to enter the Internet to avoid an asymmetric routing!
    So I'd really like to discuss with somebody who fixed all the issues listed above already!
    Thanks,
    Milan

    Hi Milan,
    I Did get a chance to be a member of  deployment of  such network for  a customer ,and he had multiple AS as well as IPv6 addresses from RIRs .The RIRs are willing to give a /32 without much concern based upon simple justifications.The equivalent of a /24 IPv4 being advertised to the internet is a /48 in IPv6 world (This is the lowest any enterprise would get).
    Regarding the inter-connectivity between the various sites and the path to the internet via the DC ,it would depend upon the architecture you have in mind.I mean if you have a Service provider MPLS backbone,provider independent inter-connectivity over the internet. 
    We used service provider backbone with multiple layers of route reflectors connectivity from the DCs to the sites and then diverting traffic to the nearest site.
    However we could discuss in detail what exact scenario lies for your case.

  • Enabling iBGP IPv6

    Hi All,
    I would like to check if to implement iBGP IPv6 the config showed below is enough and/or commands needs to be changed/removed/added:
    ===========================================================================
    current BGP (IPv4) config
    ===========================================================================
    router bgp 55555
     no synchronization
     bgp router-id 10.10.10.1
     no bgp log-neighbor-changes
     network 1x.x.x.0 mask 255.255.255.248
     network 1z.z.z.8 mask 255.255.255.248
     network 1y.y.32 mask 255.255.255.248
     neighbor 1x.x.x.113 remote-as 55555
     neighbor 1x.x.x.113 description WWWW
     neighbor 1x.x.x.113 update-source Port-channel4
     neighbor 1x.x.x.113 next-hop-self
     neighbor 1x.x.x.113 soft-reconfiguration inbound
     no auto-summary
    ===========================================================================
    adding BGP (IPv6) config
    ===========================================================================
    router bgp 262814
    no bgp default ipv4-unicast
    address-family ipv6 unicast
       neighbor 2x:270:ff:ff01::2 remote-as 55555
       neighbor 2x:270:ff:ff01::2 description WWWW
       neighbor 2x:270:ff:ff01::2 update-source Port-channel4
       neighbor 2x:270:ff:ff01::2 next-hop-self
       neighbor 2x:270:ff:ff01::2 soft-reconfiguration inbound
       neighbor 2x:270:ff:ff01::2 activate
       network 2x:270::/40
       no auto-summary
    ===========================================================================
    Thanks,
    Marcelo

    Hello.
    Neighbour configuration should be done under router mode, then you activate per neighbour under address-family ipv6.

  • Firmware upgrade for WRT120N to support IPV6?

    IPV4 IP addresses will be running out in less than a year and I wanted to know, will there be a firmware update for WRT120N to support IPV6?
    If not, why?
    Also, if I have to buy another router to support IPV6, I'm going to buy a D-Link. It's nothing personal, I just find it absolutely idiotic that a router that supports wireless-N doesn't support IPV6. You have to ask your self, how does the standard IPV6 spec thats a few years old not make it to the final product of a router, but a non-standard wireless-N spec implementation somehow got the O.K....?

    If you want to know about a firmware update you have to call Linksys support. You won't get an official answer here.
    It's absolutely not ridiculous. Maybe IPv6 implementations are around for a while. But it was mostly basic routing and connectivity. All major companies only started maybe two or three years ago to fully support IPv6 in their pro devices. Before that, IPv6 was usually an update not included in the base firmwares. Often it was a paid option. And even today you'll find IPv6 not really equally supported in high-end firewalls which is why some companies are even now reluctant to deploy IPv6 because they are afraid to weaken their firewalls...
    And you write yourself: your provider is testing IPv6 now. Isn't that ridiculous, too?
    And even today you'll find many client devices in stores which don't at all support IPv6, yet, for instance printers, VoIP phones...
    Thus which consumer brand do you think is so much more trustful? And to work perfectly on an Internet connection where even your ISP is still in test phase?

  • IPv6 on Webservers

    Hi,
    I wanted to deploy IPv6 services on my all webservers m not having idea to deploy IPv6 on web servers like IIS or Apache .
    Could someone help me into this concern.

    Hi Nick,
    cheers for the response.
    We've been running ipv6 capable smtp servers for the past three years and have had ipv6 implemented across the rest of our infrastructure since 2003.
    While I appreciate that ipv6 users may be in the minority at the moment that situation will change over the next few years.
    One of the reasons that we went with Ironport was the fact that we were told
    that v6 would be implemented in Q4 '08.
    Just wondering if this is likely to happen in the foreseeable future.
    Regards,
    Ronan

  • IPv6 on AsyncOS

    Any roadmap to support IPv6 on AsyncOS?
    Thanks.

    Hi Nick,
    cheers for the response.
    We've been running ipv6 capable smtp servers for the past three years and have had ipv6 implemented across the rest of our infrastructure since 2003.
    While I appreciate that ipv6 users may be in the minority at the moment that situation will change over the next few years.
    One of the reasons that we went with Ironport was the fact that we were told
    that v6 would be implemented in Q4 '08.
    Just wondering if this is likely to happen in the foreseeable future.
    Regards,
    Ronan

  • IPv6 traffic inspection on AIP SSM20

    Hi fellas!
    I'm a little confused. It says that for the ASA AIP SSM-20 it has ipv6 support. Yet when I look for how to do it, it says that the ASA's Modular Policy Framework does not support ipv6. Any bright ideas on this one?
    http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807335ca.shtml
    Sent from Cisco Technical Support iPad App

    ooooo boy. I might just need to raise a query case for this. There's gonna be a meeting on how to proceed with ipv6 implementation soon and I need to know if this baby can really dance to ipv6's tune.
    Sent from Cisco Technical Support iPad App

  • Getting ipv4 loop-back address on a pure ipv6 solaris machine

    import java.net.*;
    public class x {
    public static void main (String [] args) {
    try {
    //System.setProperty("java.net.preferIPv4Stack", "false");
    //InetAddress ia= InetAddress.getByName("::1");
    InetAddress ia= InetAddress.getByName(null);
    //InetAddress ia= InetAddress.getLocalHost();
    System.out.println(ia.getHostName());
    System.out.println(ia.getHostAddress());
    ServerSocket ss= null;
    ss = new ServerSocket(7833,1,ia);
    } catch(Exception e){
    e.printStackTrace();
    The above program generates the following exception.
    Machine: pure ipv6
    OS : SunOS uni6505l1-sun1 5.10 Generic sun4u sparc SUNW,Sun-Fire-V440
    I never had any ipv4 address listed when I did ifconfig -a, nor I have any ipv4 address in my /etc/hosts or /etc/hostname6.*
    java.net.BindException: Cannot assign requested address
    at java.net.PlainSocketImpl.socketBind(Native Method)
    at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
    at java.net.ServerSocket.bind(ServerSocket.java:319)
    at java.net.ServerSocket.<init>(ServerSocket.java:185)
    at x.main(x.java:12)
    Actually this is a part of my bigger problem with Tomcat6, which tries to listen on hard-coded ipv4 loop-back address for its shutdown port. As my machine is pure IPv6, or at least has above configuration, it fails to create a socket on 127.0.0.1, but, the above program returns me a 127.0.0.1 if I call InetAddress.getByName(null).
    My question is, why is it returning 127.0.0.1, when I never had it as my loop-back address, I had ::1 configured.
    Thanks,

    Accoridng to my expereince, JDK 5/6 maybe uses 127.0.0.1 when creating the serversocket.
    I tried it on a Windows 2008 RC box. If I disable the IPv4 by "netsh interface ipv4 uninstall" so that "127.0.0.1" is not accessible, I can not create the ServerSocket any more.
    However, If I disable the IPv4 by unchecking the IPv4 stack in the network property so that "127.0.0.1" is still accessible, the Serversocket can work for me.
    You can try to enable the "127.0.0.1" on your Sun box and run your code again.
    I also find that this issue may be fixed in JDK 7 beta. You can also try the JDK 7 beta with your code.
    http://bugs.sun.com/view_bug.do?bug_id=6379550
    It is known that JDK 5/6 has big issues on Windows Vista/2008 because of the IPv6 implementation. I am wondering whether Sun OS has the similar problem.

  • IPv6 EBGP

    I have a EBGP-peering connecting two AS with both address-family ipv4 and ipv6 but the prefixes advertized from each AS does get dropped by the other end of the session by local policy:
    "MP_REACH NEXT_HOP Martian: n/a 2239"
    The BGP session is set up between the IPv4 addresses on the link.
    What does this message in "sh ip bgp ipv6 unicast neighbors" mean? Why isn?t the IPv6 prefixes accepted?

    The impact of running two sessions is obviously that you will consume more resources on the box. It might not make a difference if you only have a handful of peers.
    One more thing to remember. If you are going to use the v4 session to carry v6 prefixes between iBGP peers, you will need to explicitly set the v6 NH using a route-map. Otherwise, the NH will be the v4 of the iBGP peer and it will not work.
    As for best practices, in my experience, people are most of the time using a v6 session to carry v6 updates.
    Hope this helps,

  • IPv6 Support Needed

    I am bewildered to see that the first posting about the need for IPv6 support in Linksys routers was made in August of 2006.  It is now April 2010, and there is still very little (if any) support for IPv6 in Linksys routers.
    In case nobody was paying attention--the IPv4 address space will be exhausted next year!  Heelloo--wake up!
    We need robust IPv6 implementation support now if we're going to have our app's ready to go when there will be no alternative.

    Comcast starts trial testing of IPv6 with customers in June.  It's time to stop putting it off and get IPv6 support into the firmware.

  • Link Local BGP peering between Cisco and Juniper (M-Series)

    Hi,
    has anybody successfully managed to get a working IPv6 session between a Cisco and a Juniper router using Link Local IPs?
    I got it working between two cisco routers and two Juniper Routers but not with the two different vendors.
    Configuration on the Juniper site:
       family inet6 {
           address FE80::1/64;
      protocols {
          bgp {
              group customer_ipv6 {
                  neighbor fe80::2 {
                      local-interface at-2/0/0.119;
                      peer-as 65300;
                      as-override;
    Configuration on the Cisco site:
    interface ATM0/0/0.1 point-to-point
    bandwidth 2033
    ip address 10.194.235.42 255.255.255.252
    ip access-group AL-SECURITY-WAN out
    ip mtu 1500
    ipv6 address FE80::2 link-local
    ipv6 enable
    bfd interval 999 min_rx 999 multiplier 15
    pvc 1/32
      vbr-nrt 2244 2244 1
      tx-ring-limit 3
      encapsulation aal5snap
    router bgp 65300
    bgp router-id 10.213.58.185
    bgp log-neighbor-changes
    no bgp default ipv4-unicast
    neighbor FE80::1%ATM0/0/0.1 remote-as 65300
    neighbor FE80::1%ATM0/0/0.1 version 4
    neighbor FE80::2%GigabitEthernet0/1 remote-as 65300
    neighbor FE80::2%GigabitEthernet0/1 version 4
    address-family ipv4
    exit-address-family
    address-family ipv6
      neighbor FE80::1%ATM0/0/0.1 activate
      neighbor FE80::1%ATM0/0/0.1 advertisement-interval 5
      neighbor FE80::1%ATM0/0/0.1 soft-reconfiguration inbound
      neighbor FE80::1%ATM0/0/0.1 route-map NH6 out
      neighbor FE80::2%GigabitEthernet0/1 activate
      neighbor FE80::2%GigabitEthernet0/1 advertisement-interval 5
      neighbor FE80::2%GigabitEthernet0/1 soft-reconfiguration inbound
      neighbor FE80::2%GigabitEthernet0/1 route-map NH6 out
    exit-address-family
    CE_HOSTNAME# show ip bgp ipv6 uni su
    BGP router identifier 10.213.58.185, local AS number 65300
    BGP table version is 7, main routing table version 7
    4 network entries using 656 bytes of memory
    4 path entries using 320 bytes of memory
    1/1 BGP path/bestpath attribute entries using 128 bytes of memory
    2 BGP AS-PATH entries using 48 bytes of memory
    2 BGP community entries using 48 bytes of memory
    0 BGP route-map cache entries using 0 bytes of memory
    0 BGP filter-list cache entries using 0 bytes of memory
    BGP using 1200 total bytes of memory
    BGP activity 34/12 prefixes, 38/12 paths, scan interval 60 secs
    Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
    FE80::1%ATM0/0/0.1
                    4        65300       0       0        1    0    0 never    Idle
    FE80::2%GigabitEthernet0/1
                    4        65300      15      16        7    0    0 00:10:59        4
    CE_HOSTNAME#
    The console monitoring states the following:
    Nov 10 06:30:33.023 MET: %BGP-3-NOTIFICATION: sent to neighbor FE80::1%ATM0/0/0.1 active 2/7 (unsupported/disjoint capability) 0 bytes
    Nov 10 06:30:33.023 MET: %BGP-4-MSGDUMP: unsupported or mal-formatted message received from FE80::1%ATM0/0/0.1:
    FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 001D 0104 505A 005A 52D2 C023 00
    Nov 10 06:30:33.023 MET: %BGP-3-NOTIFICATION: received from neighbor FE80::1%ATM0/0/0.1 active 2/5 (authentication failure) 0 bytes
    de-ipc-ulmdon-ce-02#
    Nov 10 06:30:33.023 MET: %BGP_SESSION-5-ADJCHANGE: neighbor FE80::1%ATM0/0/0.1 IPv6 Unicast topology base removed from session  BGP Notification sent
    The Cisco Router is running IOS 15.2, the Juniper Site JunOS 10.4
    Any Ideas how I can get this to work?
    Thanks in advance!

    Marcin,
    I updated the debugging log, the previous one was created using override-capability-neg on the neighbor (experimental).
    >>0) Do you see similar scenario for working session? (Between two Cisco routers)
    The working connection between two cisco routers doesn't show any output
    >>1) What verion of IOS are you running? Something failrly recent I hope?
    Show Version:
    Cisco IOS Software, C1900 Software (C1900-UNIVERSALK9-M), Version 15.2(1)T1, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2011 by Cisco Systems, Inc.
    Compiled Mon 19-Sep-11 16:24 by prod_rel_team
    ROM: System Bootstrap, Version 15.0(1r)M9, RELEASE SOFTWARE (fc1)
    CE_HOSTNAME uptime is 2 weeks, 5 days, 21 hours, 35 minutes
    System returned to ROM by reload at 18:43:21 MET(S) Fri Oct 21 2011
    System restarted at 18:44:50 MET(S) Fri Oct 21 2011
    System image file is "flash:c1900-universalk9-mz.SPA.152-1.T1.bin"
    Last reload type: Normal Reload
    Last reload reason: Reload Command
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    [email protected].
    Cisco CISCO1941/K9 (revision 1.0) with 446464K/77824K bytes of memory.
    Processor board ID FCZ1504C0G8
    1 DSL controller
    2 Gigabit Ethernet interfaces
    1 ATM interface
    1 terminal line
    DRAM configuration is 64 bits wide with parity disabled.
    255K bytes of non-volatile configuration memory.
    250880K bytes of ATA System CompactFlash 0 (Read/Write)
    License Info:
    License UDI:
    Device#   PID                   SN
    *0        CISCO1941/K9          FCZ1504C0G8
    Technology Package License Information for Module:'c1900'
    Technology    Technology-package           Technology-package
                  Current       Type           Next reboot
    ipbase        ipbasek9      Permanent      ipbasek9
    security      None          None           None
    data          datak9        Permanent      datak9
    Configuration register is 0x2102
    >>2) Can we have some more info from Juniper side (logs/debugs).
    Sadly not. The Juniper Traceoptions don't show anything
    All I can offer you at this point is the neighbor show command:
    user@Juniper> show bgp neighbor fe80::2 instance vrf-test
    Peer: fe80::2 AS 65300         Local: unspecified AS 20570
      Type: External    State: Idle           Flags:
      Last State: NoState       Last Event: NoEvent
      Last Error: None
      Export: [ pol-standard-bgp-export ] Import: [ pol-standard-bgp-import ]
      Options:
      Options:
      Address families configured: inet6-unicast
      Path-attributes dropped:  128
      Holdtime: 90 Preference: 170
      Number of flaps: 0
      Trace options:  all
      Trace file: /var/log/bgp_ipv6_ll_20111110 size 131072 files 10
    user@Juniper> show bgp summary instance vrf-test
    Groups: 2 Peers: 2 Down peers: 1
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    vrf-2.inet.0          37         16          0          0          0          0
    vrf-.inet6.0           0          0          0          0          0          0
    vrf-24.mdt.0           0          0          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    10.194.235.42         65300       1149       1076       0       1     8:44:00 Establ
      vrf-test.inet.0: 6/7/7/0
    fe80::2               65300          0          0       0       0     9:38:32 Idle
    >>3)
    CE_HOSTNAME#
    Nov 10 15:35:49.574 MET: BGP: ses global 10.194.235.41 (0x2970EDA4:1) Keep alive timer fired.
    Nov 10 15:35:49.574 MET: BGP: 10.194.235.41 KEEPALIVE requested (bgp_keepalive_timer_expired)
    Nov 10 15:35:49.574 MET: BGP: ses global 10.194.235.41 (0x2970EDA4:1) service keepalive IO request.
    Nov 10 15:35:49.574 MET: BGP: 10.194.235.41 KEEPALIVE write request serviced in BGP_IO
    CE_HOSTNAME#
    Nov 10 15:35:50.598 MET: BGP: ses global FE80::2%GigabitEthernet0/1 (0x316FBDDC:1) Keep alive timer fired.
    Nov 10 15:35:50.598 MET: BGP: FE80::2%GigabitEthernet0/1 KEEPALIVE requested (bgp_keepalive_timer_expired)
    Nov 10 15:35:50.598 MET: BGP: ses global FE80::2%GigabitEthernet0/1 (0x316FBDDC:1) service keepalive IO request.
    Nov 10 15:35:50.598 MET: BGP: FE80::2%GigabitEthernet0/1 KEEPALIVE write request serviced in BGP_IO
    CE_HOSTNAME#
    Nov 10 15:35:52.850 MET: BGP: 10.194.235.41 received KEEPALIVE, length (excl. header) 0
    CE_HOSTNAME#
    Nov 10 15:35:54.694 MET: BGP: FE80::1%ATM0/0/0.1 active went from Idle to Active
    Nov 10 15:35:54.694 MET: BGP: FE80::1%ATM0/0/0.1 open active, local address FE80::2
    Nov 10 15:35:54.698 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Adding topology IPv6 Unicast:base
    Nov 10 15:35:54.698 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Send OPEN
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active went from Active to OpenSent
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active sending OPEN, version 4, my as: 65300, holdtime 180 seconds, ID AD53AB9
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active KEEPALIVE write request serviced in BGP_IO
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active service 2 read request in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active KEEPALIVE write request serviced in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active service 2 read request in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active service 2 read request in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv message type 1, length (excl. header) 10
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Receive OPEN
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv OPEN, version 4, holdtime 90 seconds
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv OPEN w/ OPTION parameter len: 0
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active went from OpenSent to Closing
    Nov 10 15:35:54.702 MET: %BGP-3-NOTIFICATION: sent to neighbor FE80::1%ATM0/0/0.1 active 2/7 (unsupported/disjoint capability) 0 bytes
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Send NOTIFICATION 2/7 (unsupported/disjoint capability) 0 bytes
    Nov 10 15:35:54.702 MET: %BGP-4-MSGDUMP: unsupported or mal-formatted message received from FE80::1%ATM0/0/0.1:
    FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 001D 0104 505A 005A 52D2 C023 00
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv message type 3, length (excl. header) 2
    Nov 10 15:35:54.702 MET: %BGP-3-NOTIFICATION: received from neighbor FE80::1%ATM0/0/0.1 active 2/5 (authentication failure) 0 bytes
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Receive NOTIFICATION 2/5 (authentication failure) 0 bytes
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active bad state change from Closing to Closing
    Nov 10 15:35:54.702 MET: -Traceback= 21B3370Cz 21B33C74z 21B34258z
    Nov 10 15:35:54.702 MET: BGP: tbl IPv4 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl IPv6 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl VPNv4 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl VPNv6 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl IPv4 Multicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) NSF delete stale NSF not active
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) NSF no stale paths state is NSF not active
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) Resetting ALL counters.
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active closing
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Session close and reset neighbor FE80::1%ATM0/0/0.1 topostate
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) Resetting ALL counters.
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active went from Closing to Idle
    Nov 10 15:35:54.702 MET: %BGP_SESSION-5-ADJCHANGE: neighbor FE80::1%ATM0/0/0.1 IPv6 Unicast topology base removed from session  BGP Notification sent
    CE_HOSTNAME#CE_HOSTNAME#
    Nov 10 15:35:49.574 MET: BGP: ses global 10.194.235.41 (0x2970EDA4:1) Keep alive timer fired.
    Nov 10 15:35:49.574 MET: BGP: 10.194.235.41 KEEPALIVE requested (bgp_keepalive_timer_expired)
    Nov 10 15:35:49.574 MET: BGP: ses global 10.194.235.41 (0x2970EDA4:1) service keepalive IO request.
    Nov 10 15:35:49.574 MET: BGP: 10.194.235.41 KEEPALIVE write request serviced in BGP_IO
    CE_HOSTNAME#
    Nov 10 15:35:50.598 MET: BGP: ses global FE80::2%GigabitEthernet0/1 (0x316FBDDC:1) Keep alive timer fired.
    Nov 10 15:35:50.598 MET: BGP: FE80::2%GigabitEthernet0/1 KEEPALIVE requested (bgp_keepalive_timer_expired)
    Nov 10 15:35:50.598 MET: BGP: ses global FE80::2%GigabitEthernet0/1 (0x316FBDDC:1) service keepalive IO request.
    Nov 10 15:35:50.598 MET: BGP: FE80::2%GigabitEthernet0/1 KEEPALIVE write request serviced in BGP_IO
    CE_HOSTNAME#
    Nov 10 15:35:52.850 MET: BGP: 10.194.235.41 received KEEPALIVE, length (excl. header) 0
    CE_HOSTNAME#
    Nov 10 15:35:54.694 MET: BGP: FE80::1%ATM0/0/0.1 active went from Idle to Active
    Nov 10 15:35:54.694 MET: BGP: FE80::1%ATM0/0/0.1 open active, local address FE80::2
    Nov 10 15:35:54.698 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Adding topology IPv6 Unicast:base
    Nov 10 15:35:54.698 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Send OPEN
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active went from Active to OpenSent
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active sending OPEN, version 4, my as: 65300, holdtime 180 seconds, ID AD53AB9
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active KEEPALIVE write request serviced in BGP_IO
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active service 2 read request in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active KEEPALIVE write request serviced in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active service 2 read request in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active service 2 read request in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv message type 1, length (excl. header) 10
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Receive OPEN
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv OPEN, version 4, holdtime 90 seconds
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv OPEN w/ OPTION parameter len: 0
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active went from OpenSent to Closing
    Nov 10 15:35:54.702 MET: %BGP-3-NOTIFICATION: sent to neighbor FE80::1%ATM0/0/0.1 active 2/7 (unsupported/disjoint capability) 0 bytes
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Send NOTIFICATION 2/7 (unsupported/disjoint capability) 0 bytes
    Nov 10 15:35:54.702 MET: %BGP-4-MSGDUMP: unsupported or mal-formatted message received from FE80::1%ATM0/0/0.1:
    FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 001D 0104 505A 005A 52D2 C023 00
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv message type 3, length (excl. header) 2
    Nov 10 15:35:54.702 MET: %BGP-3-NOTIFICATION: received from neighbor FE80::1%ATM0/0/0.1 active 2/5 (authentication failure) 0 bytes
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Receive NOTIFICATION 2/5 (authentication failure) 0 bytes
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active bad state change from Closing to Closing
    Nov 10 15:35:54.702 MET: -Traceback= 21B3370Cz 21B33C74z 21B34258z
    Nov 10 15:35:54.702 MET: BGP: tbl IPv4 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl IPv6 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl VPNv4 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl VPNv6 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl IPv4 Multicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) NSF delete stale NSF not active
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) NSF no stale paths state is NSF not active
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) Resetting ALL counters.
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active closing
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Session close and reset neighbor FE80::1%ATM0/0/0.1 topostate
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) Resetting ALL counters.
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active went from Closing to Idle
    Nov 10 15:35:54.702 MET: %BGP_SESSION-5-ADJCHANGE: neighbor FE80::1%ATM0/0/0.1 IPv6 Unicast topology base removed from session  BGP Notification sent
    CE_HOSTNAME#

  • IPv6 in Merlin (JDK 1.4)

    Hi there
    I have tried to play with the IPv6 implementation of Java 1.4
    Well, it works, locally.
    As soon as I try to establish remote, nothin happens, even no exception or error.
    I use Win2k with a protocol stack developed at University of Lancaster.
    The IPv6 address I try to use is 2000::102.
    Are there any hints?
    Thanks
    Bjoern

    When you say IPv6 on Windows 2000 I assume you mean the research/preview seperate stack implementation - this is not supported by J2SE 1.4. In order to test with IPv6 you need to use Linux (rebuild kernel to include IPv6), or Solaris 8.

  • BGP Troublshooting

    I have configured network contaion  3 routers R1----R2-----R3, router 2 & 3 connected together via EBGP direct connect & router 1 & 2 connect together via IBGP , I have Advertise the follwoing networks 10.10.10.0, 20.20.20.0, 30.30.30.0, from router 3 to router 2 , the problem is i have the previous subnets in my router 1 but i cannot ping to it also when i have turn on debug ip BGP events i have the follwoing massage :
    Mar  5 15:34:30.063: BGP: Regular scanner event timer
    *Mar  5 15:34:30.063: BGP: Import timer expired. Walking from 1 to 1
    *Mar  5 15:34:45.063: BGP: Regular scanner event timer
    *Mar  5 15:34:45.063: BGP: Performing BGP general scanning
    *Mar  5 15:34:45.063: BGP(0): scanning IPv4 Unicast routing tables
    *Mar  5 15:34:45.063: BGP(IPv4 Unicast): Performing BGP Nexthop scanning for general scan
    *Mar  5 15:34:45.067: BGP(0): Future scanner version: 70, current scanner version: 69
    *Mar  5 15:34:45.067: BGP(1): scanning IPv6 Unicast routing tables
    *Mar  5 15:34:45.071: BGP(IPv6 Unicast): Performing BGP Nexthop scanning for general scan
    *Mar  5 15:34:45.071: BGP(1): Future scanner version: 71, current scanner version: 70
    *Mar  5 15:34:45.071: BGP(2): scanning VPNv4 Unicast routing tables
    *Mar  5 15:34:45.071: BGP(VPNv4 Unicast): Performing BGP Nexthop scanning for general scan
    *Mar  5 15:34:45.071: BGP(2): Future scanner version: 71, current scanner version: 70
    *Mar  5 15:34:45.071: BGP(4): scanning IPv4 Multicast routing tables
    *Mar  5 15:34:45.075: BGP(IPv4 Multicast): Performing BGP Nexthop scanning for general scan
    *Mar  5 15:34:45.075: BGP(4): Future scanner version: 71, current scanner version: 70
    *Mar  5 15:34:45.075: BGP(5): scanning IPv6 Multicast routing tables
    *Mar  5 15:34:45.075: BGP(IPv6 Multicast): Performing BGP Nexthop scanning for general scan
    *Mar  5 15:34:45.075: BGP(5): Future scanner version: 71, current scanner version: 70
    Best Regards

    Hi Ven :
    ( Router 3)
    MAIN-SOURSE#show ip bgp
    BGP table version is 4, local router ID is 40.40.40.1
    Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
                  r RIB-failure, S Stale
    Origin codes: i - IGP, e - EGP, ? - incomplete
       Network          Next Hop            Metric LocPrf Weight Path
    *> 20.20.20.0/32    0.0.0.0                  0         32768 i
    *> 30.30.30.0/32    0.0.0.0                  0         32768 i
    *> 40.40.40.0/32    0.0.0.0                  0         32768 i
    MAIN-SOURSE#
    router bgp 400
    no synchronization
    bgp log-neighbor-changes
    network 20.20.20.0 mask 255.255.255.255
    network 30.30.30.0 mask 255.255.255.255
    network 40.40.40.0 mask 255.255.255.255
    neighbor 217.173.48.206 remote-as 500
    no auto-summary
    ip forward-protocol nd
    ip route 20.20.20.0 255.255.255.255 Null0
    ip route 30.30.30.0 255.255.255.255 Null0
    ip route 30.30.30.1 255.255.255.255 Null0
    ip route 40.40.40.0 255.255.255.255 Null0
    ip route 40.40.40.1 255.255.255.255 Null0
    MAIN-SOURSE#show cdp neighbors
    Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                      S - Switch, H - Host, I - IGMP, r - Repeater
    Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
    ISP-Main         Gig 0/0            159          R        7206VXR   Gig 0/0
    MAIN-SOURSE#
    ( Router 2)
    ISP-Main#show ip bgp
    BGP table version is 4, local router ID is 217.173.48.206
    Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
                  r RIB-failure, S Stale
    Origin codes: i - IGP, e - EGP, ? - incomplete
       Network          Next Hop            Metric LocPrf Weight Path
    *> 20.20.20.0/32    217.173.48.205           0             0 400 i
    *> 30.30.30.0/32    217.173.48.205           0             0 400 i
    *> 40.40.40.0/32    217.173.48.205           0             0 400 i
    router bgp 500
    no synchronization
    bgp log-neighbor-changes
    neighbor 172.21.1.2 remote-as 500
    neighbor 172.21.1.2 next-hop-self
    neighbor 217.173.48.205 remote-as 400
    no auto-summary
    ISP-Main#show cdp neighbors
    Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                      S - Switch, H - Host, I - IGMP, r - Repeater
    Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
    Router           Gig 1/0            126          R        7206VXR   Gig 0/0
    MAIN-SOURSE      Gig 0/0            126          R        7206VXR   Gig 0/0
    ( Router 1)
    Router#show ip bgp
    BGP table version is 4, local router ID is 172.21.1.2
    Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
                  r RIB-failure, S Stale
    Origin codes: i - IGP, e - EGP, ? - incomplete
       Network          Next Hop            Metric LocPrf Weight Path
    *>i20.20.20.0/32    172.21.1.1               0    100      0 400 i
    *>i30.30.30.0/32    172.21.1.1               0    100      0 400 i
    *>i40.40.40.0/32    172.21.1.1               0    100      0 400 i
    Router#
    router bgp 500
    no synchronization
    bgp log-neighbor-changes
    neighbor 172.21.1.1 remote-as 500
    no auto-summary
    ip forward-protocol nd
    no ip http server
    no ip http secure-server
    Router#show cdp neighbors
    Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                      S - Switch, H - Host, I - IGMP, r - Repeater
    Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
    ISP-Main         Gig 0/0            171          R        7206VXR   Gig 1/0
    Router#

Maybe you are looking for