action #111171
closedHandle installation of new FC switch size:M
Added by nicksinger almost 2 years ago. Updated over 1 year ago.
0%
Description
Motivation¶
A new FC switch was ordered for the NetApp testing and should be installed as replacement for the older existing pantani-data-switch
## Suggestions
- Switch needs to picked up from Reception (Iwona Maha)
- It needs to be clarified where the switch needs to be, what connections, who will handle it etc.
- Can be stored in the QA temporary storage
- Connect and await feedback from common users, e.g. sebchlad and mmoese, if everything works as expected
Updated by okurz almost 2 years ago
- Due date set to 2022-05-31
- Status changed from Workable to Feedback
- Assignee changed from nicksinger to sebchlad
- Target version changed from Ready to future
We picked the switch from postal station, is now in cold storage, directly below the white board. Waiting for further clarification from Seba.
Updated by okurz almost 2 years ago
- Assignee changed from sebchlad to nicksinger
- Target version changed from future to Ready
mgriessmeier needs the serial number for procurement, no rush.
Updated by mkittler almost 2 years ago
- Due date changed from 2022-05-31 to 2022-06-06
Updated by nicksinger almost 2 years ago
- Assignee changed from nicksinger to sebchlad
Updated by sebchlad almost 2 years ago
nicksinger wrote:
I think that means we now need input from @sebchlad how we should continue.
@sebchlad - did I understand you right that we can just pull out the old switch and plug the new one in and you can do the rest of the configuration/mapping remotely?
@nicksinger: from our conversation on slack:
"I will drop some comments in the ticket but in essence if you happen to replace the old one with a new one and do the cabling as they are we should be good; of course I would need to access the san switch later on to prepare the zones etc. but I can easily handle that; as a matter of fact such access would be essential as some tests require re-zoning etc."
"the old one... I think ideally you would keep it where it is so eventually we can do more cabling and have more testing set-ups"
I will contact you over slack to provide the input ;-)
Updated by okurz almost 2 years ago
- Due date changed from 2022-06-06 to 2022-06-17
- Status changed from Feedback to New
- Assignee changed from sebchlad to nicksinger
Thx Seba, so the next time we are at the location we can handle this
Updated by okurz almost 2 years ago
- Due date changed from 2022-06-17 to 2022-07-01
nicksinger unavailable right now
Updated by okurz almost 2 years ago
Installed the switch. nsinger and me configured it initially using a serial terminal connected to /dev/ttyS0 on qanet using the command screen /dev/ttyS0 9600. Configured passwords for user "admin" with password same as network switches in QA, same for user "user". Following https://techdocs.broadcom.com/us/en/fibre-channel-networking/switches/g620-switch/1-0/v25857540/GUID-CECEE437-3618-4BBF-BB80-1F9DE5F09E2D_1/GUID-5739CC68-2907-4C0D-9A24-EAC0B1A415B5_1.html we configured for DHCP using the command ipaddrset and write "On" when asked about DHCP:
DHCP [Off]:On
IP address is being changed...
Done.
2022/06/21-13:01:30, [IPAD-1000], 17, CHASSIS, INFO, BrocadeG620, SW/0 Ether/0 IPv4 manual none/none DHCP On.
SWG620:FID128:admin> 2022/06/21-13:01:32, [IPAD-1000], 18, CHASSIS, INFO, BrocadeG620, SW/0 Ether/0 IPv4 DHCP 10.162.32.230/18 DHCP On.
2022/06/21-13:01:32, [IPAD-1001], 19, CHASSIS, INFO, BrocadeG620, CP/0 IPv4 DHCP 10.162.63.254 DHCP On.
2022/06/21-13:01:32, [IPAD-1003], 20, CHASSIS, INFO, BrocadeG620, DNS parameters saved successfully.
On qanet dhcp log:
Jun 21 14:55:58 qanetnue dhcpd: DHCPDISCOVER from d8:1f:cc:7c:0f:e0 via sif0
Jun 21 14:55:59 qanetnue dhcpd: DHCPOFFER on 10.162.32.230 to d8:1f:cc:7c:0f:e0 (SWG620) via sif0
Jun 21 14:55:59 qanetnue dhcpd: DHCPREQUEST for 10.162.32.230 (10.162.0.1) from d8:1f:cc:7c:0f:e0 (SWG620) via sif0
Jun 21 14:55:59 qanetnue dhcpd: DHCPACK on 10.162.32.230 to d8:1f:cc:7c:0f:e0 (SWG620) via sif0
Added DHCP and DNS config: https://gitlab.suse.de/qa-sle/qanet-configs/-/commit/344d99a845ca1539afde8cc80c39859904f276f2
We then moved the serial cable connection to sonic. So connected to ttyS0 on sonic.
Updated by okurz almost 2 years ago
- Tags deleted (
next-office-day) - Status changed from New to Feedback
- Assignee changed from nicksinger to okurz
And now we have documented everything we found in racktables which means first adding all the missing interfaces to the target machines.
@sebchlad can you check if everything is good?
Updated by livdywan almost 2 years ago
- Due date changed from 2022-07-01 to 2022-07-08
Bumping due to hackweek
Updated by nicksinger almost 2 years ago
- Due date changed from 2022-07-08 to 2022-07-15
Seba is on vacation till the end of this week. Bumping due date even a little more due to that
Updated by okurz almost 2 years ago
- Subject changed from Handle installation of new FC switch to Handle installation of new FC switch size:M
- Description updated (diff)
- Due date deleted (
2022-07-15) - Status changed from Feedback to Resolved
No problems were reported so far. We ensured the switch is generally usable and remotely configurable so we can resolve this ticket and reopen whenever there are questions or complaints.
Updated by sebchlad almost 2 years ago
- Status changed from Resolved to Feedback
since I'm back from my holidays I wanted to check the set-up (also discussed during my holidays in the slack: https://suse.slack.com/archives/C02CANHLANP/p1657000684109309?thread_ts=1656918009.916579&cid=C02CANHLANP)
so I'm moving it to feedback.
Updated by okurz almost 2 years ago
nsinger pointed out a problem in the network configuration https://gitlab.suse.de/search?search=10.162.3.87&nav_source=navbar&project_id=2585&group_id=585&search_code=true&repository_ref=master . I am awaiting the fix.
Updated by nicksinger over 1 year ago
okurz wrote:
nsinger pointed out a problem in the network configuration https://gitlab.suse.de/search?search=10.162.3.87&nav_source=navbar&project_id=2585&group_id=585&search_code=true&repository_ref=master . I am awaiting the fix.
The fix is already in place and was introduced with https://gitlab.suse.de/qa-sle/qanet-configs/-/commit/fe27a773621dfc1f13cf652b04ef663cb73b2b1a