fsIssuMode

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsIssuMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "fullcompatible",
    "(",
    "1",
    ")",
    ",",
    "basecompatible",
    "(",
    "2",
    ")",
    ",",
    "incompatible",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object specifies the ISSU upgrade process that can be done in two modes. - In 'fullcompatible' software upgrade, the node which gets upgraded gets reloaded in 'warm-boot mode'. Hence data traffic through that node does not get impacted during the upgrade procedure. Static configuration and dynamic states are synched up from the active node to the upgraded standby node. This mode is feasible ONLY when software upgrade is across minor releases. - In 'basecompatible' software upgrade, the standby node which gets upgraded is booted in 'cold-boot'mode. Static configuration and dynamic states are synched up from the active node to the upgraded standby node. This mode feasible for a major version of software upgrade. - In 'incompatible' software upgrade, the standby node which gets upgraded is booted in 'cold-boot'mode. The static configuration and dynamic states are NOT synched up from the active node. When software upgrade to an incompatible software version is required then ISSU in 'incompatible mode' should be configured. The administrator triggered compatibility check helps to decide whether the ISSU mode has to be configure in fullcompatible, basecompatible or incompatible mode. Note: - Configuring 'fullcompatible or basecompatible mode' of ISSU, will leave system unpredictable when the compatibility check resulted 'incompatible'. - Appropriate ISSU mode should be configured before starting the ISSU procedure through ISSU commands\"",
    "DEFVAL",
    "{",
    "fullcompatible",
    "}",
    "::=",
    "{",
    "fsIssuSystem",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "fullcompatible",
            1
          ],
          [
            "basecompatible",
            2
          ],
          [
            "incompatible",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object specifies the ISSU upgrade process that can be done in two modes. - In 'fullcompatible' software upgrade, the node which gets upgraded gets reloaded in 'warm-boot mode'. Hence data traffic through that node does not get impacted during the upgrade procedure. Static configuration and dynamic states are synched up from the active node to the upgraded standby node. This mode is feasible ONLY when software upgrade is across minor releases. - In 'basecompatible' software upgrade, the standby node which gets upgraded is booted in 'cold-boot'mode. Static configuration and dynamic states are synched up from the active node to the upgraded standby node. This mode feasible for a major version of software upgrade. - In 'incompatible' software upgrade, the standby node which gets upgraded is booted in 'cold-boot'mode. The static configuration and dynamic states are NOT synched up from the active node. When software upgrade to an incompatible software version is required then ISSU in 'incompatible mode' should be configured. The administrator triggered compatibility check helps to decide whether the ISSU mode has to be configure in fullcompatible, basecompatible or incompatible mode. Note: - Configuring 'fullcompatible or basecompatible mode' of ISSU, will leave system unpredictable when the compatibility check resulted 'incompatible'. - Appropriate ISSU mode should be configured before starting the ISSU procedure through ISSU commands"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "fullcompatible"
    ]
  ]
}