Closed
Bug 741820
Opened 14 years ago
Closed 14 years ago
route 10.22/16 via 10.10.0.1 for im-log03 replacement access
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Atoll, Unassigned)
Details
(Whiteboard: [qa-])
per 740139, we'll need to force 10.22/16 via bondX.706 to access the im-log03 replacement. put this into place.
10.22/16 gw 10.10.0.1 added to adm1, route-bond1.706
09:04 <casey> [root@wp-adm01.phx.weave ~]# nc -vz 10.22.75.50 22
09:04 <casey> Connection to 10.22.75.50 22 port [tcp/ssh] succeeded!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•14 years ago
|
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•