09-15-2014
Quote:
Originally Posted by
yuvarakasil
we have chosen different IP(192.168.7.xxx) of vlan 100 for new servers in IBM Pureflex, however the existing server have IP range 192.168.0.xxx) of vlan 100.
Your network setup is faulty from the beginning: a "VLAN" is a virtual construct which matches a collision domain, therefore to interact with another network you need to couple these with either a bridge or something operating on a layer higher than 2 (like a router, ...).
If you configure your VLAN 100 to be the basis of network 192.168.0, which is a Class-C-network (=8 bit host mask) it can't be the basis of the network 192.168.7 at the same time, because this is
another Class-C network.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. IP Networking
Hi,
I would like to know how i can setup my unix computer to connect to novell. Anybody any idea? (5 Replies)
Discussion started by: edw1ns
5 Replies
2. Solaris
I have 4 V440 servers running Solaris 9. I have their interfaces configured (ce0) and have connectivity to our network. However, after reboot,...the connectivity is lost although the interface shows that its still up after an ifconfig -a.
Only after I reconfigure the interface do I restore... (19 Replies)
Discussion started by: StorageGuy
19 Replies
3. Solaris
I have a solaris 10 x86 installed on a VMware server. It has been runing well for a couple weeks, but started to have network connectivity issue since last week. The network card seems to be up and down every one minute. So I got connection closed after I sshed to it for about one minute.
#... (2 Replies)
Discussion started by: fredao
2 Replies
4. UNIX for Advanced & Expert Users
Hi guys,
I had two computer which is one with vista and other one with fedora and they are connected via one router.
from vista to fedora is fine.. I can ping or connect via putty using Ip address but I couldn't connect putty using hostname/domain.
If I typed in fedora the hostname,... (0 Replies)
Discussion started by: peac3
0 Replies
5. UNIX for Dummies Questions & Answers
red hat 5 update 4 64bit. linux newby. on an interactive boot i can ping -t my vm linux server from my physical MS XP workstation and a vm W2000 64 bit server until xend is started, after that i get destination unreachable. if i choose not to start xend on the interactive boot i retain... (1 Reply)
Discussion started by: slartibartfast9
1 Replies
6. Shell Programming and Scripting
Hello,
I have a requirement to check the tcp network connectivity between server it's running on and the list of host's and ports combination.
i have written the below code but it doesn't work, but when i execute the nc command outside the script it works fine.
please help me where i am... (8 Replies)
Discussion started by: sknovice
8 Replies
7. IP Networking
ello,
i am new to the networking side.
I have a requirement to check the tcp network connectivity between server it's running on and the list of host's and ports combination.
please help me where i am going wrong.
my code:
#!/bin/bash
#read the file line by line
cd "$1"
cat... (17 Replies)
Discussion started by: sknovice
17 Replies
8. HP-UX
Newbie with UNIX here.
Currently troubleshooting a UNIX terminal we have.
I determined it to be bad and swapped it out with a known good terminal. I went in and changed the IP address and host name to reflect the old terminal. Although now there is no connectivity.
I swapped out the NIC... (1 Reply)
Discussion started by: kevinlord190
1 Replies
9. UNIX for Dummies Questions & Answers
Hi!
I am not sure if this is the right place to post this question. What I did was to download vmware onto my laptop, them install a linux distro as a guest O.S., on VM network configuration I have used "bridge", them I used Virtual Network Editor to chose the network interface, but as I write... (4 Replies)
Discussion started by: fretagi
4 Replies
10. Shell Programming and Scripting
Hello All,
We are running multiple codes in prod all having different sources of databases in other servers. Many times due to network issue connectivity and DB issue the jobs got failed and to recover them become very brainstorming . I planning to create one script that can pre check if all the... (0 Replies)
Discussion started by: looney
0 Replies
LEARN ABOUT FREEBSD
if_gre
GRE(4) BSD Kernel Interfaces Manual GRE(4)
NAME
gre -- encapsulating network device
SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file:
device gre
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_gre_load="YES"
DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where
they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop.
gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands.
This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the
type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco
routers. gre also supports Cisco WCCP protocol, both version 1 and version 2.
The gre interfaces support a number of additional parameters to the ifconfig(8):
grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option.
enable_csum Enables checksum calculation for outgoing packets.
enable_seq Enables use of sequence number field in the GRE header for outgoing packets.
EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.*
/
/
+------ the Internet ------+
Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal
address 192.168.2.1, the following commands will configure the tunnel:
On router A:
ifconfig greN create
ifconfig greN inet 192.168.1.1 192.168.2.1
ifconfig greN inet tunnel A B
route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1
On router B:
ifconfig greN create
ifconfig greN inet 192.168.2.1 192.168.1.1
ifconfig greN inet tunnel B A
route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1
NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending
on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8).
For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop.
The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero.
SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8)
A description of GRE encapsulation can be found in RFC 2784 and RFC 2890.
AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org>
Heiko W.Rupp <hwr@pilhuhn.de>
BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as
if they would belong to this interface.
The sequence number field also used only for outgoing packets.
BSD
November 7, 2014 BSD