CADANT-TC
Cadant Inc.This MIB module contains the textual conventions that are shared among multiple ARRIS MIBs.
snmptranslate -m CADANT-TC -Tpsnmpwalk -v2c -c <community> -m CADANT-TC <host> 1.3.6.1.4.1.4998.0Imports
| CADANT-PRODUCTS-MIB | cadant |
|---|---|
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP |
| SNMPv2-SMI | Bits, Counter64, Integer32, IpAddress, MODULE-IDENTITY, MibIdentifier, OBJECT-IDENTITY, OBJECT-TYPE, TimeTicks, Unsigned32, iso |
| SNMPv2-TC | DisplayString, PhysAddress, TEXTUAL-CONVENTION |
OID tree
| Name | OID | Type | Access | Status |
|---|---|---|---|---|
| IcadTextualConventions | 1.3.6.1.4.1.4998.0 | |||
identity This MIB module contains the textual conventions that are shared among multiple ARRIS MIBs. | ||||
Textual conventions
AAAmethodINTEGERgroup(5)line(2)local(4)none(1)This TEXTUAL-CONVENTION describes the type of AAA methods available on the C4.
AccountingTypeINTEGERstart-stop(1)stop-only(2)This TEXTUAL-CONVENTION describes the different types of accounting services.
AdminStateINTEGERdown(2)up(1)The administrative or the desired states of the element and are set by the EMS.
CadAclStringOCTET STRING (SIZE (0..32))The name of the ACL this ACE is part of.
CadAclTypeINTEGERext-access-list(2)ipv6-access-list(5)none(0)rate-limit-access-list(3)remark(4)std-access-list(1)The type of ACL this ACE is part of.
CadBridgeGroupIdInteger32 (33..255)Uniquely identifies the bridge group.
CadBridgePortTypeINTEGERany(4)cm(1)cpeauth(2)cpeunauth(3)none(5)Type of traffic allowed on a bridge port. Ethernet ports allow any type of traffic. RF ports can be sub divided for CM traffic, authorized CPE traffic, and unauthorized CPE traffic.
CadCpeDeviceTypesBitscable-modem(0)cpe(1)dva(7)erouter(6)mta(3)ps(2)reserved10(10)reserved11(11)reserved12(12)reserved13(13)reserved14(14)reserved15(15)reserved16(16)reserved17(17)reserved18(18)reserved19(19)reserved20(20)reserved21(21)reserved22(22)reserved23(23)reserved24(24)reserved25(25)reserved26(26)reserved27(27)reserved28(28)reserved29(29)reserved30(30)reserved31(31)reserved9(9)sg(8)stb(4)tea(5)CPE Device types.
CadDoubleCounter64Display hint:
d-10This type is used to express and display 64-bit, double-precision floating-point values.
CadExtAclConditionINTEGEReq(1)ge(6)gt(5)le(4)lt(3)na(0)ne(2)range(7)This TEXTUAL-CONVENTION describes the condition of Extended ACLs.
CadIfDirectionINTEGERin(1)out(2)A direction of flow on an interface.
CadIpPortINTEGER (0..65535 | -1)The port of an IP packet. The value -1 indicates that this field is not used.
CadIpTosINTEGER (0..254)The type-of-service of an IP packet. The value 0 indicates that this field is not used.
CadIpTosMaskINTEGER (0 | 30 | 224 | 254)The allowed type-of-service mask of an IP packet. 30 is used when the 4 bit TOS is specified. 224 is used when the 3 bit precedence is specified, and 254 is used when the entire 7 bit TOS is specified. A value of 0 indicates that the TOS field is not used.
CadProtocolTypeINTEGER (0..255 | -1)The protocol type an IP packet (8 bits). 0 is IP, 1 is ICMP, 2 is IGMP, 6 is TCP 17 is UDP. See RFC-1700 for complete list. The value -1 indicates an invalid/unused protocol type.
CadTcpFlagsBitsack(1)fin(5)push(2)rst(3)syn(4)urg(0)The values available in the flags portion of the TCP header.
CardIdInteger32 (1..99)Uniquely identifies the individual Circuit Pack. Number of 99 indicates an invalid CardId.
CardSubIdInteger32 (0..1)Uniquely identifies an entity on the circuit pack.
CardSubTypeINTEGERdcard0d12u(35)dcard1d8u(20)dcard2d8u(21)dcardiu1d8u(1)dcardiu2d12u(23)dcardiu2d8u(22)discdriveA(13)discdriveB(14)dmm16m(37)dmm16m16p4iu(36)ecard1gig(34)ecard1oc12(33)ecard4e(2)ecard4oc3(31)ecard7oc3(32)ecard8e(30)fanA(7)fanB(8)fanC(9)fanD(10)fcard(3)invalid(99)mcard(4)powerA(11)powerB(12)rcard(6)rcardhcp(40)unknown(98)Enumeration of more specific current Card Type. For cards with only one subtype, the type and subtype should be identical.
CardTypeINTEGERdcard(1)discdriveA(13)discdriveB(14)dmm(15)ecard(2)fanA(7)fanB(8)fanC(9)fanD(10)fcard(3)invalid(99)mcard(4)powerA(11)powerB(12)rcard(6)unknown(98)Enumeration of generic Card Type.
DiskVolumeUsageLevelINTEGERcritical(4)major(3)minor(2)normal(1)Describe the disk volume usage level
DuplexStatusINTEGERactive(1)notapplicable(0)protected(4)simplex(3)standby(2)not applicable to all components
EqActionTypeINTEGERcardreset(7)initialize(1)notapplicable(0)remove(3)restorecond(4)restoreuncd(5)switch(2)systemreset(6)not applicable to all components
FirmwareSourceINTEGERboot1(3)boot2(4)committed(1)transient(2)unknown(5)This type describes the initial source of the firmware running on a card. Committed and transient indicate the card flash device and the downloaded image, respectively. Boot1 and Boot2 indicate which of the resident boot images was used to boot the card.
FlowActivityStateINTEGERgreedy(3)needy(1)normal(2)Flow Activity State describes the recent bandwidth utilization history of a service flow relative to its Service Level Agreement. A flow that is operating below its Tmin is said to be 'needy'. A flow that is operating above Tmin but below Tmid is said to be 'normal'. A flow that is operating above Tmid but below Tmax is said to be 'greedy'.
FlowControlModeINTEGERdesired(3)invalid(99)off(2)on(1)unknown(98)flow control settings for a network port.
InetAddressIPv4or6OCTET STRING (SIZE (0 | 4 | 8 | 16 | 20))This TEXTUAL-CONVENTION is similar to InetAddress as defined in the INET-ADDRESS-MIB. However, InetAddressIPv4or6 does not allow DNS addresses and its address type, either IPv4 or IPv6, can be readily determined from its length alone. If the address is an IPv4 address, then the length will be exactly 4 bytes. If the address is an IPv6 address, then the length will be either 16 or 20 bytes. If the length if 0, then the address is empty or null. If the length is 4: octets contents encoding 1-4 IP address network-byte order If the length is 8: octets contents encoding 1-8 EUI IPv6 address network-byte order If the length is 16: octets contents encoding 1-16 IPv6 address network-byte order If the length is 20: octets contents encoding 1-16 IPv6 address network-byte order 17-20 scope identifier network-byte order The scope identifier (bytes 17-20) MUST NOT be present for global IPv6 addresses. For non-global IPv6 addresses (e.g. link-local or site-local addresses), the scope identifier MUST always be present. It contains a link identifier for link-local and a site identifier for site-local IPv6 addresses. The scope identifier MUST disambiguate identical address values. For link-local addresses, the scope identifier will typically be the interface index (ifIndex as defined in the IF-MIB, RFC 2233) of the interface on which the address is configured. The scope identifier may contain the special value 0 which refers to the default scope. The default scope may be used in cases where the valid scope identifier is not known (e.g., a management application needs to write a site-local InetAddressIPv6 address without knowing the site identifier value). The default scope SHOULD NOT be used as an easy way out in cases where the scope identifier for a non-global IPv6 is known.
LineTypeINTEGERconsole(1)vty(2)This TEXTUAL-CONVENTION describes the type line connections available on the C4.
MacChlPortTypeINTEGERdport(1)invalid(99)uchannel(8)Enumeration of current Port Type.
MacPortIdInteger32 (1..448)A valid unique identifier for a MAC port in a C4 CMTS system.
MacPortIdWithInvalidInteger32 (1..449)Identifier for a MAC port in a C4 CMTS system.
OUIAddressOCTET STRING (SIZE (3))Display hint:
1x:Represents the first three(3), most significant bytes of an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first.
OverloadStatusINTEGERnormal(1)red(3)yellow(2)Three levels indicating how much work the card is doing.
PicTypeINTEGERcam16d(14)cam16dspare(15)cameven(1)camevensp1to1(2)camevensp2to1(3)camevensp4to1(4)camevensp8to1(5)camodd(6)camoddsp1to1(7)camoddsp2to1(8)camoddsp4to1(9)camoddsp8to1(10)camspare(11)invalid(99)nam(12)scm(13)unknown(98)This type describes the PIC attached to the backplane behind a a card.
PortDetectedModeINTEGERfullDuplex100Mpbs(2)fullDuplex10Mpbs(4)halfDuplex100Mpbs(3)halfDuplex10Mpbs(5)invalid(99)sfpFullDuplex1000BaseCWDM(20)sfpFullDuplex1000BaseDWDM(21)sfpFullDuplex1000BaseLH(17)sfpFullDuplex1000BaseLX(16)sfpFullDuplex1000BaseLXLH(18)sfpFullDuplex1000BaseSX(15)sfpFullDuplex1000BaseT(9)sfpFullDuplex1000BaseZX(19)sfpFullDuplex100BaseT(11)sfpFullDuplex10BaseT(13)sfpHalfDuplex1000BaseT(10)sfpHalfDuplex100BaseT(12)sfpHalfDuplex10BaseT(14)unknown(98)xfpFullDuplex10GBaseER(25)xfpFullDuplex10GBaseLR(24)xfpFullDuplex10GBaseLRM(23)xfpFullDuplex10GBaseLX4(27)xfpFullDuplex10GBaseSR(22)xfpFullDuplex10GBaseZR(26)detected mode settings for a network port.
PortIdInteger32 (1..99)Uniquely identifies the port. Number of 99 indicates an invalid PortId.
PortModeINTEGERautoNegotiate(1)fullDuplex10000Mpbs(8)fullDuplex1000Mpbs(6)fullDuplex100Mpbs(2)fullDuplex10Mpbs(4)halfDuplex1000Mpbs(7)halfDuplex100Mpbs(3)halfDuplex10Mpbs(5)invalid(99)mode settings for a network port.
PortTypeINTEGERdport(1)dportMac(10)eport10000BaseT(9)eport1000BaseT(7)eport100BaseT(4)eport10BaseT(3)invalid(99)macport(5)mport(6)uchannel(8)uport(2)Enumeration of current Port Type.
PrimaryStateINTEGERis(1)oos(2)The operational state IS(1): The element is operable and available for use OOS(2): The element/resource is inoperable and unable to provide service UNEQ(3): The element/resource is unequiped.
SchedDayBitsd1(0)d10(9)d11(10)d12(11)d13(12)d14(13)d15(14)d16(15)d17(16)d18(17)d19(18)d2(1)d20(19)d21(20)d22(21)d23(22)d24(23)d25(24)d26(25)d27(26)d28(27)d29(28)d3(2)d30(29)d31(30)d4(3)d5(4)d6(5)d7(6)d8(7)d9(8)r1(31)r10(40)r11(41)r12(42)r13(43)r14(44)r15(45)r16(46)r17(47)r18(48)r19(49)r2(32)r20(50)r21(51)r22(52)r23(53)r24(54)r25(55)r26(56)r27(57)r28(58)r29(59)r3(33)r30(60)r31(61)r4(34)r5(35)r6(36)r7(37)r8(38)r9(39)The set of days in a month on which a scheduled action should take place. There are two sets of bits one can use to define the day within a month: Enumerations starting with the letter 'd' indicate a day in a month relative to the first day of a month. The first day of the month can therefore be specified by setting the bit d1(0) and d31(30) means the last day of a month with 31 days. Enumerations starting with the letter 'r' indicate a day in a month in reverse order, relative to the last day of a month. The last day in the month can therefore be specified by setting the bit r1(31) and r31(61) means the first day of a month with 31 days. Setting multiple bits will include several days in the set of possible days for this schedule. Setting all bits will cause the scheduler to ignore the day within a month. Setting all bits starting with the letter 'd' or the letter 'r' will also cause the scheduler to ignore the day within a month.
SchedHourBitsh0(0)h1(1)h10(10)h11(11)h12(12)h13(13)h14(14)h15(15)h16(16)h17(17)h18(18)h19(19)h2(2)h20(20)h21(21)h22(22)h23(23)h3(3)h4(4)h5(5)h6(6)h7(7)h8(8)h9(9)The set of hours within a day during which the scheduled action should take place.
SchedMinuteBitsm0(0)m1(1)m10(10)m11(11)m12(12)m13(13)m14(14)m15(15)m16(16)m17(17)m18(18)m19(19)m2(2)m20(20)m21(21)m22(22)m23(23)m24(24)m25(25)m26(26)m27(27)m28(28)m29(29)m3(3)m30(30)m31(31)m32(32)m33(33)m34(34)m35(35)m36(36)m37(37)m38(38)m39(39)m4(4)m40(40)m41(41)m42(42)m43(43)m44(44)m45(45)m46(46)m47(47)m48(48)m49(49)m5(5)m50(50)m51(51)m52(52)m53(53)m54(54)m55(55)m56(56)m57(57)m58(58)m59(59)m6(6)m7(7)m8(8)m9(9)The set of minutes within an hour when the scheduled action should take place.
SchedMonthBitsapril(3)august(7)december(11)february(1)january(0)july(6)june(5)march(2)may(4)november(10)october(9)september(8)The set of months during which the scheduled action should take place. Setting multiple bits will include several months in the set of possible months for this schedule. Setting all bits will cause the scheduler to ignore the month.
SchedWeekDayBitsfriday(5)monday(1)saturday(6)sunday(0)thursday(4)tuesday(2)wednesday(3)The set of weekdays on which the scheduled action should take place. Setting multiple bits will include several weekdays in the set of possible weekdays for this schedule. Setting all bits will cause the scheduler to ignore the weekday.
SecondaryStateINTEGERdegrade(6)diagnostic(3)fault(2)firmwarepump(9)initializing(7)manual(1)normal(5)notapplicable(0)overload(4)swdownload(8)For each PrimaryState, there might be an associated secondary state
ServerTypeINTEGERftp(2)other(7)radius(5)snmp(3)syslog(4)tacacs(6)telnet(1)This TEXTUAL-CONVENTION describes the INET services available on the SCM.
ShelfIdInteger32 (1..99)Uniquely identifies the shelf. Number of 99 indicate an invalid ShelfId.
SshAuthMethodINTEGERpassword(1)public-key(2)This TEXTUAL-CONVENTION describes the authentication method available in SSH on the C4.
SshCipherBitsaes(5)arcfour(2)blowfish(3)cast(4)other(0)threedes(1)This TEXTUAL-CONVENTION describes the ciphers available in SSH on the C4.
SshCipherTypeINTEGERaes128(6)aes192(7)aes256(8)arcfour(3)blowfish(4)cast128(5)des(9)other(1)rc4(10)threedes(2)This TEXTUAL-CONVENTION describes the specific cipher type on the C4.
SshMacAlgINTEGERhmac-sha1(2)none(1)This TEXTUAL-CONVENTION describes the MAC algorithm available in SSH on the C4.
SshProtocolINTEGERssh1(1)ssh1ssh2(3)ssh2(2)This TEXTUAL-CONVENTION describes the SSH protocol versions available in SSH on the C4.
SshServiceINTEGERsftp(2)terminal(1)This TEXTUAL-CONVENTION describes the SSH service types available in SSH on the C4.
UnknownStateINTEGERknown(0)unknown(1)Similar to TMN representation of the Unknown Status.
VlanIdInteger32 (1..1000000)The unique identifier for a Virtual LAN. A value of 1000000 indicates unknown VLAN.