Force JunOS to use ntp server

Ak sa nam stane ze mam spravne nakonfigurovany ntp server a po commite sa nam nenastavi spravny cas je potrebne spravit “force” na nastavenie casu

> show configuration system ntp 
server 192.168.1.86;
source-address 10.0.10.2;

> set date ntp all-members 192.168.1.86 
fpc0:
--------------------------------------------------------------------------
16 Nov 23:13:05 ntpdate[81186]: step time server 192.168.1.86 offset 0.000631 sec

Rescue configuration is not set

Ak nam na Juniper zariadeni svieti oranzovy alarm, tak o aky alarm sa jedna skontrolujeme prikazok

dubnik@juniper>show system alarms 
1 alarms currently active
Alarm time               Class  Description
2014-06-28 18:03:48 CEST Minor  Rescue configuration is not set

jedna sa o to ze nemame nastaveny rescue config, ktory si ukladame ako vychodzi a v pripade problemov ho vieme kedykolvek loadnut.Rescu config vytvorime nasledovnym prikazom

dubnik@juniper> request system configuration rescue save 

A skontroulujeme

dubnik@juniper>show system alarms
No alarms currently active

Device has booted from the backup JunOS image

Hlaska, ktora sa nam moze objavit pri starte EX-series switchu, po tom ako sme nekorektne vypli, ci uz nam vypadala eklektrika alebo sme zabudli ze nemama Cisco switch a na vypnutie zariadenia je aj prislusny command.Kazdopadne ked sa nam objavi tato hlaska

Warning:

    ****************************************************************************************
    ** **
    ** WARNING: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE **
    ** **
    ** It is possible that the primary copy of JUNOS failed to boot up **
    ** properly, and so this device has booted from the backup copy. **
    ** **
    ** Please re-install JUNOS to recover the primary copy in case **
    ** it has been corrupted. **
    ** **
    ****************************************************************************************

Respektive ked mame alarm

ser@switch> show chassis alarms
    1 alarms currently active
    Alarm time Class Description
    2011-02-17 05:48:49 PST Minor Host 0 Boot from backup root

Pravdepodobne ma to ma nieco spolocne s nekorektnym vypnutim zariadenia a nie je sa coho bat.V podstate zariadenie len nabootovalo pre istotu z backup particie, aby sa vyhlo bootovaniu z poskodeneho filesystemu.Ak chceme opravit povodni primaty particiu, slizu na to nasledovny command.

ser@switch> request system snapshot media internal slice alternate

Tymto zabezpecim konzistentnost na primary aj backup particii, bez potreby restartovania zariadenia.

Juniper virtual-chasis

VIRTUAL-CHASIS

spojenie switchov do jednej jednotky(max 10 switchov)
spajaju sa pomocout VCP portov do 5m, SFP porty do 50km

member roles

• master(1) – menezuje zvychnych clenov virtual-chasis – plna kontrola nad VC konfiguraciou, menezuje switch vo VC, routing-engine
• backup(1) – drzi backup configu bezi na nom routing-engine,bere rolu mastra v pripade vypadku mastra – backup
• linecard – zvysne switche, bezia junos v line-card mode

master, backup dame najvyssiu prioritu (255) aby bol hladky prechod master-backup pri vypadku mastra

master sa vybera – priorita,posledny master,najdlsie vo virtual chasis,najnizsia mac-adresa

   0|----
sw-a|    |
   1|----|--
         |  |
   0|--  |  | 
sw-b|  | |  | 
   1|----   |
       |    |
   0|-------
sw-c|  |
   1|---

–Preprovisioned configuration

-umoznuje priradit member ID ku kazdemi switchu vo VCH
1.spravime list serial numbers vetkych switchov

root@coresw01-bb> show chassis hardware 
Hardware inventory:
Item             Version  Part number  Serial number     Description
Chassis                                CU0213208748      EX2200-48T-4G
Routing Engine 0 REV 23   750-026325   CU0213208748      EX2200-48T-4G
FPC 0            REV 23   750-026325   CU0213208748      EX2200-48T-4G
  CPU                     BUILTIN      BUILTIN           FPC CPU
  PIC 0                   BUILTIN      BUILTIN           48x 10/100/1000 Base-T
  PIC 1          REV 23   750-026325   CU0213208748      4x GE SFP
Power Supply 0                                           PS 100W AC
Fan Tray                                                 Fan Tray

2.vybereme ktory switch bude v mode routing-engine alebo line-card, switch ktory nastavime ako line-card uz nebude mozne prehodit na master,backup

3.prepojime switch VCP

4.zapneme master switch, ostatne nechame vypnute

5(optinal).nastavime virtual management interface

user@switch# set interfaces vme unit 0 family inet address /ip-address/mask/

6.Nastavime preprovisioned mode:

[edit virtual-chassis]
user@switch# set preprovisioned

7.Z mastra nastavime membrov VC, member number,serial a rolu

[edit virtual-chassis]
user@switch# set member 0 serial-number abc123 role routing-engine
user@switch# set member 1 serial-number def456 role line-card
user@switch# set member 2 serial-number pqr678 role routing-engine

8.AK mame len 2 switche nastavime no-split-detection

The master switch “dies”. To the remaining switch (old backup), this could be seen as a “split” since there were only two members in the VC and now it’s just itself in this “part”. Per VC split rule, this “old backup” remains to be “active”. Everything is fine.
The backup switch “dies”. To the remaining switch (old master), this could be seen as a “split” since there were only two members in the VC and now it’s just itself in this “part”. Per VC split rule, this “old master” becomes “inactive”. This is not necessarily desirable as now both members of the original VC are “inactive” – one died and one deactivated itself, possibly even under a “single” failure such as that of a power supply failure.

user@switch#set no-split-detection

9.zapneme zvysne switche

–Nonprovisioned

1.prepojime switche

2.zapneme switch ktory chceme mat mastra

3(optional).nastavime virtual management interface

user@switch# set interfaces vme unit 0 family inet address /ip-address/mask/

4.nastavime membership prioritu

[edit virtual-chassis]
user@switch# set member 0 mastership-priority 255
user@switch# set member 1 mastership-priority 255

5.AK mame len 2 switche nastavime no-split-detection

user@switch#set no-split-detection

6.zapneme postupne switche jeden po druhom.