- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- LAN Routing
- >
- Re: HP A5120 Routing Table Problem
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
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
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
11-20-2018 10:06 PM
11-20-2018 10:06 PM
Hello,
I have interesting problem with my HP A5120 device. I have 5 vlan
vlan1 192.168.0.1
vlan2 192.168.1.1
vlan3 192.1682.1
vlan4 192.168.3.1
vlan5 172.16.10.1
I checking ton interface IPV4 Routing tab and I can see here only vlan4 as showen,
0.0.0.0 0.0.0.0 Static 60 192.168.0.254 Vlan-interface1
127.0.0.0 255.0.0.0 Direct 0 127.0.0.1 InLoopBack0
127.0.0.1 255.255.255.255 Direct 0 127.0.0.1 InLoopBack0
172.16.10.0 255.255.255.0 Direct 0 172.16.10.1 Vlan-interface5
172.16.10.1 255.255.255.255 Direct 0 127.0.0.1 InLoopBack0
192.168.0.0 255.255.255.0 Direct 0 192.168.0.1 Vlan-interface1
192.168.0.1 255.255.255.255 Direct 0 127.0.0.1 InLoopBack0
192.168.1.0 255.255.255.0 Direct 0 192.168.1.1 Vlan-interface2
192.168.1.1 255.255.255.255 Direct 0 127.0.0.1 InLoopBack0
192.168.2.0 255.255.255.0 Direct 0 192.168.2.1 Vlan-interface3
192.168.2.1 255.255.255.255 Direct 0 127.0.0.1 InLoopBack0
And I can ping vlan1,2,3,5 as success but when try ping to vlan 4 I receive ping message " ttl expired in transit"
What can ı do for that.
Thank you for your help.
Yakup
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2018 02:23 PM - edited 11-21-2018 02:24 PM
11-21-2018 02:23 PM - edited 11-21-2018 02:24 PM
Re: HP A5120 Routing Table Problem
Can you paste outputs of these three:
- display ip routing-table statistics
- display ip routing-table
- display ip routing-table verbose
CLI commands?
I'm not an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2018 10:14 PM
11-21-2018 10:14 PM
Re: HP A5120 Routing Table Problem
All is here;
display ip routing-table statistics
Proto route active added deleted freed
DIRECT 10 10 20 10 10
STATIC 1 1 1 0 0
Total 11 11 21 10 10
display ip routing-table
Routing Tables: Public
Destinations : 11 Routes : 11
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/0 Static 60 0 192.168.0.254 Vlan1
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
172.16.10.0/24 Direct 0 0 172.16.10.1 Vlan5
172.16.10.1/32 Direct 0 0 127.0.0.1 InLoop0
192.168.0.0/24 Direct 0 0 192.168.0.1 Vlan1
192.168.0.1/32 Direct 0 0 127.0.0.1 InLoop0
192.168.1.0/24 Direct 0 0 192.168.1.1 Vlan2
192.168.1.1/32 Direct 0 0 127.0.0.1 InLoop0
192.168.2.0/24 Direct 0 0 192.168.2.1 Vlan3
192.168.2.1/32 Direct 0 0 127.0.0.1 InLoop0
display ip routing-table verbose
Routing Table : Public
Destinations : 11 Routes : 11
Destination: 0.0.0.0/0
Protocol: Static Process ID: 0
Preference: 60 Cost: 0
NextHop: 192.168.0.254 Interface: Vlan-interface1
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
State: Active Adv GotQ Age: 1d21h46m55s
Tag: 0
Destination: 127.0.0.0/8
Protocol: Direct Process ID: 0
Preference: 0 Cost: 0
NextHop: 127.0.0.1 Interface: InLoopBack0
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
State: Active NoAdv Age: 1d22h52m51s
Tag: 0
Destination: 127.0.0.1/32
Protocol: Direct Process ID: 0
Preference: 0 Cost: 0
NextHop: 127.0.0.1 Interface: InLoopBack0
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
State: Active NoAdv Age: 1d22h52m51s
Tag: 0
Destination: 172.16.10.0/24
Protocol: Direct Process ID: 0
Preference: 0 Cost: 0
NextHop: 172.16.10.1 Interface: Vlan-interface5
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
State: Active Adv Age: 1d22h52m52s
Tag: 0
Destination: 172.16.10.1/32
Protocol: Direct Process ID: 0
Preference: 0 Cost: 0
NextHop: 127.0.0.1 Interface: InLoopBack0
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
State: Active NoAdv Age: 1d22h52m53s
Tag: 0
Destination: 192.168.0.0/24
Protocol: Direct Process ID: 0
Preference: 0 Cost: 0
NextHop: 192.168.0.1 Interface: Vlan-interface1
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
State: Active Adv Age: 1d21h47m09s
Tag: 0
Destination: 192.168.0.1/32
Protocol: Direct Process ID: 0
Preference: 0 Cost: 0
NextHop: 127.0.0.1 Interface: InLoopBack0
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
State: Active NoAdv Age: 1d21h47m10s
Tag: 0
Destination: 192.168.1.0/24
Protocol: Direct Process ID: 0
Preference: 0 Cost: 0
NextHop: 192.168.1.1 Interface: Vlan-interface2
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
State: Active Adv Age: 1d21h54m51s
Tag: 0
Destination: 192.168.1.1/32
Protocol: Direct Process ID: 0
Preference: 0 Cost: 0
NextHop: 127.0.0.1 Interface: InLoopBack0
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
State: Active NoAdv Age: 1d21h54m52s
Tag: 0
Destination: 192.168.2.0/24
Protocol: Direct Process ID: 0
Preference: 0 Cost: 0
NextHop: 192.168.2.1 Interface: Vlan-interface3
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
State: Active Adv Age: 1d22h52m59s
Tag: 0
Destination: 192.168.2.1/32
Protocol: Direct Process ID: 0
Preference: 0 Cost: 0
NextHop: 127.0.0.1 Interface: InLoopBack0
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
State: Active NoAdv Age: 1d22h53m00s
Tag: 0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2018 04:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2018 04:54 AM
11-23-2018 04:54 AM
Re: HP A5120 Routing Table Problem
Can you specify what Firmware version your Switch was running on with the issue and what exact version "solved"? ...pretty strange behaviour (it looks like it didn't save the VLAN you added)
I'm not an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2019 06:19 PM - edited 01-10-2019 01:08 AM
01-09-2019 06:19 PM - edited 01-10-2019 01:08 AM
Re: HP A5120 Routing Table Problem
What is the Firmware version of your switch?