Closed Bug 1002622 Opened 12 years ago Closed 12 years ago

issues with 4 seamicro nodes

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: arich, Assigned: afernandez)

References

Details

I'm powering-on a bunch of seamicro nodes in preparation for kickstarting them, but 4 of the 14 I'm trying are having issues: https://inventory.mozilla.org/en-US/systems/show/7113/ I can see it power on on the console, and it tries to get an address from dhcp but times out/fails: net0: 00:22:99:45:86:72 on PCI01:00.1 (open) [Link:up, TX:0 TXE:0 RX:0 RXE:0] Waiting for link-up on net0... ok DHCP (net0 00:22:99:45:86:72)................ Connection timed out (0x4c106035) https://inventory.mozilla.org/en-US/systems/show/7119/ https://inventory.mozilla.org/en-US/systems/show/7120/ https://inventory.mozilla.org/en-US/systems/show/7121/ These three power on, but then the screen goes blank, and it doesn't appear to even get to the point where dhcp is queried. They all claim to be powered on and up, though: show server summary 55,61-63 Server NIC IP MAC #VDisks Status -------------------------------------------------------------- 55 0 not assigned 0022.9945.8672 1 up 55 1 not assigned 0022.9945.8674 - - 55 2 not assigned 0022.9945.8670 - - 55 3 not assigned 0022.9945.8676 - - 55 4 not assigned 0022.9945.8677 - - 55 5 not assigned 0022.9945.8671 - - 55 6 not assigned 0022.9945.8673 - - 55 7 not assigned 0022.9945.8675 - - 61 0 not assigned 0022.9945.8752 1 up 61 1 not assigned 0022.9945.8754 - - 61 2 not assigned 0022.9945.8750 - - 61 3 not assigned 0022.9945.8756 - - 61 4 not assigned 0022.9945.8757 - - 61 5 not assigned 0022.9945.8751 - - 61 6 not assigned 0022.9945.8753 - - 61 7 not assigned 0022.9945.8755 - - 62 0 not assigned 0022.9945.8762 1 up 62 1 not assigned 0022.9945.8764 - - 62 2 not assigned 0022.9945.8760 - - 62 3 not assigned 0022.9945.8766 - - 62 4 not assigned 0022.9945.8767 - - 62 5 not assigned 0022.9945.8761 - - 62 6 not assigned 0022.9945.8763 - - 62 7 not assigned 0022.9945.8765 - - 63 0 not assigned 0022.9945.8772 1 up 63 1 not assigned 0022.9945.8774 - - 63 2 not assigned 0022.9945.8770 - - 63 3 not assigned 0022.9945.8776 - - 63 4 not assigned 0022.9945.8777 - - 63 5 not assigned 0022.9945.8771 - - 63 6 not assigned 0022.9945.8773 - - 63 7 not assigned 0022.9945.8775 - -
Blocks: 1002630
dcops doesnt have much interaction with the seamicros other than the initial hardware setups/hands on support. moc/sres, can you assist with this?
Assignee: server-ops-dcops → server-ops
Component: Server Operations: DCOps → Server Operations
QA Contact: dmoore → shyam
Yeup, already briefly poked at this earlier with arr on irc. For node 55, a DHCP IP is obtained on other nics but not nic0. :arr needs it to be in nic0. As for the other nodes, I haven't poked those yet but will revisit this issue towards the later half of my day.
Case C-4439 created with Seamicro, will await WebEx invite.
Got off WebEx with Seamicro. The issue with node 55 has to do with the fact that node's 55 nic0 mac address is configured to use IP: 10.26.48.49 which is the same IP as the inband IP configured on the chassis (run: show running-config interface inband). Changing the IP of the node (in DHCP/DNS) will fix that issue. We then proceeded to check nodes 61-63 which were automagically working now (ie after we rebooted them)... so perhaps the inband IP conflict was to blame but technically this shouldn't be the case.
Assignee: server-ops → afernandez
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
I'm not sure who configured the inband IP (they didn't put it in inventory) or what it's for, but I guarantee it's on the wrong network if it's needed. inband is on vlan216. Aj: any idea what this is used for?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
FYI, I've unconfigured the inband interface for the moment till we can figure out what it's for. Once I did that, the IP for 55 came up fine.
After further discussion, I think we're just going to leave inband disabled.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.