Calix Cloud - Setting up Calix Ops Cloud on AXOS E7
Draft:
For EXA, the probe goes on CMS server and Calix agent does this.
May see an alarm 25% of the time, known issue where see a DB backup fail alarm in the morning. (creates a backup task for F5 nodes that no one has.) fix is to restart the CMS service.
For AXOS, it is per E7. Calix Ops cloud is totally independent from SMx when it comes to synchronizing.
the call home uses 7777, 5555 for something else
Not this add system button (this is for CMS)
In calix ops cloud web gui here
First, need to set up regions/ locations
User > Admin > Ops cloud > add region
configure
aaa user opscloud password GENERATED_PW_HERE role admin
top
call-home netconf-client NODE_NAME
ssh endpoints endpoint COC address opscloud-us.calix.com port 7777
exit
connection-type periodic reconnect-timeout 1
exchange-device-info enable
end
copy r s
In E7
sh call-home
sh ntp
sh run ip name
ping 8.8.8.8
sh ipfix
ADD THIS CONFIG:
configure
aaa user opscloud password GENERATED_PW_HERE role admin
top
call-home netconf-client NODE_NAME
ssh endpoints endpoint COC address opscloud-us.calix.com port 7777
exit
connection-type periodic reconnect-timeout 1
exchange-device-info enable
end
copy r s
creates a new user to the E7, we used the same PW as the new CMS account
NODE_NAME best practice just name it the same thing as node hostname
ex. 
sh call-home
to see the status, normal for it to bounce inactive/active, should stay active once it connects to ops cloud
Back in web gui
Call home
Device name format & OLT node name are both also the hostname
MAC is in SMx or can get in CLI
