- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Procurve 5412zl - unable to traceroute to dire...
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
тАО03-07-2010 03:45 PM
тАО03-07-2010 03:45 PM
Procurve 5412zl - unable to traceroute to direct attached devices
Devices on the 192.168.1.x subnet can access and use the PIX at that address. Upon adding a VLAN and new subnet, it has been discovered that other subnets cannot access this device. Long story short: performing a traceroute from *inside* the 192.168.1.1 switch fails to 192.168.250.2 (which is directly attached). To further complicate the issue, this same switch is able to ping the device successfully. How can ping complete successfully if the switch doesn't even know how to traceroute to a direct-attached device in the same subnet and vlan?
To further complicate the issue, other devices in the 192.168.1.x subnet are able to access the PIX at 192.168.1.2. I had another device in a similar situation and I was able to fix the issue by unplugging it and moving it to a different port but this did not work for the PIX.
I have spent the last two months figuring this out. I can't reboot the switch without a ton of planning because iSCSI is running through the switch for a lot of servers (I inherited this situation - not my design).
Any insight can be payed for out of pocket - I am that frustrated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2010 09:14 PM
тАО03-07-2010 09:14 PM
Re: Procurve 5412zl - unable to traceroute to direct attached devices
Because these are 2 different VLANS and 2 different subnets so for sure you will not be able to comunicate between them unless there is a device handling routing between them, so in this case you can just enable routing on the switch by issuing the command
#ip routing
Also make sure ro assing an ip address under the 2nd VLAN if not already assigned.
Then test the connectivity :)
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2010 05:33 AM
тАО03-08-2010 05:33 AM
Re: Procurve 5412zl - unable to traceroute to direct attached devices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2010 06:37 AM
тАО03-08-2010 06:37 AM
Re: Procurve 5412zl - unable to traceroute to direct attached devices
Contact Cisco Support and check this with them plz and let us know
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2010 06:40 AM
тАО03-08-2010 06:40 AM
Re: Procurve 5412zl - unable to traceroute to direct attached devices
This is my problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2010 09:12 PM
тАО03-08-2010 09:12 PM
Re: Procurve 5412zl - unable to traceroute to direct attached devices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2010 02:00 AM
тАО03-09-2010 02:00 AM