Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-2978

Missing remote peer information for Juniper pseudowires

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery
    • None

    Description

      When listing the pseudowires gathered from the JUNIPER-VPN-MIB the remote endpoint information is missing (see attached image). Maybe the system is struggling to resolve the remote device address (jnxVpnRemotePeIdAddress). Example from the debug bellow.

      array(
      		 
        [bgpL2Vpn] => array(
      		 
        [L2VPN-1003] => array(
      		 
        [131073] => array(
      		 
        [jnxVpnPwRowStatus] => string(6) "active"
      		 
        [jnxVpnPwAssociatedInterface] => string(3) "569"
      		 
        [jnxVpnPwLocalSiteId] => string(1) "2"
      		 
        [jnxVpnPwTunnelName] => string(18) "to-PE1"
      		 
        [jnxVpnPwTunnelType] => string(6) "rsvpTe"
      		 
        [jnxVpnRemotePeIdAddrType] => string(4) "ipv4"
      		 
        [jnxVpnRemotePeIdAddress] => string(33) "30 30 30 2E 30 30 2E 30 2E 30 30 "
      		 
        [jnxVpnPwRemoteSiteId] => string(1) "1"
      		 
       )

      From the debug:

      "Not found correct peer address. See snmpwalk for 'jnxVpnRemotePeIdAddress'."

      Attachments

        Activity

          [OBS-2978] Missing remote peer information for Juniper pseudowires
          lbalbinot Luis Balbinot added a comment -

          Thanks! It works.

          lbalbinot Luis Balbinot added a comment - Thanks! It works.
          landy Mike Stupalov added a comment -

          Yah, I see what you mean.. fixed now in r9800.
          Tnx!

          landy Mike Stupalov added a comment - Yah, I see what you mean.. fixed now in r9800. Tnx!
          lbalbinot Luis Balbinot added a comment -

          The thing is that you try to hex2ip() that string, instead you should treat it like you do with jnxBgpM2PeerLocalAddr/jnxBgpM2PeerRemoteAddr with the BGP4-V2-MIB-JUNIPER.

          lbalbinot Luis Balbinot added a comment - The thing is that you try to hex2ip() that string, instead you should treat it like you do with jnxBgpM2PeerLocalAddr/jnxBgpM2PeerRemoteAddr with the BGP4-V2-MIB-JUNIPER.
          landy Mike Stupalov added a comment -

          If it's just your value, than all other "correctly" addresses we already detect and store in db.
          If you have other endpoint pseudowire device with this IP it will linked in db.

          landy Mike Stupalov added a comment - If it's just your value, than all other "correctly" addresses we already detect and store in db. If you have other endpoint pseudowire device with this IP it will linked in db.
          lbalbinot Luis Balbinot added a comment - - edited

          The MIB definition is OCTET STRING. Juniper won't change that as it is used by their various management platforms. It's OCTET STRING because it can be of many types according to jnxVpnRemotePeIdAddrType.

          The value 000.00.0.00 is by me (I sanitised the output as I don't have a lab box to test it).

          Since it's a proprietary MIB we should work around it I think. I'll look into it then.

          lbalbinot Luis Balbinot added a comment - - edited The MIB definition is OCTET STRING. Juniper won't change that as it is used by their various management platforms. It's OCTET STRING because it can be of many types according to jnxVpnRemotePeIdAddrType. The value 000.00.0.00 is by me (I sanitised the output as I don't have a lab box to test it). Since it's a proprietary MIB we should work around it I think. I'll look into it then.
          landy Mike Stupalov added a comment -

          This not possible fix on our side, because this is firmware bug. Try update junos firmware or write to vendor.

          This snmp string can not be converted to known ip address:

          [jnxVpnRemotePeIdAddress] => string(33) "30 30 30 2E 30 30 2E 30 2E 30 30 "

          This should be HEX representation of ipv4 (4 pairs hex numbers).
          And if I try convert this as hex string to normal string I also get senseless text: "000.00.0.00".

          landy Mike Stupalov added a comment - This not possible fix on our side, because this is firmware bug. Try update junos firmware or write to vendor. This snmp string can not be converted to known ip address: [jnxVpnRemotePeIdAddress] => string(33) "30 30 30 2E 30 30 2E 30 2E 30 30 " This should be HEX representation of ipv4 (4 pairs hex numbers). And if I try convert this as hex string to normal string I also get senseless text: "000.00.0.00".

          People

            landy Mike Stupalov
            lbalbinot Luis Balbinot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: