Topic
  • 2 replies
  • Latest Post - ‏2013-01-24T01:32:42Z by esarakaitis
barryb
barryb
1 Post

Pinned topic web interface links to ethernet and FC switches from FSM

‏2012-09-20T16:26:40Z |
We are having an issue when we try to launch the EN4093 Ethernet or FC3171 web interfaces from the FSM. A separate web page opens up as expected, but it looks like it is trying to connect to the IPv6 address of the given switch instead of the IPv4 address. Not sure how to correct this.

Note: the v7000 web interface launches fine from the FSM, and the switch web interfaces launch fine on their own and from the CMM (all as IPv4 addresses).

Thanks for any help
Updated on 2013-01-24T01:32:42Z at 2013-01-24T01:32:42Z by esarakaitis
  • BrandonH
    BrandonH
    1 Post

    Re: web interface links to ethernet and FC switches from FSM

    ‏2012-09-26T04:19:12Z  
    If the chassis was configured as part of a Foundation by IBM Lab Services, IPv6 may have been configured on the systems. Even if not, those systems still use a Link Local IPv6 address by default. When the chassis and chassis elements are configured with IPv6, IPv6 takes priority over IPv4. So whenever Launch in Context is attempted, it tries to use the IPv6 address, not an IPv4 (even if IPv4 is configured on the element). The priority of IPv6 over IPv4 is working as designed. However, a PMR has recently been opened and the support team is looking into it to determine if this can be changed.

    Even though the elements in the chassis have IPv4 addresses, you may need to un-manage the chassis and rediscover it, ensuring that it is discovered with the IPv4 addresses, not the IPv6 addresses. That would be the best work-around until further investigation can be handled by the support team.

    Brandon Harrell
    IBM Advanced Technical Skills
  • esarakaitis
    esarakaitis
    38 Posts

    Re: web interface links to ethernet and FC switches from FSM

    ‏2013-01-24T01:32:42Z  
    • BrandonH
    • ‏2012-09-26T04:19:12Z
    If the chassis was configured as part of a Foundation by IBM Lab Services, IPv6 may have been configured on the systems. Even if not, those systems still use a Link Local IPv6 address by default. When the chassis and chassis elements are configured with IPv6, IPv6 takes priority over IPv4. So whenever Launch in Context is attempted, it tries to use the IPv6 address, not an IPv4 (even if IPv4 is configured on the element). The priority of IPv6 over IPv4 is working as designed. However, a PMR has recently been opened and the support team is looking into it to determine if this can be changed.

    Even though the elements in the chassis have IPv4 addresses, you may need to un-manage the chassis and rediscover it, ensuring that it is discovered with the IPv4 addresses, not the IPv6 addresses. That would be the best work-around until further investigation can be handled by the support team.

    Brandon Harrell
    IBM Advanced Technical Skills
    Did you try to go into the CMM and address the switches with IPv4 IP Addresses?

    I have a guide for doing so right here: Configuring IPv4 IP Addresses in the IBM PureFlex Environment