- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- route add for backup NIC
Operating System - HP-UX
1757410
Members
3349
Online
108860
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
Discussions
Discussions
Forums
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
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
тАО08-03-2009 09:52 PM
тАО08-03-2009 09:52 PM
route add for backup NIC
Hi All,
In my environment backup server takes backup through cbi NIC card, for that backup server should able ping the backup NIC of the server1. How to add a route entry for CBI NIC to make it pingable by backup server.
Here are the details
There are 3 NIC's configured in server1
Server1# ifconfig lan2
lan2: flags=1843
inet 10.10.1.10 netmask ffffff00 broadcast 10.10.1.255
Server1# ifconfig lan5
lan5: flags=1843
inet 153.6.3.12 netmask ffffff00 broadcast 153.6.3.255
Server1# ifconfig lan900
lan900: flags=8000000000001843
inet 153.6.4.18 netmask fffffc00 broadcast 153.6.7.255
above lan5 is the cbi NIC
Server1# netstat -nvr
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136
10.10.1.10/255.255.255.255 10.10.1.10 UH 0 lan2 4136
153.6.3.12/255.255.255.255 153.6.3.12 UH 0 lan5 4136
153.6.4.18/255.255.255.255 153.6.4.18 UH 0 lan900 4136
153.6.164.2/255.255.255.255 153.6.3.254 UGH 0 lan5 1500
153.6.162.6/255.255.255.255 153.6.3.254 UGH 0 lan5 1500
153.6.162.8/255.255.255.255 153.6.3.254 UGH 0 lan5 1500
153.6.3.0/255.255.255.0 153.6.3.12 U 2 lan5 1500
10.10.1.0/255.255.255.0 10.10.1.10 U 2 lan2 1500
153.6.4.0/255.255.252.0 153.6.4.18 U 2 lan900 1500
127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 4136
default/0.0.0.0 153.6.7.254 UG 0 lan900 1500
Backup server:/# ifconfig -a
lo0: flags=1000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
ce0: flags=1000843 mtu 1500 index 2
inet 153.6.188.57 netmask fffffc00 broadcast 153.6.191.255
ether 0:3:ba:24:18:bf
In my environment backup server takes backup through cbi NIC card, for that backup server should able ping the backup NIC of the server1. How to add a route entry for CBI NIC to make it pingable by backup server.
Here are the details
There are 3 NIC's configured in server1
Server1# ifconfig lan2
lan2: flags=1843
inet 10.10.1.10 netmask ffffff00 broadcast 10.10.1.255
Server1# ifconfig lan5
lan5: flags=1843
inet 153.6.3.12 netmask ffffff00 broadcast 153.6.3.255
Server1# ifconfig lan900
lan900: flags=8000000000001843
inet 153.6.4.18 netmask fffffc00 broadcast 153.6.7.255
above lan5 is the cbi NIC
Server1# netstat -nvr
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136
10.10.1.10/255.255.255.255 10.10.1.10 UH 0 lan2 4136
153.6.3.12/255.255.255.255 153.6.3.12 UH 0 lan5 4136
153.6.4.18/255.255.255.255 153.6.4.18 UH 0 lan900 4136
153.6.164.2/255.255.255.255 153.6.3.254 UGH 0 lan5 1500
153.6.162.6/255.255.255.255 153.6.3.254 UGH 0 lan5 1500
153.6.162.8/255.255.255.255 153.6.3.254 UGH 0 lan5 1500
153.6.3.0/255.255.255.0 153.6.3.12 U 2 lan5 1500
10.10.1.0/255.255.255.0 10.10.1.10 U 2 lan2 1500
153.6.4.0/255.255.252.0 153.6.4.18 U 2 lan900 1500
127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 4136
default/0.0.0.0 153.6.7.254 UG 0 lan900 1500
Backup server:/# ifconfig -a
lo0: flags=1000849
inet 127.0.0.1 netmask ff000000
ce0: flags=1000843
inet 153.6.188.57 netmask fffffc00 broadcast 153.6.191.255
ether 0:3:ba:24:18:bf
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2009 01:26 AM
тАО08-04-2009 01:26 AM
Re: route add for backup NIC
hi ,
when the backup server is in the same subnet as the lan5 , it should be pinged.
as far as my knowledge goes virtual IP's should be in the same subnet as mother (lan5)
Could you please provide the backup server subnet ?
Regards,
bobby
when the backup server is in the same subnet as the lan5 , it should be pinged.
as far as my knowledge goes virtual IP's should be in the same subnet as mother (lan5)
Could you please provide the backup server subnet ?
Regards,
bobby
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2009 02:12 AM
тАО08-04-2009 02:12 AM
Re: route add for backup NIC
To make this possible, there must be a router ( or layer 3 switch act as a router) between CBI NIC and the backup server, this router must be added as static route entry on both the backup server and the CBI NIC.
For example in server1, this router must be in the same subnet as CBI NIC ex. 153.6.3.1, then add a static route for the 153.6.188.57 through this router.
And for the backup server(I do not know the default router for that server) the router must know how can reach 153.6.3.0 network.
For example in server1, this router must be in the same subnet as CBI NIC ex. 153.6.3.1, then add a static route for the 153.6.188.57 through this router.
And for the backup server(I do not know the default router for that server) the router must know how can reach 153.6.3.0 network.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2009 06:43 AM
тАО08-04-2009 06:43 AM
Re: route add for backup NIC
Assuming 156.6.3.254 is the router for this network, you already should have this connectivity. Having said that, in most enterprise data center environments, icmp packets (which ping relies on) is not let go from one network to the other, i.e., firewalls or routers are set to prevent this from happening.
Make sure your backup server has a static route coming to this network or host and make sure the firewall between the backup server and this server is allowing traffic for the ports that backup application is using. And you should be golden.
If your backup client setup is requiring the ping test to succeed, you will need to talk to your network guys to have this traffic allowed but I am sure they will balk at that as it introduces a lot of unnecessary traffic on the router.
Make sure your backup server has a static route coming to this network or host and make sure the firewall between the backup server and this server is allowing traffic for the ports that backup application is using. And you should be golden.
If your backup client setup is requiring the ping test to succeed, you will need to talk to your network guys to have this traffic allowed but I am sure they will balk at that as it introduces a lot of unnecessary traffic on the router.
________________________________
UNIX because I majored in cryptology...
UNIX because I majored in cryptology...
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP