FreeBSD Doc (Archived)/books_handbook — Turkish (tr_TR) @ Weblate: <prompt>%</prompt> <userinput>snmpwalk -v 2c -c public bridge1.example.com</userinput> enterprises.fokus.begemot.begemotBridge BEGEMOT-BRIDGE-MIB::begemotBridgeBaseName."bridge0" = …

The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation

Content

Source string comment (itstool) path: sect2/screen

English

<prompt>%</prompt> <userinput>snmpwalk -v 2c -c public bridge1.example.com</userinput>
enterprises.fokus.begemot.begemotBridge
BEGEMOT-BRIDGE-MIB::begemotBridgeBaseName."bridge0" = STRING: bridge0
BEGEMOT-BRIDGE-MIB::begemotBridgeBaseName."bridge2" = STRING: bridge2
BEGEMOT-BRIDGE-MIB::begemotBridgeBaseAddress."bridge0" = STRING: e:ce:3b:5a:9e:13
BEGEMOT-BRIDGE-MIB::begemotBridgeBaseAddress."bridge2" = STRING: 12:5e:4d:74:d:fc
BEGEMOT-BRIDGE-MIB::begemotBridgeBaseNumPorts."bridge0" = INTEGER: 1
BEGEMOT-BRIDGE-MIB::begemotBridgeBaseNumPorts."bridge2" = INTEGER: 1
...
BEGEMOT-BRIDGE-MIB::begemotBridgeStpTimeSinceTopologyChange."bridge0" = Timeticks: (116927) 0:19:29.27 centi-seconds
BEGEMOT-BRIDGE-MIB::begemotBridgeStpTimeSinceTopologyChange."bridge2" = Timeticks: (82773) 0:13:47.73 centi-seconds
BEGEMOT-BRIDGE-MIB::begemotBridgeStpTopChanges."bridge0" = Counter32: 1
BEGEMOT-BRIDGE-MIB::begemotBridgeStpTopChanges."bridge2" = Counter32: 1
BEGEMOT-BRIDGE-MIB::begemotBridgeStpDesignatedRoot."bridge0" = Hex-STRING: 80 00 00 40 95 30 5E 31
BEGEMOT-BRIDGE-MIB::begemotBridgeStpDesignatedRoot."bridge2" = Hex-STRING: 80 00 00 50 8B B8 C6 A9

Turkish (tr_TR)

Needs editing

Context	English	Turkish (tr_TR)	State
	<prompt>#</prompt> <userinput>ifconfig bridge0 addm fxp0 addm fxp1 addm fxp2 addm fxp3 monitor up</userinput> <prompt>#</prompt> <userinput>tcpdump -i bridge0</userinput>	<prompt>#</prompt> <userinput>ifconfig bridge0 addm fxp0 addm fxp1 addm fxp2 addm fxp3 monitor up</userinput> <prompt>#</prompt> <userinput>tcpdump -i bridge0</userinput>
	<acronym>SNMP</acronym> Monitoring	<acronym>SNMP</acronym> gözlemleme
	The bridge interface and <acronym>STP</acronym> parameters can be monitored via <citerefentry><refentrytitle>bsnmpd</refentrytitle><manvolnum>1</manvolnum></citerefentry> which is included in the FreeBSD base system. The exported bridge <acronym>MIB</acronym>s conform to <acronym>IETF</acronym> standards so any <acronym>SNMP</acronym> client or monitoring package can be used to retrieve the data.	Köprü arayüzü ve <acronym> STP </acronym> parametreleri, FreeBSD temel sistemine dahil edilen <citerefentry><refentrytitle>bsnmpd</refentrytitle><manvolnum>1</manvolnum> </citerefentry> ile izlenebilir. Dışa aktarılan köprü <acronym> MIB </acronym>, <acronym> IETF </acronym> standartlarına uygundur, böylece verileri almak için herhangi bir <acronym> SNMP </acronym> istemcisi veya izleme paketi kullanılabilir.
	To enable monitoring on the bridge, uncomment this line in <filename>/etc/snmpd.config</filename> by removing the beginning <literal>#</literal> symbol:	Köprüde izlemeyi etkinleştirmek için, başlangıç <literal> # </literal> sembolünü kaldırarak <filename> /etc/snmpd.config </filename> 'de bu satırın işaretini kaldırın:
	begemotSnmpdModulePath."bridge" = "/usr/lib/snmp_bridge.so"	begemotSnmpdModulePath."köprü" = "/usr/lib/snmp_bridge.so"
	Other configuration settings, such as community names and access lists, may need to be modified in this file. See <citerefentry><refentrytitle>bsnmpd</refentrytitle><manvolnum>1</manvolnum></citerefentry> and <citerefentry><refentrytitle>snmp_bridge</refentrytitle><manvolnum>3</manvolnum></citerefentry> for more information. Once these edits are saved, add this line to <filename>/etc/rc.conf</filename>:	Topluluk adları ve erişim listeleri gibi diğer yapılandırma ayarlarının bu dosyada değiştirilmesi gerekebilir. Bkz. <citerefentry><refentrytitle>bsnmpd</refentrytitle><manvolnum>1</manvolnum> </citerefentry><manvolnum> 3 bilgi. Bu düzenlemeler kaydedildikten sonra, bu satırı <filename> /etc/rc.conf </filename> klasörüne ekleyin:
	bsnmpd_enable="YES"	bsnmpd_enable="YES"
	Then, start <citerefentry><refentrytitle>bsnmpd</refentrytitle><manvolnum>1</manvolnum></citerefentry>:	Ardından, <citerefentry><refentrytitle>bsnmpd</refentrytitle><manvolnum>1</manvolnum> </citerefentry> 'i başlatın:
	<prompt>#</prompt> <userinput>service bsnmpd start</userinput>	<prompt>#</prompt> <userinput>service bsnmpd start</userinput>
	The following examples use the <application>Net-SNMP</application> software (<package>net-mgmt/net-snmp</package>) to query a bridge from a client system. The <package>net-mgmt/bsnmptools</package> port can also be used. From the <acronym>SNMP</acronym> client which is running <application>Net-SNMP</application>, add the following lines to <filename>$HOME/.snmp/snmp.conf</filename> in order to import the bridge <acronym>MIB</acronym> definitions:	Aşağıdaki örnekler, bir istemci sisteminden bir köprüyü sorgulamak için <application> Net-SNMP </application> yazılımını (<package> net-mgmt / net-snmp </package>) kullanır. <package> net-mgmt / bsnmptools </package> bağlantı noktası da kullanılabilir. <application> Net-SNMP </application> çalıştıran <acronym> SNMP </acronym> istemcisinden, içe aktarmak için aşağıdaki satırları <filename> $ HOME / .snmp / snmp.conf </filename> öğesine ekleyin. köprü <acronym> MIB </acronym> tanımları:
	mibdirs +/usr/share/snmp/mibs mibs +BRIDGE-MIB:RSTP-MIB:BEGEMOT-MIB:BEGEMOT-BRIDGE-MIB	mibdirs +/usr/share/snmp/mibs mibs +BRIDGE-MIB:RSTP-MIB:BEGEMOT-MIB:BEGEMOT-BRIDGE-MIB
	To monitor a single bridge using the IETF BRIDGE-MIB (RFC4188):	IETF kulanarak tek bir körüyü gözlemlemek için BRIDGE-MIB (RFC4188):
	<prompt>%</prompt> <userinput>snmpwalk -v 2c -c public bridge1.example.com mib-2.dot1dBridge</userinput> BRIDGE-MIB::dot1dBaseBridgeAddress.0 = STRING: 66:fb:9b:6e:5c:44 BRIDGE-MIB::dot1dBaseNumPorts.0 = INTEGER: 1 ports BRIDGE-MIB::dot1dStpTimeSinceTopologyChange.0 = Timeticks: (189959) 0:31:39.59 centi-seconds BRIDGE-MIB::dot1dStpTopChanges.0 = Counter32: 2 BRIDGE-MIB::dot1dStpDesignatedRoot.0 = Hex-STRING: 80 00 00 01 02 4B D4 50 ... BRIDGE-MIB::dot1dStpPortState.3 = INTEGER: forwarding(5) BRIDGE-MIB::dot1dStpPortEnable.3 = INTEGER: enabled(1) BRIDGE-MIB::dot1dStpPortPathCost.3 = INTEGER: 200000 BRIDGE-MIB::dot1dStpPortDesignatedRoot.3 = Hex-STRING: 80 00 00 01 02 4B D4 50 BRIDGE-MIB::dot1dStpPortDesignatedCost.3 = INTEGER: 0 BRIDGE-MIB::dot1dStpPortDesignatedBridge.3 = Hex-STRING: 80 00 00 01 02 4B D4 50 BRIDGE-MIB::dot1dStpPortDesignatedPort.3 = Hex-STRING: 03 80 BRIDGE-MIB::dot1dStpPortForwardTransitions.3 = Counter32: 1 RSTP-MIB::dot1dStpVersion.0 = INTEGER: rstp(2)	<prompt>%</prompt> <userinput>snmpwalk -v 2c -c public bridge1.example.com mib-2.dot1dBridge</userinput> BRIDGE-MIB::dot1dBaseBridgeAddress.0 = STRING: 66:fb:9b:6e:5c:44 BRIDGE-MIB::dot1dBaseNumPorts.0 = INTEGER: 1 ports BRIDGE-MIB::dot1dStpTimeSinceTopologyChange.0 = Timeticks: (189959) 0:31:39.59 centi-seconds BRIDGE-MIB::dot1dStpTopChanges.0 = Counter32: 2 BRIDGE-MIB::dot1dStpDesignatedRoot.0 = Hex-STRING: 80 00 00 01 02 4B D4 50 ... BRIDGE-MIB::dot1dStpPortState.3 = INTEGER: forwarding(5) BRIDGE-MIB::dot1dStpPortEnable.3 = INTEGER: enabled(1) BRIDGE-MIB::dot1dStpPortPathCost.3 = INTEGER: 200000 BRIDGE-MIB::dot1dStpPortDesignatedRoot.3 = Hex-STRING: 80 00 00 01 02 4B D4 50 BRIDGE-MIB::dot1dStpPortDesignatedCost.3 = INTEGER: 0 BRIDGE-MIB::dot1dStpPortDesignatedBridge.3 = Hex-STRING: 80 00 00 01 02 4B D4 50 BRIDGE-MIB::dot1dStpPortDesignatedPort.3 = Hex-STRING: 03 80 BRIDGE-MIB::dot1dStpPortForwardTransitions.3 = Counter32: 1 RSTP-MIB::dot1dStpVersion.0 = INTEGER: rstp(2)
	The <literal>dot1dStpTopChanges.0</literal> value is two, indicating that the <acronym>STP</acronym> bridge topology has changed twice. A topology change means that one or more links in the network have changed or failed and a new tree has been calculated. The <literal>dot1dStpTimeSinceTopologyChange.0</literal> value will show when this happened.	<literal> dot1dStpTopChanges.0 </literal> değeri ikidir, bu da <acronym> STP </acronym> köprü topolojisinin iki kez değiştiğini gösterir. Bir topoloji değişikliği, ağdaki bir veya daha fazla bağlantının değiştiği veya başarısız olduğu ve yeni bir ağacın hesaplandığı anlamına gelir. Bu olduğunda <literal> dot1dStpTimeSinceTopologyChange.0 </literal> değeri gösterilir.
	To monitor multiple bridge interfaces, the private BEGEMOT-BRIDGE-MIB can be used:	çoklu köprü arayüzlerini izlemek için özel BEGEMOT-BRIDGE-MIB kullanılabilir:
	<prompt>%</prompt> <userinput>snmpwalk -v 2c -c public bridge1.example.com</userinput> enterprises.fokus.begemot.begemotBridge BEGEMOT-BRIDGE-MIB::begemotBridgeBaseName."bridge0" = STRING: bridge0 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseName."bridge2" = STRING: bridge2 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseAddress."bridge0" = STRING: e:ce:3b:5a:9e:13 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseAddress."bridge2" = STRING: 12:5e:4d:74:d:fc BEGEMOT-BRIDGE-MIB::begemotBridgeBaseNumPorts."bridge0" = INTEGER: 1 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseNumPorts."bridge2" = INTEGER: 1 ... BEGEMOT-BRIDGE-MIB::begemotBridgeStpTimeSinceTopologyChange."bridge0" = Timeticks: (116927) 0:19:29.27 centi-seconds BEGEMOT-BRIDGE-MIB::begemotBridgeStpTimeSinceTopologyChange."bridge2" = Timeticks: (82773) 0:13:47.73 centi-seconds BEGEMOT-BRIDGE-MIB::begemotBridgeStpTopChanges."bridge0" = Counter32: 1 BEGEMOT-BRIDGE-MIB::begemotBridgeStpTopChanges."bridge2" = Counter32: 1 BEGEMOT-BRIDGE-MIB::begemotBridgeStpDesignatedRoot."bridge0" = Hex-STRING: 80 00 00 40 95 30 5E 31 BEGEMOT-BRIDGE-MIB::begemotBridgeStpDesignatedRoot."bridge2" = Hex-STRING: 80 00 00 50 8B B8 C6 A9	<prompt>%</prompt> <userinput>snmpwalk -v 2c -c public bridge1.example.com</userinput> enterprises.fokus.begemot.begemotBridge BEGEMOT-BRIDGE-MIB::begemotBridgeBaseName."bridge0" = STRING: bridge0 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseName."bridge2" = STRING: bridge2 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseAddress."bridge0" = STRING: e:ce:3b:5a:9e:13 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseAddress."bridge2" = STRING: 12:5e:4d:74:d:fc BEGEMOT-BRIDGE-MIB::begemotBridgeBaseNumPorts."bridge0" = INTEGER: 1 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseNumPorts."bridge2" = INTEGER: 1 ... BEGEMOT-BRIDGE-MIB::begemotBridgeStpTimeSinceTopologyChange."bridge0" = Timeticks: (116927) 0:19:29.27 centi-seconds BEGEMOT-BRIDGE-MIB::begemotBridgeStpTimeSinceTopologyChange."bridge2" = Timeticks: (82773) 0:13:47.73 centi-seconds BEGEMOT-BRIDGE-MIB::begemotBridgeStpTopChanges."bridge0" = Counter32: 1 BEGEMOT-BRIDGE-MIB::begemotBridgeStpTopChanges."bridge2" = Counter32: 1 BEGEMOT-BRIDGE-MIB::begemotBridgeStpDesignatedRoot."bridge0" = Hex-STRING: 80 00 00 40 95 30 5E 31 BEGEMOT-BRIDGE-MIB::begemotBridgeStpDesignatedRoot."bridge2" = Hex-STRING: 80 00 00 50 8B B8 C6 A9
	To change the bridge interface being monitored via the <literal>mib-2.dot1dBridge</literal> subtree:	<literal> mib-2.dot1dBridge </literal> alt ağacı üzerinden izlenen köprü arabirimini değiştirmek için:
	<prompt>%</prompt> <userinput>snmpset -v 2c -c private bridge1.example.com</userinput> BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2	<prompt>%</prompt> <userinput>snmpset -v 2c -c private bridge1.example.com</userinput> BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2
	Link Aggregation and Failover	Bağlantı Toplama ve Yük Devretme
	<primary>lagg</primary>	<primary>lagg</primary>
	<primary>failover</primary>	<primary>failover</primary>
	<primary><acronym>FEC</acronym></primary>	<primary><acronym>FEC</acronym></primary>
	<primary><acronym>LACP</acronym></primary>	<primary><acronym>LACP</acronym></primary>
	<primary>loadbalance</primary>	<primary>loadbalance</primary>
	<primary>roundrobin</primary>	<primary>roundrobin</primary>
	FreeBSD provides the <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry> interface which can be used to aggregate multiple network interfaces into one virtual interface in order to provide failover and link aggregation. Failover allows traffic to continue to flow as long as at least one aggregated network interface has an established link. Link aggregation works best on switches which support <acronym>LACP</acronym>, as this protocol distributes traffic bi-directionally while responding to the failure of individual links.	FreeBSD, yük devretme ve bağlantı birleştirme sağlamak için birden çok ağ arabirimini tek bir sanal arabirimde toplamak için kullanılabilen <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum> </citerefentry> arabirimini sağlar. Yük devretme, en az bir birleştirilmiş ağ arabirimi yerleşik bir bağlantıya sahip olduğu sürece trafiğin akmaya devam etmesini sağlar. Bağlantı toplama en iyi şekilde <acronym> LACP </acronym> 'i destekleyen anahtarlarda çalışır, çünkü bu protokol trafiği iki yönlü olarak dağıtırken, bireysel bağlantıların başarısızlığına yanıt verir.
	The aggregation protocols supported by the lagg interface determine which ports are used for outgoing traffic and whether or not a specific port accepts incoming traffic. The following protocols are supported by <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry>:	Gecikme arabirimi tarafından desteklenen toplama protokolleri, giden bağlantı noktaları için hangi bağlantı noktalarının kullanıldığını ve belirli bir bağlantı noktasının gelen trafiği kabul edip etmediğini belirler. Aşağıdaki protokoller <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum> </citerefentry> tarafından desteklenmektedir:
	failover	Yük devretme
	This mode sends and receives traffic only through the master port. If the master port becomes unavailable, the next active port is used. The first interface added to the virtual interface is the master port and all subsequently added interfaces are used as failover devices. If failover to a non-master port occurs, the original port becomes master once it becomes available again.	Bu mod yalnızca ana bağlantı noktası üzerinden trafik gönderir ve alır. Ana bağlantı noktası kullanılamaz duruma gelirse, bir sonraki etkin bağlantı noktası kullanılır. Sanal arabirime eklenen ilk arabirim ana bağlantı noktasıdır ve daha sonra eklenen tüm arabirimler yük devretme aygıtı olarak kullanılır. Ana olmayan bir bağlantı noktasına yük devretme oluşursa, orijinal bağlantı noktası yeniden kullanılabilir duruma geldiğinde ana hale gelir.
	fec / loadbalance	fec/ yük dengesi
	<trademark class="registered">Cisco</trademark> Fast <trademark class="registered">EtherChannel</trademark> (<acronym>FEC</acronym>) is found on older <trademark class="registered">Cisco</trademark> switches. It provides a static setup and does not negotiate aggregation with the peer or exchange frames to monitor the link. If the switch supports <acronym>LACP</acronym>, that should be used instead.	<trademark class= "registered"> Cisco </trademark> Hızlı <ticari marka sınıfı = "kayıtlı"> EtherChannel </trademark> (<acronym> FEC </acronym>) eski <trademark class = "registered"> Cisco'da bulundu </trademark> anahtarları. Statik bir kurulum sağlar ve bağlantıyı izlemek için eş veya takas çerçeveleriyle birleşme görüşmesi yapmaz. Anahtar <acronym> LACP </acronym> 'ı destekliyorsa, bunun yerine kullanılmalıdır.

Loading…

browndie

New translation

FreeBSD Doc (Archived) / books_handbook — Turkish (tr_TR)

English

Turkish (tr_TR)

7 months ago

Browse all component changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Turkish (tr_TR)
integer	tam sayı	FreeBSD Doc (Archived)
prompt	komut istemi	FreeBSD Doc (Archived)
string	karakter dizisi,karakter katarı,dizge	FreeBSD Doc (Archived)

Source information

Source string comment

(itstool) path: sect2/screen

Flags

no-wrap

Source string location

book.translate.xml:65535

String age

9 months ago

Source string age

a year ago

Translation file

books/tr_TR/handbook.po, string 11033