[f-nsp] Difference between'ip address' and VE IP address? ServerIron XL

[Drew Weaver]

ServerIRON XL 07.4.01mT12

In a config for an older load balancer I have:

vlan 5 by port
 untagged ethe 1 to 8
  router-interface ve 4

ip address 192.168.1.94 255.255.255.224

then:

interface ve 4
 ip address 192.168.1.67 255.255.255.224

I notice at seemingly random intervals when I am having nagios ping 192.168.1.67 I get random spikes of latency:

Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time=1ms TTL=61
Reply from 192.168.1.67: bytes=32 time=1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time=18ms TTL=61
Reply from 192.168.1.67: bytes=32 time=9ms TTL=61
Reply from 192.168.1.67: bytes=32 time=6ms TTL=61
Reply from 192.168.1.67: bytes=32 time=7ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time=13ms TTL=61
Reply from 192.168.1.67: bytes=32 time=4ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time=2ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time=8ms TTL=61
Reply from 192.168.1.67: bytes=32 time=1ms TTL=61
Reply from 192.168.1.67: bytes=32 time=55ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time=3ms TTL=61
Reply from 192.168.1.67: bytes=32 time=56ms TTL=61
Reply from 192.168.1.67: bytes=32 time=50ms TTL=61
Reply from 192.168.1.67: bytes=32 time=15ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time=53ms TTL=61
Reply from 192.168.1.67: bytes=32 time=25ms TTL=61
Reply from 192.168.1.67: bytes=32 time=68ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time=54ms TTL=61
Reply from 192.168.1.67: bytes=32 time=46ms TTL=61
Reply from 192.168.1.67: bytes=32 time=43ms TTL=61
Reply from 192.168.1.67: bytes=32 time=24ms TTL=61
Reply from 192.168.1.67: bytes=32 time<1ms TTL=61
Reply from 192.168.1.67: bytes=32 time=107ms TTL=61

and if I nail a ping on 192.168.1.94 during the same time of latency it stays at <1ms.

#1 Are these routed different, use different resources to respond to pings?
#2 Is this a problem?
#3 I can't even remember why I have the VE in there like that it has been years since we set this up but it seems extraneous. I am sure there is some reason I did this originally but now I am totally drawing a blank.

Any thoughts?

-Drew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20101015/50126813/attachment.html>