Cisco Cisco MDS 9000 NX-OS Software Release 5.2 Informationshandbuch
Rick Leonard, Vendor Services Lab Manager
System z® Hardware Development
International Business Machines Corporation
System z® Hardware Development
International Business Machines Corporation
Page 3 of 3
The following table contains the test cases run against the Cisco switches and directors during IBM’s testing:
Test Case Name
Test
Complete
Test Case Description
Unit Level Tests
Verify concurrent code load, power requirements, port swap, IML,
LPAR act./deact...
LPAR act./deact...
Fabric Security and Fabric Event Notification
Tests
Tests
Basic security tests for cascaded switches and fabric change
notification (RSCN) tests in different configurations. This testing
should be implicit (completed while doing other work).
notification (RSCN) tests in different configurations. This testing
should be implicit (completed while doing other work).
CEC IMLs
Run EXEC that does system resets forcing light on channels up
and down
and down
Mixed Workload Test
Combination of SAK and z/OS runs made in an LPAR
environment with several partitions.
environment with several partitions.
EXPING/INGCTV all configurations
SAK exerciser for FTV (emulated I/O) which checks basic
architecture.
architecture.
SAK EXCITE / ICTVDR Non-RCV
DPU with Real I/O Tape and DASD
EXCITE runs traffic at a maximum data rate (data pusher mode)
followed by traffic with halts, clears, and resets. In recovery mode
the program may also inject interface errors. The program is run
with a high ratio of output ports in order to maximize switching.
followed by traffic with halts, clears, and resets. In recovery mode
the program may also inject interface errors. The program is run
with a high ratio of output ports in order to maximize switching.
ITAPE0, IFTAPE, ITAPEX
SAK EXCTCP / IOCTCP
SAK exerciser for FICON CTC.
All Applicable SAK EXDASD
(IDASD0,IDSCAN,IDASDX)
Includes IDASD0, IDASDX, UDESSI all run to 2105-800/DS-
8000/DS-6000 to maximize data transfer.
8000/DS-6000 to maximize data transfer.
SAK OFCPIO, OSASF
FCP I/O driver program under SAK.
PAWS (not SAK)
Stand alone FCP test program.
CHNLDRVR
z/OS program to drive data on FICON channels.
Verify 4, 8, and 10 Gb/sec speed on ports
Verify 4, 8, and 10 Gb/sec port speed with Finisar analyzer
Verify 8 Gb to 4 Gb/sec Auto-negotiation
Verify 8 Gb to 2 Gb/sec Auto-negotiation
Verify 8 Gb to 2 Gb/sec Auto-negotiation
Test auto-negotiation from 8 Gb/sec to x Gb/sec.
New Switch ==> Old Switch
New switch ==> Shark
New Switch ==> CEC
New Switch ==> Old Switch
New switch ==> Shark
New Switch ==> CEC
Extend 2 Gb/sec ISL on CWDM
Extend 2 Gb/sec ISL up to 100 km through a CWDM
Extend 4 Gb/sec ISL on CWDM
Extend 2 Gb/sec ISL up to 40 km through a CWDM
Extend 4 Gb/sec ISL on DWDM
Extend 4 Gb/sec ISL up to 300 km through a DWDM
Extend 10 Gb/sec ISL on DWDM
Extend 10 Gb/sec ISL up to 100 km through a DWDM with
DWDM optic and 300 km with DWDM transponder
DWDM optic and 300 km with DWDM transponder
Extend FCIP Link
Verify FCIP Link traffic with Anue tester for distance up to 300 km.
NPIV
NPIV tests to verify RSCN counts
Serviceability Test
Fail different cards in switch to make sure error reporting is
correct.
May require cards or code from vendor to allow error injection.
correct.
May require cards or code from vendor to allow error injection.
SAK IRNDUP Single LPAR, Multi-channel Path,
Single Switch Partition, Multiple Copies, Split Port
Range, and FAF
Single Switch Partition, Multiple Copies, Split Port
Range, and FAF
SAK exerciser for switch CUP functions. A CU exerciser for the
CUP. Run on 2 partitions with 2 paths from each (requires MULT
parm).
CUP. Run on 2 partitions with 2 paths from each (requires MULT
parm).
SA OS/390 (I/O Ops)
This is the real program used for "in band management" of the
fabric through the CUP feature under z/OS.
fabric through the CUP feature under z/OS.
Improvised Testing
This is additional testing initiated by the Test Team Leader which
is intended to uncover latent problems in the equipment under
test.
is intended to uncover latent problems in the equipment under
test.
Regression
Verify that no breaks in code were introduced while fixing
problems found during test.
problems found during test.