validate ex2200 configs for Tegra move

RESOLVED FIXED

Status

Infrastructure & Operations
NetOps
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: van, Unassigned)

Tracking

Details

(Reporter)

Description

4 years ago
hi netops, 

we're moving tegras from mtv to scl3. we're going to be setting up 8x ex2200s for RelEng. since we've been configuring the switches differently than in the past, please validate the 1st switch's config and we can configure the other 7.

hostname: switch1.r602-11.ops.releng.scl3.mozilla.net
oob: 10.22.1.3 -> configured as me0 
OPs IP: 10.26.9.0 -> configured and shown up but not pingable
parent: core1.releng.console.scl3.mozilla.net: ge-1/0/28


also 3 CDUs are attached to this switch, however none of them are reachable. The IPs are on the newly created vlan 284 so can you confirm that it's passing traffic? 

pdu1.r602-11.tegra.releng.scl3.mozilla.com --ip 10.26.84.199
pdu2.r602-11.tegra.releng.scl3.mozilla.com --ip 10.26.84.200
pdu3.r602-11.tegra.releng.scl3.mozilla.com --ip 10.26.84.201
(Reporter)

Updated

4 years ago
Blocks: 949751
(Reporter)

Comment 1

4 years ago
i fat fingered the next-hop so the OPs IP is pingable now. still unable to reach my CDUs.

-    route 0.0.0.0/0 next-hop 10.26.84.1;
+    route 0.0.0.0/0 next-hop 10.26.8.1;
(Reporter)

Comment 2

4 years ago
i was able to figure out the issue. like a noob, i fat fingered my gateway so when it didnt work, commit confirmed rolled back and that's why my CDUs didn't ping after I fixed the gateway.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Blocks: 945995
I upgraded that switch to 12.3R3.4 and got rid of the warning "THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE".
(Reporter)

Comment 4

4 years ago
i upgraded the other 7 switches to 12.3R3.4 as well.

switch[12].r[26]0[12]-11
Blocks: 957278
You need to log in before you can comment on or make changes to this bug.