The test: sun/security/pkcs11/KeyGenerator/TestKeyGenerator.java has a hard-coded check for keysizes between 40 and 128, however, it appears that on flicker, our new 2-way 4150, the PKCS11 impl here has larger keys available.

        test("Blowfish", 0, p, TestResult.FAIL);
        test("Blowfish", 24, p, TestResult.FAIL);
        test("Blowfish", 32, p, TestResult.FAIL);
        test("Blowfish", 40, p, TestResult.PASS);
        test("Blowfish", 128, p, TestResult.PASS);
        test("Blowfish", 136, p, TestResult.FAIL);
        test("Blowfish", 448, p, TestResult.FAIL);
        test("Blowfish", 456, p, TestResult.FAIL);

Testing Blowfish, 0 bits...
Testing Blowfish, 24 bits...
Testing Blowfish, 32 bits...
Testing Blowfish, 40 bits...
Testing Blowfish, 128 bits...
Testing Blowfish, 136 bits...
STDERR:
java.lang.Exception: Generated SunPKCS11-Solaris Blowfish secret key, 136 bits (
id 139470576, session object, not sensitive, extractable) using invalid key leng
th
        at TestKeyGenerator.test(TestKeyGenerator.java:72)
        at TestKeyGenerator.main(TestKeyGenerator.java:117)
        at PKCS11Test.premain(PKCS11Test.java:69)
        at PKCS11Test.testDefault(PKCS11Test.java:103)
        at PKCS11Test.main(PKCS11Test.java:76)
        at TestKeyGenerator.main(TestKeyGenerator.java:47)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:623)
        at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:
94)
        at java.lang.Thread.run(Thread.java:674)

If you do a cryptoadm list on shimmer, it lists blowfish. If you do a cryptoadm list on flicker, it lists blowfish 448. Probably have new algorithm sizes on the new machine.