Bisher war ein Software Update in einem Virtuellen Chassis immer mit einer Downtime verbunden.<\/p>\n
Man musste die Software einspielen und dann beide Member mit der neuen Version booten.<\/p>\n
Da die 6900 doch eine gewisse Zeit zum booten brauchen, gab es einen Ausfall im Minuten Bereich.
\nMit den neuen Releases (7.3.1.748 und 7.3.2.374R01) wird nun die M\u00f6glichkeit eines ISSU (In-Service Software Upgrade) unterst\u00fctzt.<\/p>\n
Vereinfacht spielt man in einen Virtual-Chassis System die Software ein und st\u00f6\u00dft das Upgrade an.
\nDann wird als erstes der Secondary mit der Software versorgt und damit gebootet. Ist er hochgefahren und bereit \u00fcbernimmt er die Masterrolle und der vorher aktive bekommt die neue Firmware.
\nNachdem auch die Box gebootet hat ist das VC mit der neuen Software bereit, der Ausfall sollte dann minimal sein.<\/p>\n
Voraussetzung das neue Image (Tos.img und das passende issu_version file) liegt auf dem Master in einem Verzeichnis z.B. new_firm<\/p>\n
Konkret:
\nKopieren der Konfig<\/p>\n
\r\ncp working\/vcboot.cfg new_firm\r\ncp working\/vcsetup.cfg new_firm\r\n<\/pre>\nAbspeichern (sicher ist sicher)<\/p>\n
\r\nwrite memory flash-synchro \r\n<\/pre>\nDann geht es los:<\/p>\n
\r\nissu from new_firm\r\nAre you sure you want an In Service System Upgrade? (Y\/N) : y\r\n\r\nThu Sep 26 14:19:55 : ChassisSupervisor issuMgr info message:\r\n+++ VCISSU: validating images on master. (directory \"new_firm\")\r\n\r\nThu Sep 26 14:20:16 : ChassisSupervisor issuMgr info message:\r\n+++ VCISSU: images validated.\r\n+++ VCISSU: all slaves copying images...\r\n\r\nThu Sep 26 14:21:02 : ChassisSupervisor issuMgr info message:\r\n+++ VCISSU: slave 1 finished copying images.\r\n+++ VCISSU: all slaves have copied images.\r\n+++ VCISSU: slave 1 is rebooting\r\n\r\nThu Sep 26 14:21:24 : vcmCmm port_mgr info message:\r\n+++ CMM:vcmCMM_client_rx_pm@1412: VFL link 2\/0 down (last 2\/1\/20) [L2]\r\n\r\nThu Sep 26 14:21:24 : ChassisSupervisor bootMgr info message:\r\n+++ bootMgrVCMTopoDataEventHandler: remote chassis 1 no longer in the topology - closing connections\r\n\r\nThu Sep 26 14:21:24 : vcmCmm ipc info message:\r\n+++ CMM:vcmCMM_peer_disconnected@1756: Remote endpoint (chassis 1, slot 65)\r\n\r\nThu Sep 26 14:21:24 : ChassisSupervisor prbDB info message:\r\n+++ fanTray 1,chassis 1 extracted\r\n\r\nThu Sep 26 14:21:24 : ChassisSupervisor issuMgr info message:\r\n+++ VCISSU: slave 1 topology change. Waiting for shared memory update.\r\n\r\nThu Sep 26 14:21:24 : ChassisSupervisor vcReloadMgr info message:\r\n+++ Remote chassis 1 slot 65 disconnected - status 0\r\n\r\nThu Sep 26 14:21:55 : ChassisSupervisor vcReloadMgr info message:\r\n+++ Reload transaction timeout - canceling\r\n<\/pre>\nAuf dem Slave sieht man:<\/p>\n
\r\nThu Sep 26 14:20:16 : flashManager FlashMgr Main info message:\r\n+++ File vcsetup.cfg differs in \/flash\/myissu and \/flash\/new_firm - copying file\r\n\r\nThu Sep 26 14:20:28 : flashManager FlashMgr Main info message:\r\n+++ Image file Tos.img differs - copying file- duplicated 1 times!\r\n\r\nThu Sep 26 14:21:02 : ChassisSupervisor issuMgr alert message:\r\n+++ VCISSU: Slave Chassis rebooting under command from master chassis\r\n\r\nThu Sep 26 14:21:02 : flashManager FlashMgr Main info message:\r\n+++ Verifying image directory new_firm on CMM flash\r\n\r\nThu Sep 26 14:21:02 : ChassisSupervisor issuMgr alert message:\r\n+++ VCISSU: boot manager is reloading from image directory \"new_firm\".\r\n\r\nThu Sep 26 14:21:24 : ChassisSupervisor reloadMgr info message:\r\n+++ reloadMgrSetupReboot: rebooting primary CMM\r\n\r\nThu Sep 26 14:21:24 : ChassisSupervisor bootMgr info message:\r\n+++ bootMgrRebootCMM: Rebooting CMM\r\n[..]\r\n\r\n(none) login: \r\nThu Sep 26 14:23:48 : ChassisSupervisor Power Mgr info message:\r\n+++ PS 1 is up\r\n\r\nThu Sep 26 14:23:49 : vcmCmm init info message:\r\n+++ CMM:vcm_mip_eoic_cmm@532: Virtual-chassis mode (chassis 1, protocol 'vcm', max 2) [L0]\r\n\r\nThu Sep 26 14:23:49 : ChassisSupervisor CS Main info message:\r\n+++ Updating chassis ID to 1\r\n\r\nThu Sep 26 14:23:49 : ChassisSupervisor prbDB info message:\r\n+++ PS 1,chassis_id 1 inserted\r\nAlcatel-Lucent OS6900-X40 7.3.2.374.R01 Service Release, August 30, 2013.\r\nCopyright(c), 1994-2013 Alcatel-Lucent. All Rights reserved.\r\n\r\n\r\nThu Sep 26 14:23:54 : ipv4 itf info message:\r\n+++ Interface EMP-CHAS1 192.168.252.1\/255.255.255.0\r\nchassis mode is\r\n2\r\n\r\nThu Sep 26 14:25:53 : vcmCmm chas_sup info message:\r\n+++ CMM:vcmCMM_cs_handle_chassis_ready@3602: Chassis 1 ready (data 0) [L1]\r\n\r\nThu Sep 26 14:25:56 : vcmCmm port_mgr info message:\r\n+++ CMM:vcmCMM_client_rx_pm@1551: VFL link 1\/0 up (pri 1\/1\/1:0x0) [L2]\r\n\r\nThu Sep 26 14:25:56 : vcmCmm protocol info message:\r\n+++ CMM:vcmCMN_protocol_ready_update_cb@13348: Chassis 1, role Slave, status Running, master 2 [L3]\r\n\r\nThu Sep 26 14:25:57 : vcmCmm ipc info message:\r\n+++ CMM:vcmCMM_peer_connected@1792: Remote endpoint (chassis 2, slot 65) [L4]\r\n\r\nThu Sep 26 14:25:57 : vcmCmm node_sync info message:\r\n+++ CMM:notify_sync_complete@757: Sync complete 'multi node' (peers 1, conn 1, sync 1) [L5]\r\n\r\nThu Sep 26 14:25:59 : healthCmm main warning message:\r\n+++ CPU crossed Above the Threshold Limit!\r\n\r\nThu Sep 26 14:26:10 : ChassisSupervisor prbDB info message:\r\n+++ PS 1,chassis_id 2 inserted\r\n\r\nThu Sep 26 14:26:10 : isis_spb_0 TASK info message:\r\n+++ Base MAC changed to e8:e7:32:0e:65:69\r\n\r\nThu Sep 26 14:26:10 : ChassisSupervisor bootMgr info message:\r\n+++ Sending VC Takeover to NIs and applications [L6]\r\n\r\nThu Sep 26 14:26:10 : ConfigManager CONFD info message:\r\n+++ Slave Configuration Manager waiting for Master sync\r\n+++ Slave Configuration Manager Connecting with Master\r\n\r\nThu Sep 26 14:26:12 : isis_spb_0 TASK info message:\r\n+++ VC Takeover: chassis_id:1\r\n\r\nThu Sep 26 14:26:12 : ipv4 itf info message:\r\n+++ Interface EMP-CHAS1 192.168.252.1\/255.255.255.0\r\n\r\nThu Sep 26 14:26:12 : SNMP aluSubagent_thread info message:\r\n+++ snmp_vc_takeover_callback | VC Takeover complete\r\n\r\nThu Sep 26 14:26:12 : appfpCmm main error message:\r\n+++ Master running old version : \r\n\r\nThu Sep 26 14:26:13 : qosNi Info info message:\r\n+++ VC Takeover in progress.\r\n+++ VC Takeover complete.\r\n\r\nThu Sep 26 14:26:13 : appfpNi main error message:\r\n+++ Master running old version : \r\n\r\nThu Sep 26 14:26:16 : ChassisSupervisor bootMgr info message:\r\n+++ Received VC Takeover Complete event from all apps [L7]\r\nChassis Supervision: CMM has reached the ready state [L8]\r\n\r\nThu Sep 26 14:26:18 : ChassisSupervisor reloadMgr info message:\r\n+++ Redundancy time expired - updating next running to new_firm\r\n\r\nThu Sep 26 14:26:50 : vcmCmm port_mgr info message:\r\n+++ CMM:vcmCMM_client_rx_pm@1569: VFL link 1\/0 down (last 1\/1\/20) [L2]\r\n\r\nThu Sep 26 14:26:50 : vcmCmm config info message:\r\n+++ CMM:vcmCMM_check_emp_exec@15094: No EMP query - controlled reset (chassis 2, mac e8:e7:32:0e:66:89)\r\n\r\nThu Sep 26 14:26:50 : ChassisSupervisor bootMgr info message:\r\n+++ bootMgrVCMTopoDataEventHandler: remote chassis 2 no longer in the topology - closing connections\r\n\r\nThu Sep 26 14:26:50 : healthNi main info message:\r\n+++ [hmon_reconnect_to_cmm:156] \r\n\r\nThu Sep 26 14:26:50 : vcmCmm ipc info message:\r\n+++ CMM:vcmCMM_peer_disconnected@1907: Remote endpoint (chassis 2, slot 65)\r\n\r\nThu Sep 26 14:26:50 : ipni udprelay info message:\r\n+++ UDPRelay disconnected (104)\r\n\r\nThu Sep 26 14:26:50 : ChassisSupervisor prbDB info message:\r\n+++ fanTray 1,chassis 2 extracted\r\n\r\nThu Sep 26 14:26:50 : ChassisSupervisor vcReloadMgr info message:\r\n+++ Remote chassis 2 slot 65 disconnected - status 0\r\n\r\nThu Sep 26 14:26:50 : ChassisSupervisor bootMgr alert message:\r\n+++ Master chassis ID has changed (1\/65) - triggering a Virtual Chassis Takeover\r\n\r\nThu Sep 26 14:26:50 : ChassisSupervisor bootMgr info message:\r\n+++ Sending VC Takeover to NIs and applications [L6]\r\n+++ bootMgrSendSecondaryMasterChanged: entry\r\n\r\nThu Sep 26 14:26:55 : ChassisSupervisor bootMgr info message:\r\n+++ Received VC Takeover Complete event from all apps [L7]\r\nChassis Supervision: CMM has reached the ready state [L8]\r\n\r\nThu Sep 26 14:26:57 : ChassisSupervisor reloadMgr info message:\r\n+++ Redundancy time expired - updating next running to new_firm\r\n\r\nThu Sep 26 14:26:59 : healthCmm main warning message:\r\n+++ CPU crossed Below the Threshold Limit!\r\n<\/pre>\nDer Slave hat also mit der neuen Firmware geboote.<\/p>\n
Es ist dann Master geworden und hat das Management \u00fcbernommen, damit der vorherige Master das Update machen kann<\/p>\n
Die Ausgabe auf dem (Ex)Master dabei:<\/p>\n
\r\nThu Sep 26 14:25:56 : vcmCmm port_mgr info message:\r\n+++ CMM:vcmCMM_client_rx_pm@1394: VFL link 2\/0 up (pri 2\/1\/1:0x20000) [L2]\r\n\r\nThu Sep 26 14:25:57 : vcmCmm ipc info message:\r\n+++ CMM:vcmCMM_peer_connected@1634: Remote endpoint (chassis 1, slot 65) [L4]\r\n\r\nThu Sep 26 14:25:57 : vcmCmm port_lib error message:\r\n+++ CMM:vcmCMM_process_config_sync_msg@4010: Get port info (vfl 0, ifidx 40000257, ret -3)\r\n\r\nThu Sep 26 14:26:10 : ChassisSupervisor prbDB info message:\r\n+++ PS 1,chassis_id 1 inserted\r\n\r\nThu Sep 26 14:26:10 : ChassisSupervisor issuMgr info message:\r\n+++ VCISSU: slave 1 updated shared memory. Waiting for slave vc takeover events.\r\n\r\nThu Sep 26 14:26:15 : ChassisSupervisor prbDB info message:\r\n+++ PS 1,chassis_id 1 inserted\r\nFor Chassis 1 slot 1 flag is 1 :haVlanHandleCsNIUp\r\n\r\nThu Sep 26 14:26:16 : evbCmm main error message:\r\n+++ plGetUportRangeFromChassisSlot failed: 1\/2, rv=-30\r\n\r\nThu Sep 26 14:26:16 : rmon main error message:\r\n+++ plGetUportRangeFromChassisSlot chass: 1 slot: 2 ret: -30\r\n\r\nThu Sep 26 14:26:16 : evbCmm main error message:\r\n+++ plGetUportRangeFromChassisSlot failed: 1\/3, rv=-30\r\n\r\nThu Sep 26 14:26:16 : rmon main error message:\r\n+++ plGetUportRangeFromChassisSlot chass: 1 slot: 3 ret: -30\r\n\r\nThu Sep 26 14:26:16 : ChassisSupervisor issuMgr info message:\r\n+++ VCISSU: slave 1 finished vc takeover events. Waiting for vc ready acknowledgement.\r\n\r\nThu Sep 26 14:26:20 : ChassisSupervisor prbDB info message:\r\n+++ PS 1,chassis_id 1 inserted\r\n\r\nThu Sep 26 14:26:25 : ChassisSupervisor prbDB info message:\r\n+++ PS 1,chassis_id 1 inserted\r\n\r\nThu Sep 26 14:26:30 : ChassisSupervisor prbDB info message:\r\n+++ PS 1,chassis_id 1 inserted\r\n\r\nThu Sep 26 14:26:35 : ChassisSupervisor prbDB info message:\r\n+++ PS 1,chassis_id 1 inserted\r\n\r\nThu Sep 26 14:26:46 : ChassisSupervisor issuMgr info message:\r\n+++ VCISSU: slave 1 acknowledged vc ready. VCISSU complete for this slave.\r\n\r\nThu Sep 26 14:26:46 : ChassisSupervisor issuMgr alert message:\r\n+++ VCISSU: Master Chassis rebooting at end of VCISSU procedure\r\n\r\nThu Sep 26 14:26:46 : flashManager FlashMgr Main info message:\r\n+++ Verifying image directory new_firm on CMM flash\r\n\r\nThu Sep 26 14:26:46 : ChassisSupervisor issuMgr alert message:\r\n+++ VCISSU: boot manager is reloading from image directory \"new_firm\".\r\n\r\nThu Sep 26 14:26:49 : ChassisSupervisor reloadMgr info message:\r\n+++ reloadMgrSetupReboot: rebooting primary CMM\r\n\r\nThu Sep 26 14:26:49 : ChassisSupervisor bootMgr info message:\r\n+++ bootMgrRebootCMM: Rebooting CMM\r\n\r\nThu Sep 26 14:26:49 : MIP_GATEWAY mipgwd info message:\r\n+++ msgRouter: Client unavailable, dropping response msg=MIP_SETF_RSP(15) msg_id(55509069) (APPID_CHASSISUPER(64\/0) -> APPID_CLI(67\r\nDisabling ports\r\nAll ports disabled\r\n\r\nThu Sep 26 14:26:49 : ChassisSupervisor bootMgr alert message:\r\n+++ _bootMgrRebootCMM: rebooting system\r\n\r\nThu Sep 26 14:26:50 2013 :: Local Flash Sync complete - fail watchdog is 0\r\nThu Sep 26 14:26:50 2013 :: Unmounting flash\r\n\r\n\r\n[..]\r\n<\/pre>\nNachdem das durch ist haben beide Maschinen die neue Firmware. (Hier ein Update von 7.3.1.748 auf 7.3.2.374)<\/p>\n","protected":false},"excerpt":{"rendered":"
Bisher war ein Software Update in einem Virtuellen Chassis immer mit einer Downtime verbunden. Man musste die Software einspielen und dann beide Member mit der neuen Version booten. Da die 6900 doch eine gewisse Zeit zum booten brauchen, gab es einen Ausfall im Minuten Bereich. Mit den neuen Releases (7.3.1.748 und 7.3.2.374R01) wird nun die … Alcatel Virtual Chassis – neue Firmware als ISSU<\/span> weiterlesen<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[55,1,7,12],"tags":[37,31,38,39],"class_list":["post-378","post","type-post","status-publish","format-standard","hentry","category-alcatel","category-allgemein","category-erfahrungen","category-job","tag-37","tag-alcatel","tag-issu","tag-job-2"],"_links":{"self":[{"href":"https:\/\/janscholten.de\/blog\/wp-json\/wp\/v2\/posts\/378","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/janscholten.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/janscholten.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/janscholten.de\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/janscholten.de\/blog\/wp-json\/wp\/v2\/comments?post=378"}],"version-history":[{"count":5,"href":"https:\/\/janscholten.de\/blog\/wp-json\/wp\/v2\/posts\/378\/revisions"}],"predecessor-version":[{"id":383,"href":"https:\/\/janscholten.de\/blog\/wp-json\/wp\/v2\/posts\/378\/revisions\/383"}],"wp:attachment":[{"href":"https:\/\/janscholten.de\/blog\/wp-json\/wp\/v2\/media?parent=378"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/janscholten.de\/blog\/wp-json\/wp\/v2\/categories?post=378"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/janscholten.de\/blog\/wp-json\/wp\/v2\/tags?post=378"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}