[Nocrancid] autopop-onenet.net router config diffs
rancid at rancid.noc.onenet.net
rancid at rancid.noc.onenet.net
Mon Oct 30 05:04:39 CDT 2017
Index: configs/core.hut.waur.onenet.net
===================================================================
--- configs/core.hut.waur.onenet.net (revision 158527)
+++ configs/core.hut.waur.onenet.net (working copy)
@@ -26,6 +26,16 @@
# TFEB 0 TBB PFE Chip OK
# TFEB 0 TFEB PCIE TSen OK
# TFEB 0 TFEB PCIE Chip OK
+# TFEB 0 QX 0 TSen OK
+# TFEB 0 QX 0 Chip OK
+# TFEB 0 LU 0 TSen OK
+# TFEB 0 LU 0 Chip OK
+# TFEB 0 MQ 0 TSen OK
+# TFEB 0 MQ 0 Chip OK
+# TFEB 0 TBB PFE TSen OK
+# TFEB 0 TBB PFE Chip OK
+# TFEB 0 TFEB PCIE TSen OK
+# TFEB 0 TFEB PCIE Chip OK
# Fans Fan 1 OK
# Fan 2 OK
# Fan 3 OK
Index: configs/opt.okc.onenet.net
===================================================================
--- configs/opt.okc.onenet.net (revision 158527)
+++ configs/opt.okc.onenet.net (working copy)
@@ -57,7 +57,6 @@
<interface name="LINE-1-3-1" abbr_name="LINE-1-3-1" admin_state="down" spanning_tree_metric="" description="Unknown" type="EXP" monitoring_state="no-monitor"></interface>
</part>
<part name="SLOT-1-5" description="15454-40-DMX-C=" hw_version="A0" part_id="15454-40-DMX-C=" part_num="800-27455-03" serial_number="CAT1424B2G4" slot="SLOT-1-5" vendor_id="Cisco">
- <interface name="CHAN-1-5-1-TX" abbr_name="CHAN-1-5-1-TX" admin_state="up" spanning_tree_metric="" description="" type="DMX" monitoring_state="monitor"></interface>
<interface name="CHAN-1-5-2-TX" abbr_name="CHAN-1-5-2-TX" admin_state="up" spanning_tree_metric="" description="" type="DMX" monitoring_state="monitor"></interface>
<interface name="CHAN-1-5-3-TX" abbr_name="CHAN-1-5-3-TX" admin_state="up" spanning_tree_metric="" description="" type="DMX" monitoring_state="monitor"></interface>
<interface name="CHAN-1-5-4-TX" abbr_name="CHAN-1-5-4-TX" admin_state="down" spanning_tree_metric="" description="" type="DMX" monitoring_state="no-monitor"></interface>
@@ -229,6 +228,7 @@
<interface name="CHAN-3-3-17-RX" abbr_name="CHAN-3-3-17-RX" admin_state="up" spanning_tree_metric="" description="" type="MUX" monitoring_state="monitor"></interface>
<interface name="CHAN-3-3-18-RX" abbr_name="CHAN-3-3-18-RX" admin_state="down" spanning_tree_metric="" description="" type="MUX" monitoring_state="no-monitor"></interface>
<interface name="CHAN-3-3-19-RX" abbr_name="CHAN-3-3-19-RX" admin_state="down" spanning_tree_metric="" description="" type="MUX" monitoring_state="no-monitor"></interface>
+ <interface name="CHAN-3-3-20-RX" abbr_name="CHAN-3-3-20-RX" admin_state="down" spanning_tree_metric="" description="" type="MUX" monitoring_state="no-monitor"></interface>
<interface name="CHAN-3-3-21-RX" abbr_name="CHAN-3-3-21-RX" admin_state="down" spanning_tree_metric="" description="" type="MUX" monitoring_state="no-monitor"></interface>
<interface name="CHAN-3-3-22-RX" abbr_name="CHAN-3-3-22-RX" admin_state="down" spanning_tree_metric="" description="" type="MUX" monitoring_state="no-monitor"></interface>
<interface name="CHAN-3-3-23-RX" abbr_name="CHAN-3-3-23-RX" admin_state="down" spanning_tree_metric="" description="" type="MUX" monitoring_state="no-monitor"></interface>
More information about the Nocrancid
mailing list