Project

General

Profile

action #111171

Handle installation of new FC switch

Added by nicksinger about 2 months ago. Updated 1 day ago.

Status:
Feedback
Priority:
Low
Assignee:
Target version:
Start date:
2022-05-16
Due date:
2022-07-08
% Done:

0%

Estimated time:

Description

  • 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

History

#1 Updated by okurz about 2 months ago

  • Target version set to Ready

#2 Updated by okurz about 2 months 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.

#3 Updated by okurz about 1 month ago

  • Assignee changed from sebchlad to nicksinger
  • Target version changed from future to Ready

mgriessmeier needs the serial number for procurement, no rush.

#4 Updated by mkittler about 1 month ago

  • Due date changed from 2022-05-31 to 2022-06-06

#5 Updated by mgriessmeier about 1 month ago

S/N is EWY1928S029

#7 Updated by okurz about 1 month ago

What does that mean now for any next steps?

#8 Updated by nicksinger about 1 month ago

  • Assignee changed from nicksinger to sebchlad

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?

#9 Updated by sebchlad 26 days 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 ;-)

#10 Updated by okurz 25 days 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

#11 Updated by okurz 17 days ago

  • Due date changed from 2022-06-17 to 2022-07-01

nicksinger unavailable right now

#12 Updated by okurz 11 days 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.

#13 Updated by okurz 11 days 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?

#14 Updated by cdywan 1 day ago

  • Due date changed from 2022-07-01 to 2022-07-08

Bumping due to hackweek

Also available in: Atom PDF