Closed
Bug 799486
Opened 12 years ago
Closed 12 years ago
Plumb Eucalyptus VLANs (1200-1299) into all nodes in SCL3/102-14 rack
Categories
(Infrastructure & Operations Graveyard :: NetOps, task)
Infrastructure & Operations Graveyard
NetOps
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gozer, Assigned: ahill)
References
()
Details
The newly assigned VLAN range for Eucalyptus should be plumbed into all nodes in the Petri rack in SCL3 (102-14). Could all the ports in that rack be trunked into these VLANs, keeping the current labs physical VLAN (111) as the default, untagged one ? Thanks!
Reporter | ||
Comment 1•12 years ago
|
||
Gentle ping?
Should be complete. I used the existing interface-range for these servers, so let me know if anything got missed.
Reporter | ||
Comment 3•12 years ago
|
||
All hosts in that rack dropped off. Did you keep all untagged traffic on the labs physical VLAN (I suspect not) ?
Yes. I switched the port mode to trunk, set the native vlan-id (untagged) to phy-labs (111), and gave access on the trunk to all of the Eucalyptus vlans (tagged). Let me know if I can help troubleshoot or if I should revert.
Reporter | ||
Comment 5•12 years ago
|
||
Sounds like the correct thing to do. But, definitely something wrong, as I can't reach any of the hosts in that rack anymore... For instance, you can test with euca0.phy.labs.scl3.mozilla.com. No need to quickly revert this, as the eucalyptus rack is not in use yet, but would be nice to troubleshoot this. How about I hunt you down on IRC sometime tomorrow and track this down?
We got this figured out.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Infrastructure & Operations
Updated•2 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•