Ok, so this is a little tricky but here goes.
We had 3 subnets.
192.168.128.0/23 which has change as per past posts.
192.168.130.0/24 which was our management network that we would
access our servers from the corp network
192.168.254.0/24 which is the internal production network. i.e. all
the boxes would talk to each other on this network.
3 AFSDB's are on the internal network and the management network.
3 fileservers are on the internal network and the management network.
we changed the management network from 192.168.130.0/24 to
192.168.200.0/22
AFSDB1 had
192.168.254.21
192.168.130.21
AFSDB2 had
192.168.254.22
192.168.130.22
AFSDB3 had
192.168.254.31
192.168.130.31
Fileserver1 had
192.168.254.20
192.168.130.20
Fileserver2 had
192.168.254.11
192.168.130.11
Fileserver3 had
192.168.254.48
192.168.130.48
Because of the need to change the ip's in the corp network we needed
to change the ip's in the managment network. NOTE: the internal
production network stayed the same.192.168.254.0/24
AFSDB1
192.168.200.111 (was 192.168.130.21)
AFSDB2
192.168.200.112 (was 192.168.130.22)
AFSDB3
192.168.200.113 (was 192.168.130.31)
Fileserver1
192.168.200.121 (was 192.168.130.20)
Fileserver2
192.168.200.122 (was 192.168.130.11)
Fileserver3
192.168.200.123 (was 192.168.130.48)
Yesterday I was dealing with issues getting the 'fs' process working
on the Fileservers. What I ended up doing was shutting down the
192.168.200.0/24 ip's and everything was fine. Then I did a vos
syncvldb and it was saying that a certain volume was located on
another server. (note earlier someone ran vos syncserv without doing
a syncvldb before hand)
Now today I ran,
vos syncvldb on all servers and vos syncserv on all server and it
worked. I have the 192.168.200.0/22 network shutoff.
Fileserver1 and Fileserver3 are working, but Fileserver2 give me the
following error in /usr/afs/logs/FileLog
-----snip-----
Fri Oct 20 11:25:41 2006 File server starting
Fri Oct 20 11:25:41 2006 afs_krb_get_lrealm failed, using
office.h2st.net.
Fri Oct 20 11:25:41 2006 VL_RegisterAddrs rpc failed; The IP address
exists
on a different server; repair it
Fri Oct 20 11:25:41 2006 VL_RegisterAddrs rpc failed; See VLLog for
details
Fri Oct 20 11:25:41 2006 Fatal error in library initialization,
exiting!!
---------------
It would seem that I've done something wrong. i.e. way back when I
did vos changeaddr
Any ideas?
On Oct 20, 2006, at 10:38 AM, Derrick J Brashear wrote:
On Fri, 20 Oct 2006, Pucky Loucks wrote:
What I mean is that we had AFS working on 192.168.130.0/24 and
our corporate network is on 192.168.128.0/23. The corp network
needs to grow, so we are changing it to 192.168.128.0/22 (this
is where are our issue starts) 130 will end up being included in
192.168.128.0/22(which is not what we want for other reasons).
Ok, so, you did or did not renumber the fileserver?
yes I renumbered the fileservers
ok, so, from what to what, and where does the vlserver believe the
data is, and where is it really?
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
