HPE GreenLake Administration
- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Playing with VPLS - only tracert gives "Request ti...
Comware Based
1832645
Members
3035
Online
110043
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
06-06-2012 07:38 AM - edited 06-06-2012 07:39 AM
06-06-2012 07:38 AM - edited 06-06-2012 07:39 AM
Playing with VPLS - only tracert gives "Request time out"
I started a small VPLS lab: 4 switches so far, LDP with dynamic LSPs and OSPF
routing works:
display ospf routing OSPF Process 1 with Router ID10.0.1.3 Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 10.0.1.1/32 2 Stub 10.0.1.105 10.0.1.1 0.0.0.0 10.0.1.2/32 1 Stub 10.0.1.105 10.0.1.2 0.0.0.0 10.0.1.3/32 0 Stub 10.0.1.3 10.0.1.3 0.0.0.0 10.0.1.4/32 1 Stub 10.0.1.110 10.0.1.4 0.0.0.0 10.0.1.100/30 2 Transit10.0.1.105 10.0.1.2 0.0.0.0 10.0.1.104/30 1 Transit10.0.1.106 10.0.1.2 0.0.0.0 10.0.1.108/30 1 Transit10.0.1.109 10.0.1.3 0.0.0.0 10.0.1.112/30 2 Stub 10.0.1.110 10.0.1.4 0.0.0.0 Total Nets: 8 Intra Area: 8 Inter Area: 0 ASE: 0 NSSA: 0
ping works:
ping lsp ipv410.0.1.1 32 LSP Ping FEC: IPV4 PREFIX10.0.1.1/32 : 100 data bytes, press CTRL_C to break Reply from10.0.1.101: bytes=100 Sequence=1 time = 3 ms Reply from10.0.1.101: bytes=100 Sequence=2 time = 3 ms Reply from10.0.1.101: bytes=100 Sequence=3 time = 8 ms Reply from10.0.1.101: bytes=100 Sequence=4 time = 3 ms Reply from10.0.1.101: bytes=100 Sequence=5 time = 3 ms
But with tracert I´m getting "Request time out"
tracert lsp ipv410.0.1.1 32 LSP Trace Route FEC: IPV4 PREFIX10.0.1.1/32 , press CTRL_C to break TTL Replier Time Type Downstream 0 Ingress 10.0.1.109/[1025] 1 10.0.1.109 3 ms Transit 10.0.1.105/[1025] 2 10.0.1.105 2 ms Transit 10.0.1.101/[3] 3 Request time out 4 10.0.1.101 4 ms Egress
The question is why?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP