- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Issue Pint connectivity
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2017 02:54 PM
тАО12-18-2017 02:54 PM
Issue Pint connectivity
Hi Team,
WE are facing in our network that we have bgp peering with Alcatel router Point to Point.When we try to ping the IP,we are not able to ping but while we ping with the source of any interface ,we were able to ping the remote IP.PLease help to suggest the way forward.
<KARBLRHTR01>display bgp peer ipv4 vpn-instance OAM
BGP local router ID: 10.166.32.134
Local AS number: 65521
Total number of peers: 2 Peers in established state: 2
* - Dynamically created peer
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
10.166.32.129 65010 619 701 0 1762 03:42:22 Established
10.166.32.133 65010 1041 1723 0 1759 05:48:11 Established
<KARBLRHTR01>
<KARBLRHTR01>
<KARBLRHTR01>
Direct Point to Point Ping:
<KARBLRHTR01>ping -vpn-instance OAM 10.166.32.129
Ping 10.166.32.129 (10.166.32.129): 56 data bytes, press CTRL_C to break
Request time out
Request time out
Request time out
--- Ping statistics for 10.166.32.129 in VPN instance OAM ---
4 packet(s) transmitted, 0 packet(s) received, 100.0% packet loss
<KARBLRHTR01>
Ping with Source Interface IP:
<KARBLRHTR01>ping -a 10.166.36.1 -vpn-instance OAM 10.166.32.129
Ping 10.166.32.129 (10.166.32.129) from 10.166.36.1: 56 data bytes, press CTRL_C to break
56 bytes from 10.166.32.129: icmp_seq=0 ttl=64 time=8.723 ms
56 bytes from 10.166.32.129: icmp_seq=1 ttl=64 time=1.100 ms
56 bytes from 10.166.32.129: icmp_seq=2 ttl=64 time=66.176 ms
56 bytes from 10.166.32.129: icmp_seq=3 ttl=64 time=1.077 ms
56 bytes from 10.166.32.129: icmp_seq=4 ttl=64 time=1.016 ms
--- Ping statistics for 10.166.32.129 in VPN instance OAM ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 1.016/15.618/66.176/25.452 ms
<KARBLRHTR01>
Regards,
Namit Joshi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2017 06:18 PM
тАО12-18-2017 06:18 PM
Re: Issue Pint connectivity
Useful thing . Thanks for share
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-15-2018 10:36 PM
тАО04-15-2018 10:36 PM
Re: Issue Pint connectivity
I notice that the ping that works comes from a different IP subnet to the routing address - 10.166.36.1 against i take it 10.166.32.133 as you are trying to ping 10.166.32.129.
How is your subnet set up? Are the 2 routing interfaces in different subnets or the same subnet? If they are in the same subnet are you just not routing as the switch/router that is the source is not forwarding the packets due to the subnetting?
Just a thought.