對 Juniper ScreenOS 客戶閘道裝置的 AWS Site-to-Site VPN 連線進行故障診斷 - AWS Site-to-Site VPN
IKE 和 IPsec通道BGP

本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。

對 Juniper ScreenOS 客戶閘道裝置的 AWS Site-to-Site VPN 連線進行故障診斷

當您對 Juniper ScreenOS 型客戶閘道裝置的連線進行疑難排解時，請考慮以下四件事：IKE、、IPsec通道和 BGP。您可以按任何順序對這些區域進行故障診斷，但我們建議您從 IKE（網路堆疊底部） 開始並向上移動。

IKE 和 IPsec

使用下列 命令。回應顯示已正確IKE設定的客戶閘道裝置。

ssg5-serial-> get sa
total configured sa: 2
HEX ID    Gateway         Port Algorithm     SPI      Life:sec kb Sta   PID vsys
00000002<   72.21.209.225  500 esp:a128/sha1 80041ca4  3385 unlim A/-    -1 0
00000002>   72.21.209.225  500 esp:a128/sha1 8cdd274a  3385 unlim A/-    -1 0
00000001<   72.21.209.193  500 esp:a128/sha1 ecf0bec7  3580 unlim A/-    -1 0
00000001>   72.21.209.193  500 esp:a128/sha1 14bf7894  3580 unlim A/-    -1 0

您應該會看到一或多行包含通道中所指定的遠端閘道遠端地址。Sta 數值應為 A/-，而 SPI 應為非 00000000 的十六進位數字。其他狀態的項目表示 IKE 未正確設定。

如需進一步疑難排解，請啟用IKE追蹤選項 （如範例組態檔案中的建議）。

通道

首先，請再次檢查您有沒有必要的防火牆規則。如需規則清單，請參閱AWS Site-to-Site VPN 客戶閘道裝置的防火牆規則。

如果您的防火牆規則設定正確，則繼續使用下列命令來進行故障診斷。

ssg5-serial-> get interface tunnel.1
  Interface tunnel.1:
  description tunnel.1
  number 20, if_info 1768, if_index 1, mode route
  link ready
  vsys Root, zone Trust, vr trust-vr
  admin mtu 1500, operating mtu 1500, default mtu 1500
  *ip 169.254.255.2/30
  *manage ip 169.254.255.2
  route-deny disable
  bound vpn:
    IPSEC-1

  Next-Hop Tunnel Binding table
  Flag Status Next-Hop(IP)    tunnel-id  VPN

  pmtu-v4 disabled
  ping disabled, telnet disabled, SSH disabled, SNMP disabled
  web disabled, ident-reset disabled, SSL disabled

  OSPF disabled  BGP enabled  RIP disabled  RIPng disabled  mtrace disabled
  PIM: not configured  IGMP not configured
  NHRP disabled
  bandwidth: physical 0kbps, configured egress [gbw 0kbps mbw 0kbps]
             configured ingress mbw 0kbps, current bw 0kbps
             total allocated gbw 0kbps

您一定要看到 link:ready，而且 IP 地址符合客戶閘道裝置通道內部地址。

接著，使用下列命令，以您虛擬私有閘道的內部 IP 地址取代 169.254.255.1。您的結果看起來應該類似此處顯示的回應。

ssg5-serial-> ping 169.254.255.1
Type escape sequence to abort

Sending 5, 100-byte ICMP Echos to 169.254.255.1, timeout is 1 seconds
!!!!!
Success Rate is 100 percent (5/5), round-trip time min/avg/max=32/32/33 ms

如需進一步故障診斷，請檢閱組態。

BGP

執行下列命令。

ssg5-serial-> get vrouter trust-vr protocol bgp neighbor
Peer AS Remote IP       Local IP          Wt Status   State     ConnID Up/Down
--------------------------------------------------------------------------------
   7224 169.254.255.1   169.254.255.2    100 Enabled  ESTABLISH     10 00:01:01
   7224 169.254.255.5   169.254.255.6    100 Enabled  ESTABLISH     11 00:00:59

兩個BGP對等項的狀態應為 ESTABLISH，這表示與虛擬私有閘道的BGP連線處於作用中狀態。

如需進一步故障診斷，請使用下列命令，以您虛擬私有閘道的內部 IP 地址取代 169.254.255.1。

ssg5-serial-> get vr trust-vr prot bgp neigh 169.254.255.1
peer: 169.254.255.1,  remote AS: 7224, admin status: enable
type: EBGP, multihop: 0(disable), MED: node default(0)
connection state: ESTABLISH, connection id: 18 retry interval: node default(120s), cur retry time 15s
configured hold time: node default(90s), configured keepalive: node default(30s)
configured adv-interval: default(30s)
designated local IP: n/a
local IP address/port: 169.254.255.2/13946, remote IP address/port: 169.254.255.1/179
router ID of peer: 169.254.255.1, remote AS: 7224
negotiated hold time: 30s, negotiated keepalive interval: 10s
route map in name: , route map out name:
weight: 100 (default)
self as next hop: disable
send default route to peer: disable
ignore default route from peer: disable
send community path attribute: no
reflector client: no
Neighbor Capabilities:
  Route refresh: advertised and received
  Address family IPv4 Unicast:  advertised and received
force reconnect is disable
total messages to peer: 106, from peer: 106
update messages to peer: 6, from peer: 4
Tx queue length 0, Tx queue HWM: 1
route-refresh messages to peer: 0, from peer: 0
last reset 00:05:33 ago, due to BGP send Notification(Hold Timer Expired)(code 4 : subcode 0)
number of total successful connections: 4
connected: 2 minutes 6 seconds
Elapsed time since last update: 2 minutes 6 seconds

如果對BGP等，請確認您的客戶閘道裝置正在將預設路由 （0.0.0.0/0） 公告至 VPC。此命令適用於 ScreenOS 6.2.0 版及更新版本。

ssg5-serial-> get vr trust-vr protocol bgp  rib neighbor 169.254.255.1 advertised
i: IBGP route, e: EBGP route, >: best route, *: valid route
               Prefix         Nexthop    Wt  Pref   Med Orig    AS-Path
--------------------------------------------------------------------------------------
>i          0.0.0.0/0         0.0.0.0 32768   100     0  IGP
Total IPv4 routes advertised: 1

此外，請確定您VPC從虛擬私有閘道收到與 對應的字首。此命令適用於 ScreenOS 6.2.0 版及更新版本。

ssg5-serial-> get vr trust-vr protocol bgp  rib neighbor 169.254.255.1 received
i: IBGP route, e: EBGP route, >: best route, *: valid route
               Prefix         Nexthop    Wt  Pref   Med Orig    AS-Path
--------------------------------------------------------------------------------------
>e*     10.0.0.0/16   169.254.255.1   100   100   100  IGP   7224
Total IPv4 routes received: 1