IP addresses reassigned

[Evolvenet]

Hi there,

Not wanting to jump the chain of command but is this standard operating procedure at Jaguar? Is there someone who can fix this?

- - - Tech - - - : Zishan. 2008-06-30 / 12:03:40
We had a network issue that caused the traffic to bounce back and forth. This affected all the servers in the data center. This looping issue has been resolved and network is accessible now so you should be all set.

Let us know if you need further assistance.

Regards,
Zishan


+ + + Client + + + : Marc.Hauge 2008-06-30 / 12:10:12

Nope. No ping from my end. A quick traceroute seems to die

traceroute -I e.volve.net
traceroute to e.volve.net (69.73.138.221), 64 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 1.426 ms 0.853 ms 2.201 ms
2 dsl211-210-165.sea1.dsl.speakeasy.net (74.211.210.165) 1.418 ms 1.340 ms 1.177 ms
3 er1.sea1.speakeasy.net (64.81.168.1) 16.634 ms 14.230 ms 15.232 ms
4 220.ge-0-1-0.cr2.sea1.speakeasy.net (69.17.83.233) 15.266 ms 14.188 ms 10.164 ms
5 ge3-0.cr02.sea01.pccwbtn.net (198.32.180.13) 10.570 ms 14.162 ms 14.939 ms
6 gnax.ge2-13.br01.atl01.pccwbtn.net (63.216.31.130) 81.253 ms 80.153 ms 85.921 ms
7 209.51.131.90 (209.51.131.90) 80.656 ms 80.854 ms 81.910 ms
8 icharts.in (69.73.138.116) 80.995 ms 85.225 ms 90.212 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *

No issue to you guys though

traceroute -I jaguarpc.com
traceroute to jaguarpc.com (69.73.138.32), 64 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 1.165 ms 0.582 ms 0.634 ms
2 dsl211-210-165.sea1.dsl.speakeasy.net (74.211.210.165) 1.620 ms 1.355 ms 1.206 ms
3 er1.sea1.speakeasy.net (64.81.168.1) 13.955 ms 14.383 ms 15.135 ms
4 220.ge-0-1-0.cr2.sea1.speakeasy.net (69.17.83.233) 9.680 ms 9.789 ms 9.970 ms
5 ge3-0.cr02.sea01.pccwbtn.net (198.32.180.13) 15.159 ms 10.078 ms 9.875 ms
6 gnax.ge2-13.br01.atl01.pccwbtn.net (63.216.31.130) 120.550 ms 206.812 ms 202.179 ms
7 209.51.131.90 (209.51.131.90) 85.880 ms 85.286 ms 80.914 ms
8 goliath.nocdirect.com (69.73.138.32) 91.007 ms 85.098 ms 94.323 ms




- - - SYSTEM - - - 2008-06-30 / 12:37:25
A customer service representative has begun working on this issue.

- - - Tech - - - : Zishan. 2008-06-30 / 13:10:59
-Internal Update-


- - - SYSTEM - - - 2008-06-30 / 13:29:44
A customer service representative has begun working on this issue.

- - - Tech - - - : Jeff.S 2008-06-30 / 13:41:10



+ + + Client + + + : Marc.Hauge 2008-06-30 / 13:51:13

Hmmm,
Down again although it was up for the last couple hours.

traceroute -I e.volve.net
traceroute: Warning: e.volve.net has multiple addresses; using 69.73.138.221
traceroute to e.volve.net (69.73.138.221), 64 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 1.304 ms 0.650 ms 0.949 ms
2 dsl211-210-165.sea1.dsl.speakeasy.net (74.211.210.165) 1.827 ms 1.428 ms 1.383 ms
3 er1.sea1.speakeasy.net (64.81.168.1) 33.198 ms 229.097 ms 60.735 ms
4 220.ge-0-1-0.cr2.sea1.speakeasy.net (69.17.83.233) 14.201 ms 9.856 ms 12.046 ms
5 ge3-0.cr02.sea01.pccwbtn.net (198.32.180.13) 9.384 ms 15.240 ms 12.645 ms
6 gnax.ge2-13.br01.atl01.pccwbtn.net (63.216.31.130) 117.067 ms 108.523 ms 155.560 ms
7 209.51.131.90 (209.51.131.90) 82.441 ms 81.175 ms 82.382 ms
8 phobos.nocdirect.com (69.73.138.150) 82.965 ms 82.222 ms 82.504 ms
9 icharts.in (69.73.138.116) 82.921 ms 82.076 ms 83.436 ms
10 * * *
11 * * *
12 * *




- - - SYSTEM - - - 2008-06-30 / 14:25:28
A customer service representative has begun working on this issue.

+ + + Client + + + : Marc.Hauge 2008-06-30 / 15:10:20

Hi there,

Just looking for an update on this VPS instance.
Thanks,
Marc


+ + + Client + + + : Marc.Hauge 2008-06-30 / 15:22:50

Hmmm,

Not sure why the traceroute dies at icharts.in. Doesn't seem to be hosted with jaguar. Any idea what's going on there?

8 phobos.nocdirect.com (69.73.138.150) 82.965 ms 82.222 ms 82.504 ms
9 icharts.in (69.73.138.116) 82.921 ms 82.076 ms 83.436 ms




+ + + Client + + + : Marc.Hauge 2008-06-30 / 16:50:41

Hi there,

I'm going to need an ETA on this sometime soon.

Marc


- - - Tech - - - : Stefan. 2008-06-30 / 16:55:03

Hi,

Please hold on we are working on your issue we will update you very soon.

Feel free to contact us if you need further assistance.
-----
Best Regards,
Stefan
Technical Support | JaguarPC


- - - SYSTEM - - - 2008-06-30 / 17:02:11
A customer service representative has begun working on this issue.

- - - Tech - - - : Zishan. 2008-06-30 / 17:06:05
The Ips attached to your VPS were problematic and were having conflicts. That was the source of problem. Those Ips have been removed and the new Ips have been assigned:

69.73.164.85
69.73.164.86
69.73.164.87

You will need to update the Nameservers Ips and the sites Ips.

Let us know if you need further assistance.

Regards,
Zishan


+ + + Client + + + : Marc.Hauge 2008-06-30 / 21:02:22

Hi there,

I'm not sure I find that acceptable. You're telling me you can't route my previous IPs? At all? If it is the case can you expand on why it's "problematic" before I have to spend the evening digging through mail, httpd, dns and so forth.

Marc


- - - SYSTEM - - - 2008-06-30 / 22:41:43
A customer service representative has begun working on this issue.

- - - Tech - - - : Howard.A. 2008-06-30 / 22:49:22

Hi Marc,

Sorry for the inconvenience. It appears that the IPs on your server were causing problem and were routing to another server on the network. Therefore, we had to assign three new IPs to your server. You can update your site IPs and the IPs of your private nameservers (if registered) at your registrar to the new corresponding ones provided above.
I am pasting them for you below.

69.73.164.85
69.73.164.86
69.73.164.87

Please advise.

Do let us know if you need further assistance.

Regards,
Howard A.
JaguarPC


+ + + Client + + + : Marc.Hauge 2008-06-30 / 22:57:04

Any particular reason the other server shouldn't have it's IPs revoked given that I've had these for a year or more?





+ + + Client + + + : Marc.Hauge 2008-07-01 / 00:52:47

It's a tad more than an inconvenience. Arbitrarily reprovisioning the IP's I've had seems suspect. Is there a reason the original IPs can't be used? Did ARIN take them away? Help me understand your predicament here.


- - - SYSTEM - - - 2008-07-01 / 01:15:45
A customer service representative has begun working on this issue.

- - - Tech - - - : Howard.A. 2008-07-01 / 01:21:00

Hi Marc,

The previous tech is not currently in shift, and I am not sure about the reason those IPs are assigned to the other server. You need not worry or suspect about anyone adding your IPs as they can only be added on the server through the Virtuozzo panel which manages the VPSs. I am not sure about the reason your IPs are currently assigned on another server, however, I suggest that you update your IPs at the registrar as soon as possible to avoid any downtime.
Please advise.

Do let us know if you need further assistance.

Regards,
Howard A.
JaguarPC


+ + + Client + + + : Marc.Hauge 2008-07-01 / 01:29:59

Downtime has been had and I'm a little miffed. Can the IP's in question be reassigned to my VPS instance? More importantly will you reassign them?

It concerns me that Jag would do this without a proper explanation as to why it needed to be done other than, "the IPs on your server were causing problem".


- - - SYSTEM - - - 2008-07-01 / 04:35:45
A customer service representative has begun working on this issue.

- - - Tech - - - : Edward. 2008-07-01 / 05:25:22
Hi,

Actually a dedicating client was using our IP's without informing us. He just added some IP's from 69.73.138 range to his server which caused this conflict. To avoid happening this again we changed your IP's and assigned IP's to you from a new range.

Please advice that do you need old IP's assigned to your VPS.

Let us know if you need further assistance.

Regards,
Edward


+ + + Client + + + : Marc.Hauge 2008-07-01 / 10:18:21

Yes, actually, I would require the old IPs. To avoid this in the future you might make a protocol for other customers hijacking IPs already in use.


- - - SYSTEM - - - 2008-07-01 / 10:21:59
A customer service representative has begun working on this issue.

- - - Tech - - - : Edward. 2008-07-01 / 10:40:34
Hi,

We have already informed client responsible for it. New IP's from our fresh range have been already assigned to you. Are you having any problem with these.

Let us know if you need further assistance.

Regards,
Edward


+ + + Client + + + : Marc.Hauge 2008-07-01 / 10:46:21

I think you're missing my point. The solution to your problem is NOT letting another customer decide how your IPs will be routed. If the decision is from Jaguar to knock me offline with no notice and reroute my IP addresses in favor of a dedicated server client paying more I can understand.

But if that's not the case (and even if it is) it raises some questions about how you guys manage and treat your customers.


- - - SYSTEM - - - 2008-07-01 / 10:57:05
A customer service representative has begun working on this issue.

- - - Tech - - - : Zishan. 2008-07-01 / 12:04:05
Marc,

We do not favor any client just because he is paying more. The Ips are conflicting with a dedicated server and we don't have root password for it. We have already contacted that client to provide us the root password so that we can check that why those Ips are assigned to it. We don't allow this at all that clients add Ips on your own to their servers. The reason that your Ips were changed was just to being you online ASAP. If we will wait for the dedicated client's response then you would have been offline till now.

We will not wait for ever for the root password. I have just sent an email to his partner and if we don't hear from them, we will get the root password reset to check the Ips status.

Let us know if you need further assistance.

Regards,
Zishan


+ + + Client + + + : Marc.Hauge 2008-07-01 / 20:13:51

Is there resolution as to where these IPs are going to land?


+ + + Client + + + : Marc.Hauge 2008-07-01 / 20:18:47

Also, just as a thought, you could simply switch the offending machine off. That might get their attention. It got mine.


- - - SYSTEM - - - 2008-07-01 / 20:20:49
A customer service representative has begun working on this issue.

- - - Tech - - - : Andrew. 2008-07-01 / 20:28:38

Hi,
We already turned that server down and the IP related issue is already resolved.

Let us Know if you need further assistance.

Regards,
Andrew


+ + + Client + + + : Marc.Hauge 2008-07-02 / 01:01:17
That's good news except that 69.73.138.221 still hasn't been returned. Is there a reason for that?

Sure looks like it's heading to the same place

traceroute -I 69.73.138.221
traceroute to 69.73.138.221 (69.73.138.221), 64 hops max, 60 byte packets
1 192.168.2.1 (192.168.2.1) 1.505 ms 1.053 ms 0.918 ms
2 * * *
3 ge-1-5-ur01.seattle.wa.seattle.comcast.net (68.86.99.49) 9.210 ms 18.470 ms *
4 te-8-4-ar01.burien.wa.seattle.comcast.net (68.86.96.189) 11.433 ms 18.968 ms 9.502 ms
5 68.86.90.222 (68.86.90.222) 10.298 ms 11.941 ms 9.694 ms
6 68.86.90.221 (68.86.90.221) 13.643 ms 13.238 ms 15.045 ms
7 pos-0-7-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.85.201) 26.827 ms 42.997 ms 25.891 ms
8 pos-0-6-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.85.78) 29.477 ms 29.306 ms 31.425 ms
9 te-1-1-pr01.11greatoaks.ca.ibone.comcast.net (68.86.84.126) 33.950 ms 31.882 ms 38.513 ms
10 Tenge13-3.br02.sjo01.pccwbtn.net (63.218.179.25) 33.980 ms 32.198 ms 33.957 ms
11 gnax.ge2-13.br01.atl01.pccwbtn.net (63.216.31.130) 88.529 ms 89.223 ms 91.547 ms
12 209.51.131.90 (209.51.131.90) 98.085 ms 92.611 ms 94.406 ms
13 icharts.in (69.73.138.116) 95.686 ms 91.642 ms 87.092 ms
14 * * *
15 * * *
16 * * *

At any rate, are you guys unable to return 69.73.138.221? If you can is there an estimate on when that would happen?

[Evolvenet]

Ahh, the power of the boards. Fixed. Thanks gentlemen for doing what should have been the right thing all along.

traceroute -I 69.73.138.221
traceroute to 69.73.138.221 (69.73.138.221), 64 hops max, 60 byte packets
1 192.168.2.1 (192.168.2.1) 1.435 ms 1.217 ms 0.937 ms
2 * * *
3 ge-1-5-ur01.seattle.wa.seattle.comcast.net (68.86.99.49) 8.333 ms 12.360 ms 8.254 ms
4 te-8-4-ar01.burien.wa.seattle.comcast.net (68.86.96.189) 10.161 ms 10.394 ms *
5 68.86.90.222 (68.86.90.222) 13.492 ms 9.719 ms 14.638 ms
6 68.86.90.221 (68.86.90.221) 18.409 ms 16.667 ms 14.041 ms
7 pos-0-7-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.85.201) 28.976 ms 26.441 ms 25.775 ms
8 pos-0-6-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.85.78) 31.905 ms 28.864 ms 32.054 ms
9 te-1-1-pr01.11greatoaks.ca.ibone.comcast.net (68.86.84.126) 33.909 ms 32.994 ms 33.375 ms
10 Tenge13-3.br02.sjo01.pccwbtn.net (63.218.179.25) 31.515 ms 34.408 ms 38.331 ms
11 gnax.ge2-13.br01.atl01.pccwbtn.net (63.216.31.130) 86.580 ms 87.638 ms 87.967 ms
12 209.51.131.90 (209.51.131.90) 86.107 ms 87.738 ms 85.852 ms
13 phobos.nocdirect.com (69.73.138.150) 88.071 ms 92.060 ms 88.715 ms
14 e.volve.net (69.73.138.221) 88.019 ms 87.099 ms 89.047 ms

Marc

[kickerofelves]

I am having the exact same problem with my SDX site, largeheartedboy.com (timing out at icharts.in).

1 24 33 41 72.249.0.65 -
2 56 122 36 8.9.232.73 ge-6-18.car1.dallas1.level3.net
3 51 60 74 4.68.19.69 ae-23-79.car3.dallas1.level3.net
4 54 35 53 4.68.63.194 -
5 67 84 81 213.248.80.145 atl-bb1-link.telia.net
6 75 74 69 213.248.90.54 globalnet-127291-atl-bb1.c.telia.net
7 94 132 118 63.247.69.178 atl-core-g-g1-6.gnax.net
8 80 85 75 209.51.131.90 -
9 41 79 112 69.73.138.116 icharts.in
10 Timed out Timed out Timed out -
11 Timed out Timed out Timed out -
12 Timed out Timed out Timed out -
13 Timed out Timed out Timed out -

I just put in a ticket.

[JPC-Awais]

kickerofelves,

We have corrected this and replied your ticket.

[kickerofelves]

kickerofelves,

We have corrected this and replied your ticket.

And quickly, as always. Thanks to you and the support team, Edward.

[the_ancient]

Ahh, the power of the boards. Fixed.

Ask for escalation next time... I would have after the tech repeated him self for the 3rd time....

on the 4th repeating of the same response an email bomb to Greg and Masood would have went out....