OSPF Point to Point network question

I just have a quesiton about the linkstate database. I have a point-to-point link between a couple routers(makes sense) and when I look at the database for the lsa type 1, it shows the router has 2 links in the area and one is a stub. I don't under stand how thats possible.
            OSPF Router with ID (4.4.4.4) (Process ID 1)
                Router Link States (Area 1)
  LS age: 1136
  Options: (No TOS-capability, DC)
  LS Type: Router Links
  Link State ID: 4.4.4.4
  Advertising Router: 4.4.4.4
  LS Seq Number: 80000007
  Checksum: 0xC738
  Length: 60
  Number of Links: 3
    Link connected to: another Router (point-to-point)
     (Link ID) Neighboring Router ID: 1.1.1.1
     (Link Data) Router Interface address: 192.168.41.2
      Number of TOS metrics: 0
       TOS 0 Metrics: 10
    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 192.168.41.0
     (Link Data) Network Mask: 255.255.255.0
      Number of TOS metrics: 0
       TOS 0 Metrics: 10
Can anyone explain to me what I'm seeing here? Thanks

Full config
hostname R4
boot-start-marker
boot-end-marker
no aaa new-model
memory-size iomem 5
no ip icmp rate-limit unreachable
ip cef
no ip domain lookup
multilink bundle-name authenticated
archive
 log config
  hidekeys
ip tcp synwait-time 5
interface FastEthernet0/0
 ip address 192.168.104.1 255.255.255.0
 ip ospf authentication message-digest
 ip ospf message-digest-key 1 md5 dallas
 ip ospf 1 area 1
 duplex auto
 speed auto
interface FastEthernet0/1
 ip address 192.168.41.2 255.255.255.0
 ip ospf authentication message-digest
 ip ospf message-digest-key 1 md5 dallas
 ip ospf 1 area 1
 duplex auto
 speed auto
router ospf 1
 router-id 4.4.4.4
 log-adjacency-changes
ip forward-protocol nd
no ip http server
no ip http secure-server
control-plane
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
end
R4#

Similar Messages

  • Looking For Help Performing a many point to many network reachability validation with a script after a Major Routing Modification

    I have inherited a network that was not put together so well...as it has 50 sites but 11 points of mulual redistribution between OSPF and BGP.
    The result is not surprising some route paths that although stable are asymmetrical and they cause issues for certain applications....like Voice and RDP.
    This evening I  have a maintence window to try to fix this.
    I need to validate with ping and traceroute from many points (Cisco Siwtches and Routers) in the to many points in the network.
    Can anyone point me to a TCL Shell script that would serve as an example of how to accomplish this?
    Please be advised that I am only nominally functional with TCL shell scripting language.
    Respectfully,
    Duane Bodle               

    The first thing to do is:
    regexp "match regexp = ([0-9]+)" $_cli_result match count
    if $count eq 0
    exit 0
    end
    The second is a bit more challenging.  I think this will work:
    cli command "show call active voice br"
    foreach line $_cli_result "\n"
    regexp "^([0-9a-zA-Z]+) : " $line match callid
    if $_regexp_result eq 1
      continue
    end
    regexp "^dur 1d" $line
    if $_regexp_result eq 1
      cli command "show call active voice br | section $callid"
      syslog msg "$_cli_result"
    end
    end

  • Question POS point to point with no APS

    One side
    POS1/0/0
    SECTION
    LOF = 0 LOS = 0 BIP(B1) = 0
    LINE
    AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0
    PATH
    AIS = 1 RDI = 2 FEBE = 1119 BIP(B3) = 463
    PLM = 4 UNEQ = 0 TIM = 0 TIU = 0
    LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0
    Active Defects: None
    Active Alarms: None
    Alarm reporting enabled for: SF SLOS SLOF B1-TCA B2-TCA PLOP B3-TCA
    Framing: SONET
    APS
    COAPS = 0 PSBF = 0
    State: PSBF_state = False
    Rx(K1/K2): 00/00 Tx(K1/K2): 00/00
    S1S0 = 00, C2 = 16
    Remote aps status (none); Reflected local aps status (none)
    Other end
    POS1/0/0
    SECTION
    LOF = 0 LOS = 0 BIP(B1) = 0
    LINE
    AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0
    PATH
    AIS = 1 RDI = 1 FEBE = 419 BIP(B3) = 859
    PLM = 3 UNEQ = 0 TIM = 0 TIU = 0
    LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0
    Active Defects: None
    Active Alarms: None
    Alarm reporting enabled for: SF SLOS SLOF B1-TCA B2-TCA PLOP B3-TCA
    Framing: SONET
    APS
    COAPS = 0 PSBF = 0
    State: PSBF_state = False
    Rx(K1/K2): C0/15 Tx(K1/K2): 00/00
    S1S0 = 00, C2 = 16
    Remote aps status (none); Reflected local aps status (none)
    My question is the Kbytes what does that mean loss of signal on RX ? Rx(K1/K2): C0/15 Tx(K1/K2): 00/00
    There is no Auto protection Switching on this circuit it is straight point to point.

    Hello,
    the meaning of the K1/K2 bytes are defined in "Telcordia document GR-253—Synchronous Optical Network (SONET) Transport Systems: Common Generic Criteria".
    K1/K2 = 00/00 means no APS (respective no APS requests)
    K1/K2 = C0/15 means
    K1 = 11000000, which translates to "low priority signal failure on protected channel"
    K2 = 00010101, which translates to "working channel 1 in 1+1 redundancy, bidirectional mode"
    So this can mean, that the provider equipment on one end has APS configured, whereas your euipment has no APS configured. APS is local between your interface and the provider equipment (multiplexer).
    Hope this helps! Please rate all posts.
    Regards, Martin

  • RV082 DMZ Configuration Question - Point to Point

    Hello,
    We have 2 offices in different countries both using the RV082 router.  Currently both offices have an internet connection on WAN1 and that is working fine.
    We are adding a Point to Point circuit between the two offices, and my question is on the RV082 configuration on each side.
    I was going to configure WAN2 in DMZ mode on each router, then connect the point to point circuit to the WAN2 port.  On the China side, the DMZ IP will have to be a private address (192.168.177.1), while the DMZ port on the San Diego side will be a public IP. 
    We need internal computers to be able to go to the internet normally through WAN1, but also go through WAN2 if they are trying to reach the other network.  I will be adding routes on each RV082 for this.
    Is there anything wrong with this configuration?  Do I need to change the routers from Gateway to Router mode?  Does it matter if the DMZ WAN2 port has a private IP address?
    Any advice or tips are greatly appreciated!
    Thank you in advance,
    Eric

    Thanks Tom but that thread is not exactly what I was looking for.  Mainly I just want to know if the RV082 can act as a fully functioning router with the two WAN ports going to different networks.  So the LAN side would hit the router, look at the routing table and know which WAN port to go out of.  Using the DMZ seems like it will work, but I have never tried it so I wanted to throw it out there and see if anyone has done this before.

  • Design Help with MPLS/BGP and Point to Point VPNs using OSPF as backup

    I need some advice on the configuration I want to implement. Basically we have a MPLS cloud using BGP. We are using OSPF for internal routing. Everything is working fine. Now we want to add a Point to Point VPN using new Cisco ASA's for a backup path at all of our remote locations. We want it to be on standby. I want to use OSPF for this. Miami and LA are datacenters. I want the VPN's to go into both datacenters if possible running OSPF for backups. I have a feeling this will be very tricky. I also wanted to use floating routes. Now I know I get the VPN's up and running using OSPF with no problem. Here are my questions:
    But being that I am using different areas, will OSPF through the VPN work correctly? I have the Cisco PDF on setting this up but it looks like they are using the same, AREA0, in the example.
    Can I get both VPN's to work with no problems? Or will it be too much of a pain?
    What would you guys suggest?
    Thanks.

    We are implementing the same solution, and was only able to make this work using HSRP one router for the MPLS connection and one for the VPN tunnel. I opened a TAC case and the tech couldn't get it to work either. I was able to establish the Lan-2-lan tunnel but triggering the route update was the problem. We ended up pulling our ASA5505's out and putting in 1841 routers.

  • How do I use Airport Extreme to create wired access point on wireless network?

    Bit of an odd situation. I just went from cable to DSL at home and the modem moved from right by my computer to upstairs.
    Trouble is, there's no real easy way to get a cable from the modem upstairs to my X-box (sans wireless connector) downstairs.
    I could buy the wireless adaptor for the X-Box, but I was hoping I wouldn't have to spend any more money.
    I have my airport extreme, and I was hoping I could use it to create a wired access point on the network, recieving the signal from the wireless modem upstairs and allowing me to plug in the X-Box.
    Is this possible? If so, how? I've been through the config panel about a dozen times, but can't figure out what combination to set up.
    Thanks.

    Will it work if I use the express to create the network?
    Yes, providing that you have an 802.11n version of the AirPort Express and the Express has been configured to "Allow this network to be extended".
    Then, the AirPort Extreme can be configured to "extend" the Express network. When you do this, the AirPort Extreme will provide more wireless coverage and the LAN Ethernet ports are enabled, so you can connect an Ethernet device.
    This will not be a "normal" Ethernet connection. It will only work as well as the wireless "hop" between the Express and Extreme allow.
    For best results and performance, a wired connection through the hole in the wall is always best. If you decide to do this, you will need the "new" AirPort Express with both a WAN and LAN port on the device. But, you could try wireless first to see if it will meet your goals before you reach for the tools.

  • After moving shared profiles to Windows 7/32 Pro PC, I can't access them from XP box mapped to the profile share (P:\Profiles...) after editing profiles.ini to point to the network share. I can edit files in the profile directory from XP.

    Previous configuration: Shared profiles located at D:\profiles\ on PC1 (XP Pro SP3). 2nd PC (PC2 also XP Pro SP3) mapped to \\PC1\Profiles via mapped drive P: and using absolute reference in profiles.ini on PC2. Remote profiles work OK on PC2.
    New PC added (PC7) to eventually replace PC1 (Windows 7/32 Pro). Profiles moved to D:\Profiles on that box. Firefox and Thunderbird work fine on PC7 with the local profiles. Profiles.ini edited on PC1 to point to the network share and will not access the remote profiles. Access permissions are set to full for everyone. I can write and edit to files in the profile directories from PC1.
    I tried adding a profile with the profile manager and tried to force it to use the network share, but it still located the new profile down in the default directory ...\application data\Mozilla\Firefox\

    Well, try this (I was able to fix my with these steps):
    Go Utilities > Disk Utility
    Select your Startup Disk, e.g. Macintosh HD
    Then, under the First Aid Tab, click Verify Disk Permissions.
    If there are errors, then click repair Disk Permissions.
    After it is done, restart the computer and see if your problem is resolved.
    I hope this help.
    Zeke
    www.ZekeYuen.com/blog/

  • GRE over DSL with OSPF in an MPLS network

    Hi guys,
    we run 2 GRE tunnels in our network. The A end is a PE router while the B end are 2 different CPE DSL sites.
    Both tunnels at the A end (PE) are using as a source a gig sub inteface which is in the same VRF
    interface Tunnel40 (for branch office 1)
    ip vrf forwarding example
    ip address x.x.x.250 255.255.255.252
    ip mtu 1476
    ip tcp adjust-mss 1420
    ip ospf dead-interval 60
    ip ospf mtu-ignore
    keepalive 10 6
    tunnel source Gig x/x.z
    tunnel destination x.x.x.x.
    tunnel vrf example
    interface Tunnel60 (for branch office 2)
    the frame is as above
    router ospf 1 vrf example
    log-adjacency-changes
    capability vrf-lite
    passive-interface default
    no passive-interface Tunnel40
    no passive-interface Tunnel60
    network x.x.x.250 0.0.0.0 area x.x.x.x
    .network ......
    CPE example
    interface Tunnel1
    ip address x.x.x.249 255.255.255.252
    ip flow ingress
    ip flow egress
    ip ospf dead-interval 60
    ip ospf mtu-ignore
    keepalive 10 6
    tunnel source Dialer1
    tunnel destination z.z.z.1 ( this is the subinterafce Gig x/x.z on the PE router)
    router ospf 1
    router-id x.x.x.x
    log-adjacency-changes
    passive-interface default
    no passive-interface Tunnel1
    no passive-interface Vlan1
    network x.x.x.x 0.0.0.0 area x.x.x.x
    network x.x.x.249 0.0.0.0 area x.x.x.x
    same is the config for CPE 2 ( just the frame of the commands no the ospf areas , IP s etc)
    The problem is that when the tunnel fails for cpe 1 then it fails for CPE 2 exactly the same time.
    Any advice.
    Thanks

    Hi my friend,
    I didnt know about that command and the purpose you use that  but I was searching a bit. Do you use that command for
    normal GRE tunnels?  This is not a point to multipoint topology and every tunnel is a point to point and I run ospf for the point to point link is is differnet area than the other tunnel. Do you beleive that its still could be related to the tunnel key?
    Many thanks fo ryour advice. Please reply at your erliest convenience
    I know it looks like hub and spoke or point to miltipoint but does it actually dehave like that?
    Thank,
    Spyros

  • How to set up a point to point connection in 4 sites

    Hi all.
    I'm investigating the option of set up a point to point connection around 4 sites.
    I will call Site01, Site02, Site03 and Site04.
    Site01 will be the main one with a Main Domain Controller.
    Site02, Site03 and Site04 will be the Secondary Domain Controllers.
    I need to install an VPN Router on each Site to create a full VPN Network, I mean, All the computers should see the other computers.
    I need some support about it.
    I suppose that I have to config like this:
    Site01 with VPNRouter01 will have the IP range 192.168.1.X.
    Site02 with VPNRouter02 will have the IP range 192.168.2.X.
    Site03 with VPNRouter03 will have the IP range 192.168.3.X.
    Site04 with VPNRouter04 will have the IP range 192.168.4.X.
    If I config on each VPNRouter 3 point to point VPN connection is the only config that I have to do?
    I mean, is not neccesary to config anything else?
    I suppose that for example, the client with IP 192.168.1.10 should have the following IP address as well:
    192.168.2.10
    192.168.3.10
    192.168.4.10
    Is this neccesary to see all the clients on the remote networks?
    Thanks and best regards.

    HI,
    Try the below
    1) Configure site to site vpn from all the three site to the HUB site.
    2) Configure ospf or any dynamic routing protocol on the vpn, thus you will have routes of site1, site2 and site3 in site4 and visaversa.
    Once you have the connectivity established you can access any computers from any site.

  • WLC and Point-to-Point Bridge/Repeater

    Hi all,
    I have a WLC2125 and 11 LAPs installed in our warehouse. There is going to be one additional AP but the problem is we can´t provide cabling in that area. The idea is to have this additional AP connected to one of the existing LAPs and repeat the signal of it or to create point-to-point link, the question is, would LAPs and WLC support such configuration, is it possible at all? If so, please let me know the config process or some documentation.
    Thanks in advance.

    Hi,
    Q> What do I gain by going for mesh topology?
    >> A lot.. here is the details..
    http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps6548/prod_brochure0900aecd8036884a.html
    http://www.cisco.com/en/US/netsol/ns621/index.html
    Q> I can´t eliminate WLC from my network,
    >> Mesh network will not work without WLC.
    Q> instead  I thought of leaving one LAP as autonomous AP and bridging it with the new AP that will not have a physical connection
    >> The only way to Integrate the Autonomous AP to LWAPP AP is by using the WGB Mode, the REPEATER is not supported and even the Point to Point bridging. The WGB doesnot provide Wireless where in you can conect a switch and conect wired clients to it.
    Regards
    Surendra

  • IPv6 Addressing Point to Point Links in the enterprise

    For an enterprise, it doesn't seem to make sense to use Global addressing for point to point, transit-only links and loopbacks.
    Link-local only addressing breaks debugging tools like traceroute, DNS, etc.
    Is Unique Local the correct choice for this?
    I've searched quite a bit and I've not found a lot of discussion about scope selection for point to point links.  Some RFCs such as 6164 imply Global scope vs Unique Local scope usage is a preference.  Most discussions of point to point addressing focus on bit length.  I'm assuming this means design concerns are agnostic toward scope selection.
    Is anyone aware of documentation I've missed or have any recommendations in this area?
    If ULA was the correct choice, address hierarchy might look like this:
    DataNetwork1 -- Router1 -- ULA.1.1 -- Link -- ULA1.2 -- Agg Router -- Core
    DataNetwork2 -- Router2 -- ULA.2.1 -- Link -- ULA2.2 -- Agg Router /
    DataNetwork3 -- Router3 -- ULA.3.1 -- Link -- ULA3.2 -- Agg Router /
    The network core would have summarized entries for DataNetwork[1|2|3] and ULA[1|2|3].  IE, there would be a Global hierarchy and a ULA hierarchy.

    Scott,
    Let me break this down into some categories for you.
    Address selection:
    I believe that best practice is to use Global Unicast Addressing everywhere (coupled with a proper security policy at your edge). ULA was a compromise for Site Local never being properly defined and whilst it can be used in the same way as GUA I don't believe it is worth it. Irrespective of what you use (GUA or ULA), subject to your security and routing policy traceroute will work from both ends (e.g. you tracing out, someone tracing in)
    Address masking:
    The general rule of thumb is that you allocate /64s to eveything and then mask down to the appropriate mask for the function you are expecting (P.S. Forget everything you learnt about IPv4 address conservation). If you are using /127 masks then in theory every p2p link in your network is either a 0 (::) or a 1 (::1)
    e.g.
    traceroute HostB:
    1     2001:1234:abcd:1::1
    2     2001:1234:abcd:2::1
    3     2001:1234:abcd:3::1
    4     2001::4:10
    The only exception to this is loopbacks, you can sequentially allocate /128s from the same /64 block
    NOTE: /127 support is recent and may not be supported by some vendors, in this case use /126 masking (same as you would use /30s in IPv4)
    If you have a /48 ( a normal enterise allocation) or larger then this should not be an issue ( you have access to 65536 x /64s) the only reason you would consider ULA for infrastructure numbering is because you have a small IPv6 pool. I would still argue you should get more IPv6 addresses than use ULA.
    I hope this helps
    Cheers

  • Can't ping routers across point-to-point frame-relay

    'evening,
      Really basic setup.  Designed with Packet Tracer, trying to ping routers across a point-to-point frame-relay.  I've designed this according to three different training sources who all say the same thing.  Yet, all pings failed.
    The shows:
    R1
    R1#copy run st
    Destination filename [startup-config]? 
    Building configuration...
    [OK]
    R1#show run
    Building configuration...
    Current configuration : 883 bytes
    version 12.2
    no service timestamps log datetime msec
    no service timestamps debug datetime msec
    no service password-encryption
    hostname R1
    no ip domain-lookup
    interface FastEthernet0/0
     no ip address
     duplex auto
     speed auto
     shutdown
    interface FastEthernet0/1
     no ip address
     duplex auto
     speed auto
     shutdown
    interface Serial1/0
     no ip address
     encapsulation frame-relay
    interface Serial1/0.12 point-to-point
     ip address 192.168.12.1 255.255.255.0
     frame-relay interface-dlci 102
    interface Serial1/0.13 point-to-point
     ip address 192.168.13.1 255.255.255.0
     frame-relay interface-dlci 103
    ip classless
    end
    R1#show frame-relay lmi
    LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 638       Num Status msgs Rcvd 638
     Num Update Status Rcvd 0       Num Status Timeouts 16
    LMI Statistics for interface Serial1/0.12 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 0         Num Status msgs Rcvd 0
     Num Update Status Rcvd 0       Num Status Timeouts 16
    LMI Statistics for interface Serial1/0.13 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 0         Num Status msgs Rcvd 0
     Num Update Status Rcvd 0       Num Status Timeouts 16
    R1#show frame-relay map
    Serial1/0.12 (up): point-to-point dlci, dlci 102, broadcast, status defined, active
    Serial1/0.13 (up): point-to-point dlci, dlci 103, broadcast, status defined, active
    R1#show frame-relay pvc
    PVC Statistics for interface Serial1/0 (Frame Relay DCE)
    DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.12
    input pkts 14055       output pkts 32795        in bytes 1096228
    out bytes 6216155      dropped pkts 0           in FECN pkts 0
    in BECN pkts 0         out FECN pkts 0          out BECN pkts 0
    in DE pkts 0           out DE pkts 0
    out bcast pkts 32795   out bcast bytes 6216155
    DLCI = 103, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.13
    input pkts 14055       output pkts 32795        in bytes 1096228
    out bytes 6216155      dropped pkts 0           in FECN pkts 0
    in BECN pkts 0         out FECN pkts 0          out BECN pkts 0
    in DE pkts 0           out DE pkts 0
    out bcast pkts 32795   out bcast bytes 6216155
    R2
    R2#SHOW RUN
    Building configuration...
    Current configuration : 772 bytes
    version 12.2
    no service timestamps log datetime msec
    no service timestamps debug datetime msec
    no service password-encryption
    hostname R2
    no ip domain-lookup
    interface Serial1/0
     no ip address
     encapsulation frame-relay
    interface Serial1/0.12 point-to-point
     ip address 192.168.12.2 255.255.255.0
     frame-relay interface-dlci 201
    ip classless
    end
    R2#show fr map
    Serial1/0.12 (up): point-to-point dlci, dlci 201, broadcast, status defined, active
    R2#show fr pvc
    PVC Statistics for interface Serial1/0 (Frame Relay DTE)
    DLCI = 201, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.12
    input pkts 14055       output pkts 32795        in bytes 1096228
    out bytes 6216155      dropped pkts 0           in FECN pkts 0
    in BECN pkts 0         out FECN pkts 0          out BECN pkts 0
    in DE pkts 0           out DE pkts 0
    out bcast pkts 32795   out bcast bytes 6216155
    R2#show fr lmi
    LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 679       Num Status msgs Rcvd 678
     Num Update Status Rcvd 0       Num Status Timeouts 16
    LMI Statistics for interface Serial1/0.12 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 0         Num Status msgs Rcvd 0
     Num Update Status Rcvd 0       Num Status Timeouts 16
    R3
    R3#show run
    Building configuration...
    Current configuration : 772 bytes
    version 12.2
    no service timestamps log datetime msec
    no service timestamps debug datetime msec
    no service password-encryption
    hostname R3
    interface Serial1/0
     no ip address
     encapsulation frame-relay
    interface Serial1/0.13 point-to-point
     ip address 192.168.13.2 255.255.255.0
     frame-relay interface-dlci 301
    ip classless
    end
    R3#show fr map
    Serial1/0.13 (up): point-to-point dlci, dlci 301, broadcast, status defined, active
    R3#show fr lmi
    LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 703       Num Status msgs Rcvd 702
     Num Update Status Rcvd 0       Num Status Timeouts 16
    LMI Statistics for interface Serial1/0.13 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 0         Num Status msgs Rcvd 0
     Num Update Status Rcvd 0       Num Status Timeouts 16
    R3#show fr pvc
    PVC Statistics for interface Serial1/0 (Frame Relay DTE)
    DLCI = 301, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.13
    input pkts 14055       output pkts 32795        in bytes 1096228
    out bytes 6216155      dropped pkts 0           in FECN pkts 0
    in BECN pkts 0         out FECN pkts 0          out BECN pkts 0
    in DE pkts 0           out DE pkts 0
    out bcast pkts 32795   out bcast bytes 6216155
      Any input would really be appreciated.
    Thanks

    Turns out the mistake was not adding a mask to the subnet. Ex:
    Router_2(config_router)# network 192.168.0.0 0.0.255.255
    Router_2(config_router)# network 172.27.0.0 0.0.255.255
    Doing that on both routers made the hosts capable of pinging each other.
    Thanks for the tips everyone 

  • Broadcast and point to point server in the same port

    I'm trying to set up a system where I can send point to point messages via sockets to certain ips, send broadcast messages to every pc in the network, and also be able to listen for point to point messages and broadcast messages, all in the same port. I've been able to establish a point to point connection using the Socket class to send the message, and using the ServerSocket class to listen for messages, but I can't seem to get broadcasting to work.
    I read somewhere that for broadcasting one should use the DatagramSocket class. The problem is i'm not sure which ip i'm supposed to specify when I send the message. Also, do I need a special listener to listen for broadcast messages, or will the ServerSocket listener work for that?
    This is what I have for the broadcasting part:
    String msg = myId;
    DatagramSocket sendSocket;
    sendSocket = new DatagramSocket(Constants.COM_PORT); // 4567
    InetAddress group = InetAddress.getByName(Constants.BROADCAST_ADDR); // "192.168.1.1"
    DatagramPacket dp = new DatagramPacket(msg.getBytes(), msg.getBytes().length, group, Constants.COM_PORT);
    sendSocket.send(dp);
    sendSocket.close();
    Thanks in advance
    Diego

    It worth mentioning that UDP/broadcast and robust do go together easily.
    - UDP does not guarantee delivery. i.e. messages can be dropped and you won't be told. Lost packets are not retransmitted either.
    - UDP can fragment packets if larger than 532 bytes long.
    - UDP packets can arrive out of order (though I have never seen this myself)
    If your receiver is under load/busy it can miss many packets if its buffers overflow.

  • Aironet 1300 Point to Point Bridging

    Hi, I am new to the forums so please accept my apologises if this is really easy question!!
    We have purchsed 2 Aironet 1300's that we are wanting to use to create a bridge, but after hours of trying and net searching we cannot get them to talk to each other. Can anyone please help? Thanks

    Here's the online config guide:
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008058f53e.shtml
    Here's the Point-to-Point Troubleshooting FAQ:
    http://www.cisco.com/en/US/products/hw/wireless/ps2360/products_qanda_item09186a00801d29ff.shtml
    Wireless Point-to-point Troubleshooting Guide:
    http://www.cisco.com/en/US/products/hw/wireless/ps2360/products_tech_note09186a00801d2a0c.shtml
    Sample Config and Command Guide:
    http://www.cisco.com/en/US/products/hw/cable/ps2217/products_configuration_example09186a0080193dac.shtml
    Other possible issues are to make sure you have solid line-of-site ("more than you think you need" because of some properties associated with the "Freznel Zone")
    Check it out and let us know if you are still having problems.
    Good Luck
    Scott

  • Why does DNS server entry in ipconfig break point-to-point ethernet?

    My application uses a panel pc as the user interface for a cRIO controlling a medical device.  The panle pc and cRIO communicate using shared variables.  During development, both devices (panel pc and cRIO) were on our company network.  Curiously, when I connected them point-to-point with a crossover cable, they refused to communicate when running their LabVIEW application code.  Pings from the panel pc to cRIO were successful.  Much troubleshooting ensued.
    Long story short, the fix was to simply delete the DNS server IP entry from both the panel pc and the cRIO ipconfig tables (see attached pic for the WinXP version of this table).  If either of them had our company's DNS server IP address fillied in, my LabVIEW application would fail.
    This leads me to suspect that there is something in my LabVIEW executables that wants to touch the company network.  Apparently, if there is a DNS server entry in the ipconfig table, this something thinks it has a chance to "phone home" and it tries to do so.  When this happens on the panel pc end of the crossover cable, the machine acts like it's locked up, but the task manager shows the CPU to be ~98% idle.
    If there is no entry for a DNS server, I guess this something realizes that there is no way to "phone home", so it doesn't try and my application works great.  Since the application works with no DNS server table entry, I think my crossover cable is working correctly.
    Does anyone have any idea what this something might be?
    Jeff
    Climbing the Labview learning curve!
    Sanarus Medical
    Pleasanton, CA
    Attachments:
    IPform.gif ‏12 KB

    You've hit the nail on the head Ben.  For point to point communications, the IP addresses should be fixed, therefore there is no need for DNS.  If a DNS is configured, the NIC (Network Interface Card) drivers will try to contact it.
    In my test system, I need DNS for the test computer, but I am communicating with a dedicated Spectrum Analyzer over TCP/IP.  So I added a second NIC.  The main NIC is configured for DNS and all that jazz.  The second NIC (plugged into PCI slot) is configured with a hard coded address, no DNS, no Gateway, nothing else.  I connect that NIC to the spectrum analyzer using a crossover cable.  The analyzer is configured with a hard coded address also.  Now my computer can get on our company network, and the spectrum analyzer is isolated from the network, so it can't catch any viruses, etc., and it still talks to the computer.  When using a configuration such as this, it is best to use a dedicated address for the 2nd NIC and spectrum analyzer in the range of 192.168.100.0 to 254
    - tbob
    Inventor of the WORM Global

Maybe you are looking for